Build the proof before the deploy.
Two founding roles, one on the product and one on how developers find it. The compensation is on this page rather than behind a conversation, because it decides this for most people and they should not have to ask.
There is no salary for either role currently. Both equity ranges are written down here.
These are the ranges, not a finalized offer, and the specific number inside a range would be agreed with you. What is fixed is the part above: no salary is paid for either role today.
Nothing on this page says when that changes, because nothing has decided it. There is no vesting schedule here, no funding announcement, no location requirement and no benefits list, and their absence is the honest state rather than an omission. If you need any of those to be true, this is the wrong time to join and it costs you nothing to have read one screen.
One builds the product, one builds how developers reach it. Both are early enough to own an area outright.
Founding engineer
0.5% to 2% equityNo salary currently
Build the path from a developer's repository to a working production rehearsal. Own the engine, the control plane, or the developer experience, and follow your own work all the way to a result somebody can inspect.
Show us something you built, a hard failure you diagnosed, or a system you made dependable. A public repository is welcome and not required.
Apply for this roleFounding growth
0.25% to 2% equityNo salary currently
Help developers find Antifailure, understand what it does, and reach their first useful result. Own the experiments in positioning, distribution and activation, with real conversations behind the numbers.
Show us something you helped people discover or adopt. Say what you tried, what changed, and what you learned when it did not work.
Apply for this role
Show us your work. A short introduction is enough.
No account and no resume upload. Please leave out confidential work, credentials, and anything sensitive about you that this does not ask for.
What you send goes to a private review queue that an authorized operator reads. It is not a public issue, a mailing list, or an analytics event. Applications are removed after 180 days by scheduled maintenance, and you can ask for yours to be removed sooner.
- About the projectWhat Antifailure is, the category it claims, and the limits it states rather than footnotes.Read
- How it is builtThe control plane, the engine, and where the boundary between them falls.Read
- What we hold about youIncluding the application itself: what is stored, who reads it, and when it expires.Read
Know what happens before you deploy.
Create a disposable production twin for every risky change. Catch migration failures before they reach customers.