I’m looking for some guidance as I prepare for a role transition.
For the past few years, I’ve been working as a Software Architect. My responsibilities have primarily involved reviewing and critiquing design documents, providing architectural guidance, and supporting other staff engineers in their execution. The role has been valuable for building broad perspective, but it hasn’t carried much direct accountability for delivery. Hands-on work has been quite limited, and I realize I’ve drifted away from the practice of designing and building solutions end-to-end myself.
I’m about to move into a Staff Engineer role (different company) in about a month.
I feel that my solution design skills have atrophied. I’m comfortable reviewing others’ proposals and spotting gaps, but I struggle when starting from a blank page. I want to rebuild confidence in designing systems and making concrete technical decisions.
If you’ve been through a similar shift—or coached someone who has—I’d love to hear what helped you or your colleagues succeed.
I have seen this case a lot, especially at Meta as there's effectively a ban on the software architect archetype. Many senior+ engineers were forced to transition as they had this traditional architect role at their previous company. Most failed but a couple succeeded. Here's what I saw from those who succeeded:
#1 is the main one. Just get your hands dirty again. Try doing some last minute coding at your current company, scoping out tasks and writing system design docs. On the side, you can try doing side projects and/or open-source.
#2 is also extremely important, and I recommend this other thread for that: "What’s the most effective way to switch domains in tech?"