How to write a Python resume that gets interviews in 2026

The 30-second pass

Recruiters skim. Not read, skim. The first pass is ~7 seconds in tools like Greenhouse or Workday and ~30 seconds total if you survive. Everything you write has to clear those two bars.

Your resume is being scored on three things: did you ship something, can you describe it in numbers, and is the stack we care about somewhere in the top half. Anything that doesn't move one of those needles is taking space from something that would.

Three bullet shapes that actually work

Pick one of these patterns for every line. They look formulaic because they are — recruiters have been trained on them for a decade.

• Outcome bullet — 'Reduced API p95 latency from 480ms to 92ms by replacing the synchronous Stripe call with a Celery-backed write-behind queue.' Numbers + change + how.
• Built bullet — 'Built a FastAPI + Postgres SaaS with JWT auth, Stripe subscriptions, and a 30-PR golden eval suite (live URL).' Concrete stack + concrete artifacts.
• Owned bullet — 'Owned the migration from Celery 4 to RQ across 12 services, cutting infra cost 32% while keeping at-least-once semantics.' Scope + measurable result.

What to cut

These are the lines that make recruiters skim faster. None of them are wrong. They're just background noise that crowds out the lines that do work.

• 'Passionate about clean code.' Everyone says this. Means nothing.
• 'Used Python to solve real-world problems.' What problems? Solved how? Result?
• 'Strong communication skills.' Show this in your portfolio README, not your resume.
• Any tool you used once, three jobs ago, and never since.
• GPA, unless you're under 12 months out of school and it's above 3.7.

The portfolio link is doing 40% of the work

The most common reason a Python junior gets passed over isn't lack of experience — it's an empty GitHub. If your resume links to a profile with three half-done forks, the recruiter has decided before the call.

Two finished projects beat 14 abandoned ones. One project with a deployed URL, a real README, and visible commit history beats two private repos with 'Various data projects' as the only description.

If you do nothing else this week: pick one project, ship a real README, deploy it somewhere, and link directly to it in the resume header — not on the second page next to your education.

The 4 sections, in order

Recruiters read top-down. Put load-bearing material first.

• Header — name, email, GitHub, deployed-portfolio URL. Phone optional. No address. No headshot.
• Highlights — 3 bullets max, the strongest you have. This is the only section that gets read on the first pass for some recruiters.
• Experience — reverse-chronological, bullets in the shape above. Cut anything older than 8 years unless you're applying to a specific role that needs it.
• Education + certs — bottom. One line each. No coursework lists unless you're under a year out of school.

ATS-friendly without being ugly

Most companies run Greenhouse, Lever, or Workday. They strip formatting and parse text. If your resume is a beautiful two-column Figma export, half of it disappears in the parse.

Use a single column. Avoid text boxes, headers, footers, and tables. Use plain bullet characters (•, –, *). Save as PDF, but check what it looks like as plain text — open it in Preview / Acrobat and copy-paste into a notes app. If your bullets disappear, the ATS will eat them too.

A worked example

Bad: 'Worked with team on Python backend. Helped solve bugs and added features.'

Better: 'Owned the auth migration from Django session-cookies to JWT across 9 internal services. Wrote the migration RFC, shipped feature-flagged rollout, deprecated old code in 6 weeks.'

Best: 'Owned the auth migration from Django session-cookies to JWT across 9 internal services; cut p95 login latency from 220ms to 38ms and reduced auth-related support tickets 71% over 2 quarters.'

The 'best' version is the same project. Same work. The difference is showing the trade-off you owned and quantifying the impact. That's the move.