← All roles
Engineering

Member of Technical Staff (Developer Relations)

San Francisco Bay AreaOn-siteFull-timeFounding team
About ArettaOur mission is to make AI provably trustworthy, starting with the world’s software.

AI is about to write the world’s software. All of it, from the critical infrastructure everything depends on to the apps people use every day. We want a future where people decide what software should do and machines prove that it does. We’re starting with the tools engineers need to ship AI-written code knowing it’s correct.

Within six months of starting, we're deployed with paying design partners in databases and data infrastructure, where we've found 60+ critical bugs, including data-loss bugs that survived their testing and simulation stacks. We're backed by visionaries like Ion Stoica, Kurt Keutzer, Sanjit Seshia, Ram Shriram and Sriram Rajamani. The founders, Sushant and Adwait, were previously PhD and postdoc at UC Berkeley.

The role

Most engineers have never used formal verification, and many who have found it slow and hard to use. You’ll change how people see it. You’ll tell Aretta’s story, from how we prove code correct to what that means for the future of software engineering, and your voice will turn our technology into that vision. Day to day, that means engaging blog posts, case studies built on real customer results, and docs people enjoy reading, written closely with our engineers and researchers so the deep technical details are right.

Problems you’d own

  • Make deep tech accessible. Write about how Aretta proves code correct so a working engineer understands it in one read, without dumbing it down.

  • Turn results into stories. We’ve found 60+ critical bugs with our design partners, including data-loss bugs their testing missed. Turn findings like these into case studies engineers share.

  • Make the docs the best part of the product. Write and maintain developer documentation, quickstarts and examples that get someone to their first verified result fast.

  • Build the community. Grow our presence where engineers and researchers talk: X, GitHub, Hacker News, conferences and meetups. Be a real participant, not a broadcaster.

  • Make launches land. Write the launch post, the thread and the demo script, and help make the video that makes people get it.

  • Bring the outside in. Tell the team what developers are confused by, excited about and asking for.

You don’t need to have done all of this. We care about how you’d approach it.

You might be a fit if

You’re an engineer who loves explaining things. You’ve written technical posts people bookmarked, given talks people remembered, or written docs people thanked you for. You can read code, and you’ll learn to read a proof, well enough to know when an explanation is wrong. You have a voice of your own, and you’d rather be precise than hype anything.

You don’t need

  • A background in formal methods. You’ll learn it from the people building it.

Bonus points

  • An audience: engineers or researchers already follow your work and trust what you write.

  • Video: you make polished videos or animations.

  • Talks: you’ve spoken at conferences or meetups.

  • Open source: you’ve maintained an open-source project or run a community.

Who we hire

We hire at every level, and we mean it. If you’re senior, you’ll come in as a hands-on engineer and grow into leading and building a team. If you’re early in your career, fresh out of school or a few years in, you’ll get real ownership fast and as much scope as you can take on. What matters is the same bar for everyone: mastery, the drive to grow, and the instinct to help others grow too.

Compensation and logistics

  • Type: full-time, part-time or contract.

  • Benefits (full-time only): unlimited PTO, health, dental and vision insurance, and a 401(k).

How we work

We work in roughly six-week cycles: five intense weeks, then a week for reflection, polish, feedback and mentorship. We bring opinionated ideas backed by evidence, bias for action, fix the class of problem rather than the instance, and close the loop with the people we serve. Read more in Our Culture.

Aretta comes from aretē, the Greek word for excellence and virtue: becoming the best version of yourself in everything you do. We value excellence for its own sake, and we believe it’s built across a whole life, not just the hours at a desk.

Where we work

We work in person in the San Francisco Bay Area. For the right person we’ll consider remote, so don’t let location stop you from applying.

How we hire

Our hiring process is probably unlike any you've been through, so please read about it before you apply. Everyone joins Aretta the same way: No puzzles, no whiteboards, and the process typically takes about a week end to end (subject to scheduling availability). You share real work you've done, then we spend a few hours on a real problem together to get a mutual feel for working side by side. Learn more here: How We Hire.