r/DeveloperJobs • • Feb 20 '26

I Failed Uber’s System Design Interview Last Month. Here’s Every Question They Asked.

371 Upvotes

If you’re Googling: Uber system design interview, let me save you 3 hours: Every blog post says the same thing: Design Uber.

They show you a Rider App, a Driver App, and a matching service. Box, arrow, done.

I’m not going to do that. Because I couldn’t make it.

Last month I made it to the final round of Uber’s onsite loop for a Senior SDE role. My system design round was: Design a real-time surge pricing engine.

They wanted me to design the engine, the thing that ingests millions of GPS pings per second, calculates supply vs. demand across an entire city in real-time, and spits out a multiplier that changes every 30 seconds.

I thought I nailed it but I was wrong on my end.

Here’s exactly what happened, every question, every answer, and exactly where I think it fell apart.

Interview Setup

Uber’s onsite loop is 4–5 rounds, each 60 minutes, usually spread across two days. Here’s the breakdown:

Press enter or click to view image in full size

System design round is where Senior candidates are made or broken. You can ace every coding round and still get rejected here.

I used Excalidraw to diagram during the virtual onsite. I recommend having it open before you start.

Question: “Design Uber’s Surge Pricing System”

Here’s exactly how the interviewer framed it:

My first instinct was to start drawing boxes. I stopped myself.

Press enter or click to view image in full size

Step 1: Requirements (The 5 Minutes I Actually Got Right)

I asked clarification questions before touching the whiteboard. I think this is the move that separates L4 from L5.
What do you think?
Write in comments.

Functional Requirements I Confirmed:

  • The system must compute surge multipliers per geographic zone.

  • It must ingest real-time supply (driver GPS pings) and demand (ride requests).

  • Multipliers should reflect current conditions, not just historical averages.

  • The output feeds directly into the pricing service shown to riders.

Non-Functional Requirements I Proposed (and the interviewer nodded):

  • Latency: Multiplier must be recalculated within 60 seconds. (P99 < 5s for the pipeline).

  • Scale: Support 10M+ active users across 500+ cities globally.

  • Availability: 99.99% uptime — if surge fails, the fallback is 1.0x (no surge).

  • Accuracy vs. Speed: We optimize for speed. A slightly stale multiplier is better than no multiplier.

Step 2: “H3 Hexagonal Grid” Insight (My Secret Weapon)

This is the part where I pulled ahead. I had studied Uber’s H3 open-source library the night before.

I started saying like:

The interviewer looked impressed. (This was the last time I felt confident.)

Here’s the high-level data flow I drew:

[ Driver GPS Pings ] ──► [ H3 Hex Mapper ] ──► [ Supply Counter (per hex) ]
                                                        │
[ Ride Requests ]    ──► [ H3 Hex Mapper ] ──► [ Demand Counter (per hex) ]
                                                        │
                                                        ▼
                                              [ Surge Calculator ]
                                                        │
                                                        ▼
                                              [ Pricing Cache (Redis) ]
                                                        │
                                                        ▼
                                              [ Rider App: "2.1x Surge" ]

Key Components:

  1. H3 Hex Mapper: Converts raw lat/long into an H3 hex ID. Sub-millisecond operation.

  2. Supply/Demand Counters: Sliding window counters (last 5 minutes) stored in Redis, keyed by hex ID.

  3. Surge Calculator: A streaming job (Apache Flink) that runs every 30–60 seconds, reads both counters, and computes the multiplier.

  4. Pricing Cache: The output is written to a low-latency Redis cluster that the Pricing Service reads from.

Step 3: The Deep Dive (Where the Interview Gets Hard)

The interviewer didn’t let me stay at the high level. They pushed.

“How does the Surge Calculator actually compute the multiplier?”

I proposed a simple formula first:
surge_multiplier = max(1.0, demand_count / (supply_count * target_ratio))

Then I immediately said: “But this is the naive version.”

The real version layers in:

  • Neighbor hex blending: If hex A has 0 drivers but hex B (adjacent) has 10, we shouldn’t show 5x surge in A. We blend supply fromkRing(hex_id, 1), the 6 surrounding hexagons.

  • Historical baselines: A Friday night in Manhattan always has high demand. The model should distinguish “normal Friday” from “Taylor Swift concert Friday.”

  • External signals: Weather API data, event calendars, even traffic data from Uber’s own mapping service.

“What happens if the Flink job crashes mid-calculation?”

This was the failure scenario question. I thought I was ready.

My Answer:

  1. Stale Cache Fallback: Redis keys have a TTL of 120 seconds. If no new multiplier is written, the old one stays. Riders see a slightly stale surge (better than no surge or a crash).

  2. Dead Letter Queue: Failed Flink events go to a DLQ (Kafka topic). An alert fires. The on-call engineer investigates.

  3. Circuit Breaker: If the Surge Calculator is down for > 3 minutes, the Pricing Service defaults to 1.0 x no surge. This protects riders from being overcharged by a stale, artificially high multiplier.

The interviewer nodded. But then came the follow-up I wasn’t ready for:

“How do you handle surge pricing across city boundaries where hexagonal zones overlap different regulatory regions?”

I froze. I hadn’t thought about multi-region regulatory compliance i.e different cities have surge caps (NYC caps at 2.5x, some cities ban it entirely). My answer was vague: “We’d add a config per city.” The interviewer pushed: “But your Flink job is processing globally. How does it know which regulatory rules to apply per hex?” I stumbled through something about a lookup table, but I could feel the energy shift. That was the moment I lost it.

Step 4: The Diagram Walkthrough (Narrative Technique)

Instead of just pointing at boxes, I narrated a user journey through my diagram:

This narrative technique turns a static diagram into a living system in the interviewer’s mind.

The Behavioral Round (Where I Thought I Recovered)

After the system design stumble, I walked into the behavioral round rattled. The question:

I told the story of advocating for event-driven architecture over a polling-based system at my last company. I used the STAR-L method:

  • Situation: Our notification system was polling the database every 5 seconds, causing CPU spikes.

  • Task: I proposed migrating to a Kafka-based event stream.

  • Action: I built a proof-of-concept in 3 days, presented the latency data (polling: 5s avg, events: 200ms avg), and addressed concerns about Kafka operational complexity.

  • Result: The team adopted the event-driven approach. CPU usage dropped 60%.

  • Learning: I learned that data wins arguments, not opinions. Every technical disagreement should be fought with a prototype and a benchmark, not a slide deck.

I felt good about this one. But in hindsight, one strong behavioral round can’t save a wobbly system design.

The Rejection Email

Three days later:

Six months. That stung.

I asked my recruiter for feedback. She was kind enough to share: “Strong system design fundamentals, but the committee felt the candidate didn’t demonstrate sufficient depth in cross-region system complexity and edge case handling.”

Translation: I knew the happy path. I didn’t know the edge cases well enough.

What I’m Doing Differently (For Next Time)

I’m not done. I’m definitely going to apply again. Here’s my new playbook:

  1. Edge cases: I’m spending 50% of my system design prep on failure modes, regulatory constraints, and multi-region complexity. The happy path diagram gets you a Strong L4. The edge cases get you the L5.

  2. Read the Uber Engineering Blog cover to cover. Uber publishes their actual architecture decisions, H3, Ringpop, Schemaless. It’s free and if you’re interviewing at Uber and haven’t read their blog, you’re leaving points on the table. I read some of it. Next time, I’ll read all of it.

  3. Practice with follow-up pressure. Generic “Design Twitter” didn’t prepare me “…but what about regulatory zones?” kind of questions I need practice and that’s where someone pushes back. I’ve been doing mock interviews on Pramp and studying company-specific follow-up questions on PracHub and Glassdoor.

  4. Record myself. Narrating a diagram to your mirror is not the same as narrating it while someone challenges every arrow. I’m recording mock sessions on Excalidraw and watching myself stumble. It’s painful. It’s working.

Your Uber System Design Cheat Sheet (Learn From My Mistakes)

Press enter or click to view image in full size

Final Thoughts

I’d be lying if I said the rejection doesn’t still sting.

But here’s what I keep telling myself: I now know more about Uber’s system design than 95% of candidates who will interview there this year. I have the diagram. I have the failure modes. And now I have the edge case that cost me the offer.

Next time, I’ll be ready for the follow-up.

If you’re prepping for Uber, don’t just learn the architecture try preparing for the curveballs. Study their actual questions. And for the love of all things engineering, prepare for the question after the question.

Source: PracHub


r/DeveloperJobs • • Apr 18 '26 Heartwarming Bravo

I got Google Internship with this CV

Post image
350 Upvotes

r/DeveloperJobs • • Jun 06 '26 Regret

I introduced AI workflows at my startup, then got laid off a month later

323 Upvotes

I graduated this year (2026). I was working at a us-based startup, and we were a very small team with only 4 developers. I joined in February. I also had previous experience since I was working during my college years.

They hired me as a backend developer. My role was mainly writing backend endpoints and building caching services. Later, I also worked on the frontend using Golang and WebAssembly. All the other developers were much older than me, mostly in their 40s, and I was the youngest on the team. Most of them were using AI, but they weren't very familiar with some of the newer workflows around it.

While working there, I noticed the platform had strict rules for how endpoints had to be written. A lot of the work was repetitive and we had to manually follow the same patterns again and again for every endpoint. Because of that, I introduced the team to claude skills so we could avoid doing so much manual work. They really liked the idea and appreciated my work. They were already using claude by prompting it, but they weren't aware of claude skills.

After that, I felt pretty good about my work. We were able to move a bit faster while also maintaining consistency across the application.

In April, the founders and I had a discussion about how the skills worked. I explained them in detail and also showed them some other AI agents and workflows they could use. Later that day, they asked me to write skills for frontend design patterns, state management, database schemas, and caching services.

Because I had received positive feedback earlier, I didn't think much about it and went ahead with it.

I wrote skills for each service and also helped them create skills for other modules of the application. I documented how everything worked and how those skills should be used.

I felt this was good progress in my work. After they started using those skills regularly, it significantly improved their productivity. They had more time to focus on other parts of the application, and we were able to ship features faster.

Then, at the end of May, they decided to let me go. Their reasoning was that they could now manage backend development themselves with the help of Claude, and letting me go would also reduce costs. They did pay me an extra month of salary, but I'm no longer working there.

Right now, I don't have a job. I don't think I'll have any financial problems this month, but from next month onward, I'll need to find another role.

What would you do in my situation? Any suggestions?


r/DeveloperJobs • • Mar 03 '26 Bravo

How I’m Landing 4-5 Interviews Daily (The System)

Post image
290 Upvotes

Since my last post blew up, here is the exact "Volume & Velocity" strategy I’m using.

The Strategy: 100 Apps / Day

In this market, "quality over quantity" is a trap if it limits you to 5 apps a day. I treat it like a sales funnel:

  • Massive Volume: I submit 100+ applications daily.

  • Beyond LinkedIn: I use Remote Rocketship to find fresh listings before they’re saturated.

  • Instant Tailoring: I use my AI Chrome Extension to auto-generate resumes that hit 95+ ATS scores for every specific JD.

The Proof

I’ve attached a screenshot of my calendar/pipeline to this post. It’s not luck—it’s math.

DMs are open if you want to see my templates or the extension setup. Let's get everyone hired. 🚀


r/DeveloperJobs • • Mar 15 '26

Can't believe Linus Torvalds created Linux at 21 without Claude or Al

245 Upvotes

Can't believe Linus Torvalds created Linux at 21 without Claude or Al.

→ He didn't even have a co-founder.

→ No VC funding.

→ No office.

→ No team.

→ Just a personal project

He posted this announcement on Usenet in 1991:

"I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones."

34 years later, it runs 96% of the world's servers, all Android smartphones, the International Space Station, most of the cloud (AWS, GCP, Azure), every major stock exchange, and basically is the internet's backbone.

The most important software in history started as someone's side project.

Living legend.


r/DeveloperJobs • • Jan 24 '26

Just finished ~40 interviews in a month (Full Stack). The market is weird, but here’s what I actually got asked.

200 Upvotes

Just wrapped up a month-long sprint where I interviewed with around 40 companies. The market is definitely tough, but people are hiring if you can actually get past the resume screen.

I wanted to dump everything I learned while it's still fresh in my brain. Hopefully, this saves you guys some time.

The Application Spam I stopped trying to be selective. I just went for volume. Used Simplify Copilot to speed things up (auto-apply bots were trash for me, kept applying to irrelevant roles).

  • Resume Hack: I added some AI-related keywords to my resume. Even for generic full-stack roles, I swear this triggered the ATS or recruiter attention more often. Everyone wants to "pivot to AI" right now, so play the game.

The Tech Stack Trap One mistake I made early on: I used Python for frontend LeetCode questions because it's faster to write. Don't do this. Unless it's Google/Meta, interviewers got confused why a "Frontend" candidate was writing Python. I switched back to JS/TS and the vibes improved instantly.

  • The "Basics" that aren't basic: Closures, Event Loop, Promises (async/await), and this binding. If you can't explain these clearly, you fail.

  • Frameworks: It’s not enough to know how to use React/Vue. They asked how it works. E.g., "How does Angular's dependency injection actually function?" or "React vs Vue performance tradeoffs."

  • Practical Coding (No LeetCode):

    • Build a traffic light component (auto switches + manual override).

    • Fetch data -> Render Table -> Add Pagination/Search.

    • Implement debounce and throttle from scratch.

    • Build a nested Modal.

    • Lazy load a massive list (Virtual scroll).

System Design & Backend I didn't get asked to code a database from scratch, but lots of "How would you scale this?"

  • Concepts: JWT vs Sessions, Database Indexing, Rate Limiting, Graceful Shutdowns.

  • Design Prompts: The classics are still popular. URL Shortener, YouTube history, Rate Limiter, Real-time Chat.

  • My template: Clarify requirements -> Diagram (API+Data flow) -> Deep dive on DB/Caching -> Trade-offs. Always mention trade-offs.

The "Soft" Stuff Matters More Than I Thought I used to think code was king. But after talking to ~30 hiring managers, I realized the "Behavioral" round is where decisions are actually made.

For behavioral questions companies like to asked I was able to find them on Glassdoor / Blind, For actual technical interview questions I was able to find them on Prachub

  • If you are senior: Show humility.

  • If you are junior: Show hunger/potential.

  • Unblock yourself: The biggest green flag I felt I gave off was describing how I solve problems when I'm stuck without pinging my manager immediately.

You see people posting huge TC offers and it feels bad, but remember you only need one yes. I failed plenty of these interviews before landing offers.

Good luck out there.


r/DeveloperJobs • • Apr 08 '26

I don’t want to be a programmer anymore

194 Upvotes

So, let me start by saying this after 11 years: I’m a self-taught full-stack software developer in both Web2 and Web3. My journey started in 2011, just before I finished high school. That’s when I started learning how to write computer code. At first, I learned HTML, then I switched to Xcode and started learning how to build iOS games. I really sucked at it, but my game did work, although it was never published.

<?php echo "Hello, world!"; ?>

Then it came time for graphics, but I just couldn’t do it. So I switched back to HTML, stuck with it, and kept learning new languages. My favorite was PHP, which I worked with for many years, until I was told that PHP was a dying language. So I swung back to HTML, CSS, and JavaScript.

Fast forward, and now I know how to code in many languages, from Solidity for Web3, SQL, AWS, NodeJS, Angular, JQuery, ReactJS, React Native, to Python, and even Liquid for Shopify. But with all this knowledge, I still never broke into the industry. I wasn’t given a job because I didn’t have a college diploma. Just like that, my dream was dead.

Fast forward to AI: projects that would have taken me five months to complete now take me one to two hours, like building a pure HTML, CSS, and JavaScript secret messaging website. And while I was building my own applications online, AI made me a better and faster programmer. I was able to build 15 different applications.

But it came with a big reality check… the internet is actually dead. It’s almost impossible to get a good amount of organic users. I ran some Google ads, and users came in, but they left just as fast as the ads were paused. The big internet companies like Meta and Google have gobbled up the entire internet, and you can’t really make money building applications unless you’re able to commit an ungodly amount of money.

And at this point in my life, I signed off and decided to leave programming to the robots and AIs of the world. I’ll miss it. Programming, to me, was a fun space where I just loved seeing how people used the tools that I built. And now, moving on feels bittersweet.

I hope to relive this life and get it right the second time.

Well, that was just my rant, if you can call it that.

Signed off.

<?php echo "Bye, programming world!"; ?>


r/DeveloperJobs • • Feb 27 '26

2 weeks into job search (IT/Backend) – 4-5 interviews/day. Happy to share what's working.

Post image
175 Upvotes

Hey r/DeveloperJobs, —happy to share what's working for me after 2 weeks of active applying in IT/Backend. Getting 4-5 interviews daily now.

Main takeaway: Stop relying only on LinkedIn. Platform strategy matters.

No matter of your YOE.

DMs open if you want to swap tips, connect, or just vent about the process. We got this! 🚀


r/DeveloperJobs • • Jan 07 '26

Got an Internship

Post image
167 Upvotes

After giving multiple interviews and uncountable applications, At last I cracked one.


r/DeveloperJobs • • Dec 13 '25

As a 20-year-old, this feels like the wildest time to be alive in tech.

160 Upvotes

AI is evolving faster than my semester deadlines. People are building real startups from dorm rooms. Skills are starting to matter more than degrees.

It’s exciting… and honestly a bit overwhelming.

On one hand, there’s never been more opportunity. On the other, it feels like if you stop learning for a few months, you’re already behind.

Anyone else in their early 20s feeling this mix of hype, pressure, and confusion? How are you navigating it — focusing deep on one skill, or exploring everything while it’s all moving so fast?

Would love to hear different perspectives.


r/DeveloperJobs • • Mar 05 '26

Hiring Fullstack role(next js , node js)

132 Upvotes

Hey everyone, We are hiring Fullstack dev(3) , Please respond if you know above tech and upvote and comment "interested".

Don't dm , comment here I will respond to everyone. Upvote so that it reach to everyone. I will edit this post if we get our 3 dev.

Edit: Thanks everyone. Hring is closed we interviewed 15 candidate and 2 get selected but 1 dev is still required but will reach out after somedays.


r/DeveloperJobs • • Sep 04 '26

I hate my job since we work with AI

127 Upvotes

The title says it. I used to like my job, I love programming and being in that chaos for minutes/hours to find that your problem was just because of a typo. I love creating something from nothing and resolving problems. It's been a few months since we integrated Claude into our job and it does everything. I simply prompt and wait. I feel like I’m just pushing a button and waiting for the result. I understand why we are working like that, because the industry is gaining on us and it's better to be on the boat than in the raft, but I hate it. There is no satisfaction in doing feature and making it work after hours of hard work and thinking. I don’t understand how people love vibe coding but it ain’t for me.

For people in the same situation as I am, how are you living it?


r/DeveloperJobs • • Feb 13 '26

Is Software Development Still a Good Career in the Age of AI? What Should We Be Focusing On Now?

119 Upvotes

Hey everyone,

I’m currently working as a software engineer and lately I’ve been thinking a lot about the future of our industry.

With tools like GPT, Copilot, and other AI coding assistants becoming insanely good, it feels like more and more code is being generated by AI. Boilerplate, CRUD, even decent system design drafts — AI handles a lot of it already.

This makes me wonder:

What will the interview process look like in 3–5 years?

Will companies still focus heavily on DSA?

Or will interviews shift more toward system design, architecture, and problem understanding?

If AI can write optimized code, what are companies really evaluating?

Is there still a strong future in software development?

Or will the number of developers needed reduce significantly?

Will dev roles become more “AI supervisors” instead of builders?

What fields make the most sense to move into now?

AI/ML?

Distributed systems?

Security?

DevOps/Infra?

Product engineering?

Something else?

Is grinding DSA still worth it?

Or should we be focusing more on fundamentals, design, domain expertise, and AI tooling?

I’m not asking from a fear perspective, but from a strategic one. If someone is early in their career today (or even mid-level), what skills would actually future-proof them?

Would love to hear thoughts from:

Senior engineers

Hiring managers

Founders

People already using AI heavily in production workflows

Trying to understand whether we’re at:

A normal tech evolution phase

Or a genuine structural shift in how software engineering works

Thanks!


r/DeveloperJobs • • Jun 01 '26

Finallyyyyy Placed !!!!! Ladies and Gentlemen, after a long struggle I’ve finally made my switch

Post image
116 Upvotes

Hey Hi guys, I have recently got an offer from Marriott Tech Accelerator and it was an intense struggle to finally switch from my first company(TCS) and move into my first product based company and can’t wait to leave TCS P.S - Hope you guys make your moves and good luck with them.

My prep-

Just ate co-pilot at work to understand everything abt our projects, I work in a maintenance team but it didn’t stop me to go out of my way to know the product end to end and that gave me confidence. I discussed with my colleagues to understand how things are developed and handled real time infact knowing these things helped me alot in the interview. So don’t limit yourself and keep asking the question why.

Then came DSA - I started my prep a long back and I made sure I understood the concept than went after quick solutions and easy- low medium questions are more than enough to get into most startup’s unless it’s FAANG you’re eying for.

Finally java - read everything there is to prep for an interview and then made chat gpt take interviews, I mean multiple typed in my answers learned where I was wrong and polished my basics basics


r/DeveloperJobs • • 16d ago

Urgently Looking for Work

113 Upvotes

Hey everyone,

I'm 40 years old and have been developing software for 20 years. Honestly, over the past three months, I've gotten exhausted from sending out resumes, applying for freelance gigs, trying platforms like Outlier, and pretty much everything else I can think of, without landing a single job. The tech job market is brutal right now.

I'm in a really difficult situation. I have a daughter with a disability, and her health insurance coverage has been suspended due to outstanding payments. The total debt is around 1.8 million Argentine pesos, but if I can raise about 950,000 pesos (roughly $650 USD), I can get the coverage reinstated.

So I'm offering my services for pretty much any software development work you might need. I can build websites, develop web applications, desktop software, mobile apps, train AI models, handle deployments, work with databases, build integrations, and much more. I have a broad range of experience, and I'm willing to take on whatever kind of technical work I can help with.

I'm not looking for handouts. I'm looking for an opportunity to work, deliver results, and earn the money I urgently need to get my daughter's health insurance back.

If you have a project, need a hand with something technical, or know someone who does, I'd be incredibly grateful if you reached out.

Thanks for taking the time to read this.

Much love, everyone! ❤️


r/DeveloperJobs • • Sep 15 '26

Is the tech job market really this bad right now?

112 Upvotes

I’m in Europe and currently looking for new opportunities, and I’m genuinely curious if others are seeing the same thing.

Not sure if it’s just September and things are only starting to pick up again, if there’s something wrong with my CV/positioning, or if the job market has simply been fucked by agentic AI and the current state of tech hiring.

A year ago, I remember having 3-4 interviews in a single week without too much trouble.

Right now, I’m struggling to get even one.

I’m a senior full-stack developer with 8+ years of experience, mostly around Angular/TypeScript, Java/Spring, Python and Node.js, so I wouldn’t expect the difference to be this dramatic.

For other developers looking for work in Europe or anywhere else right now: are you seeing the same thing?

Is September just slow to get moving, or has the market genuinely changed that much in a year?


r/DeveloperJobs • • Feb 23 '26

[HIRING]💰 Paying $350/ week to Chat & Send Emails (5 Hrs/Day) – No Experience Needed

108 Upvotes

Hey everyone 👋

I’m currently hiring multiple people for simple remote work.

💼 What You’ll Do:

• Reply to chats

• Send basic emails

• Follow simple scripts (provided)

• No calling, no selling, no experience required

⏰ Time Commitment:

• 5 hours per day

• Fully remote

• Flexible schedule

💰 Pay:

• $350 per Week

• Paid consistently

• Long-term work available for good performers

✅ Requirements:

• Based in United States

• Basic English

• Internet connection

• Ability to follow instructions

• Must be reliable

🚀 How to Apply (IMPORTANT):

1️⃣ Upvote this post

2️⃣ Comment if you are serious (No time Wasters)


r/DeveloperJobs • • Dec 18 '25

Please review and hire me

Post image
105 Upvotes

r/DeveloperJobs • • Jan 04 '26

I am not getting jobs or internships . What do I change ??

Post image
101 Upvotes

r/DeveloperJobs • • Sep 30 '26

Has anyone else noticed how different the tech job market feels lately?

100 Upvotes

I’ve been having a few conversations with developers recently, and it got me thinking about how much the job market seems to have changed.

I remember a time when finding a new developer role felt relatively straightforward. Now I keep hearing about people sending out dozens of applications, waiting weeks for replies, or going through several interview rounds just to hear nothing back.

I’m curious because I don’t want to judge the whole market based only on what I see online.

For those currently looking for work, what has your experience actually been like lately?

Are you getting interviews, or has it been mostly silence?


r/DeveloperJobs • • Mar 02 '26

Crossed 1000+ Application without an Job.

Post image
85 Upvotes

Quick background: I had a stable job earning 1+ LPM, but I didn’t enjoy the work. I decided to transition into software development because it’s something I genuinely want to build a career in.

Now I’m honestly frustrated. I refuse to believe I’m so bad that no one wants to hire me, or that there’s always someone better for every single role. I’ve applied to jobs ranging from 3 LPA to 20 LPA, and still no offer.

So far:

  • Got into 3 interview pipelines

  • Pipeline 1: Rejected in Round 1

  • Pipeline 2: Cleared until Round 3, then HR ghosted me

  • Pipeline 3: Cleared 3 rounds, but the compensation was too low and negotiations broke down

It’s been mentally exhausting. I feel sad and demotivated at times, but I’m not quitting.

In fact, I’m more determined than ever. I’m making this post as a commitment to myself:

Within the next 2 years, I will be working at a FAANG-level company.

Save this post. Hold me accountable.


r/DeveloperJobs • • Jan 29 '26

I interviewed with ~40 companies last month — how I prepared for Full Stack / Frontend interviews

82 Upvotes

Following up on my previous post. Over the past month or so, I interviewed with around 40 companies, mostly for Full Stack / Frontend roles (not pure backend). A lot of people asked how I prepared and how I get interviews, so I wanted to share a little bit more about the journey.

How I got so many interviews

Honestly, nothing fancy: Apply a lot! literally every position I could find in the states.

I used Simplify Copilot to speed up applications. I tried fully automated bots before, but the job matching quality was awful, so I went back to manually filtering roles and applying efficiently.

My tech stack is relatively broad, so I fit a wide range of roles, which helped. If you have referrals, use them. but I personally got decent results from cold applying + in-network reach-outs.

One thing that helped: add recruiters from companies before you need something. Don’t wait until you’re desperate to message them. By then, it’s usually too late.

Also, companies with super long and annoying application flows had the lowest interview response rates in my experience. I skipped those and focused on fast applications instead.

Resume notes

I added some AI-related keywords even if the role wasn’t AI-heavy. Almost every company is moving in that direction, and ATS systems clearly favor those terms.

My recent work experience takes up most of the resume. Older roles are summarized briefly.
If you’re applying to bigger companies, make sure your timeline is very clear — gaps will be questioned.

Keep tech stacks simple. If it’s in the JD, make sure it appears somewhere on your resume. Details can be reviewed right before the interview.

Frontend interview topics I saw most often

HTML / CSS

  • Semantic HTML

  • Responsive layouts

  • Common selectors

  • Basic SEO concepts

  • Browser storage

JavaScript

  • Scope, closures, prototype chain

  • this binding

  • Promises / async–await

  • Event loop

  • DOM manipulation

  • Handwriting JS utilities (debounce, throttle, etc.)

Frameworks (React / Vue / Angular)

  • Differences and trade-offs

  • Performance optimization

  • Lifecycle, routing, component design

  • Example questions:

    • React vs Vue?

    • How to optimize a large React app?

    • How does Vue’s reactivity work?

    • Why Angular fits large projects?

Networking

  • HTTP vs HTTPS

  • Status codes & methods

  • Caching (strong vs negotiated)

  • CORS & browser security

  • Fetch vs Axios

  • Request retries, cancellation, timeouts

  • CSRF / XSS basics

Practical exercises (very important)
Almost every company had hands-on tasks,

  • Build a modal (with nesting)

  • Paginated table from an API

  • Large list optimization

  • Debounce / throttle in React

  • Countdown timer with pause/reset

  • Multi-step form

  • Lazy loading

  • Simple login form with validation

Backend (for Full Stack roles)

Mostly concepts, not heavy coding:

  • Auth (JWT, OAuth, session-based)

  • RESTful APIs

  • Caching issues (penetration, avalanche, breakdown)

  • Transactions & ACID

  • Indexes

  • Redis data structures

  • Consistent hashing

Framework questions depended on stack (Go / Python / Node), usually about routing, middleware, performance, and lifecycle.

Algorithms

I’m not a hardcore LeetCode grinder. My approach:

  • Get interviews first

  • Then prepare company-specific questions from past interviewer from PracHub

If your algo foundation is weak or time is limited, 200–300 problems covering common patterns is enough.

One big mistake I made early:
👉 Use the same language as the role.
Writing Python for frontend interviews hurt me more than I expected. Unless you’re interviewing at Google/Meta, language bias is real.

System design

Very common questions:

  • URL shortener

  • Rate limiter

  • News feed

  • Chat app

  • Message queue

  • File storage

  • Autocomplete

General approach:

  • Clarify requirements

  • Estimate scale

  • Break down components

  • Explain trade-offs

  • Talk about caching, availability, and scaling

Behavioral interviews (underrated)

I used to think tech was everything. After talking to 30+ hiring managers, I changed my mind.

When technical skill is similar across candidates, communication, judgment, and attitude decide.

Some tips that helped me:

  • Use “we” more than “I”

  • Don’t oversell leadership

  • Answer concisely — don’t ramble

  • Listen carefully and respond to what they actually care about

Offer & mindset

You only need one offer.

Don’t measure yourself by other people’s posts or compensation numbers. A good job is one that fits your life stage, visa situation, mental health, and priorities.

After each interview, practice emotional detachment:

  • Finish it

  • Write notes

  • Move on

Obsessing doesn’t help. Confidence comes from momentum, not perfection.

One last note: I’ve seen verbal offers withdrawn and roles canceled. Until everything is signed and cleared, don’t relax too early. If that happens, it probably saved you from a worse situation long-term.

Good luck to everyone out there.
Hope one morning you open your inbox and see that “Congrats” email.


r/DeveloperJobs • • Feb 16 '26

Hiring Junior Devs (Part-Time) – Work with US Clients on Automation Projects

80 Upvotes

Hey folks,
I’m currently working with a few US clients who are looking to automate parts of their businesses. I already have a small team (5–6 devs), but we’re getting more work than we can handle, so I’m looking to add a few junior developers.

  • Part-time role (around 3–5 hours/day)

  • You’ll be guided properly by senior devs

  • Real client projects (automation, integrations, etc.)

  • Scope to move to full-time if your work is good

If you’re interested, comment “Portfolio sent” and send your portfolio. I’ll review personally and DM you if it’s a fit.

Next steps are simple:
Short interview → then we discuss payout → start working.

This is a bit urgent since new projects are coming in, so I’ll be reviewing quickly.

Thanks!

EDIT : Share your portfolio or GitHub in the comments — I’ll review and reply. My team will also review from their accounts, so please comment and avoid DMs. Please upvote for better engagement.


r/DeveloperJobs • • Feb 19 '26 Bravo

I applied to 1000 jobs in 48 hours

78 Upvotes

Hello, yes like the title says, I was tired of applying to jobs and most of the auto-apply services are paid and its a shit show. so I took matter into my own hands. I present ApplyPilot fully automated 6 stage pipeline to discover jobs, filter, tailor resume and apply.

within 48 hours I have 7 interviews scheduled and many pending next step. I never expected this to be that good so I am sharing it with everyone.


r/DeveloperJobs • • Jun 26 '26

AI was supposed to kill engineering jobs. The numbers say the opposite.

76 Upvotes

Big tech cut hiring 25% since 2019.

Engineering hiring only dropped 11%.

Engineers are now 55% of all new hires, up from 46% in 2019.

Startups hired MORE engineers in 2025 than 2019.

If AI was really replacing engineers, this is where it should show up first. It's not happening.

The twist: almost none of this is going to new grads. It's all senior + AI-native engineers. The bar just got higher, not lower.

Anyone else noticing this? Easier or harder to get interviews right now vs last year?