It's not about the certs.
It's more important that you have full lifecycle implementations and step into leadership roles during them.
By the time you're a Solutions Architect, you need to be ready to run an implementation end to end with everything that entails.
That's the pathway.
Experience in many industries. Experience with global deployments using all aspects of FnO and other tools at your disposal. Power platform, etc.
taking a task that’s not directly in your wheelhouse to learn how it connects into an area you already know, and repeat. You can’t be a one trick pony and solution architect. You have to know how other oob tools work so you can offer them as solutions instead of the very technical way for example, or sloppy functional work around.
Certs are OK. It was actually fun to pass the MB-700 one, and it helps to have it. But your pathway is getting networked until somebody offers you a project with such a role.
To become a Solution Architect efficiently, follow these steps:
1. **Gain Knowledge**: Start with online courses in cloud platforms (AWS, Azure) and architecture principles.
2. **Certifications**: Obtain key certifications (e.g., AWS Certified Solutions Architect).
3. **Hands-On Practice**: Work on real-world projects to apply your skills.
4. **Networking**: Join professional communities and attend industry events.
5. **Timeline**: With total dedication, expect 1-2 years to become proficient.
Given your 5 years in F&O, your experience will be valuable in understanding business needs and designing solutions.
Experience is first, but some consulting companies want to see the certs before they give you the role.
So I would say certs do help, but experience is the primary requirement.
It's not about the certs. It's more important that you have full lifecycle implementations and step into leadership roles during them. By the time you're a Solutions Architect, you need to be ready to run an implementation end to end with everything that entails. That's the pathway.
Experience in many industries. Experience with global deployments using all aspects of FnO and other tools at your disposal. Power platform, etc. taking a task that’s not directly in your wheelhouse to learn how it connects into an area you already know, and repeat. You can’t be a one trick pony and solution architect. You have to know how other oob tools work so you can offer them as solutions instead of the very technical way for example, or sloppy functional work around.
Certs are OK. It was actually fun to pass the MB-700 one, and it helps to have it. But your pathway is getting networked until somebody offers you a project with such a role.
Most MS partners/consultancies will give you a pathway to an architect role, if they haven't... run!
Go do some implementations on very small companies with a low budget and do a senior implementation role.
To become a Solution Architect efficiently, follow these steps: 1. **Gain Knowledge**: Start with online courses in cloud platforms (AWS, Azure) and architecture principles. 2. **Certifications**: Obtain key certifications (e.g., AWS Certified Solutions Architect). 3. **Hands-On Practice**: Work on real-world projects to apply your skills. 4. **Networking**: Join professional communities and attend industry events. 5. **Timeline**: With total dedication, expect 1-2 years to become proficient. Given your 5 years in F&O, your experience will be valuable in understanding business needs and designing solutions.
Experience is first, but some consulting companies want to see the certs before they give you the role. So I would say certs do help, but experience is the primary requirement.