Resume Help · Primly Community

what does a software engineer resume actually need in 2026 (I read 50 JDs so you don't have to)

backend_bekah · 5 replies

I've been quietly job searching for about two months and I did something maybe a little unhinged: I collected 50 SWE job descriptions across different levels and company types and tried to identify what actually keeps showing up vs. what's resume advice folklore.

Here's what I found.

What's in almost every JD: System design / distributed systems (for senior+) Specific tech stacks: Python, Go, Java, TypeScript, and AWS/GCP by far the most common 'Cross-functional collaboration' or 'works well with product and design' in some form Ownership language: 'end-to-end', 'from concept to production', 'led the technical direction'

What that means for your resume: if you have any of those, they need to be visible, not buried. Not in a skills list at the bottom. In your bullets.

What's in some JDs but not as a dealbreaker: Specific cloud certifications (mentioned but rarely screened hard on) Kubernetes (common in infra JDs, rare in product eng JDs) Exact years of experience (most mid-level JDs say 3-5 years but routinely interview people outside that)

What I think people over-index on: The objective/summary section. Half the JDs I read are going to have someone skim your resume for 30 seconds. Your first bullet under your most recent role does more work than your summary.

Also: a GitHub link matters much less than the bullet that describes what you built. I've gotten feedback from interviewers who never clicked the link.

Formatting: One page if under 8 YOE. Two pages is fine above that, but not automatically better. Dense is worse than spacious. Readable beats optimized.

None of this is revolutionary. But I wanted to ground it in actual JDs rather than resume-coach vibes.

5 replies

ml_mike

The GitHub link thing. I stopped including mine after an interviewer told me flat out he doesn't look at portfolio links in the resume review stage. Your resume bullets need to make the case without expecting anyone to click through.

ux_uma

Adding data: I track my own application-to-screen rate. Rate went up ~8 percentage points after I moved key tech stack items from a skills section into my first three bullets. Same resume, different structure.

sec_sasha

Does the one page rule still apply for new grads? I have two internships, two projects, coursework. Fits on one page but barely.

ae_andre

One page for new grads is basically still the rule. Two internships, two projects, skills section. That's your resume. The coursework section can usually come out unless a JD specifically asks for it.

sdr_sky

The first bullet under most recent role being the thing that matters is accurate. I decide whether to keep reading based on that one line. Put your best impact there, not your job duties.