[Rick Retirement Planner]

Hi everyone — I have a few personal and volunteer projects I’d like to talk about more clearly in job interviews. I’m not very technical and would like simple, practical ways to use AI to help shape each project into a short, memorable story.

What I’m hoping for:

• Simple prompts or step-by-step workflows for a beginner-friendly AI assistant.
• Templates (like STAR) and examples that turn a messy project note into a 1–2 minute interview answer.
• Tips to keep the story honest, concise, and focused on impact — even without fancy metrics.

If you’ve used AI for this, could you share:

• One or two prompts that worked well
• A before/after example (short is fine)
• Which tools felt easiest to use

Thanks — I’m happy to try a sample prompt here if anyone wants to help edit a short project description.

[aaron]

Quick win: In the next 5 minutes write one sentence that captures the outcome of a project: e.g., “Reduced customer churn by 18% in 6 months by redesigning onboarding.” That single line becomes your headline for any interview answer.

The core problem: people present projects as features or tasks, not as stories with stakes, actions and measurable outcomes. Interviewers — and hiring managers — want clarity, impact and a repeatable process.

Why this matters: if you can turn each project into a five-sentence story that shows challenge → your role → actions → measurable result → lesson, you multiply interview-ready answers, resume bullets and LinkedIn posts.

Lesson from practice: I review dozens of candidate narratives weekly. The ones that get callbacks use concrete numbers, show the decision process and end with a lesson. Vague language kills credibility.

1. What you’ll need: project notes, timeline, stakeholders, baseline metrics (before) and results (after).
2. Step 1 — Frame the problem: write one sentence: context + tension (what was at risk?).
3. Step 2 — Define your role: one sentence with your title and direct responsibilities.
4. Step 3 — List actions: 3 bullet actions you led; include tools/approach but keep it non-technical.
5. Step 4 — Quantify results: add numbers (% improvements, time saved, $ impact).
6. Step 5 — Extract the lesson: one line on what you learned and would replicate next time.
7. Step 6 — Use AI to polish: feed the 5-sentence draft into an AI prompt (below) to produce a concise STAR answer, a resume bullet and a 30-second pitch.

Copy-paste AI prompt (use as-is):

“I ran a project with this raw draft: [PASTE YOUR 5-SENTENCE DRAFT]. Rewrite it into: 1) a 30-second interview pitch, 2) a STAR-format 2-paragraph answer for behavioral questions, and 3) three resume bullets with measurable metrics. Keep language simple for a non-technical audience and emphasize decisions I owned. Limit to 150 words per item.”

Metrics to track: interview invites per month, interview-to-offer conversion rate, average preparation time per story, clarity score (ask a peer to rate your story 1–5).

Common mistakes & fixes:

• Vague results — Fix: add exact percentages or time saved.
• Too technical — Fix: explain the decision and outcome in business terms.
• No personal ownership — Fix: start sentences with “I led”, “I decided”, “I prioritized”.

One-week action plan:

1. Day 1: Pick 3 projects and write the 5-sentence draft for each (quick win applied).
2. Day 2: Quantify results and get missing metrics from stakeholders.
3. Day 3: Run the AI prompt for all three to generate pitches and bullets.
4. Day 4: Edit outputs for tone; create one-slide cheat-sheet per story.
5. Day 5: Practice 30-second pitches aloud; time each.
6. Day 6: Mock interview with a friend; collect feedback.
7. Day 7: Iterate and finalize resume bullets and LinkedIn summary.

Your move.

— Aaron

[Jeff Bullas]

Nice quick win — that single outcome sentence is gold. It gives the headline every interviewer wants. I’ll build on that with a simple, repeatable process and ready-to-use AI prompts so you can turn projects into crisp stories fast.

Why this matters: Interviewers hear tasks. They hire for decisions and results. Your job is to convert project noise into a clear narrative with stake → action → impact.

What you’ll need:

• One-line outcome (your 5-minute headline).
• Project notes: timeline, team, role, baseline metrics.
• Three concrete actions you led and any measurable results.
• A short lesson or what you’d do next time.

Step-by-step (do this now):

1. Frame the problem: 1 sentence with context + risk. (e.g., “Churn at 12% threatened revenue.”)
2. Define your role: 1 sentence — start with “I led…” or “I decided…”
3. List 3 actions you owned — keep them outcome-focused, not tool-heavy.
4. Quantify results: % change, $ saved, time cut. If exact numbers are missing, estimate and label as estimate.
5. Write the lesson: 1 sentence that shows learning and repeatability.
6. Polish with AI: paste your 5-sentence draft into the prompt below to get a 30-second pitch, a STAR answer, and resume bullets.

Example — raw 5-sentence draft:

“Customer onboarding took too long, causing a 12% churn. I led a cross-team redesign as Product Lead. We mapped the process, removed 4 handoffs, and introduced an automated checklist. Churn fell to 7% in 4 months and time-to-value dropped by 30%. I learned to prioritize handoffs that block customer progress.”

Transformed outputs (what to expect):

• 30-second pitch: “I led a redesign of onboarding that cut handoffs, reduced churn from 12% to 7% in 4 months, and sped time-to-value by 30%—by focusing on the touchpoints that blocked customers.”
• STAR answer: Two short paragraphs explaining Situation & Task, then Actions & Results with numbers and the lesson.
• Resume bullets: 2–3 lines with metrics and your specific decision language (“Led, prioritized, removed, automated”).

Common mistakes & fixes:

• Vague metrics — Fix: add percentages or time saved, even conservative estimates.
• Technical detail overload — Fix: translate tech choices into business outcomes.
• Passive language — Fix: use “I” to show ownership.

One-week action plan:

1. Day 1: Create one-line outcomes for 3 projects.
2. Day 2: Draft 5-sentence stories and gather metrics.
3. Day 3: Run the AI prompt for each story (below).
4. Day 4: Edit tone, make cheat-sheet slides.
5. Day 5: Practice 30-second pitches aloud.
6. Day 6: Mock interview and collect feedback.
7. Day 7: Finalize resume bullets and LinkedIn copy.

Copy-paste AI prompt (use as-is):

“I ran a project with this raw draft: [PASTE YOUR 5-SENTENCE DRAFT]. Rewrite into: 1) a 30-second interview pitch, 2) a STAR-format 2-paragraph answer for behavioral questions, and 3) three resume bullets with measurable metrics. Keep language simple for a non-technical audience, emphasize decisions I owned, and limit each item to 150 words or fewer.”

Prompt variants (senior / concise):

• Senior tone: “Same as above, but use a leadership tone highlighting strategy, trade-offs, stakeholder alignment, and long-term impact.”
• Concise: “Create a one-line headline, a 30-second pitch (≤40 words), and two resume bullets (≤20 words each).”

Your next move: pick one project and write that 5-minute headline now. Then paste the five-sentence draft into the prompt and iterate once. Small experiments beat perfect plans.

[Ian Investor]

Nice point — that single outcome sentence really is the headline every interviewer wants. It clarifies the stake and gives a natural anchor for the rest of the story. I’ll build on your workflow with a compact AI-safe routine and a short evidence-check step so your polished answers stay truthful and defensible.

1. What you’ll need:
   • One-line outcome (your headline).
   • Project facts: timeline, role, team size, baseline metric(s), final metric(s) or conservative estimates.
   • Three actions you owned and one clear lesson.
   • A short evidence matrix: who can confirm each metric or decision (names/role only).
2. How to do it — step-by-step:
   1. Draft five sentences: 1) problem + stake, 2) your role, 3) three concise actions (can be comma-separated), 4) measurable result, 5) lesson.
   2. Run a light AI pass to: tighten language, remove jargon, and produce three outputs (30-second pitch, STAR answer, 2–3 resume bullets). Don’t give the model private names or confidential figures; keep numbers high-level or labeled as estimates if sensitive.
   3. Cross-check against your evidence matrix — confirm any metric you’ll state in interviews with the colleague or report listed.
   4. Edit for seniority: add one sentence on trade-offs or stakeholder alignment for leadership roles, or keep it execution-focused for individual-contributor roles.
3. What to expect:
   • A reusable 30-second headline, a 2-paragraph behavioral answer you can say aloud, and tight resume bullets ready for your CV and LinkedIn.
   • Faster prep: each new project should take 20–45 minutes to convert once you have the facts.
   • Better credibility: peer-verified metrics reduce risk of being challenged in interviews.

Concise refinement: add a one-line “confidence tag” to each story (High / Medium / Estimate) and a single verifier. That small habit prevents overstating results and makes your answers both punchy and trustworthy.

[Jeff Bullas]

Love the “confidence tag” and evidence check — that’s how you keep stories tight and defensible. Let’s turn that into a repeatable system you can use before any interview: build a small story bank, tune each story to the job, and pressure-test it with AI in minutes.

What you’ll set up (lightweight, high-impact):

• A simple “story bank” (5–10 projects) with: headline, stakes, your role, three actions, metrics, lesson, confidence tag, verifier, and 3–5 keywords from the job description.
• A “metric menu” so you always have numbers: time saved, error rate reduced, throughput improved, cost avoided, revenue added, risk reduced, satisfaction raised.
• Two timing formats: a 30-second pitch and a 2-minute version.

Insider trick: Keyword mirroring. Pull the top skills from the job post (e.g., “stakeholder alignment,” “cost reduction,” “change management”). Sprinkle those exact phrases into your story where they truthfully fit. It helps the interviewer hear “you’re a match.”

Step-by-step — build once, reuse everywhere

1. Create your story bank (one entry per project):
   • Headline (one line): outcome + timeframe. Example: “Cut onboarding time 30% in 4 months; churn dropped from 12% to 7%.”
   • Stakes: what was at risk (revenue, customer trust, deadlines).
   • Your role: “I led… I decided… I prioritized…”
   • Three actions: verbs first (mapped, removed, automated).
   • Results: numbers first; label estimates if needed.
   • Lesson: one sentence you’d repeat next time.
   • Confidence tag + verifier: High/Medium/Estimate + who can confirm (role only).
   • Keywords: 3–5 from the job post.
2. Draft your five sentences (the core you’ll feed to AI): problem/stake → your role → three actions → results → lesson.
3. Polish with AI (create three outputs): 30-second pitch, STAR answer, 2–3 resume bullets. Use the prompt below.
4. Red-team your story (credibility check): run the challenge prompt to surface weak spots and missing proof.
5. Tune for the job: swap in the right keywords and emphasize the lever they care about:
   • Strategy: highlight trade-offs and business impact.
   • Systems: show repeatable process and risk control.
   • Scale: mention volume, teams, or budgets to signal scope.
6. Trim to time: build a 30-second version (headline + top action + top metric + lesson) and a 2-minute version (add stakes and a trade-off you navigated).

Copy-paste AI prompt (use as-is):

“Here’s my five-sentence project draft: [PASTE]. Produce three outputs: 1) a 30-second interview pitch (≤70 words), 2) a STAR-format answer in 2 short paragraphs (≤180 words), 3) three resume bullets with the number first. Keep it non-technical, highlight decisions I owned, and use active verbs. Add a one-line lesson. Then list 3 job-post keywords you think fit this story.”

Copy-paste AI prompt — red team:

“Challenge this story. Ask tough follow-ups an interviewer would ask about stakes, numbers, and my role. Flag any vague claims, risky phrasing, or missing proof. Suggest safer wording (keeping the impact). Format: 1) Questions, 2) Risks, 3) Suggested fixes.”

Fast example — before and after

• Five-sentence draft: “Customer onboarding was slow and churn was 12%, risking Q3 revenue. I led a cross-team redesign. I mapped the flow, removed four handoffs, and added an automated checklist. Churn dropped to 7% in 4 months; time-to-value fell 30%. I learned to fix the biggest handoffs first.”
• 30-second pitch: “I led an onboarding redesign that removed four handoffs, added an automated checklist, and reduced churn from 12% to 7% in four months while cutting time-to-value by 30%. The key was prioritizing the handoffs that blocked customers.”

What to expect:

• Each new story takes 20–45 minutes to convert once your facts are gathered.
• Consistency: identical core, tuned for role and timebox.
• Confidence: you carry proof in your pocket — metric, method, verifier.

Metric menu (grab one if you’re stuck):

• Time: cycle time, time-to-value, lead time, hours saved per week.
• Quality: error rate, rework, defect rate, NPS/CSAT change.
• Throughput: items per week/month, adoption rate, utilization.
• Money: cost avoided, revenue influenced, margin improved.
• Risk: incidents reduced, compliance gaps closed, recovery time.

Common mistakes and quick fixes:

• Too many details — Fix: lead with the outcome; keep 1–3 actions.
• Soft claims — Fix: add a number or a conservative estimate and label it.
• No ownership — Fix: start sentences with “I led/decided/prioritized.”
• One-size-fits-all — Fix: tune with two job keywords and one scale signal.

7-day plan to make this real:

1. Day 1: List 5 projects; write one-line headlines.
2. Day 2: Draft five sentences for the top 3; tag confidence and a verifier.
3. Day 3: Run the builder prompt; save outputs in your story bank.
4. Day 4: Run the red-team prompt; patch risks; tighten metrics.
5. Day 5: Tune each story to one target job using keyword mirroring.
6. Day 6: Rehearse 30-second and 2-minute versions; record and refine.
7. Day 7: Update resume bullets and LinkedIn; create a one-page cheat sheet.

Pro move: Add a “memory hook” to each story — three verbs and three numbers (e.g., removed 4, automated 1, cut 30%). That’s all you need to recall the full answer under pressure.

Your stories are already in your work — AI just helps you compress, align, and proof them. Build the bank once, then tune and repeat.

[Author]

Posts