Resume Help · Primly Community

senior software engineer resume format that doesn't look like a LinkedIn export

backend_bekah · 4 replies

Seven years in, currently a senior backend eng at a fintech, actively searching. I redesigned my resume last month after getting basically no traction for six weeks and I want to share what I changed because the before/after was actually kind of dramatic.

What my resume looked like before: LinkedIn-export energy. Dense paragraph bullets under each role. Skills section at the bottom crammed with every tool I'd ever touched. Education at the top for some reason (I graduated in 2017). No whitespace anywhere. Looked like I was trying to hide something.

What I changed:

Education moved to the bottom. It's 2026, nobody cares about my 2017 BS after seven years of work.

Skills section moved to the top, but cleaned up. Four categories: languages (Python, Go, Java), infrastructure (Kafka, Postgres, Redis, Kubernetes), patterns (distributed systems, event-driven arch, API design), and tools (Datadog, Terraform, GitHub Actions). Not a wall of everything. Just what I actually want to talk about in interviews.

Bullets went from long paragraphs to short punchy lines. Target: one concept per bullet, one line if possible. If a bullet needed two sentences it was two bullets.

Added a three-line summary at the top: who I am, what I'm known for technically, what I'm looking for. Took me two hours to write it but every recruiter I've talked to has said something about it.

Whitespace increased significantly. I went from 11pt to 12pt font and added more margin. Resume is now 2 pages instead of 1.5 but it reads in 30 seconds instead of 3 minutes.

Response rate went from roughly 5% to maybe 18% over the last four weeks. Not scientific, just what I've observed.

One thing I haven't figured out: how to handle the on-call/reliability work I've done. It's genuinely important to my skill set but it doesn't bullet cleanly. Any suggestions?

4 replies

sre_sol

for on-call/reliability: frame it as ownership. "Owned oncall rotation for X services, drove MTTR down from 45min to 12min over 18 months." If you have incident counts or SLO history you can cite, use them. If not, the MTTR framing or "maintained 99.95% uptime for payment processing service" still works. Reliability is the point, not that you were woken up at 3am.

hardware_hugo

i actually do have some MTTR data from our incident tracker. going to pull that. appreciate it.

firsttime_mgr

Response rate going from 5% to 18% after a format change is consistent with what i've seen others report. the information in your resume matters less than whether a recruiter can parse it in 30 seconds. format is the highest-leverage change most people can make and the most underinvested.

market_realist

The skills section organization you described is exactly what i've been trying to do and failing. I keep either listing too much (looks desperate) or too little (looks junior). Your four category approach is clean. Stealing it.