Company
Hercules
Annual salary
$200k – $300k/yr
Location
San Francisco, CA
Listed
26d ago
- Experience:
- 2 to 10 years
- Workplace:
- Hercules is based in San Francisco (Kearny & Bush), and the founding team works in-office. A remote arrangement could be arranged for an exceptional candidate, but it should not be the default.
- Equity:
- 0.01% - 0.25%
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
- Build and own user-facing products across the Hercules platform end to end, including the AI Agent, App Builder, Mobile (PWA) experience, and headless SaaS SDK products like Hercules Auth (Users & Access), CMS, Files & Media (CDN), Email, and Commerce
- Take ownership of entire product areas from a clear goal with an open-ended solution, and drive them to finished, working products shaped by user feedback
- Work closely with the founders on high-level product requirements and iterate quickly with feedback from Hercules' hundreds of thousands of users, many of them non-technical business owners
- Design and build minimal, very simple UX/UI that lets non-technical users run critical business systems like CRMs, ERPs, warehouse management, and HR platforms
- Lead features from design through architecture, data modeling, and API design to production launch, then iterate after launch
- Build and improve core SaaS capabilities like billing and entitlements, product analytics, A/B testing and feature flags, i18n, and notifications to improve adoption, retention, and revenue
- Use frontier AI coding tools to 10x your own output and move with urgency as one of only about 7 people What we look for (operating principles): We ship, we strive for excellence, we move with urgency, we are hungry, and we communicate clearly. Candidates should show a fast upward career path (high slope).
What you need
- We need a senior or staff-level product engineer, usually with 4, 10 years of professional experience, who is strong across the full stack, strongest on the frontend, and has fully owned large, core product modules from start to finish. You should be comfortable taking an unclear goal like "go solve identity and access management" or "go solve CMS" and shipping a simple product that real users can serve themselves. You should have a track record of shipping many major features or whole modules to end users, not just bug fixes. Bonus points for pre-Series C startup experience, founder or YC experience, lots of GitHub or open-source contributions, a public record of launches, or long-form technical writing.
Common questions
How do I apply for the Staff Software Engineer, Infrastructure (US) role at Hercules? +
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 Hercules role pay? +
The listing gives $200k – $300k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. Hercules is based in San Francisco (Kearny & Bush), and the founding team works in-office. A remote arrangement could be arranged for an exceptional candidate, but it should not be the default.
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 →