Jobs
One system. Four roles.
Platform Engineer
The metaphysician of the organisation. Own the underlying structure of SDLC.works. Turn rough requirements into systems that provide the required behavior with minimal conceptual and implementation complexity.
Requirements
- Reasons from first principles with epistemic humility.
- Defends decisions with reason and evidence, regardless of convention or authority.
Experience Engineer
Own every surface a human touches — dashboard, CLI, onboarding, docs, error messages. Two ideas govern the work: people don't behave rationally, so the interface must guide and forgive them; and attention is scarce, so every click, concept and second between intent and outcome must earn its place.
Requirements
- Strong frontend engineering with genuine product-design sensibility — ships polished UI, not mockups.
- Works from evidence: user observation and funnel data, not taste alone.
- Writes clearly — microcopy and error text are part of the interface.
Product Engineer
Combine platform capability and experience into product. The Platform Engineer asks "does the system work?"; the Experience Engineer asks "can a human use it?"; the Product Engineer asks "will someone pay for this, and is it actually finished?"
Requirements
- Full-stack engineer who owns a feature's business outcome, not only its code — and is allergic to 80%-done.
- Uses AI-assisted development to ship production-grade work in days, not quarters.
Forward-Deployed Engineer
Embed inside customer companies and move their entire development process onto the platform — the field arm of the enterprise transformation offering.
Requirements
- Strong generalist engineer who can read unfamiliar infrastructure quickly and work credibly with CXOs and their teams.
- Treats dysfunction as a systems problem: transforms the system, never lectures the developers.
How applying works
Three rounds
-
Tell us about yourself.
Download the Markdown questionnaire, answer the questions, and email it with your resume and anything else you'd like us to know.
-
Show us how you think.
If your self-description fits a role, we'll send you a couple of problems we're facing right now. Solve them and explain your reasoning to move to the next round.
-
Meet the team and get hired (hopefully).
If you pass the written round, join the team for a live, in-depth back-and-forth about the problem you've chosen and your preliminary solution.
How we work
Founder’s Remarks
With this hiring drive, our focus is not to build a billion-dollar product. It is to build an organisation of people who can build billion-dollar products.
We disregard norms not because they are wrong (even if they turn out to be), but because we refuse to follow them without explanations.
Thinking from first principles is not just a “skill to have”; it is a virtue for us. We follow Popperian philosophy. We make guesses, offer explanations for them, and subject both to rigorous criticism through empirical evidence and reason. That is how we attain knowledge. We therefore reject an authoritative organisational structure: you can critique anyone’s ideas here.