Back to Resources

Your next act

8 min read · July 31, 2026

Last verified: July 31, 2026

The Ageism-Proof Interview Prep

Five prompts to prep for the questions that are really about your age, without ever saying the word "age" — done in one sitting the night before.

What this is for

You've got an interview scheduled and you know, without anyone saying it out loud, that some of the questions will really be testing whether you're too senior, too settled, or too far from the current stack. This gets you ready for that subtext, not the generic "tell me about yourself" prep.

Before you start

  • The job posting for this specific role
  • Your resume or a rundown of your last 2-3 roles
  • 20-30 minutes, ideally with something to talk into or type into in real time for Prompt 5

The prompts

1. Reframe long tenure as velocity and pattern recognition

Use either. Read the output aloud before the interview and cut anything that doesn't sound like you.

ROLE: You are an interview coach who helps senior candidates reframe long
tenure as an advantage instead of a liability.

CONTEXT: I've been at my current company for [NUMBER] years, and before
that [NUMBER] years at [PREVIOUS COMPANY]. Interviewers sometimes read
long tenure as complacency or being "stuck." Here's what actually
happened during that time: [LIST 3-4 REAL THINGS — e.g. "took over a
failing product line and turned it profitable in 18 months," "was moved
into 3 different roles as the company restructured," "trained the last
2 people who now outrank me"]

CONSTRAINTS:
- Reframe tenure as pattern recognition (I've seen this exact problem
  before, under different names) and velocity (I don't need a ramp-up
  period), using the specifics I gave you — not generic claims.
- No more than 4 sentences per reframe. This needs to be sayable out
  loud in an interview, not a paragraph I'd read off a page.
- Do not use the words "seasoned," "veteran," or "wisdom" — they read as
  a euphemism for old.

OUTPUT FORMAT: 2 versions of the reframe — one for "walk me through your
background," one for "why should we hire you over someone earlier in
their career."

2. Answer "why this role now" when it's sideways or down

Use either. Be honest with the AI about the real reason — a coached-sounding answer is easier to spot than an honest one.

ROLE: You are an interview coach specializing in career-transition
narratives for candidates moving into a role that is a lateral move or
a step down in title or scope from their most recent position.

CONTEXT: My last role was [TITLE/LEVEL, e.g. "VP of Operations, 40
direct reports"]. This role is [TITLE/LEVEL, e.g. "Director of
Operations, 8 direct reports"]. The real reason I want it:
[YOUR ACTUAL REASON — e.g. "I want to build again instead of managing
managers," "my last company's leadership team was let go and I'm
restarting," "I'm choosing scope and sanity over title"]

CONSTRAINTS:
- Build an answer that states the move plainly and gives the real,
  specific reason — do not paper over the step down or pretend it's not
  one.
- Do not use the phrase "I'm looking for work-life balance" as the
  entire answer — it's true for a lot of people but it answers nothing
  about why THIS role.
- End the answer with what I'm optimizing for now that's different from
  what I optimized for before.

OUTPUT FORMAT: One 4-6 sentence answer, plus one follow-up line I can
use if they push with "but won't you be bored / won't you leave when
something bigger comes along."

3. Demonstrate current-stack fluency without overclaiming

Use either. Be precise about your real level with each tool — this keeps you honest, not more fluent-sounding.

ROLE: You are a technical interview coach helping a candidate describe
their real, current level of fluency with modern tools accurately and
credibly.

CONTEXT: The job post lists these tools/skills: [PASTE FROM POST, e.g.
"Salesforce, HubSpot, basic SQL, AI-assisted reporting"]. My honest
level with each: [LIST YOUR REAL LEVEL PER TOOL, e.g. "Salesforce -
daily user 3 years," "HubSpot - used it at previous job, rusty," "SQL -
can read queries, can't write complex ones," "AI reporting tools -
started using ChatGPT for this in the last 6 months"]

CONSTRAINTS:
- For each tool, write one honest sentence I can say in an interview —
  claiming exactly my real level, not rounding up.
- For anything below "daily user," include a bridge sentence showing
  how fast I could close the gap (what I'd do in week one), not an
  excuse for why I don't know it.
- Flag any tool where my honest answer is a real risk for this role, so
  I know where to expect follow-up questions.

OUTPUT FORMAT: A table — tool, my honest one-line answer, bridge
sentence if needed, risk flag (yes/no).

4. Handle "are you comfortable reporting to someone younger"

Use either. This rarely gets asked directly — it usually comes disguised, so this preps you for both versions.

ROLE: You are an interview coach helping a candidate handle age-related
questions that are illegal to ask directly but common in disguised form
(e.g. "how do you feel about a fast-paced, young team," "will you be ok
taking direction from someone with less experience").

CONTEXT: I am [YOUR AGE OR AGE RANGE] and the hiring manager or team I'd
report to is younger than me. I have [REPORTED TO SOMEONE YOUNGER
BEFORE / NOT DONE THIS BEFORE — say which].

CONSTRAINTS:
- Give me a direct answer to the disguised version of this question that
  addresses reporting structure and authority without saying the word
  "age" or "young" myself.
- The answer should state plainly that I care about the person's
  judgment and the work, not their tenure — backed by one real example
  if I have one.
- Do not write an answer that sounds defensive or over-eager to prove
  I'm not bothered — both read as protesting too much.

OUTPUT FORMAT: One direct answer (3-4 sentences), plus a one-line note
on tone (how it should sound spoken, e.g. "matter-of-fact, not
enthusiastic").

5. Prep 3 questions that signal you're a peer, not a relic

Use either, near the end of the interview when they ask "any questions for us."

ROLE: You are a senior hiring manager advising a candidate on what
questions to ask at the end of an interview to signal they think like a
peer and a near-term contributor, not someone assessing whether the job
is beneath them.

CONTEXT: The role is [TITLE], at [COMPANY/INDUSTRY]. The job post's top
priority seems to be [1-2 THINGS FROM THE POST, e.g. "scaling a support
team from 5 to 20," "modernizing a legacy reporting process"].

CONSTRAINTS:
- Generate 3 questions, each tied to the specific priority I gave you,
  not generic ("what's the culture like") questions.
- At least one question should probe a real tradeoff or tension the
  team is likely facing, showing I already think at their level.
- None of the questions should be about schedule, benefits, or PTO —
  save those for the offer stage.

OUTPUT FORMAT: 3 questions, each with a one-line note on what it
signals about me if I ask it.

Role-play the interviewer, progressively tougher

Use ChatGPT or Claude in voice mode if you can — saying answers out loud is the point.

ROLE: You are a hiring manager conducting a first-round interview for
[JOB TITLE] at a company like [COMPANY/INDUSTRY]. You will ask me one
question at a time and wait for my answer before continuing.

CONTEXT: My background: [2-3 SENTENCE SUMMARY]. The job post:
[PASTE KEY REQUIREMENTS].

CONSTRAINTS:
- Start with 2 standard, comfortable questions.
- Then escalate: ask one question that indirectly probes whether I'm
  "too senior" or "too expensive" for the role, one that tests whether
  my skills are current, and one that pushes back skeptically on
  whatever I say in response to the previous question — don't accept my
  first answer at face value.
- After I answer each question, before moving to the next one, give me
  one blunt sentence of feedback on how that answer landed.
- Stay in character as the interviewer; do not break to explain what
  you're doing.

OUTPUT FORMAT: One question at a time, my answer, then your one-line
feedback, then the next question. Stop after 5 questions and give an
overall 3-sentence debrief.

Where this goes wrong

  • You memorize the AI's exact wording. Recited answers sound recited, and an experienced interviewer will notice the seam. Use the prompts to find the right structure and facts, then say it in your own words.
  • You skip the role-play because it feels awkward. The awkwardness is the rehearsal working — the first time you say a hard answer out loud shouldn't be in the actual interview.
  • You're not honest with the AI about weak spots in Prompt 3. If you inflate your tool fluency in the prompt, the AI builds you a script that will fall apart under a real follow-up question. The bridge-sentence approach exists so you don't have to inflate anything.

The 2-minute version

Run Prompt 1 and Prompt 5 tonight — those cover how you'll open and close the interview. If you have 10 more minutes, run the role-play (Prompt 6) once through, out loud.


Where you stand with AI, in 10 minutes. The free AI Readiness Quiz gives you a personalized roadmap instead of another tool list: genxcelerate.com

Weekly, on Tuesdays. The Gen Xcelerator — practical AI intelligence for people who already know how to do the job. Subscribe free

Experience Is the API. — GenXcelerate

Related resources

The Gen Xcelerator

A new one every Tuesday. Short, useful, and written for people who already know how to run things.

Get the newsletter