Company
Reform
Annual salary
$150k – $200k/yr
Location
San Francisco
Listed
30d ago
- Experience:
- 0 to 4 years
- Workplace:
- 5 days in-office in San Francisco
- Equity:
- 0.3-0.7%
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in San Francisco.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Software Engineer to join our team. We are looking for someone who thrives on ownership, loves building robust, high-performance systems, and can help us scale our engineering efforts. This hire is crucial for adding more bandwidth to the engineering team.
What will you be doing?
Own the complete lifecycle of high-stakes projects - from initial architecture and design to deployment and continuous optimization.
Design, build, and deploy end-to-end features across our stack (Python, Next.js, Node).
Contribute to architectural decisions and the long-term technical direction of the product.
Rebuild core features using the latest technology to improve upon existing solutions.
Uphold engineering excellence through thoughtful code review and testing, shipping to production daily.
Common questions
How do I apply for the Software Engineer (US) role at Reform? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Reform role pay? +
The listing gives $150k – $200k/yr.
Is this role remote? +
The listing gives the location as San Francisco. 5 days in-office in San Francisco.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →