A slightly late memo to my younger self, written from the other side of the learning curve
I walked into tech thinking competence was the whole game. Learn the tools, ship the work, get better every quarter, and the rest would sort itself out. Nobody handed me a manual for the parts that actually shape a career: the politics, the pacing, the quiet erosion of confidence that happens when you compare your rough draft of a career to everyone else's highlight reel. So this is the manual I didn't get. Some of it will sound obvious once you read it. It didn't feel obvious while I was living through it.
1. Being good at the work is not the same as being valued for it.
I used to believe that if I just did excellent work, recognition would follow naturally, like gravity. It doesn't work that way, and it took a few painful cycles of watching less rigorous work get louder applause before I understood why. Visibility is a skill. Communicating your impact is a skill. Advocating for your own contributions in a room where everyone else is doing the same is a skill. None of that is dishonest or self-serving; it's just how organizations actually function. People are busy, attention is limited, and nobody is tracking your effort as closely as you are. If you don't narrate your own value, someone else will narrate it for you, usually poorly, usually briefly, usually forgotten by the next quarterly review. I had to learn to write the update nobody asked for, to say "here's what this project actually solved" in a meeting instead of assuming the solving spoke for itself. It felt uncomfortable at first, almost like bragging. It wasn't. It was translation.
2. Imposter syndrome doesn't disappear with experience. It just changes outfits.
I thought imposter syndrome was a beginner's problem, something you'd age out of once you had enough years and enough proof behind you. What actually happens is that the bar keeps moving. You stop doubting whether you can do the junior version of the job and start doubting whether you can do the senior version, then the leadership version, then the version where you're the one making calls nobody can double check for you. The discomfort doesn't vanish. It relocates. What changed for me wasn't the feeling; it was my relationship to the feeling. I stopped treating self-doubt as proof I didn't belong and started treating it as a fairly reliable sign that I was doing something that mattered enough to be scary. Comfort and growth rarely show up in the same room.
3. Your technical skills have a shelf life. Your judgment does not.
Tech moves in a way that can feel disorienting if you tie your entire identity to a specific tool, framework, or platform. I watched people who were once considered irreplaceable experts in a technology scramble when that technology quietly fell out of favor, and I watched people who had built their reputation on judgment, on knowing how to ask the right questions, diagnose the real problem, and make sound decisions under uncertainty, remain valuable no matter what the landscape did underneath them. Learn the tools. Get fluent in them. But invest even more in the underlying muscle: how to think clearly when the information is incomplete, how to weigh tradeoffs, how to know which problem is actually worth solving. That muscle transfers. The specific software rarely does.
4. Burnout doesn't always look like exhaustion. Sometimes it looks like numbness.
I had a picture in my head of what burnout would look like: crying at your desk, dreading Monday, physically depleted. What I actually experienced was quieter and, in a way, more dangerous. I stopped feeling anything about the work at all. Projects that used to excite me became tasks to clear off a list. I was still performing well by every external measure, still hitting deadlines, still showing up on time, but something underneath had gone flat. It took me longer than it should have to name that as burnout because it didn't match the version I'd been warned about. If you find yourself going through the motions competently while feeling almost nothing, that's worth paying attention to. Numbness is not the absence of a problem. It's often the body's way of managing a problem it doesn't yet have the resources to feel.
5. The people you work with matter more than the mission statement on the website.
Every company will tell you about its culture during the interview, and almost none of that language will predict what your actual day-to-day experience is like. What predicts it is your manager, your immediate team, the handful of people you talk to most. A brilliant mission with a manager who doesn't advocate for you is a miserable place to work. A modest, unglamorous project with a team that trusts you and has your back can be one of the best professional seasons of your life. I stopped weighing job offers primarily by brand name or by how exciting the product sounded and started asking sharper questions about the actual humans I'd be reporting to and working alongside. That single shift in what I prioritized changed the quality of my working life more than any raise ever did.
6. Saying no is a career skill, not a character flaw.
Early on, I said yes to almost everything, convinced that agreeableness was the fastest route to being seen as a team player. What actually happened was that I became the person everyone routed extra work to, precisely because I never pushed back. Saying yes to everything doesn't make you indispensable. It makes you available, which is a different and much less valuable thing. Learning to say "I can take this on, but it means this other thing slips" or simply "that's not something I can prioritize right now" didn't damage my reputation the way I feared it would. If anything, it sharpened it. People started trusting my yes more, because they knew it wasn't automatic.
7. Nobody is coming to hand you a five-year plan. You have to write your own.
I spent my first couple of years waiting for some external structure to tell me what came next: a formal path, a mentor with a map, a manager who would lay out the next five moves for me. That structure rarely exists, and where it does exist, it's usually built around the company's needs, not yours. The people I've watched build genuinely fulfilling careers are the ones who took ownership of their own direction early, who asked for the stretch project instead of waiting to be offered it, who treated their career as something they were actively authoring rather than something happening to them. Nobody else is going to care about your trajectory as much as you do, and once I accepted that fully, I stopped waiting for permission and started building the plan myself.
If I could hand this list to the version of me who was nervous on her first day, unsure if she belonged in any of the rooms she was walking into, I think it would have saved her some unnecessary suffering. Not all of it. Some lessons only land when you've lived through the version that hurts. But maybe it would have shortened the distance between struggling silently and understanding that almost everyone around her was navigating some version of the same uncertainty, just quietly, just alone, just like she was.
Top comments (0)