# John Doe — Working Context

Fictional example profile. Replace with your own content when setting up a new profile.

## What I'm looking for

Senior backend or platform engineering roles at mid-to-late stage startups. Strong preference for teams building developer tooling, internal platforms, or data infrastructure. Remote or hybrid in Austin, TX.

## Target titles

- Senior Backend Engineer
- Senior Platform Engineer
- Senior Infrastructure Engineer
- Senior SRE

Would also consider Staff-level roles where the scope is clearly IC rather than managerial.

## Stack I'm most productive in

- Go and Python for services
- Kubernetes, Terraform, AWS
- Postgres and Redis for storage
- GitHub Actions and ArgoCD for CI/CD

Comfortable reading and modifying TypeScript/Node codebases but wouldn't lead a frontend-heavy role.

## Compensation

- Base floor: $180,000
- Total comp target: $220,000 to $260,000 cash + equity
- Will trade some base for meaningful early-stage equity, not public-company RSU grants.

## Deal breakers

- 5-days-a-week RTO outside Austin
- Sole infrastructure owner at a Series A, without a clear hiring plan
- Rotations through a 24/7 primary on-call without compensation or time off

## What I bring

- 6 years hands-on experience scaling backend systems and developer platforms
- Cost-reduction track record: cut AWS bill 40% at Acme without SLA regression
- Built and operated a multi-region Postgres setup handling 15K TPS peak
- Genuinely comfortable in ambiguous early-stage scope, also comfortable in scaled-up teams

## Open questions I ask interviewers

- What does the team own end-to-end, and who owns the pieces adjacent to it?
- How much of the work is net-new vs maintenance, and how does that split change over a year?
- What does a week on call actually look like?
