When Plan A Fails: My Real-World Path from Mobile to Backend Engineering
Sometimes, the most honest stories start with a plan that doesn’t work out. This is one of those stories—a real-world account of what happens when you try to change direction, hit a wall, and have to find a new way forward.
The Attempt That Didn’t Work
The idea of moving from mobile to backend engineering had been on my mind for a while. But if I’m honest, I didn’t really believe it was possible once you’re already out in the wild. The call grew so strong that I eventually gathered the courage and tried to make the leap while working in a high-pressure startup—thinking I could just squeeze backend learning into my evenings and weekends. Spoiler: it didn’t work (for me).
I’ve taken risks before and, more often than not, things worked out. But not this time. And that’s an important lesson I want to share: sometimes, taking a risk doesn’t pay off right away. But that doesn’t mean you have to give up. There are always other options, even if they’re not the ones you expected.
After that failed attempt, I realized I needed a different approach. That’s what led me to take a much-needed sabbatical—not as an escape, but as a deliberate pause to rethink my direction and give myself the space to actually complete the transition.
What I’m Looking For
Now, I’m charting a new course—one that’s less about panic and more about patience. I aim to work as a backend engineer, fully remote if possible (my coffee is better at home). I’m drawn to companies that care about building things that last, not just chasing the next shiny thing. Give me a team that values collaboration, quality—the kind of environment I got accustomed to in my last position—a bit of nerdy enthusiasm and space to grow, and I’m in. I want to keep learning—especially about backend systems, DevOps, and how AI can make all of this more interesting (or at least more efficient).
What do I value most? Stability over hype, for starters. I’d rather work on something robust and maintainable than jump on every new trend. Experience matters more to me than a big paycheck—though I won’t say no to a good one. And above all, I believe in transparency and trust. If we can talk openly, set clear expectations, and respect each other’s work, we’re off to a good start.
Building Something Real
To turn intention into action, I’m building a demo backend system from scratch (more about this very soon). Not just a “hello world” app, but a real project that covers everything from requirements to deployment. I’m documenting the whole journey here and on LinkedIn—warts, wins, and all. I’m also making sure to use modern tools and practices, so I’m not just learning in theory but actually keeping my skills sharp and relevant.
This hands-on approach is helping me reinforce my technical foundation and share what I’m learning with others. It’s not just about ticking boxes; it’s about showing how I think, how I learn, and what I care about.
The Bigger Picture
Honestly, there was a moment when burnout had me questioning if I even wanted to stay in software engineering at all. But stepping back gave me the space to rediscover what I love about this field—and now, I’m more motivated than ever to come back stronger and keep enjoying this profession for years to come.
What’s next? I’ll keep sharing what I’m building, the choices I’m making, and the lessons I’m learning. If you’re curious about backend engineering, slow tech, or just want to see someone try (and occasionally fail) at leveling up, stick around. There’s plenty more to come—and hopefully, a few good stories along the way.