Email us your resume, and the work behind it.
We are a small team in Bengaluru building the security layer for AI-native software. Right now, every open role is an internship. If you like breaking things and shipping the fix, and want to learn fast doing it, we would like to hear from you.
Internships only, for the vision.
We are a small, early team, so the only roles open right now are internships, and most of them are unpaid.
Choose us if you want to work on what we are building and grow fast in AI security, learning from real problems, real users and the founders directly. If pay is what you are looking for most right now, we are not the right fit yet, and that is completely fair.
What to write
Start with a few lines on who you are, why you want to work on AI security with us, and what you would like to own. Attach your resume as a PDF, and link the work you are most proud of: code, write-ups, CTF results, a bug you found, or something you shipped that people use. Finish with where you are based, when you could start, how many hours a week you can give and for how long, and where we can find you online.
Six things we look for in your email.
Your resume
One page is plenty, as a PDF. What you built and what changed because of it matters more than titles.
Work you are proud of
GitHub, a portfolio, write-ups, CTF results, a vulnerability you found, or a product people use. Links beat descriptions.
Why Aevrin
A few honest lines on why AI security, and what you want to learn here. No cover-letter template needed.
What you want to own
Engineering, security research, design or growth, or something we have not thought of yet. Tell us where you would start.
Where and when
Where you are based, when you could start, and how many hours a week you can give, for how long.
Where to find you
LinkedIn, GitHub, X or your own site, so we can see more of how you think and what you ship.
Four things the people we work best with share.
You ship, then make it better
Version one goes out. The next ten are what make it great.
You like finding out how things break
Curiosity about failure is where security work starts.
You own a problem from start to finish
From the first question to the fix running in production.
You explain hard things in plain words
To customers, to users, and to each other.
The founders read every application. If there is a fit, we will reply to set up a conversation about the work, and about you.