This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
On burnout, imposter syndrome, and finding your voice as a developer abroad — and the unexpected failure that woke me back up.
[ERROR] Input suppressed. Reason: unknown.
[WARN] Motivation: degraded.
[ERROR] Identity: not found.
I stared at that metaphor for a long time before I realised it was my year.
There's a specific kind of silence that only developers know. Not the comfortable silence of deep focus, or the peaceful silence of a solved problem. I'm talking about the silence of knowing the answer — and choosing not to say it.
I've sat in dozens of meetings, heart quietly racing, watching a discussion go in circles — sometimes toward a solution I already knew was wrong — while a voice in my head repeated the same line: your input isn't needed here.
It wasn't shyness. It wasn't a language barrier, though I'd relocated abroad and English was my working language. It was something quieter and more corrosive: a deep-seated belief that I hadn't earned the right to take up space.
Three kinds of silence
Seniority is contextual. I knew that intellectually. I didn't know it would feel like starting over.
I call it the three silences, because that's how it showed up for me.
The language silence. I'd draft a message in Slack, then delete it. Not because it was wrong — because I'd reread it three times wondering if the phrasing sounded too foreign, too formal, too something. I started filtering myself before I even had the chance to be misunderstood.
The professional silence. I had ideas. Lots of them — architectural improvements, product suggestions, side projects that could've become real tools. But every time I thought about sharing them, imposter syndrome arrived right on cue — and at senior level, it doesn't sound naive. It sounds reasonable: This has already been done. There's a library for it, a blog post about it, a better implementation of it somewhere on GitHub. What are you going to add? The voice is more polished. It's harder to argue with.
The inner silence. This one came last, and it was the loudest. There's a particular brand of exhaustion that burnout brings — not tiredness, but numbness. I'd open my laptop, stare at the code, and feel nothing. Not frustration, not curiosity. Just absence. The IDE was running. I was not.
The lie I told myself about time
For a long time, I explained away my stagnation with a single story: I don't have time.
I was busy. The sprints were packed, life abroad had logistics I hadn't anticipated, and building a personal brand felt like a luxury for people who had already "made it." I had ideas for articles, side projects, open-source contributions — all neatly filed in Notion drafts and half-opened browser tabs, where they couldn't be judged.
Here's the thing about that story: it was comfortable. And it was a lie.
The truth was that I had pockets of time. I just didn't trust myself enough to use them. Writing a post felt pointless if nobody cared. Building something felt arrogant if I might fail.
Motivation wasn't missing. It was buried under a layer of fear I'd labelled as a scheduling problem.
What burnout actually looks like (from the inside)
People talk about burnout like it's a dramatic collapse. And sometimes it is. But the version I lived was quieter — a slow dimming rather than a sudden blackout.
I still shipped features. I still showed up to standups. From the outside, I was probably fine. From the inside, I was running on a kind of professional autopilot — doing the work, but completely disconnected from the reason I got into this field in the first place.
The hardest part wasn't the exhaustion. It was losing the thread back to myself — to the person who once pulled all-nighters not because of deadlines, but because the problem was just too interesting to put down.
The failure that woke me up
Recovery didn't come from a productivity hack or a helpful conversation. It came from a system design interview that went badly wrong.
I'd prepared. I knew the patterns. But the moment the interviewer started asking questions, something broke down. I couldn't structure my thinking. I went in circles. I could see the confusion on the screen and I couldn't stop it.
I failed. Clearly, decisively, unambiguously.
And something strange happened in the days that followed: I felt alive again.
Not happy — it stung badly. But underneath the sting was something I hadn't felt in months: genuine engagement. I was frustrated, yes. But frustration means you care. It means the signal is still there. After months of numbness, even a hard feeling was proof that I was still in there somewhere.
That failure did what nothing else had: it threw a stack trace. Suddenly I could see exactly where I'd been running in silent degraded mode. The interview didn't break me — it interrupted the autopilot. And that interruption was what I needed.
[INFO] Exception caught: SystemDesignInterviewFailure
[INFO] Stack trace:
- few years autopilot
- suppressed ideas
- unshared voice
[INFO] Attempting recovery...
Finding the voice again
After that, things moved differently.
I opened one of those Notion drafts and just finished it. I left a comment on a GitHub issue I'd been silently following for weeks. Then I did the thing I'd been postponing the longest: I started an open-source project. Not because I was sure it was needed — but because building it in the open meant I couldn't quietly abandon it. I wrote a couple of posts along the way, sharing things I'd stumbled across while building. Small discoveries, not grand conclusions. Public ones. With a name attached.
And something unexpected happened: people responded. Not to a polished, authoritative voice I thought I needed to have — but to the honest, unguarded version I'd been afraid to show.
It turns out authenticity travels across languages. Struggle is not a regional dialect.
What I'd tell my quieter self
If I could go back to that person staring at a blinking cursor, unsure whether their ideas mattered, I'd say a few things.
Your accent is not a qualifier for your competence. Years of experience don't make this easier — they just make you better at hiding the discomfort. The nervousness you feel speaking in a second language is not evidence that you don't belong. It's evidence that you're doing something genuinely hard, and doing it anyway.
Imposter syndrome isn't a diagnosis — it's a symptom. It usually means you care deeply and you're in new territory. Both of those are good things, even when they don't feel like it.
The ideas you're sitting on are not too small. The blog post you're not writing, the project you're not building, the comment you keep deleting — none of those need to be perfect to be worth sharing. Done and imperfect is infinitely more valuable than flawless and invisible.
Burnout is not a character flaw. It's what happens when a system runs too long without maintenance. You are allowed to rest. You are allowed to be unproductive. You are allowed to be a person first and an engineer second.
And sometimes the failure you're dreading is the only thing loud enough to reach you. Not because pain is a good teacher, but because numbness has no edges. Failure does.
I'm writing this now — this very post — because I'm on the other side of that quiet period. Not because everything is solved, but because I finally stopped waiting to feel ready.
If you're in the thick of it right now — navigating a new country, swallowing your ideas, running on empty — I want you to know: this is not permanent. The silence ends. And when you start speaking again, you'll find that people were waiting to hear you all along.
Your voice belongs here. It always did.
Have you experienced burnout or imposter syndrome in your tech career? I'd love to hear what shifted things for you — drop it in the comments.
Top comments (0)