A friend of mine — senior backend engineer, twelve years of experience, ex-Stripe — applied to 340 jobs last fall. Got four callbacks. Two interviews. One offer.

That ratio would’ve been unthinkable in 2021. But in the post-layoff market of 2024, it’s become disturbingly normal. I’ve been on the hiring side at DreamFlare AI for the past few months, and what I see from the other end of the table confirms it: the market is brutal, the volume of applicants is staggering, and most of the advice floating around online is outdated.

So I reached out to about two dozen developers who actually landed new roles in the past year. Not influencers. Not career coaches. Just engineers who went through the grind and came out the other side. The patterns were striking.

Mass applications are a losing game #

Every single person I talked to said the same thing, almost word for word: “I stopped applying to everything and started being strategic.”

The math is simple. When a mid-level React position gets 800 applicants in the first 48 hours, your resume is noise. ATS filters are aggressive. Recruiters skim for ten seconds. The developers who landed roles stopped playing the numbers game entirely.

What worked instead? Direct outreach. LinkedIn messages to hiring managers. Warm introductions through former colleagues. One engineer told me she landed her role because she commented something thoughtful on a VP of Engineering’s post about their tech stack — the VP DMed her the next day.

This isn’t networking advice from a self-help book. It’s survival math. In a saturated market, the application funnel is broken; the side door works better than the front.

Portfolios beat resumes #

I’ve reviewed hundreds of resumes as a CTO. Here’s a hard truth: they all look the same. “Led cross-functional teams.” “Improved performance by X%.” “Implemented microservices architecture.” I can’t tell candidates apart.

What actually catches my attention? A link to something real. A deployed project. A GitHub repo with clean commits and a README that shows the person thinks clearly. One candidate sent me a link to a side project — a small SaaS tool for managing restaurant waitlists — and I spent twenty minutes exploring it before I even looked at his resume.

The developers who landed roles in 2024 had live projects they could point to. Not toy apps from a Udemy course (hiring managers can spot those instantly). Real things that solved real problems, even small ones.

A few specifics from conversations:

• One engineer built a Chrome extension that reformats AWS billing pages into something readable. It had 2,000 users. That told me more than any resume bullet.
• Another maintained an open-source CLI tool for database migrations. Fourteen stars on GitHub, but the commit history showed consistent, thoughtful work over two years.
• A third had a personal blog where she wrote detailed postmortems of production incidents at her previous job (anonymized, obviously). Every post demonstrated debugging skill better than any whiteboard exercise could.

None of these are flashy. That’s the point.

Soft skills aren’t soft anymore #

Here’s the stat that keeps coming up: 89% of hiring managers say soft skills — communication, empathy, business acumen — are equally or more important than technical chops. I used to roll my eyes at this kind of thing. “Soft skills” felt like HR jargon for “plays well with others.”

I don’t roll my eyes anymore.

At DreamFlare, I’ve passed on technically strong candidates because they couldn’t explain their decisions. I’ve hired people with slightly weaker technical profiles because they understood the business context of what they were building. When you’re a twenty-person startup, someone who can talk to a customer, translate requirements into specs, and then build the thing — that person is worth two engineers who can only do the last part.

The developers who stood out in 2024 weren’t just coders. They were communicators. They wrote clear documentation. They could explain a technical tradeoff to a non-technical stakeholder without condescension. They asked questions in interviews that showed they were thinking about the product, not just the stack.

One hiring manager I spoke with put it bluntly: “I can teach someone a new framework in two weeks. I can’t teach them to care about the user.”

Experience matters more than it used to #

This is the uncomfortable part. Junior developers are having an exceptionally hard time right now. And I don’t have a clean answer for that.

The 2024 market disproportionately rewards experience. Companies that went through painful layoffs in 2022-2023 are hiring again, but they’re hiring fewer people and expecting more from each one. That means senior engineers with proven track records; people who’ve shipped production systems, handled on-call rotations, debugged distributed systems at 2am.

I talked to several junior developers who spent six months or more searching without success. The advice I heard from those who eventually broke through was consistent: find a way to demonstrate experience even if you don’t have corporate credentials. Contribute to open source. Build something with real users. Write about what you learned. Volunteer for a nonprofit’s tech needs.

It’s not fair that the market expects juniors to have senior-level proof of work. But fairness isn’t a feature of markets.

The interview itself changed #

Technical interviews in 2024 look different than they did even two years ago. Several developers mentioned that take-home projects and system design conversations have replaced or supplemented the classic whiteboard LeetCode grind.

That doesn’t mean algorithmic skills don’t matter. They do, especially at big companies. But the developers who landed roles said their interviews increasingly tested practical judgment: “How would you design the caching layer for this feature?” rather than “Implement a red-black tree.”

One engineer told me his final-round interview at a Series B startup was a pair-programming session where they worked on an actual production bug together. No trick questions. No gotchas. Just: “Here’s a real problem, let’s solve it.” He said it was the most humane interview he’d ever done — and the one where he felt most able to demonstrate his actual skills.

I love this trend. At DreamFlare, we’ve moved almost entirely to practical assessments. I want to see how someone thinks through a problem, not whether they memorized Dijkstra’s algorithm.

What I’d tell someone starting their search today #

I’m hesitant to frame this as advice because every job search is different and I’m keenly aware that being a CTO gives me a skewed perspective. But if I had to distill the patterns from these conversations:

Stop optimizing for volume. Sending 50 tailored applications beats 500 spray-and-pray submissions. Research the company. Reference something specific in your outreach. Show you’ve done your homework.

Build something visible. It doesn’t have to be impressive by Silicon Valley standards. A small project with real users tells a hiring manager more than a polished resume ever could.

Practice explaining things. Record yourself giving a five-minute explanation of a technical decision you made recently. If you can’t do it clearly, keep practicing. Communication is a hiring signal now, not a nice-to-have.

Lean on your network. This feels uncomfortable for a lot of engineers. We like to think our work speaks for itself. It doesn’t, at least not in this market. A warm introduction from a former colleague gets your resume past the ATS graveyard.

The market will recover. It always does. But the developers who come out of this period strongest will be the ones who treated their job search as a product problem — with strategy, iteration, and a willingness to build in public.

The ones who kept grinding LeetCode in isolation? I worry about them.