Never break when your time is tough — just stay calm, stay active, and keep moving.
🎯 The Application That Broke Me
I stopped counting after 100.
I applied to every role that matched my resume, including:
- WordPress Developer
- Full-Stack Developer
- Frontend Developer
- Backend Developer
- Business Development Executive - Entry Level
- Project Manager - Entry Level
- Junior React Native Developer
- Senior WordPress Developer
Two months. Every relevant listing I could find. Custom cover letters for the ones that mattered. Follow-ups. LinkedIn messages to hiring managers who never wrote back.
Nothing worked out.
Not one offer. Barely a handful of interviews. A few "we'll get back to you" emails that never came back.
So a few weeks ago, I picked up a food and package delivery job on Uber, riding my own Hero Xtreme 125 through morning and evening traffic. I'm writing this because I think a lot of developers reading this are living some version of the same story right now, and nobody in our field likes to say it out loud. I do.
📊 The Market Isn't in Your Head — It's Actually This Bad
If job hunting in 2026 feels harder than it should, that's not you being unskilled or unlucky. The numbers back you up.
The time it takes to get a first job offer jumped from 57 days to 83 days in 2025 — almost a month and a half longer than before. Entry-level hiring at the biggest tech companies dropped 25% between 2023 and 2024, and it still hasn't bounced back. Software job postings are still down more than a third from pre-pandemic levels, and about 7% lower than they were just a year ago.
It's not just a "big tech" problem either. At one well-known Indian engineering institute, fewer than a quarter of a graduating class of 400 students had job offers just months before their course ended. Students there are calling it a "jobpocalypse." Tech layoffs crossed 150,000 in a single year not long ago, and even though the number has come down since, Q1 2026 alone saw close to 80,000 more tech workers lose their jobs.
Here's the part that hurts if you're early in your career: it's not spread evenly. Jobs for young software developers have dropped almost 20% from their late-2022 peak. Senior and specialist roles are actually growing at some companies — Google alone posted 62% more engineering openings in the first half of 2026 than a year earlier — but that growth sits at the top of the experience ladder, not at the entry point most of us are trying to get through.
So if you've sent 50, 80, 100+ applications and heard mostly silence — you're not the exception. You're the current normal.
⚡ What's Actually Causing This
Four things are happening at once, and it helps to name them instead of just feeling them.
1. AI is eating the "easy" tickets first. Company leaders aren't hiding it anymore. Microsoft's CEO has said AI now writes a real chunk of the code in some of their projects. Salesforce's CEO said his company hired zero new engineers in a recent year because AI tools closed that gap. The small, simple tasks that used to be a junior developer's way in — quick bug fixes, boilerplate features, basic integrations — are exactly what AI coding tools now handle well. That doesn't mean developers are useless, but it does remove a lot of the "starter" work companies used to hire freshers for.
2. Companies are still recovering from over-hiring in 2021-2022. A lot of today's layoffs trace back to companies that doubled their engineering teams during the cheap-money pandemic years and are now cutting that back. This has nothing to do with your skills. It's a hiring hangover that started years before you even applied.
3. Global conflicts are adding extra pressure on hiring budgets. With active wars and unrest going on in multiple regions right now, companies are dealing with higher energy costs, shakier supply chains, and more cautious investors. Reports through 2026 show business leaders openly saying this instability is a factor in tighter, slower hiring decisions — money is moving toward "safe" spends like cybersecurity and core AI infrastructure, and away from riskier hiring plans, especially at the entry level.
4. The bar for "entry-level" quietly moved higher. Companies don't just want a degree and a to-do-list app on your GitHub anymore. They want real, shipped work — actual projects, actual collaboration, actual production experience — squeezed into what used to be an entry-level ask. It's a classic trap: you need production experience to get hired, and you need to get hired to gain production experience.
None of this means the field is dying. Developer roles are still expected to grow well into the next decade, and plenty of companies are hiring hard for the right profile. But "the right profile" has shifted, and nobody warns you about that shift until you're three months deep into rejections.
🚀 What Skills Are Actually in Demand Right Now
Going through current hiring data and job posts, the same pattern keeps showing up:
- Working with AI tools is no longer a bonus — it's expected. More than half of tech job posts now ask for AI/ML familiarity, and daily use of tools like GitHub Copilot, Cursor, Codex, or Claude Code is fast becoming a basic skill, not an impressive one.
- Depth over "I can do everything." The generalist pitch is losing ground to developers with real, provable depth in one lane — cloud, DevOps, ML, security, or a specific ecosystem.
- For WordPress specifically, the bar has moved well past "I can install a theme and turn on WooCommerce." Companies now want REST API and headless WordPress experience, React-based block development, clean OOP plugin architecture, solid Git habits, and comfort with the platform's built-in AI tooling. WordPress still runs over 40% of the web, so the demand is real — it's just concentrated on developers who've moved past template installs.
- Proof over polish. A strong GitHub history, published articles, or real shipped projects now carry more weight than a clean resume, since most hires still come through referrals and visible work, not cold applications.
⚖️ My Skills vs. What's Actually Demanded
Here's where I had to be honest with myself instead of just angry at the market.
What I bring: I've built and shipped 4 WordPress plugins from scratch, following pure OOP architecture, WordPress VIP coding standards, and proper sanitization/escaping at every layer. I've built enterprise-level websites and web apps using React and Next.js, including headless WordPress setups where the frontend is fully decoupled from the CMS. Performance and security aren't an afterthought for me — I bake them into the build from day one, whether that's caching strategy, query optimization, or basic hardening against common attack vectors. I also actively use AI tools like Codex, Claude, and GitHub Copilot as part of my real workflow — not just to autocomplete a line, but to help scaffold plugins, debug tricky WordPress hooks, and speed up full web app builds. On top of that, I keep a solid, active GitHub history and write technical articles regularly, so my work is documented and public, not sitting in private repos nobody sees.
Where the gap actually is: the problem wasn't that I lacked AI fluency — I use these tools daily and build with them. The real gap was in how I was positioning myself. I was applying into the same volume-heavy, entry-level pool as everyone else, instead of clearly showing recruiters that I already work the way the market now expects: AI-assisted, specialization-focused, with real production and architecture experience behind me. My resume wasn't telling that story loudly enough.
That gap isn't a character flaw. It's a positioning problem, and it's fixable — just not in the two months I had bills to pay in the meantime.
🛵 Why I Joined Uber
I didn't join Uber because I gave up on development. I joined because rent, food, and basic responsibilities don't pause for a job market correction, and two months of zero income while sending applications into a void just isn't sustainable for anyone.
Delivery work on my own bike gave me something a regular part-time job couldn't: income starting almost right away, with zero disruption to my ability to keep applying, interviewing, and writing during the hours I wasn't riding. It's physically harder than sitting at a desk, and yes, some pride had to be swallowed. But a bridge is a bridge, and I'd rather ride one than fall through the gap it's covering.
✅ The Onboarding Process Was Refreshingly Simple
Compared to the black-hole application process I'd just been through, signing up to deliver was almost jarring in how simple it was:
- No bond. No lock-in agreement of any kind.
- No fixed shift hours — I choose when I ride, and I choose when I stop.
- Document verification, a basic orientation, and I was live on the app within days, not weeks.
- Full control to log off any time — no penalty for taking a day off for an interview or a writing deadline. That flexibility is exactly why it works as a bridge income source. I run two shifts a day — morning and evening — and build the rest of my day around job hunting and content work.
💰 The Actual Numbers: What My Hero Xtreme 125 Earns Me
Let's do this properly, because vague "I make decent money" claims don't help anyone else weighing this option.
My setup: a Hero Xtreme 125, petrol at roughly ₹100/liter, riding two shifts a day — morning and evening — spending roughly ₹100 in fuel per shift (about ₹200/day, close to 2 liters). I also take one full day off every week to rest, both for me and the bike.
| Hours/day | Gross earning | Fuel cost | Net earning/day |
|---|---|---|---|
| 6 hrs (standard) | ₹700–800 | ~₹200 | ₹500–600 |
| 8 hrs (extended) | ₹1,000+ | ~₹200–250 | ₹750–800+ |
| 10 hrs (long day) | ~₹1,250–1,300 | ~₹280–300 | ~₹950–1,000 |
| 12 hrs (max stretch) | ~₹1,450–1,550 | ~₹320–350 | ~₹1,100–1,200 |
Notice the per-hour rate drops a bit as the hours climb — that's normal, since the best surge-pricing windows (early morning and evening rush) get used up first, and the extra hours are usually slower, lower-paying stretches.
Scaling this out with a weekly off day built in — roughly 26 riding days a month:
| Period | 6 hrs/day | 8 hrs/day | 10 hrs/day | 12 hrs/day |
|---|---|---|---|---|
| Monthly (net) | ~₹14,300 | ~₹20,000–20,800 | ~₹25,350 | ~₹29,900–31,200 |
| Yearly (net) | ~₹1,71,600 | ~₹2,40,000–2,49,600 | ~₹3,04,200 | ~₹3,58,800–3,74,400 |
A quick mileage sanity check: the Xtreme 125 is rated over 60 kmpl on paper, but real-world, stop-start delivery riding usually brings that down to somewhere between 40 and 50 kmpl. At ₹100/liter, that's roughly ₹2–2.5 per km, which lines up closely with the ₹200/day I actually spend across two shifts covering around 80–100 km total.
Worth being upfront about the parts this table doesn't show: chain lubrication, oil changes, tyre wear, and regular servicing add up over months of daily riding. So the real net is a little lower than the fuel-only numbers suggest once you spread maintenance across the year. I'd set aside roughly ₹500–800 a month for that on top of fuel.
It's not developer-salary money. It's not meant to be. It's meant to keep the lights on while I fix the real problem — landing the next role.
💭 A Few Things I'd Add From My Side
A few honest thoughts that didn't fit neatly into the sections above but felt worth saying:
- This isn't a failure story, it's a sequencing story. The job search didn't stop. It just stopped being the only thing paying the bills while it played out.
- Writing kept me sane. Publishing articles and working on side projects during this stretch gave me something the job hunt alone couldn't — a sense of moving forward on days when applications went nowhere.
- The stigma is the hardest part, not the job itself. Riding a delivery bike after years of writing production code messes with your head more than the physical work does. Worth saying plainly, because I suspect a lot of developers going through something similar feel that shame alone.
- Flexibility is underrated as a survival tool. A gig with no bond and no fixed hours meant I never had to choose between an interview and a shift. That mattered more than the pay itself.
- The market will turn — but not by waiting. Every report on this points the same way: demand for developers who can specialize and work fluently with AI tools is actually growing, even while generic entry-level postings shrink. The move isn't to give up on development. It's to close the gap between how you're positioned and what's currently getting hired.
🌱 Where This Leaves Me
I'm still applying. I'm still writing. I'm still building and the rest of my plugins work in whatever hours are left after two shifts on the bike. The Uber income isn't the destination — it's what's making sure I don't have to pause the actual goal while the market sorts itself out.
If you're in the same spot right now — sending applications into what feels like a void — you're not behind, and you're not broken. The data shows the market genuinely shifted under everyone's feet at the same time. The only real move is to keep adjusting how you show up, while keeping the lights on however you need to.
If this resonated with you, or you're going through something similar, I'd genuinely like to hear how you're handling it. Drop a comment.
Sources referenced: IEEE Spectrum, Rest of World, The Pragmatic Engineer's 2026 job market deep-dive, Final Round AI's 2026 software engineering market report, Second Talent's 2026 tech job market trends, SQ Magazine's layoff statistics roundup, Forbes' 2026 midyear geopolitical trends tracker, IDC's 2026 IT spending outlook, and current WordPress hiring guides from Wisemonk and Boundev.
Top comments (0)