Half-Year Big Tech Interview Journey: 10 Companies, 3 Offers, 4 Rejections, 3 Withdrawals

Background: Why I Decided to Leave

Let me start with my situation. Five years of Java backend experience, previously at a mid-size tech company — stable business but aging tech stack, and the promotion path was essentially blocked. By mid-2025 I was seriously considering a move. My goals were clear: join a FAANG-level company, get at least a 30% salary bump, and find real technical growth opportunities.

Honestly, I wrestled with the decision for a long time. I'd been at my previous company for over three years, had great colleagues, and was comfortable with the pace. But every time I saw salary comparisons from former coworkers who'd jumped ship, it stung. Add to that a revised performance review system that slashed year-end bonuses, and I finally made the call — I'm out.

I started preparing in September 2025, interviewed intensively from October through December, and finalized my decision in January 2026. The whole process lasted nearly half a year, cycling through anxiety, self-doubt, pleasant surprises, and agonizing decisions. Here's my complete interview retrospective.

Timeline Review

September 2025: Preparation phase. Work during the day, LeetCode + project review at night. I solved about 120 problems, focusing on arrays, linked lists, trees, and dynamic programming. I also reorganized three years of project experience, preparing five core project stories using the STAR method.

October 2025: Interview launch. Started with Amazon and Apple as warm-ups. Amazon rejected me at the second round, Apple at the first — a tough blow. But these two interviews taught me the FAANG interview rhythm, and I adjusted my strategy accordingly.

November 2025: Intensive interview month. Interviewed at Google, Microsoft, Meta, and Netflix. Got offers from Google and Meta, Microsoft rejected me at the third round, and Netflix gave an offer but the hours were brutal.

December 2025: Wrapping up. Interviewed at Stripe (rejected at second round) and Airbnb (withdrew), and withdrew from Salesforce due to slow process.

January 2026: Decision phase. Uber's process was halfway through, but I'd already committed to Google. Signed the offer in mid-January.

10 Companies: Results at a Glance

Here's the overview:

Amazon: Rejected at Round 2 — Couldn't solve the algorithm problem. It was Sliding Window Maximum; I only knew the brute force approach. The interviewer gave hints, but I ran out of time.

Google: Offer received (L5/Senior SWE) — Best overall interview experience. Interviewers were professional and patient, diving deep into projects without being adversarial.

Microsoft: Rejected at Round 3 — First two rounds went well. The third round was system design, and I wasn't prepared deeply enough.

Meta: Offer received (E5) — Efficient process: technical rounds + project round + HR round, all in one day.

Apple: Rejected at Round 1 — Weak on fundamentals. Java concurrency and JVM questions caught me off guard.

Netflix: Offer received but declined — Salary was high, but the culture of extreme hours was a dealbreaker. The interviewer even hinted at the intense pace.

Stripe: Rejected at Round 2 — Project experience mismatch. They wanted payments infrastructure experience; my background was in trading systems.

Airbnb: Withdrew — Already had offers from Google and Meta. Airbnb's compensation wasn't competitive enough to justify the time.

Salesforce: Withdrew — Process was too slow. Three weeks from application to first interview. Couldn't wait.

Uber: Withdrew — Already committed to Google. Terminated the process halfway through.

Detailed Interview Breakdown by Company

1. Amazon — First FAANG Interview, First Failure

Amazon was my earliest interview, and I wasn't fully prepared. The first round went okay — Java fundamentals, MySQL indexing, Redis caching strategies, plus Two Sum and Reverse Linked List for algorithms. The second round was where things fell apart — the algorithm was Sliding Window Maximum (LeetCode #239). I only knew the O(nk) brute force approach. The interviewer hinted at the monotonic deque approach, but I couldn't figure it out on the spot. Ran out of time. The project deep-dive wasn't great either — I fumbled through a distributed transactions question.

Lesson: Practice algorithm problems by category, not just easy ones. Amazon's algorithm difficulty is medium-to-hard; easy problems are just appetizers.

2. Google — Best Interview Experience

Google's process: Round 1 (Technical) → Round 2 (Project Deep-Dive) → Round 3 (Cross-Functional) → HR Round. About two weeks total.

Round 1 covered Java concurrency (synchronized vs. ReentrantLock, thread pool parameters), Spring AOP internals, MySQL transaction isolation levels. Algorithms were 3Sum and Validate BST — both went smoothly. Round 2 focused on projects — the interviewer was very interested in my trading system, diving into distributed locks, idempotent message consumption, and sharding strategies. Round 3 was a cross-functional interview with architecture design questions — how to design a flash sale system. HR round covered career plans and salary expectations.

Final offer: L5 Senior SWE. Salary slightly above expectations. Extremely professional experience overall.

3. Microsoft — Fell at System Design

Microsoft's process: Round 1 (Technical) → Round 2 (Project) → Round 3 (Principal Engineer / System Design).

Rounds 1 and 2 went fine. Algorithms were Longest Increasing Subsequence and Course Schedule. Project round covered microservices architecture and distributed tracing. The problem was Round 3 — the interviewer asked me to "design a social media feed." I'd prepared purely technical architectures and lacked deep thinking about social product design. The follow-up on "pull vs. push model for timeline generation" — I gave a surface-level answer without deeply comparing the trade-offs.

Lesson: System design isn't just about technical solutions — you need to analyze business scenarios. Microsoft's principal-level interviews heavily weigh product thinking.

4. Meta — Most Efficient Process

Meta's interviews were done in one day: two technical rounds in the morning, project round + HR round in the afternoon. Very tight schedule, about 45 minutes per round.

Technical rounds covered Java fundamentals, Redis distributed locks, and Kafka message reliability. Algorithms were Coin Change and Merge Intervals. The project round focused on my transaction settlement system — the interviewer was interested in the sharding approach and asked about shard key selection and cross-shard query handling. HR round covered salary and start date.

Offer: E5. Compensation similar to Google, but slightly lower base with more equity.

5. Apple — Weak Fundamentals, Quick Exit

Apple rejected me at the first round, and I deserved it. The interviewer asked a barrage of Java fundamentals: HashMap internals, ConcurrentHashMap's lock mechanism, JVM garbage collection algorithms, the volatile keyword... I stumbled through most of them, giving vague answers. I did manage to solve the algorithm problems (Merge Intervals and Min Stack), but the fundamentals damage was too much.

Lesson: Big tech first rounds heavily weigh fundamentals. Don't neglect core knowledge review just because you've practiced algorithms. Java concurrency and JVM come up at virtually every company.

6. Netflix — Highest Pay, Worst Hours

Netflix's interview intensity was high — every round included both algorithm and system design. Algorithms were Edit Distance and LRU Cache; system design was "design a group-buying system." The interviewers were top-notch with deep follow-ups. They gave an offer about 20% above Google's, but the interviewer themselves hinted at the grueling hours — "The pace here is fast; you need to be mentally prepared."

I confirmed with a friend at Netflix — 60+ hour weeks are the norm. After weighing the options, I declined. Money matters, but health matters more.

7. Stripe — Project Experience Mismatch

Stripe's interviewer was very direct — they opened by saying their team builds payment infrastructure. My experience was mainly in trading and settlement systems, which was too far from what they needed. In the second round, they asked about payment processing fundamentals (idempotency, reconciliation, settlement workflows), and I couldn't answer most of them. I did solve the algorithm problem (Path Sum III), but the project mismatch was too significant.

Lesson: Research the target team's business domain before applying. Even great algorithm skills won't compensate for a project experience mismatch.

8-10. Airbnb / Salesforce / Uber — Voluntary Withdrawals

Airbnb — already had Google and Meta offers; their compensation wasn't competitive enough to justify the time. Salesforce — process was too slow; three weeks from application to first interview, and I was already in decision mode. Uber — already committed to Google; terminated the process halfway through.

About withdrawing from interviews — there's nothing wrong with it. Interviewing is a two-way street. Time and energy are limited; withdraw when it makes sense. But communicate clearly — tell the HR rep why, and never ghost.

Interview Pacing Strategy

This is one of my most important takeaways. Ten companies in parallel is unsustainable. My strategy:

1. Apply in batches. Start with 2-3 companies as warm-ups, learn the interview patterns, then apply to your top targets. Amazon's failure made me realize I was underprepared — I took two weeks to recalibrate before interviewing again.

2. Limit parallel interviews. No more than 3 companies in progress simultaneously. Leave at least 3-4 days between interviews for review and targeted preparation.

3. Don't interview your top choice first or last. First = potentially underprepared. Last = potentially burned out. I placed my top choice in the middle-to-late position, which worked best.

4. Cut losses early. If a company's process is too slow or the interview experience is poor, withdraw without hesitation. Don't waste time.

Mindset Management

Over six months, emotional volatility was the biggest challenge. I went through several phases:

Early: Overconfident. Five years of experience, 100+ LeetCode problems — I thought I'd be fine. Amazon and Apple's rejections were a rude awakening.

Middle: Self-doubt. Two consecutive failures had me questioning my abilities. I was anxious, couldn't sleep, and my practice efficiency dropped.

Turning point: Google's offer. Once I had an offer in hand, my mindset stabilized dramatically. Having a safety net made me perform better in subsequent interviews.

Late: Calm deliberation. With Meta and Netflix offers secured, I was completely relaxed. The question shifted from "can I get an offer?" to "which company fits me best?"

My advice: Get a safety-net offer first — it changes everything. Without one, every interview feels like a last stand, and the pressure hurts your performance.

Salary Negotiation Tips

Compensation comparison across three offers (annual total package, excluding sign-on):

Google L5: Base $185K + equity ~$120K/yr = ~$305K total

Meta E5: Base $175K + equity ~$110K/yr = ~$285K total

Netflix: Base $220K + equity ~$130K/yr = ~$350K total

Key negotiation principles:

1. Never name a number first. Let the recruiter go first, then negotiate from there. If you state your expectations first, you've given away your leverage.

2. Use competing offers as leverage. After getting Meta's offer, I used it to negotiate with Google — they increased the base by $10K from their initial offer.

3. Focus on total package, not just base salary. Some companies have lower base but more equity; others have higher base but smaller bonuses. Calculate the total, and factor in equity liquidity.

4. Don't forget the sign-on bonus. Big tech companies typically offer sign-on bonuses, and they're negotiable. I got an additional $15K sign-on from Google.

Final Choice: Why Google

Comparing all three offers, I chose Google for three reasons:

1. Technical growth. Google's engineering culture and infrastructure are industry-leading. The learning opportunities are unmatched. Netflix has strong tech too, but the pace leaves little time for growth and reflection.

2. Work-life balance. Google's hours are demanding but reasonable compared to Netflix's extreme culture. Meta's intensity is somewhere in between, but Google's brand carries more weight long-term.

3. Long-term trajectory. L5 at Google is a solid senior level with a clear promotion path. Meta's E5 is comparable, but Google's internal mobility and project diversity are superior.

FAQ

Q: How many rounds are typical for experienced hires?

A: Big tech usually does 3-5 rounds: 1-2 technical (including algorithms), 1 project/system design, 1 HR. Some companies add cross-functional or principal-level rounds.

Q: How long should I prepare before interviewing?

A: Depends on your foundation. I prepared for about 2 months. If your algorithm skills are weak, plan for 3-4 months. The core triad is algorithm practice + project review + fundamentals refresh — you need all three.

Q: How much weight do algorithm problems carry?

A: About 30-40%. Algorithms are a gatekeeper — if you can't solve them, you're out. But solving them doesn't guarantee a pass either — project experience and system design matter equally.

Q: How long before I can reapply after a rejection?

A: Typically 6-12 month cooldown periods. Amazon is 6 months, Google is 1 year. Whether you pass or fail, always do a thorough post-interview review for next time.

Q: How do I balance my current job with interview prep?

A: My approach: 2 hours of LeetCode on weekday evenings + half a day of project review on weekends. Schedule interviews during lunch breaks or after work to avoid raising suspicion. During intensive interview periods, consider using PTO for concentrated interviewing.

Q: Does withdrawing from an interview hurt my chances later?

A: Generally no, as long as you communicate in advance. When I withdrew from Airbnb and Salesforce, I explained my reasons honestly, and the recruiters were understanding. The worst thing you can do is ghost or cancel at the last minute.