Company
Unit
Annual salary
$225k – $275k/yr
Location
San Francisco, CA
Listed
44d ago
- Experience:
- 5 to 10 years
- Workplace:
- On-site 5 days/week at Unit's San Francisco office. No relocation support, candidates must already be based in the SF Bay Area and able to start immediately. No remote or hybrid flexibility.
- Equity:
- <p><strong>Competitive equity grant.</strong> The hiring manager emphasized that senior hires would be positioned for leadership and encouraged to lean into equity as part of their total compensation. As an early-stage startup backed by <strong>Khosla Ventures</strong> and <strong>Air Street Capital</strong>, equity carries significant upside potential.</p>
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, CA.
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.
What you'll do
- Design and develop scalable backend systems that power the creative engine behind GTV, Unit's AI video platform
- Build core infrastructure for agentic workflows, video generation pipelines, reinforcement learning loops, and real-time data processing
- Take ownership of distributed systems architecture and drive reliability through automated testing, performance benchmarking, and end-to-end observability
- Partner closely with researchers, engineers, and designers to develop new product features and APIs
- Lead by example as a senior technical voice on the team, writing excellent code, setting engineering guidelines, and raising the bar for the entire org
- Write clear documentation, define agent skills, and communicate technical decisions effectively in a fast-moving, in-person startup environment
What you need
- We need a senior backend engineer with 5-10 years of experience who has hands-on industry experience building agentic systems and working with LLMs. You should be deeply technical, able to understand algorithms, data structures, and system design at a fundamental level, and have a proven track record at early-stage or high-growth startups. You'll serve as a technical lead and set the standard for engineering excellence on a small, high-caliber team.
Common questions
How do I apply for the Founding Software Engineer, Backend (US) role at Unit? +
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 Unit role pay? +
The listing gives $225k – $275k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. On-site 5 days/week at Unit's San Francisco office. No relocation support, candidates must already be based in the SF Bay Area and able to start immediately. No remote or hybrid flexibility.
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 →