Every week I read CVs that say "Senior Software Engineer, 8 years" from people who then fail the part of the interview that decides seniority. They can code. The code is fine. What's missing is everything around the code.
US startups use "senior" to mean something specific: you take a vague problem, turn it into a plan, ship it, and own what happens after. Years are a weak proxy for that. I've met four-year engineers who are clearly senior and twelve-year engineers who still wait to be told what to build.
Key Takeaways
- Senior at a US startup means ownership of outcomes. Tenure is a weak proxy.
- Interviewers test it through ambiguity. They leave requirements vague on purpose.
- Written design is the most underrated senior signal for remote engineers.
- You can show seniority on a CV by describing decisions and results instead of tasks.
The gap, side by side
| Situation | Mid-level response | Senior response |
|---|---|---|
| Vague ticket: "Add export to the reports page" | Asks for a spec, or builds a CSV button and waits | Asks who needs it, learns finance wants a monthly file, proposes a scheduled export and skips the button |
| Choosing a database | Picks the one they know | Lists two options, the tradeoff, and what would make them switch later |
| Production incident | Fixes the bug | Fixes it, writes the postmortem, adds the alert that would have caught it |
| Disagrees with the tech lead | Complies silently, or argues in the meeting | Writes a short doc with the alternative, then commits to whatever gets decided |
| A task is going to slip | Says so at the deadline | Says so the day they know, with a new date and what they'd cut |
How interviews test for it
System design. The interviewer leaves the problem open on purpose. "Design a notification service" has no right answer. They watch whether you ask about scale, delivery guarantees and who the users are before drawing boxes. Mid-level candidates start drawing in the first minute.
Behavioral. "Tell me about a time you disagreed with a technical decision" is a seniority question wearing a soft costume. Good answers name a specific decision, the reasoning on both sides, what you did, and how it turned out. Including the times you were wrong.
The coding round. Even here, seniors narrate tradeoffs out loud: "Dictionary for now. If this outgrows memory I'd move it to Redis." In the interviews I sit in on, candidates who talk through edge cases before typing tend to do better than faster typists. We test with and without AI tools too, which we cover in using AI tools in a coding interview.
Want to see the other side of the table? Read the questions hiring managers ask senior engineers and how they check whether a senior title is real. We wrote those for founders. For you they're a cheat sheet.
Written design is the remote senior skill
In an office, a senior engineer can win an argument at a whiteboard. Remote, you win it in a document. US teams working with LATAM engineers make a lot of decisions async, and the person who writes a clear one-page note (problem, options, recommendation, risks) gets handed bigger work.
Start small. Next time you pick up a feature that will take more than three days, write half a page before coding and share it. Some people will push back, which is the point. You can borrow the format from our post on design docs and RFCs.
A Concrete Version
A composite example. Andres is a PHP and Laravel developer in Lima, seven years in, applying for senior roles. His CV says: "Developed REST APIs for the payments module."
The senior rewrite: "Owned the payments API move from the monolith to a separate service. Cut checkout errors from about 2% to 0.3% over three months. Wrote the rollback plan we used twice."
Same job, different signal. The first line describes a task. The second shows scope (owned), a decision (move it out), a result with a number, and risk thinking (the rollback plan).
In the design round he's asked for a webhook delivery system. He spends the first five minutes asking questions. How many events per second? Can receivers handle duplicates? What happens when a receiver's endpoint is down for a day? Then he proposes a queue with retries and exponential backoff, an idempotency key, and a dead-letter queue with a dashboard. The interviewer asks what he'd cut for version one. He drops the dashboard and keeps the idempotency key, and explains why duplicates would hurt customers more than a missing dashboard hurts the team.
That last answer is the one that moves him to the senior offer.
The Honest Counterpoint
Titles are inflated in every market, the US included, and some companies really do hire "senior" by years. If you're going through a big-company HR filter, the years line still matters. Don't bury it.
There's also a trap in acting senior too early. Pushing back on every decision in your first month reads as arrogance. Senior engineers earn the right to redesign things by first shipping inside the existing design. And plenty of people are happy and valuable as strong mid-level engineers for years. That's a fine choice as long as you apply to roles that match it.
Frequently Asked Questions
How many years do I need to apply for a senior role?
Most US job posts say five or more. Treat it as a soft filter. If you can show ownership and design decisions with numbers, four strong years can pass. Each of our open roles lists the experience it expects.
Can I show seniority if my company never let me make decisions?
Partly. Look for the decisions you did make: a library choice, a refactor, an incident you handled. A side project with a written design also counts. Be honest in the interview about the limits of your scope.
Is tech lead experience required for senior?
No. Leading people is a separate track. Senior means you can own a feature or system end to end. Mentoring helps, as a bonus.
The Bottom Line
Rewrite your CV bullets as decisions and results. Ask questions before you design. Write things down. That's what US startups mean by senior, and all of it can be learned. When you're ready, look at senior roles like Python backend engineer or PHP and Laravel engineer.
---
Roberto Espinoza is CEO of Ruzora, which places senior LATAM engineers with US startups. Browse open roles.
