When the AI Rush Left Engineers Behind: Rethinking What Really Matters in Tech

A rejection email at 3 a.m. That’s how one Silicon Valley engineer found clarity about her career. After spending nearly a decade building software in one of tech’s most competitive hubs, Cristina Estupiñán faced something many of us in the tech world are grappling with right now: the pressure to jump on the AI bandwagon or risk becoming irrelevant.

But here’s where her story gets interesting. Instead of panicking and pivoting to the latest AI trend, she stepped back and asked herself a harder question: Is chasing the hottest technology really what I want to do?

This moment speaks to something bigger than one engineer’s career decision. It’s about how we think about growth, relevance, and value in tech—and why the constant push to adopt the newest trends might actually be leading talented people away from meaningful work.

The Pressure Cooker of Tech Culture

Let’s be honest. The tech industry runs on FOMO. If you’re not working with AI right now, there’s this underlying sense that you’re falling behind. Every conference is about AI. Every recruiter is asking about your AI experience. Every startup pitch includes the magic phrase: “powered by AI.”

For engineers, this creates a particular kind of stress. You’ve built real skills over years. You’ve shipped products. You’ve solved hard problems. But suddenly, there’s this whisper in the background: “Is any of that still valuable?”

The 3 a.m. rejection email Estupiñán received wasn’t just another job rejection. It was a wake-up call. That timing—the middle of the night—suggested something both automated and cold. A system that didn’t see her decade of experience as sufficient because she didn’t check the AI box.

But here’s what I think matters: Her response to that rejection revealed something that often gets lost in tech culture. Sometimes the best career moves aren’t about chasing the next big thing. Sometimes they’re about reclaiming agency over what you actually want to build.

Building Differently, Not Just Building AI

When you zoom out, there’s crucial engineering work happening everywhere that has nothing to do with generative AI. Infrastructure that keeps the internet running. Security systems protecting sensitive data. Healthcare software saving lives. Educational tools making learning accessible. Climate tech trying to solve existential problems.

These fields need skilled engineers desperately. They need people who understand systems thinking, who can write clean code, who can debug under pressure. They need exactly the kind of experience someone like Estupiñán has built.

The question isn’t whether AI matters. Of course it does. But the question that fewer people are asking is: Does every engineer need to be working on AI? The answer is clearly no.

What we’re witnessing is a correction. Engineers are realizing they have more options than they thought. Some are choosing to build in spaces where AI isn’t the primary concern. Others are exploring startups in different domains. Some are moving into education, like teaching the next generation what they’ve learned.

Taking Control of Your Own Career Narrative

Here’s what I’d want every engineer (or anyone in tech, really) to take from Estupiñán’s story:

• Your value isn’t a trend. A decade of building software matters. The skills you’ve developed—problem-solving, debugging, systems thinking—apply across domains. Don’t let a moment of industry hype convince you otherwise.
• Trends create blind spots. When everyone’s looking in one direction, opportunities flourish elsewhere. Some of the most interesting problems right now are being tackled by people who aren’t in the AI-startup hype cycle.
• The best work often feels less flashy. Building reliable, thoughtful software for healthcare, education, or infrastructure doesn’t get the same buzz as launching an AI product. But it might be more fulfilling and certainly more durable.

I’ve seen this pattern repeat. A new technology emerges. Everyone feels pressure to specialize in it immediately. A few years later, many realize they’d rather be doing something else, but by then they’ve already made the pivot.

The smarter move? Build skills that matter to you. Stay curious about new tools. But don’t let external pressure—especially not a 3 a.m. rejection email—dictate what problems you work on.

The next wave of interesting engineering problems might not involve AI at all. They might be about sustainability, accessibility, privacy, or things we haven’t even imagined yet. And they’re going to need people who know how to think clearly about code, systems, and impact.

If you’re feeling that pressure to jump on the AI train, pause. Ask yourself what you actually want to build. Your career is longer than any single trend. Choose wisely.

Source: ‘I can’t get on the AI train’: A 3 a.m. rejection email pushed an engineer to…