Changing careers into tech isn’t just about learning to code or understanding new systems it’s about rebuilding your identity from scratch. It’s the gut punch of going from being experienced and confident in your field to suddenly feeling like a lost intern who doesn’t know what a terminal command is.
When I transitioned from Visual Designer to Data Engineer it was brutal. There were more downs than ups in those first two and a half years, and at 30, after two decades in design, shifting into an entirely different world felt like learning how to walk again. Resilience wasn’t optional it was survival.
But here’s what I learned: Resilience isn’t just “pushing through” or “faking it till you make it.” It’s about:
- Being okay with looking stupid.
- Asking for help repeatedly.
- Letting go of ego.
- Realising mistakes are the only way forward.
Step 1: Accept That You Will Suck (For a While)
One of the hardest parts of transitioning into tech is accepting the drop in competence.
- In your old field? You knew your stuff. You were the go to person.
- In tech? You will feel like a clueless idiot more times than you’d like.
And that’s fine. That’s normal. If you expect to struggle, you’ll be less likely to quit.
What helped me?
- I treated every mistake as an experiment, not a failure.
- I tracked small wins (even something as simple as understanding a new concept).
- I reminded myself that even senior engineers Google basic stuff every day.
Step 2: Get Comfortable Not Knowing
One of the biggest misconceptions about working in tech is that everyone knows what they’re doing.
They don’t.
Technology is all about exploring, experimenting, and figuring things out as you go. You’re not expected to have all the answers before you start. In fact, if you waited until you felt ready, you’d probably never begin.
The people who grow the fastest aren’t the ones who know everything. They’re the ones who aren’t afraid to say, “I don’t know… yet.”
It’s also okay to ask what feels like a “stupid” question. We’ve all been there. Whether it’s understanding a piece of jargon, setting up your development environment, or asking why a line of code works the way it does, every expert was once a beginner asking those same questions.
I had to unlearn the fear of asking for help. Once I did, everything became easier.
✅ Slack and forums. Instead of spending hours stuck, I’d ask someone who’d solved it before.
✅ Pair programming. Watching someone else think through a problem taught me more than hours of tutorials.
✅ Tech communities. Meeting other career switchers reminded me that everyone starts somewhere, and nobody figures it all out alone.
The truth is, technology isn’t about knowing everything. It’s about becoming comfortable with not knowing, asking questions, and trusting yourself to figure things out one step at a time.
Step 3: Stop Trying to Be Perfect – Just Be Okay With Where You’re At
If you come from a creative or non-technical background, you probably have perfectionist tendencies.
In design, if something looked even slightly off, I’d tweak it for hours. In tech? No one cares if it’s “perfect.” Tech doesn’t reward flawless execution—it rewards iterations, debugging, and improvements over time.
The first time I deployed a pipeline… I actually woke up at 3AM in a cold sweat to check on it, and BOOM… it was broken. My gut dropped. It felt like I had just set fire to the entire system. No one else was awake. So there I was, at 3AM, trying to fix my suicidal pipeline.
Not only had it failed, but it had broken other pipelines too 😫
It was like some massive domino effect of dodgy data corrupting everything in sight. FML.
At first, I panicked.
I barely slept.
I woke up thinking …yep, this is how I die.
But instead of spiraling into a black hole of despair, I focused on fixing it (or at least getting a senior to help me fix it—oops). Once it was stable, we went through what went wrong, how to prevent it next time, and how now I had not only childhood trauma but also pipeline trauma to deal with.
The best part at work though was no one pointed fingers. No one made me feel bad. Most of the time (if your work culture is good and you work with nice people) as long as you’re accountable for your mistakes, people will respect that you’re trying because they’ve been there too.
I’ve seen senior engineers break things in crazy ways. The only difference? They knew how to fix their own disasters. But that comes with time.
Mindset Shift
❌ Old thinking: “I need to be perfect before I deliver anything.”
✅ New thinking: “I need to put this out,with the best of my ability, so I can learn from it.”
Progress > Perfection. Every mistake is a lesson. Just try not to destroy the prod environment at 3AM. 😅
Step 4: Build Resilience Through Consistency (Not Motivation)
Tech careers are built one problem at a time. You won’t wake up one day and suddenly feel like an engineer. You become one by:
- Showing up daily, even when it sucks.
- Learning from every mistake.
- Keeping a long-term mindset… you’re building a career, not just learning a skill.
🔹 What helped me?
- I treated engineering like the gym even if I didn’t feel like it, I showed up.
- I tracked progress and kept a log of things I struggled with but eventually figured out.
- I built mini wins into my day. Even fixing one bug was a success.
The moment you stop focusing on how far you have to go and start celebrating small daily progress, resilience becomes second nature.
Final Thought: Resilience is Earned, Not Given
If you’re transitioning into tech and struggling, congrats—you’re doing it right.
Resilience isn’t about feeling lost or frustrated. It’s about embracing that discomfort, pushing through, and knowing that every challenge makes you stronger.
So keep going. One bug at a time. One question at a time. One small win at a time. Because eventually, you’ll look back and realise holy sh*t, I actually made it. 🚀🔥
Let me know what was your biggest struggle when switching into tech? Drop a comment! 💡👇