Becoming a Software Architect is a current trend in the salesforce community and after attending all the “architect” happenings I could in the last TrailheadDX, I’ve reflected on the different journeys people have taken to become architects and the ups and downs people face on their transition to the role. Understanding how business oriented is the architect role, how important is to listen to others and the way job titles and certifications help were some of my major takeaways
It’s less technical that you think
As a developer you may see the architect role as a natural progression after reaching the higher seniority levels of your organization. Although this might be true, the skills that made you a successful developer are not going to be the skills that will make you a successful architect. You need to talk business with people, you need to be able to articulate a solution in business terms, as you’re not there to build an app, you’re there to solve a business problem. This is perhaps why we see many business analysts successfully jumping into the architect: they know how to talk with the business.
You’re not there to build an app, you’re there the solve a business problem
You must listen to others
Arguably the architect is one of the most influential roles in a project, but the strategic big picture perspective that an architect provides won’t be possible without his ability to listen and learn from others. And most of the time this happens in a context of different stakeholders that have strong opinions that point towards opposite directions.
Since the initial phases of the project, architects need to learn about a business proceses they want to improve, and although their previous experiences in similar domains will help them to understand the challenges of the current project, there is always going to be something new to understand through out all the stages and aspects of the project: a different way on handling this process, a alternative use of a technology, some indirect constraints to consider, etc. You need to learn how to listen, you need to learn how to coach and support the people in your project, you need to learn how get the best from everyone around you.
The strategic big picture perspective that an architect provides won’t be possible without his ability to listen and learn from others.
Certifications and job titles help a bit
You can be a software architect without the job title and the certification, but in the context where you work with other professionals the certification and the job titles do make a difference. If you are in the position where people have trusted you the with the duties of an architect (regardless of your job title), then certifications and job tiles might not be that important: you’re in fact doing the architect job that you want and enjoy. But if you work with external customers or new teams often, or if you’re trying to get your voice heard in a big project, having some credentials to show will help and formal job titles do matter. This should encourage you to apply for that architect position and complete that certification. Nothing will speak louder that your work, but the credentials will help you to get that work assigned to you in the first place.
If you’re trying to get your voice heard in a big project having some credentials to show will help and formal job titles do matter.
Are you in your journey to become a software architect? What is the step you’re going to take today to get you closer to your goal?
Angel Abrego 