From 100 Rejections to Meta – My Job Hunt Transformation with Jobbe.io
How I Went from 💯 Rejections to a Job at Meta
(Thanks to Jobbe.io) 🚀
I still remember the exact moment I hit 100 rejections ❌. It was a Tuesday evening in late November. I was sitting at my worn‑out IKEA desk, the one I’d assembled two years earlier when I first decided to “break into tech.” Outside my window the city was already dark 🌃, but inside the only light came from my monitor. On the screen, yet another email from a talent acquisition team. I didn’t even need to open it. The subject line alone said everything: “Update on your application.” We all know what that means. I clicked it anyway, scanning the same sterile paragraphs I’d read so many times before. “We’ve decided to move forward with other candidates.” I added it to my Rejection folder 📁—yes, I kept a folder—and the counter hit 100. One hundred. Not a typo.
I wish I could say that moment was rock bottom, but in truth I’d been spiralling for months. I had a solid GitHub profile, a handful of side projects that people seemed to like, and what I thought was a decent CV. I had completed a respected coding bootcamp and even done a short internship at a local startup. By all conventional measures, I should have been employable. Yet I was burning hours every day scrolling LinkedIn, Indeed, Glassdoor, AngelList, and a dozen other job boards—and getting absolutely nowhere 🌀. I had been ghosted after technical screens, rejected after take‑home assignments, and, far too many times, rejected before anyone even looked at my code. I was exhausted, demoralised, and secretly beginning to wonder if I’d made a catastrophic career mistake.
Then a friend told me about Jobbe.io 🤝. I remember the conversation clearly. We were grabbing a coffee ☕, and I was venting about how every job board felt like the same black hole. He listened quietly, then pulled out his phone and showed me a site I hadn’t seen before. It was clean. No ads. No “promoted” listings. No recruiter spam. Just a straightforward feed of tech jobs with filters that actually made sense for developers: by programming language, framework, role, location, and experience level. “I’ve been using this for a few weeks,” he said. “It’s not magic, but it’s the first place I go now.” I nodded, half‑sceptical. But when I got home that night, I opened my laptop 💻 and typed in the URL.
That small action was the beginning of everything 🌅. Over the next two months, I completely overhauled my job search. I moved from a scattershot, desperate approach to a disciplined, strategic one—and the centrepiece of that transformation was Jobbe.io. It didn’t write my code for me. It didn’t pass the interviews on my behalf. But it did something arguably more important: it gave me signal in a sea of noise 📡. And out of that signal came an offer I still sometimes have trouble believing: a Product Software Engineer role at Meta 🏢.
This is the full story of how I got there. Not the sanitised LinkedIn version, but the real, messy, frustrating, ultimately hopeful version. I’m going to walk you through the four specific changes that made the difference—each one practical, repeatable, and deeply connected to how I used Jobbe.io. If you’re a developer buried in rejections, I hope my experience gives you not just inspiration, but a concrete playbook you can start using today 📘.
💥 The breaking point nobody talks about
Before I get into the four things, I need to paint a picture of what “100 rejections” actually felt like. Because it wasn’t just a number. It was a slow erosion of confidence that affected everything.
When I started applying, I genuinely believed my profile was competitive. I had a strong foundation in JavaScript, React, and TypeScript. I had contributed to open source, built a full‑stack e‑commerce app 🛒, and even had a little experience with cloud deployment. I’d read all the career advice articles: “Tailor your resume,” “Network on LinkedIn,” “Write cover letters.” I did all of it. But I was also applying through the same channels everyone else uses: LinkedIn, Indeed, company career pages I found via random Google searches, and the occasional recruiter message that led nowhere. The volume of applicants was enormous, and I was just another needle in a very crowded haystack 📍.
Each rejection stung, but the cumulative effect was worse. I started to internalise the failure. Maybe I wasn’t good enough. Maybe my projects weren’t impressive. Maybe the bootcamp had taught me just enough to be dangerous but not enough to be hireable. I stopped telling friends I was job hunting because I was tired of the pitying looks. I would look at my Rejection folder—obsessively counting—and feel a heavy, sinking dread ⬇️. 40 rejections became 60. 60 became 80. Then 100. I wasn’t angry anymore. I was numb 😶.
But here’s the thing about hitting a breaking point: it forces you to ask hard questions. And the hardest one I finally asked was: Is the problem really me, or is the problem the system I’m using to find jobs? That question changed everything. Because the answer, I began to suspect, was that it was both. I could improve my skills, sure. But the way I was searching for jobs was fundamentally broken. I was treating the job hunt like a lottery 🎟️ instead of a targeted, strategic campaign. And that’s exactly where Jobbe.io came in.
🔎 Discovering Jobbe.io: A tool that understood developers
The first time I loaded Jobbe.io, I was struck by how minimal it was. No infinite scroll filled with irrelevant
“Senior Java Architect” roles. No pop‑ups asking me to upgrade to premium. No cluttered sidebars with “Recommended for you”
based on some opaque algorithm. Instead, I saw a simple search bar and a grid of filter options:
Programming language, framework, role, experience level, location, remote type.
I immediately selected React ⚛️, TypeScript 💙, Software Engineer,
Mid‑level, Remote (EU) 🇪🇺, and hit search.
What came back was a revelation ✨. Every single job on the page was relevant. Not “close enough.” Each posting actually aligned with the stack I’d spent two years mastering. For the first time in months, I wasn’t scrolling through 50 jobs to find three that might fit. I had a curated feed of 15 or 20 high‑quality roles, many of which I’d never seen on any other platform.
I later learned that Jobbe.io aggregates listings directly from company career pages and other reliable sources, then applies its own curation to filter out non‑tech or low‑quality roles. It’s not just another scraper. It’s a purpose‑built job board for software engineers, data scientists, and product people. And that focus makes all the difference.
Once I had that clean, relevant feed, I realised I could finally do what I had been incapable of doing before: be strategic 🎯. And that’s when I started implementing the four changes that ultimately led me to Meta.
🔧 Change #1: I stopped scrolling and started filtering like a developer
😫 The old way (broken): Every morning, I’d open LinkedIn, search “software engineer,” and scroll endlessly. The results were a mess. Job titles were inconsistent. A “Frontend Developer” role at one company might be called “UI Engineer” at another. Some postings were months old. Some were clearly agency reposts that had nothing to do with actual hiring. I’d waste two to three hours a day just trying to find 3–4 jobs that I could plausibly apply to. By the time I found them, I was mentally drained. The application itself became an afterthought—a quick upload of the same generic resume I’d sent to a hundred other companies.
🚀 The new way (using Jobbe.io): I approached the job search like a database query. I defined my criteria precisely and let the tool do the filtering for me. On Jobbe.io, I set up multiple saved searches:
- Stack‑based filter:
React+TypeScriptas mandatory. Optional: Node.js, GraphQL, PostgreSQL for full‑stack roles. - Location filter: Remote (EU) or specific cities where I could work without visa sponsorship.
- Experience filter: Mid‑level. I wasn’t a junior anymore, but I also wasn’t pretending to be a senior.
- Role filter: Software Engineer, Frontend Engineer, Product Engineer.
Every day, I’d check my saved searches. The feed would update with fresh roles. Because the filters were so specific, the number of results was manageable—usually between 10 and 20 new postings per week. Each one was a genuine possibility. I stopped feeling overwhelmed 😵💫 and started feeling in control 💪.
The practical impact: within the first week, my application‑to‑response rate went from near zero to roughly 1 in 8 📈. Suddenly, I wasn’t shouting into the void anymore. I was having conversations. And those conversations started building momentum.
⚡ Change #2: I applied within the first few hours — every time
Jobbe.io surfaces jobs directly from company career pages, often before they hit the bigger job boards. I made a rule: as soon as a new role appeared, I applied that same day — preferably within a few hours.
At Meta, the recruiter later admitted they had only deeply reviewed the first 50 applications out of 600+. My application was among those first 50 because I saw the listing on Jobbe.io early and acted immediately. Being early meant my resume actually got read by a human, not skimmed by a tired screener. 🚪
📝 Change #3: I tailored every application using the job description – not AI, but deep reading
With Meta’s posting, I saw they emphasised “performance at scale” and “cross‑functional collaboration.” I rewrote bullet points to mirror that language:
- ❌ Old: “Developed frontend components for a customer dashboard.”
- ✅ New: “Improved rendering performance of a React/TypeScript dashboard by 40% through code splitting and memoisation, serving 2M+ monthly active users.”
That alignment helped me pass the ATS and catch the recruiter’s eye. Each tailored application took 20 minutes, but the response rate skyrocketed 🚀.
Because Jobbe.io gave me a clutter‑free view of the job description, I could focus deeply on tailoring without distraction.
🎯 Change #4: I stopped applying to everything and started applying to the right everything
I became ruthlessly selective. I passed on roles that were 70% match and only applied to those where I was an 85%+ genuine fit. This reduced my applications dramatically, but my response rate jumped from 2.5% to 38% – a fifteen‑fold improvement!
(Bars animate on page load – hover for fun!)
When Meta’s listing appeared, I was ready. I had the mental bandwidth to craft a killer application because I hadn’t exhausted myself on 50 irrelevant submissions. 💪 Jobbe.io helped me see only the roles where I was a strong fit, making selectivity possible.
🏆 The Meta interview process: How the four changes carried me through
The process was tough, but the tailored stories from my resume made every behavioural answer authentic. They said my responses felt “consistent and authentic.” That’s the power of applying only to the right jobs.
🎉 The offer and the aftermath
The offer came on a Friday. I had gone from 100 rejections to a job at Meta. I didn’t open my Rejection folder after that. The right tool and the right strategy changed everything.
🪄 Jobbe.io wasn’t a magic wand
I still had to do the work. But Jobbe.io gave me signal in a sea of noise. It let me filter like a developer, apply early, tailor with care, and choose quality over quantity.
📋 Key takeaways
- 🔍 Filter like a developer – use precise technical criteria.
- ⚡ Speed is a superpower – apply within hours, not days.
- 📝 Tailor your resume manually – spend 20 minutes aligning with the job description.
- 🎯 Be ruthlessly selective – only pursue 85%+ fit roles.
- 🧰 Your job board matters – a specialised platform like Jobbe.io can be the difference.
💌 A message to anyone still counting rejections
If you’re at rejection number 30, 50, or 100, I see you. Your rejections are not a measure of your worth. Change the pond. Change your filters. Change your speed. Change your selectivity. The right role is out there – sometimes all it takes is a better tool to find it. ❤️
For me, that tool was Jobbe.io. It might not be everyone’s solution, but it was mine. And if my story can save one person from a hundred‑rejection folder, then every word I’ve written here was worth it.
The job you’re meant to land might already be listed – you just need to see it first. 👀
Comments
Post a Comment