I want to land that EA role
What do I do?
I’m Going to Utter an EA’s Favorite Sentence:
“It depends.” chuckle
I’m in School
First of all, how the heck did you even find out about EA? Truly impressive. Okay, you’re a little far from becoming an architect just yet, but what you can do now is study computer science. Learn programming and code as often as you can. Embrace that inner developer persona!
I’m in College
Are you a computer science major? Perfect! Start applying for internships at technology companies. Enterprise Architecture teams are usually small and may not take interns. So your best bet is to intern as a developer at a company that has an EA function. Then, use your networking skills to understand how EA plays a role in the organization.
I’m a Junior Software Engineer
Hang on for 10 years and—bam!—you too could be an EA. In the meantime, polish your system design skills. I personally like ByteByteGo for its simple, visually appealing diagrams that clearly explain how systems work.
I’m a Solution Architect
You’re so close! Your system design skills are strong, and this is a great time to pursue a TOGAF certification. Can you become an EA without it? Absolutely. But having the certification can increase your chances of landing the role.
The interesting thing about the Solution Architect role is that it straddles both architecture and engineering. It’s a blend of technology and strategy. Which brings up an important question: are you a builder or a thinker?
In my view, builders take joy in developing and delivering solutions to production. Thinkers enjoy designing solutions, even if they never get built. As a Solution Architect, understanding this distinction is key.
I’ve seen colleagues move from engineering into EA and struggle because they missed the sense of closure that comes from seeing something run in production. There’s no right answer here, it really depends on what drives you.
I made the same transition from engineering to architecture and absolutely loved it. Looking back, I wish I had recognized that earlier and made the move sooner.
Thinkers make excellent Enterprise Architects because they’re natural strategists and pattern recognizers. Builders thrive in engineering roles because they love solving problems and bringing things to life. An experienced Solution Architect can bring immense value to either path, depending on how the company is structured.
So there you have it. One possible path to becoming an EA. It’s not the only way, so don’t worry if your journey looks different.
Does this resonate with you? Let me know in the comments.