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

Senior Software Engineer (US)

F2 • Financial District, San Francisco, CA

Company

F2

Annual salary

$220k – $270k/yr

Location

Financial District, San Francisco, CA

Listed

23d ago

Experience:
4 to 6 years
Workplace:
3 days in-office (usually Mon, Wed) at 601 California St, Financial District, San Francisco, near Montgomery BART station
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 Senior Software Engineer with 4+ years of experience (4, 6 is the sweet spot) to take full-stack ownership of major product areas at F2, the AI platform for private markets investors. Revenue is growing faster than the 5-person engineering team, so we need AI-native generalists who want real ownership and accountability while building the tool finance professionals rely on.

What you need

  • 4+ years building production software as a true full-stack engineer (some flexibility for exceptional pedigree, e.g. a top PhD)
  • AI-native: you use agents to write and review all of your code, and you have hands-on experience building with AI (agents, harnesses), even in personal projects
  • A degree in CS or an engineering field such as computer, electrical, or mechanical engineering (no bootcamp-only backgrounds)
  • A standout "spike" in your background (a top startup, a strong engineering-culture company, or a top school), steady career progression, and a clear reason for wanting a startup
  • Able to work hybrid at least 3 days a week in our San Francisco office

What will you be doing?

  • Own a product area end to end, for example F2's AI agent that builds presentations for finance users, and drive its roadmap with customers and the PM

  • Ship across the full stack (frontend, backend, database migrations), with AI agents writing 100% of your code

  • Write and review technical design docs, and use AI agents to review code (about 10, 20% of your time)

  • Work directly with customers, sales, and customer success to turn finance users' needs into product

  • Work with staff engineers to improve your area, then take on more of the codebase over time

Common questions

How do I apply for the Senior 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 $220k – $270k/yr.

Is this role remote? +

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

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 →