Skip to main content

Why I Built ApexDevs!

 I want to start this honestly.

ApexDevs wasn't born out of a polished startup pitch or a hackathon idea I was trying to dress up as a company. It was born out of something quieter, and frankly, more uncomfortable — watching too many capable students around me get politely turned away from the thing they were told to chase their whole lives.

A job. Even an internship. Even an interview, sometimes.

This post is about why I decided to build it anyway.

The students nobody is building for

If you scroll through LinkedIn for ten minutes, you'll see the same thing on loop. The IIT kid who landed a 40 LPA offer. The girl who cracked Google in her third year. The boy who shipped an open-source project that ended up on Hacker News. We celebrate them, and we should — they worked for it.

But there is a much, much larger group of students that nobody is building for.

The average and below-average Indian student. Not the topper. Not the kid with five hackathon trophies. Just a regular student from a regular college, sitting in a regular tier-2 or tier-3 city, watching everyone around them collect "experience" through connections, internships at uncle's company, or sheer luck — while they refresh Naukri and Internshala one more time.

These students are not lazy. They're not unintelligent. They've simply never been allowed inside a real working environment to find out what they're actually capable of. They've never sat in a Slack channel where someone reviews their work. Never had a manager send a "small request" at 6:47 PM. Never been told their first version isn't good enough and to ship a v2 by Friday.

They've read about it. They've watched YouTubers describe it. They've scrolled through Glassdoor reviews trying to imagine what an actual office day looks like. But they've never tasted it.

And here is the cruel part of the system: every single job description asks for that taste before they're allowed to have it.

"Minimum 6 months experience required"

Read that line again. It is on almost every fresher posting in this country.

Think about what it really means. To get experience, you need experience. To get into the room, you need to have already been in the room. The door is locked from the inside, and the people who got in early are the ones holding the keys.

If you grew up with the right network, you got an internship through a family friend. If you went to a top-tier college, recruiters came to you. If you didn't — if you came from a regular family in a regular city studying at a regular institution — you were quietly told to "build projects" on your own and hope someone notices.

So students do that. They build a to-do app. A weather app. A clone of something. They put it on GitHub. And then they sit through interviews where the recruiter glances at it for four seconds and asks where they've worked before.

The system is dishonest about what it actually rewards. It pretends to reward skill, but it really rewards proof of having already been employed somewhere.

Why classroom projects don't fix this

I want to be direct about something else. Most college projects, bootcamp capstones, and online course "final projects" are not preparing students for work. They're preparing students for more course content.

A real work environment is not a tutorial. There is no instructor showing you the answer at the end of the video. The brief is unclear. The deadline is uncomfortable. Someone reviews your output and tells you what's wrong with it. You fix it. You ship it. Next week, there is a new brief.

That cycle — brief, build, review, revise, ship, repeat — is the actual skill of working. And almost no student gets to practice it before they're suddenly expected to perform it on day one of their first job.

This is the gap I kept staring at. Not a skill gap. An environment gap.

What ApexDevs is, in plain words

ApexDevs is my attempt to give regular students a real, structured taste of working life — before the job market asks them to prove they have it.

Here's how it actually works:

  • A student applies, and we verify their documents.
  • They get matched with an industry mentor in the direction they actually want to go — not whatever happens to be available.
  • They pick a programme length: 4, 8, or 12 weeks.
  • Every single week, they ship a real deliverable. Not a tutorial. Not a quiz. A project aligned with where they want their career to go.
  • Their mentor reviews it, gives them honest feedback, and unlocks the next week's work.
  • At the end, they walk away with three things they can actually put in front of an employer:
    1. A signed internship offer letter (after document verification).
    2. A portfolio of mentor-reviewed, career-aligned projects.
    3. A digitally-signed, verifiable completion certificate.

The whole lifecycle — applications, verification, mentor matching, weekly reviews, certificate issuance — runs on a single platform at apexdevs.net.

That's it. No fluff. No "you'll learn the secrets of FAANG." Just a real working environment, structured around real feedback, in a country where most students have never been let into one.

What I want to be honest about

ApexDevs is not magic. It will not turn a disengaged student into a top performer in four weeks. It will not guarantee anyone a job at a specific company. I'm not interested in selling that fantasy — there are already enough people doing that.

What it will do is give a student something they've been denied for years: the experience of being treated like a working professional. Of having a mentor who expects something of them. Of getting feedback that's neither cruel nor coddling. Of finishing a week and being able to point at something and say, "I built that, and someone in the industry signed off on it."

For a student from a regular background, that experience is genuinely life-changing. Not because the certificate is impressive on its own, but because the student who finishes the programme is a different person from the one who started it. They've been inside the room now. The door isn't mysterious anymore.

Why I'm doing this

Honestly? Because I'm tired of watching capable people get filtered out of opportunities by a system that pretends to be a meritocracy.

I'm tired of the polite rejection emails sent to students who never had a fair shot in the first place. I'm tired of "minimum experience required" being the first line of every fresher posting. I'm tired of the quiet, unspoken understanding in this country that opportunity is something you inherit, not something you earn.

ApexDevs is small right now. It might always be small. But every student who comes through it walks out with something real — a portfolio they built, a mentor who knows their work, and proof that they can do the job. And that is enough of a reason for me to keep building it.

If you're a student who has been refreshing job portals wondering when your turn comes — your turn doesn't come. You take it. And I'd like to help you take it.

Come find us at apexdevs.net.

Comments

Popular posts from this blog

IGDC 2025: Leveling Up in India’s Gaming Scene

  I just got back from IGDC 2025 and wow, it was epic. IGDC (India Game Developer Conference) 5-7 November is the country’s premier event for game creators and industry pros, and this year it brought everyone together in Chennai. I hung out with designers, programmers, artists, animators and the whole creative crew. Gamers, content creators and developers were everywhere – it felt like a huge community reunion. It was so cool catching up with old friends and making new ones in our gamer/dev squad.  Key Takeaways IGDC was packed with talks and booths, but the biggest moments were the aha’s that I jotted down. Here are my top learnings from the conference: Gaming = Mainstream Career: No doubt, gaming and game dev have blown up into a legit career path now. Industry reports back this up – for example, Meta’s India lead said the gaming market is set to be worth nearly $7.5 billion and create 250,000 new jobs by 2025. As one expert put it, “Gaming is no longer niche. It is mainstre...

Breadth vs Depth - Which Path Should You Follow as a Student or Fresher in Computer Science?

When you start your journey in Computer Science — whether as a first-year student just opening your first “Hello World” file, or as a final-year student applying for jobs — one question always lingers: “Should I explore everything a little or master one thing deeply?” This is the classic Breadth vs Depth dilemma. And the truth is — both paths have their place, depending on where you are in your journey. Let’s unpack this. Stage 1: The Explorer Phase (1st–2nd Year) — Go Broad At the start, your goal should be exploration. This is when you taste different domains like- web development, game design, AI, blockchain, cybersecurity, cloud, AR/VR, and so on. Here’s why breadth matters early on: You’ll discover your natural interests instead of just following trends. You’ll understand how different technologies connect — for example, how backend APIs power games or how data structures are used in AI. You’ll build a mental map of the tech ecosystem, which helps you talk intelligently in intervi...

One World, Fragmented Wires

When nations race to own the future, can an ancient Indian idea be the missing framework? A few weeks ago I was debugging a smart contract late at night — the kind of session where you forget time exists. But something kept nagging at me beyond the code. The news feed was full of stories about semiconductor export bans, AI chip restrictions, undersea cable disputes, and countries racing to wall off their digital borders. And here I was, building on a blockchain network that by design belongs to no one and everyone. The contrast hit hard. The technology we build is increasingly borderless. The politics governing it is increasingly territorial. And somewhere in that gap lives one of the most important questions of our generation: who owns the future, and who gets left out? Vasudeva Kutumbakam - a Sanskrit phrase from the Maha Upanishad - translates as "the world is one family." It is not a soft platitude. It is a philosophical assertion that the boundaries we draw between us an...