Interviewing as a late-career engineer is fundamentally different from interviewing in your 30s. The bar is higher because expectations are higher — but the surface area for self-sabotage is larger too. Talking too much about old technologies, hesitating on modern stacks, or appearing tired-of-it-all all close doors quickly.
Position yourself for senior+ roles only
Applying for “Senior Software Engineer” with 25 years of experience makes hiring managers anxious. They will assume you are coasting, you cannot keep up, or you have a hidden reason for the lateral. Aim for:
- Staff Engineer / Principal Engineer
- Architect roles
- Engineering Manager (if leadership is the right fit)
- Director / VP if you have managed managers
- Consulting partner / fractional CTO if you want flexibility
The “tell me about yourself” answer
Your career arc is too long to recite chronologically. Use a 3-act structure:
- Act 1 (15 sec): “Engineer with 25+ years across [2–3 industries], with depth in [your specialty]”
- Act 2 (45 sec): 2–3 specific accomplishments from the last 5 years (not your career)
- Act 3 (15 sec): Why you are interviewing now and why this role
Do not start at “I graduated from college in 1998.” Start in the present, work backwards only as needed.
Talking about your last decade
Recency bias is real. Interviewers want to hear about the last 5 years. Have ready:
- 3–4 system designs you led recently
- 2–3 significant technical decisions and the rationale
- 1–2 cross-functional collaboration stories
- 1–2 mentorship or growth stories
Avoiding ageism signals
Some patterns that pattern-match to “out of touch” — even if you are not:
- Mentioning specific older tech (Cobol, Solaris, Perl 4) without modern context
- “Back in my day…” framing
- Dismissing modern tools (LLMs, cloud, microservices) without nuance
- Wearing a suit to a startup interview
- Older-style email handles, outdated GitHub bio
Counter-patterns:
- Mention recent technologies you have used or evaluated
- Acknowledge what is new and good (not just what was lost)
- Have a recent GitHub project — even a small one
- Use the same calibration as the company’s engineering team (read their blog, match the vocabulary)
Coding rounds at senior+ levels
For Staff and Principal interviews, coding is often less important than design and behavioral. But it is not zero. You should be able to:
- Solve LeetCode mediums in your strongest language
- Read and critique code in unfamiliar codebases
- Walk through design and tradeoffs verbally
- Code review a PR with substantive feedback
The compensation trap
Senior+ candidates have salary history that may exceed the role’s budget. Best practices:
- Decline to share past compensation if asked (illegal to require in many states)
- Anchor on the role’s market range, not your past comp
- Negotiate equity vesting and sign-on as much as base — these are often more flexible
The ageism question
You will not be asked directly. But signals will be sent — sometimes positive (interviewer mentions “we love institutional knowledge”) and sometimes negative (interviewer focuses excessively on “cultural fit”). Trust pattern recognition. If a company gives off the wrong signal, walk.
Frequently Asked Questions
Should I shorten my resume to one page?
Two pages is the right length for senior+ candidates. One page over-compresses; three pages signals lack of editing. Lead with the last 5 years; collapse pre-2010 into “Earlier Career.”
Is it OK to admit I do not want to be a manager?
Yes — and explicitly target Staff/Principal/Architect tracks. Many companies have strong IC ladders.
Are tech companies friendlier to older candidates than they used to be?
Mixed picture. Public companies are generally better than startups. Companies with older tech stacks (banking, insurance, defense) are more receptive than consumer apps.