AI research engineer

From telecom to AI: navigating the next step in your research journey

Four hundred cold emails.

4 min readMachine Learning

The signal in this story is loud and clear: a talented researcher with three years of hands-on AI experience, a publication, a patent, and a relentless work ethic is being filtered out before anyone reads past the university name. The bottleneck isn't capability, it's access. And the proposed solution, another Master's degree abroad, treats a structural problem as a personal one. That's the wrong diagnosis, and it risks two years and significant resources on a path that may not move the needle.

The pattern here is familiar to anyone watching how AI research talent is actually sourced. The applicant's work in RL, LLMs, and systems efficiency is relevant, and their outreach shows genuine initiative. Yet 400 cold emails produced three replies. That isn't a signal about the quality of their ideas; it's a signal about how labs triage unsolicited interest. When compute is constrained and university brand carries outsized weight, the barrier isn't capability, it's visibility. This mirrors what we see in the broader AI landscape, where small models trained from scratch are outperforming standard LLMs not because they have more resources, but because they find more efficient paths. The lesson isn't to chase scale; it's to find the right leverage point.

The uncomfortable truth is that the current application pipeline rewards signals this engineer doesn't have: a recognizable university name, geography, and the social proof that comes with both. That's not a judgment on ability. It's a structural reality of how research hiring works. But it also means the traditional route, more applications, another degree, waiting for a committee to say yes, is the slowest possible path to the outcome. When small models trained from scratch are outperforming standard LLMs, the field is signaling that raw compute and brand prestige matter less than demonstrated craft. The same logic applies to careers: the work you can show may outweigh the institution that issued your diploma.

What this engineer is really facing is a matching problem. They're skilled in RL, LLMs, post-training, and systems efficiency, but they're applying to labs that see a telecom background and a non-CS degree and stop reading. The 400 cold emails tell the real story: technical curiosity gets engagement, but institutional trust does not. That gap is not a personal failure; it's a structural feature of how research hiring works. And it points to a practical truth: the path forward isn't another degree, it's a sharper strategy. A second CS Master's abroad could open doors, but it's a two-year investment with no guaranteed return. A more direct route might be targeting compute-rich industry labs, like the ones behind Small models trained from scratch are outperforming standard LLMs: here's how, where demonstrated systems efficiency and RL expertise matter more than pedigree. The same labs that ignore a cold email from Lagos often respond to a well-scoped pull request on an open-source repo.

The pattern here isn't about your skills, it's about signal. In a global market, university brand and geography act as proxies for trust, and you're being filtered out before your work can speak. That's frustrating, but it's also information. The system is telling you that your current approach, while rigorous, is optimized for a game you're not being invited to play. The good news: the rules are changing. As small models trained from scratch outperform standard LLMs and TypeSafe's Jev hits $7.5B valuation by outpacing LLMs with fewer tokens, the field is rewarding demonstrated efficiency and novel thinking over pedigree. That shift is your opening.

Your profile is stronger than your rejection rate suggests. Three years of hands-on work in RL, LLMs, and systems efficiency, even at smaller scale, is exactly the kind of practical depth that labs and startups claim to want. The problem isn't your skillset; it's the signal. A second Master's is one way to rebroadcast that signal, but it's a two-year detour with no guaranteed return. Before committing to that path, consider what your story already proves: you built expertise in a demanding field while working full-time, you published, you patented, and you kept pushing after hundreds of silent no's. That persistence is a credential in itself, and

From Machine Learning

I’m an AI research engineer based in Africa with about 3 YoEs in RL, LLMs, post-training, and systems efficiency (CUDA/vLLM). However, on a smaller scale because of compute limits. My undergrad and Master’s are both in communications engineering. I did a 5th-year Master's at my local university while working full-time at a telecom company, focusing on RL in telecom. Publication-wise, I have one paper published in a peer-reviewed mid-tier AI/telecom conference, a patent, and another paper that was accepted but never published because we couldn't fund it.

Over the past year, I’ve hit the below walls:

Read the original at Machine Learning