I keep a spreadsheet. It has 47 rows. Each one represents a company that said no to me — or worse, never said anything at all.
Row 1 is Google. Row 12 is Spotify. Row 23 is a startup I've never heard of again because they probably shut down six months later. Row 47 is a mid-stage fintech company in New York that sent me a rejection email so generic it might as well have been auto-generated. (It probably was.)
Row 48 is Figma. And row 48 is where the story changes.
The Beginning of the Spiral
Let me rewind. In January 2024, I was a senior frontend engineer at a Series C edtech company in Seattle. Life was good — until a Monday morning all-hands where the CEO announced a 40% reduction in force. My team of 8 became a team of 3, and I wasn't one of the 3.
I wasn't panicked at first. I had five years of experience, mostly in React and TypeScript, with some full-stack Node work. I'd built a real-time collaborative document editor from scratch. I'd led a team. I figured it would take a month, maybe two.
It took seven months.
The First Wave (Rejections 1-15)
The first 15 rejections were humbling but manageable. Google rejected me after the second phone screen — I choked on a dynamic programming problem I'd literally solved in practice the week before. Amazon made it to the onsite but I bombed two of the four LP rounds. I kept saying "we" when they wanted to hear "I."
Stripe sent me a coding challenge that I actually felt good about, then ghosted me for three weeks before sending a one-liner rejection. Shopify rejected me after a take-home project that took me 12 hours to complete. Twelve hours of my life for a templated "we've decided to move forward with other candidates."
At this point, I was still optimistic. "It's a numbers game," everyone said. "Just keep applying."
The Middle Desert (Rejections 16-35)
This is where it got dark.
By April, I'd burned through most of the big names and was applying to mid-stage startups, smaller companies, and roles that were honestly a step down from what I'd been doing. I was getting more interviews, but the rejections hit harder because these were supposed to be my safety nets.
Rejection 19 was a company called Lattice. The hiring manager literally told me I was their top candidate, then emailed me two days later saying they'd put the role on hold. Rejection 24 was a startup where I made it to the final round — a "culture fit" conversation with the CEO — and got rejected because (his words) "we're looking for someone earlier in their career." I was 29.
I started doubting everything. Was my resume bad? Was I bad? Was I one of those engineers who can build things but can't pass interviews? The imposter syndrome was suffocating.
My wife started tiptoeing around the topic. My parents kept calling to ask if I'd "heard anything." My savings account was shrinking in a way that made me check my banking app at 2 AM.
The Turning Point (Rejections 36-42)
Around rejection 36, I had a long phone call with my college roommate, Dev. He'd gone through a similar spiral the year before and had eventually landed at Notion. I asked him what changed.
His answer surprised me. "I stopped trying to be perfect in interviews and started trying to be present."
He explained that he'd been so focused on memorizing answers and rehearsing stories that he'd lost the ability to actually think during interviews. He was performing, not problem-solving. And interviewers could tell.
Dev also mentioned he'd started using an AI interview tool called AceRound AI during his practice sessions and even during some actual interviews. "It's like having a really smart friend whispering in your ear," he said. "Not giving you answers, but keeping you on track when your brain starts to panic."
I was desperate enough to try anything.
The Shift (Rejections 43-47)
I changed three things simultaneously, so I can't tell you which one mattered most. Probably all of them.
First, I stopped over-preparing. Instead of spending 6 hours before each interview doing LeetCode problems I'd already solved, I spent 1 hour reading the company's engineering blog and thinking about how I'd contribute to their specific challenges.
Second, I started using AceRound AI in my practice sessions. The real-time feedback was genuinely different from anything I'd tried before. During a practice behavioral question about conflict resolution, it nudged me to include the specific outcome and metric impact — things I always forgot when I was nervous. During technical problems, it helped me stay structured when I felt myself starting to spiral.
Third, I started being honest in interviews. When I didn't know something, I said "I'm not sure about the specifics, but here's how I'd approach figuring it out." When I was nervous, I said "This is a great question — let me take a second to think." Authenticity, it turns out, is its own kind of competence.
Rejections 43 through 47 still stung. But they stung differently. I could feel myself getting better. The interviews were going deeper. I was getting to final rounds more often. Feedback shifted from "not enough depth" to "really strong but we went with an internal candidate."
Row 48: Figma
The Figma interview loop was five rounds over two days. System design, two coding rounds, a behavioral, and a team collaboration exercise.
In the system design round, I was asked to design a real-time cursor tracking system for a collaborative design tool. For the first time in months, I felt genuinely excited by a problem instead of terrified by it. I took my time, laid out the architecture, discussed WebSocket vs. SSE trade-offs, talked about conflict resolution strategies. The interviewer and I actually collaborated on the problem, which is how system design rounds are supposed to feel.
The coding rounds went well — not perfectly, but well. I got stuck on an optimization in the second one and said so. The interviewer gave me a hint, I ran with it, and we got to a working solution with three minutes to spare.
The behavioral round was where I think I actually won the job. They asked about a time I'd failed. I talked about the job search. Not in a self-pitying way, but honestly — what I'd learned about myself, how I'd changed my approach, what the experience taught me about resilience. The interviewer later told me (after I got the offer) that my answer was one of the most genuine she'd heard.
What 47 Rejections Taught Me
I'm not going to pretend it was all a beautiful journey of self-discovery. It sucked. There were days I didn't get out of bed until noon. There were weeks where I applied to nothing because the thought of another rejection made me physically nauseous.
But here's what I know now that I didn't know at rejection number 1:
The process is broken, not you. Technical interviewing is a deeply flawed system that measures your ability to perform under artificial pressure, not your ability to do the job. Understanding this doesn't make rejection less painful, but it does make it less personal.
Preparation has diminishing returns. After a certain point, doing more LeetCode problems is just anxiety management disguised as productivity. The real leverage is in how you perform during the interview itself — your communication, your composure, your ability to think out loud under pressure.
Tools matter. I resisted this idea for a long time because it felt like "cheating." But using something like AceRound AI isn't cheating any more than using a calculator on a math test is cheating. It's using available resources intelligently. In my experience, it was the difference between panicking through a question and approaching it methodically.
Rejection is data, not a verdict. Each of those 47 rejections taught me something. Some taught me to study specific topics. Others taught me to communicate differently. A few taught me that the company wasn't right for me anyway (looking at you, startup #23).
It ends. This is the most important one. When you're at rejection 30 and you've been searching for five months and your savings are running low, it feels like it will never end. It does. I promise.
The Spreadsheet Now
I still have the spreadsheet. I added a column after I got the Figma offer: "Lesson Learned." Going back and filling in that column for all 47 rows was oddly therapeutic. Some rows got real insights. Others just got "their loss."
I've been at Figma for four months now. I love the work, I love the team, and I love that the 47 rejections led me here specifically. I wouldn't trade this role for an offer from any of the companies that rejected me.
Well, maybe Stripe. I'm still a little salty about the ghosting.
If you're in the middle of the grind right now, I see you. It's brutal and lonely and it messes with your head. One thing that genuinely helped me was AceRound AI — having real-time support during interviews took the edge off the panic and let me actually show what I could do. Whatever tools or strategies you use, just keep going. Row 48 is out there.
Top comments (0)