Resume & Interview Mastery
Your resume gets 7 seconds. Your interview gets 45 minutes. Here's how to make both count — from beating the ATS to negotiating the offer.
Marcus applied to 137 jobs and heard back from zero
Marcus is a marketing manager with five years of experience at a well-known consumer brand. He led a product launch that drove $2.4M in first-quarter revenue. He managed a team of four. He increased email open rates by 38%.
None of that mattered — because his resume never reached a human.
Marcus formatted his resume with two columns, a sidebar, custom icons, and a dark background. His ATS (Applicant Tracking System) parsed "Marketing Manager" as "Man aging Mark eting." His $2.4M achievement disappeared into a garbled text block. His five years of experience? The system read zero.
He rewrote his resume in a single-column format, plain fonts, clear section headers, and standard job titles. Within two weeks, he had four interview callbacks.
The problem was never Marcus's qualifications. The problem was that a robot couldn't read his resume.
By the end of this module, you'll rewrite your resume bullets to pass any ATS, build a bank of STAR interview stories, and craft follow-up emails that set you apart from 90% of candidates.
Beating the ATS: your resume's first gatekeeper
Your personal brand (from the previous module) gets you noticed. Your resume and STAR stories are what win the offer. Let's make sure both are bulletproof.
An Applicant Tracking System is software that scans, parses, and ranks resumes before a recruiter ever sees them. Over 98% of Fortune 500 companies use one. If your resume isn't ATS-friendly, you're invisible.
The 6 rules of ATS-friendly resumes:
| Rule | Why it matters | What to do |
|---|---|---|
| Single-column layout | Multi-column layouts confuse parsers | One clean column, top to bottom |
| Standard section headers | ATS looks for "Experience," "Education," "Skills" | Don't get creative with "My Journey" or "Superpowers" |
| No graphics or tables | ATS can't read images, icons, or complex tables | Text only — your design skills belong in your portfolio |
| Keywords from the job posting | ATS matches your resume against the JD | Mirror the exact phrases: if they say "project management," don't write "managing projects" |
| Standard file format | Some systems choke on PDFs with embedded fonts | Submit as .docx unless the posting specifically says PDF |
| Standard fonts | Custom fonts can render as gibberish | Arial, Calibri, Garamond, Times New Roman |
Writing bullets that make recruiters stop scrolling
The difference between a forgettable resume and one that gets interviews is how you describe your work. Most people describe responsibilities. Hiring managers want results.
✗ Responsibility-focused (weak)
- ✗Responsible for social media marketing
- ✗Managed a team of sales associates
- ✗Handled customer complaints
- ✗Worked on product launches
- ✗Created reports for leadership
✓ Result-focused (strong)
- ✓Grew Instagram following from 2K to 48K in 14 months, driving 23% of website traffic
- ✓Led team of 6 sales associates to exceed quarterly quota by 18% ($340K)
- ✓Reduced customer complaint resolution time from 72 hours to 8 hours by implementing ticket triage system
- ✓Launched 3 products generating $1.2M combined first-year revenue
- ✓Built automated weekly dashboards in Looker, saving leadership team 5 hours/week
The formula: Action verb + what you did + measurable result + context
Not every bullet needs a number. But aim for at least 60% of your bullets to include a quantified outcome — revenue, percentage, time saved, users impacted, cost reduced.
There Are No Dumb Questions
"What if my job doesn't have measurable results?"
Every job has numbers if you look hard enough. Taught 30 students? Processed 200 invoices per week? Reduced turnaround time from 5 days to 2? Managed a budget of $50K? Supported a team of 12 engineers? If you truly can't find numbers, use scope and scale: "Coordinated company-wide office relocation across 3 buildings and 450 employees."
"Should I include a summary/objective at the top?"
A summary — yes, if it's specific and compelling. "Results-driven professional" is wasted space. "Marketing manager who grew a DTC skincare brand from $0 to $2.4M in 18 months through organic social and email" is a reason to keep reading. Objectives ("Seeking a challenging role...") are outdated — skip them entirely.
Rewrite a Weak Resume Bullet
25 XPTake this weak resume bullet and rewrite it using the formula (action verb + what + result + context): **Weak version:** "Responsible for managing the company blog and creating content." Write your stronger version. Then check: does it answer "so what?" If a recruiter reads it, do they know the impact you had? _Hint: Think about traffic, engagement, leads generated, publishing frequency, or ranking improvements. Even "Published 3 articles/week, growing organic traffic from 5K to 22K monthly visitors in 6 months" transforms a vague responsibility into a clear achievement._
Sign in to earn XPThe STAR method: your interview superweapon
Behavioral interviews ("Tell me about a time when...") are the most common interview format. The STAR method is how you answer them without rambling.
S — Situation: Set the scene. Where were you? What was happening? Keep it to 2 sentences.
T — Task: What was your specific responsibility or challenge? What were the stakes?
A — Action: What did YOU do? Not your team. You. Be specific about your decisions and steps.
R — Result: What happened? Quantify if possible. What did you learn?
Example question: "Tell me about a time you handled a conflict with a coworker."
| STAR element | Example answer |
|---|---|
| Situation | "At my last company, a designer and I disagreed on the onboarding flow for our mobile app. He wanted a 5-screen tutorial; I wanted users to jump straight in." |
| Task | "As the PM, I needed to resolve this before our sprint deadline in 3 days — and keep the relationship intact." |
| Action | "I suggested we test both approaches. I set up a quick UsabilityHub test with 40 users — 20 per version. The data showed the tutorial version had 34% higher completion but the jump-in version had 22% better day-7 retention." |
| Result | "We compromised: a 2-screen tooltip intro (not 5 full screens). Day-7 retention improved by 15%. More importantly, the designer and I established a 'let's test it' norm that resolved three more disagreements that quarter." |
The result should always be specific. "It went well" is not a result. "Day-7 retention improved by 15%" is.
The 10 most common behavioral questions (with what they're really asking)
| Question | What they're evaluating |
|---|---|
| "Tell me about yourself" | Can you tell a coherent career story in 90 seconds? |
| "Tell me about a time you failed" | Self-awareness, growth mindset, accountability |
| "How do you handle conflict?" | Emotional intelligence, collaboration |
| "Describe a time you led without authority" | Influence skills, cross-functional leadership |
| "Tell me about your biggest achievement" | What you value, how you define impact |
| "How do you prioritize competing demands?" | Decision-making framework, time management |
| "Why are you leaving your current role?" | Professionalism, motivation (don't badmouth) |
| "Why this company?" | Research, genuine interest, culture fit |
| "Tell me about a time you disagreed with your manager" | Assertiveness balanced with respect |
| "Where do you see yourself in 5 years?" | Ambition aligned with the role's growth path |
There Are No Dumb Questions
"What if I don't have a dramatic failure story?"
You don't need drama. A project that took longer than expected, a presentation that fell flat, a feature that users didn't adopt — these are all valid. The interviewer wants to hear what you learned, not how spectacularly you failed. The worst answer isn't a small failure — it's "I can't think of one," which signals zero self-awareness.
"How long should my answers be?"
90 seconds to 2 minutes per STAR story. Under 60 seconds feels thin. Over 3 minutes and you're rambling. Practice with a timer. If you're naturally verbose, write out your stories and edit them down to the essential beats.
Build Your STAR Story Bank
50 XPWrite out 3 STAR stories from your career (or school/volunteer experience if you're early career). For each: 1. Pick a theme: leadership, failure, or conflict 2. Write 2 sentences for Situation 3. Write 1 sentence for Task 4. Write 3-4 sentences for Action (focus on YOUR specific actions) 5. Write 1-2 sentences for Result (include a number if possible) 6. Time yourself telling each story out loud — aim for 90-120 seconds _Hint: The action section is where most people go wrong. "We worked together to solve it" tells the interviewer nothing about what YOU did. Replace every "we" with "I" — then add back only the "we" that's genuinely collaborative._
Sign in to earn XPThe follow-up that nobody sends (and why it matters)
These numbers represent the approximate percentage of candidates who take each follow-up action (based on aggregate recruiter surveys). The bar is remarkably low — which means doing the basics sets you apart.
The ideal follow-up email (sent within 4 hours):
- Thank them for their time (1 sentence)
- Reference something specific you discussed (shows you were listening)
- Add value — a relevant article, data point, or idea that connects to the conversation
- Restate your enthusiasm for the role (1 sentence)
- Keep it under 150 words total
Write a Follow-Up Email
25 XPImagine you just interviewed for your dream role. The interviewer mentioned their team is struggling with onboarding new hires remotely. Write a follow-up email (under 150 words) that: 1. Thanks them specifically (not generically) 2. References the onboarding challenge they mentioned 3. Adds a useful insight or resource 4. Closes with enthusiasm _Hint: Generic follow-ups ("Thanks for your time, I'm excited about the opportunity") are forgettable. Specific follow-ups ("Your point about remote onboarding resonated — I actually built a 30-day onboarding checklist at my last company that reduced ramp time by 40%...") are memorable._
Sign in to earn XPSalary negotiation in the interview process
Most people accept the first number they're offered. That single moment of discomfort can cost $5,000-$15,000 per year — compounding across your entire career.
The quick version: never name a number first, research the market range before any conversation, and negotiate the full package (signing bonus, equity, PTO) — not just base salary. Salary negotiation is its own skill — Module 8 covers it in depth, with scripts, research sources, and a complete negotiation playbook.
Back to Marcus
After switching to an ATS-friendly format, Marcus landed four interviews in two weeks. He prepared STAR stories for each one, sent specific follow-up emails within hours, and negotiated his best offer up by $8K. Same qualifications, same experience — just a better system. The difference between 137 rejections and a job offer wasn't talent. It was technique.
Key takeaways
- ATS filters ~75% of resumes before a human sees them. Single-column layout, standard headers, keywords from the JD, and .docx format get you past the robots.
- Results beat responsibilities. Every bullet should answer "so what?" — action verb + what you did + measurable result.
- STAR method (Situation, Task, Action, Result) turns rambling answers into compelling 90-second stories. Prepare 8 stories, cover 50 questions.
- Follow up within 4 hours with a specific, value-adding email. Most candidates don't — which makes this a free advantage.
- Never accept the first offer. Research the range, let them name the number first, and negotiate the full package — not just salary.
- Interview prep is the highest-ROI career activity. Four hours of preparation can change your trajectory for years.
Next up: Resumes get you interviews, but relationships get you referred. In the next module, you'll learn networking strategies that actually work — even if you're an introvert who dreads professional events.
Knowledge Check
1.Marcus applied to 137 jobs with a well-designed two-column resume featuring graphics and custom fonts. He got zero callbacks. After switching to a single-column, plain-text format with standard headers, he got 4 callbacks in 2 weeks. What best explains this?
2.A resume bullet reads: 'Responsible for managing the company's social media accounts.' Using the results-focused formula, which rewrite is strongest?
3.An interviewer asks: 'Tell me about a time you failed.' Using the STAR method, which answer demonstrates the strongest response structure?
4.You receive a job offer with a base salary $8,000 below your researched market rate. The recruiter says the salary is 'firm.' What is the most effective next step?