📘 Career guides
Opinionated career advice for Python developers
Evergreen, dated when tactics could rot. We update these guides as the market changes. Read them once, come back when you're actually about to write a resume or walk into an interview.
How to write a Python resume that gets interviews in 2026
If your bullets say 'Used Python to solve problems', a recruiter is closing the tab before the second word.
Read guide →
What to put in your portfolio when you have no experience
Hiring managers don't care that you built five things. They care that one of them works, ships, and is yours.
Read guide →
How to ace a Python coding interview in 2026
The pattern catalog is small. The behavioural mistakes are predictable. The gap between 'practising LeetCode' and 'getting the offer' is mostly the second one.
Read guide →
How to negotiate your first developer offer — without losing it
The biggest single move you'll make on year-one comp is the 30 minutes between getting the offer and accepting it. Don't skip it.
Read guide →
Thriving as a remote junior developer
The single biggest risk for a remote junior is invisibility. The people who get promoted aren't the best coders — they're the ones whose managers know what they did this week.
Read guide →
Bootcamp, CS degree, or self-study in 2026: an honest comparison
The most common question we get from career-switchers — and the answers in 2026 are very different from what they were in 2018.
Read guide →
Junior → Mid Python in 18 months: a concrete promotion plan
Promotions aren't given for being good at tickets. They're given for owning scope your manager doesn't have to manage.
Read guide →
Want a guide on a topic we don't cover yet? Tell us — we write what readers actually ask for.
One Python career idea every Friday
One actionable career tip + one short tutorial, every Friday. Unsubscribe in one click.