Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
F2

Staff Software Engineer (US)

F2 • Financial District, San Francisco, CA

Company

F2

Annual salary

$290k – $340k/yr

Location

Financial District, San Francisco, CA

Listed

23d ago

Experience:
8+ years
Workplace:
3 days in-office (usually Mon, Wed) in the Financial District, San Francisco (601 California St, near Montgomery BART)
Equity:
Competitive equity

Hybrid in Financial District, 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.

About this role

We are looking for a Staff Software Engineer with 8+ years of experience to own large parts of F2's AI platform for private markets investors, end to end. We want an AI-native, full-stack generalist who makes every engineer around them better. F2's revenue is growing faster than its 5-person engineering team, and our customers include Jefferies and Golub Capital, so this is the company's top hiring priority.

What you need

  • 8+ years of software engineering experience (7 is the absolute minimum), with clear promotions and career progression
  • A degree in CS or a related engineering field (computer, electrical or mechanical). No bootcamp-only or unrelated backgrounds
  • AI-native: you already build with coding agents day to day, not by hand
  • A proven record as a force multiplier: you led a product pillar or a large infrastructure project end to end and can show its impact, including how you made other senior and staff engineers better
  • Strong engineering pedigree, ideally both big tech and startup experience, and a clear, specific reason for wanting to join an early-stage startup

What will you be doing?

  • Building hands-on across the full stack (frontend, backend, database migrations), using AI agents to write and review 100% of the code

  • Owning large product areas end to end, such as the agent that builds investment-grade presentations and memos for finance teams

  • Writing technical design docs by hand and spending 10, 20% of your time reviewing other engineers' designs and code

  • Acting as a force multiplier: raising the bar on architecture, code quality and engineering practice across the team

  • Working directly with customers, sales, customer success and product to turn the needs of finance professionals into shipped features

Common questions

How do I apply for the Staff Software Engineer (US) role at F2? +

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 F2 role pay? +

The listing gives $290k – $340k/yr.

Is this role remote? +

The listing gives the location as Financial District, San Francisco, CA. 3 days in-office (usually Mon, Wed) in the Financial District, San Francisco (601 California St, near Montgomery BART).

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.

See all 10 Software Engineer interview questions →

Related roles

F2

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 →