DEV Community: Thejus sunny

The Sad State of SWE Resumes (and How to Actually Land a Job in 2026)

Thejus sunny — Tue, 21 Jul 2026 08:26:17 +0000

The Sad State of SWE Resumes (and How to Actually Land a Job in 2026)

We've all been there, waking up early, applying for jobs, trying to be among the first to apply, even when the role doesn't match. And now with powerful LLMs, you can tailor your resume for roles you aren't qualified for. Even if the gap is 100%, somehow you end up building a resume for it.

Recruiters are overwhelmed by the volume of applications. Some say they can easily recognise AI-generated resumes, but I'm afraid that's not the case, at least from what I've seen, considering how well you can humanise and retrofit the bullets.

So the real question is: how do you land a job at a time like this? Is there even hope in building resumes?

Resumes aren't going anywhere (yet)

Truth is, resumes aren't going anywhere for a while, because most companies' hiring pipelines are built around them. That's literally the first step of screening.

That said, some companies are quietly moving away from treating the resume as a strong signal. Think AI-based task interviews where you're fully monitored during the assessment, or AI interviewers that ask questions to gauge your actual skills.

The market is tough, but not hopeless

The job market has always been tough, but hiring is actually rebounding. Software job openings are up roughly 14% year over year, and Q1 2026 saw the highest number of open SWE positions since early 2023.

And here's the thing: even if AI can write code and crush benchmarks, it doesn't fully replace humans. It increases the sheer volume of products in the market. We're talking 1000x. AI is accelerating production, not replacing it. Someone who could build a payment API in 2 months can now do it in 2 days without writing sloppy code. That's the difference.

Stop mass applying

Don't have FOMO. There are tons of tools that claim to get you interviews, and the reality is most of them don't work the way they're advertised. They probably do land interviews somehow, by tricking the ATS, but then fail almost inevitably in the actual interview.

Here's what works instead:

Apply to 3-5 high quality jobs every day, meaning jobs that actually match your profile 70-80%.

Tailor the resume per role if it's not an exact match, but respect the gaps. Don't invent bullets or numbers that you cannot justify in an actual screening.

There's actually a repo which helps you with this. Be truthful, but don't hesitate to use technology, and that's exactly what it does: https://github.com/santifer/career-ops

Use Apollo, but use it wisely. Don't email the recruiter or hiring manager saying "I'm interested in a position." Look at the role you want to apply for and ask a meaningful question about the role, or about the problem their company is trying to solve. Say you're interested to know more, or ask a question about the JD before applying. Make it subtle and natural, the goal is to grab the recruiter's attention.

Don't let Claude and Apify go on autopilot and run wild. You'll eventually get flagged by the job boards, or you'll run into an embarrassing screening session.

SWE resumes are their own thing

SWE resumes are unique. The bullets don't just represent a statement or an accomplishment. Every bullet communicates proof of work, without boring the hiring manager, coming straight to the point.

And if you ever get confused about templates: the easiest bet is Jake's Resume. It's almost the gold standard and you won't go wrong with it.

What we learned from 1000+ SWE resumes

If you're interested in what we learned after analysing 1000+ SWE resumes, and the common patterns that hold people back, you can read more about it here:

Software Engineer Resume Report | Rejectless

Analysis of 1,054 SWE resumes reveals the exact structural patterns that get engineers screened out. 85% have no quantifiable outcome. 1 in 6 flagged bullets was deleted because engineers couldn't justify it.

rejectless.app

The LaTeX Resume Problem: Why Engineers Spend More Time on Formatting Than Content

Thejus sunny — Thu, 19 Mar 2026 19:12:11 +0000

It's Sunday night. You found a job posting that actually excites you - the stack is right, the team seems great. Application deadline is tomorrow. You open your resume to update it and... you haven't touched the LaTeX source in eight months.

What follows is a ritual thousands of software engineers perform every job search cycle. You dig through Overleaf projects named resume_final_v3_ACTUAL_FINAL. You try to compile. It doesn't compile. You spend the next two hours not writing about your accomplishments — but fighting package versions, margin calculations, and mysterious vertical spacing that appeared out of nowhere.

By the time it compiles cleanly, you're too exhausted to think critically about whether the content actually sells your experience. The formatting won. Again.

The time audit nobody wants to do

A recurring thread on r/cscareerquestions asked engineers to estimate time spent on formatting versus content. The results were brutal:

I spent an entire Saturday getting my LaTeX resume to compile after upgrading TeX Live. Six hours. I changed maybe two bullet points of actual content.

— r/cscareerquestions

The median answer: for every 45 minutes spent improving content, engineers spend 3–4 hours on formatting and layout. Some reported ratios as high as 10:1 during major overhauls. That's not a workflow. That's a tax.

The LaTeX tax: greatest hits

1. The compilation error spiral

You added one line to your experience section. Now nothing compiles.

\resumeItem{Led migration of monolithic API to microservices,
  reducing p99 latency by 40%}  % forgot to escape %

! Missing $ inserted.
l.47 ...reducing p99 latency by 40%}
% A single unescaped % sign. 20 mins of debugging. Zero content improved.

2. The "make it fit" spiral

Your resume is one line too long. So begins the grand tradition of \vspace micro-adjustments:

\vspace{-7pt}  % after name
\vspace{-5pt}  % before experience
\vspace{-3pt}  % between jobs
% Three weeks later you add one bullet point.
% Everything overflows. You recalibrate everything.
% You question your life choices.

3. Package conflicts

You add one package. Three others break.

\usepackage{fontawesome5}
\usepackage{fontspec}       % now you need XeLaTeX
\usepackage[T1]{fontenc}    % conflicts with fontspec

! LaTeX Error: Option clash for package fontenc.
% You switch to XeLaTeX. fontawesome5 breaks.
% It's 1 AM. You still haven't updated your job title.

I'm a staff engineer at a FAANG company. I build distributed systems handling millions of requests per second. I cannot get my LaTeX resume to stop adding 3pt of space before my education section.

— Hacker News

The ATS problem nobody talks about

After all that time perfecting your layout — precise spacing, custom fonts, carefully aligned columns — there's a real chance the ATS can't read it properly. LaTeX PDFs fragment text in ways that confuse automated extraction. Custom fonts may lack proper Unicode mappings. Ligatures can turn fi into an unrecognizable glyph.

I switched from my custom LaTeX resume to a plain Google Docs template and my response rate tripled. Three years of tweaking that LaTeX template and it was literally working against me.

— r/experienceddevs

What actually gets you interviews

What engineers spend time on:

Fixing compilation errors
Adjusting \vspace values
Resolving package conflicts
Making content fit on one page

What actually gets interviews:

Quantified impact statements
Relevant keywords for ATS matching
Strong action verbs
Tailored content per application

The formatting trap is insidious because we're problem-solvers by nature. A LaTeX error is a puzzle, and puzzles are satisfying to solve. But optimising your \vspace values is a local maximum. The global maximum is spending that time on content.

What a modern resume workflow should look like

Formatting is a solved problem — pick a template, your content fills it, done. No compilation, no spacing hacks.
ATS compatibility is guaranteed — engineered for machine readability from the start, not reverse-engineered from a typesetting system built for academic papers.
Updates take 5 minutes, not 2 hours — add a new role, tweak a bullet, export PDF, done.
The tool helps you improve content — flagging weak bullets, missing metrics, vague phrasing.

Why I built Rejectless

The breaking point: one of us spent an entire weekend migrating a resume from one LaTeX template to another because the original used a deprecated package. The new template looked almost identical. Two days. Zero improvement to content.

Rejectless eliminates the formatting tax entirely. The builder renders Jake's Resume template pixel-perfect, ATS-compatible, every time — no compilation, no errors. The lint engine then analyses your content the way an ATS would, flagging weak phrasing and missing metrics before you submit.

The next time you're adjusting \vspace values at midnight, ask yourself: is this making my resume more likely to get me an interview? Your time is worth more than debugging compilation errors.

→ Try the Rejectless builder free — no LaTeX required.

career #webdev #beginners #productivity