What does the Solutions Architect career path look like?

Here's the path I've taken in almost ten years (a combination of the two):

Developer->Analyst->Senior Analyst->Senior Developer->Lead Developer->Consultant->Senior Consultant->Principal Consultant (solutions architect)->Business Owner->Training instructor + Principal Consultant = Mentor

It seems to be working so far. Your mileage may vary.

Michael Earls
The Cerebral Kitchen

What is your definition of Solutions Architect? Microsoft has one here:

http://www.msdn.microsoft.com/architecture/shareideas/share_certified/

From your two different paths, I'm not sure I understand what you might mean by the term.

I missed the link you had to the same URL I posted, so I'm curious how your Consultant Track works out. Maybe I'm keying too much on the Manager entry in that path ...

This seems significantly at variance from my experience. Having worked both on the consulting and developer track, I see managing as completely orthogonal to becoming a solutions architect. Developers and consultants either take a management track or a solutions architect track. Some architects later manage other architects, but developers who choose the management track never become architects.

Every time I've seen someone go into management, they're done with technology. This may not be true with everyone, but it's been my experience. A solutions architect (if we're sticking with Microsoft's definition) must possess deep pockets of technical knowledge as well as a broad understanding of many technologies and approaches. I don't think many people could go from management to a solutions architect and meet those criteria. At least, not without first becoming a developer again to refresh/catch up.

I am trying to get more details from the community versus the content we have here at Microsoft. The two tracks I presented are intentionally contentious so hopefully I evoke a strong enough reaction for people to reply.

One of the things I plan on doing this fiscal year in Architecture Strategy is to reach out to the number of developers / consultants that find architecture useful but don’t have the typical formal background of most solutions architects. The level of effectiveness will ultimately come from understanding what the career paths look like and how to tailor the content to reach the different stages along the way.

The big question from a developer standpoint is where do they get to know the business and learn some of the soft skills required for the role if not from a management posting? The title architect internally at Microsoft is very difficult to attain and normally entails a high degree of leadership elucidated through varying degrees of management postings. Now I know this isn't the norm for the community hence my request (plea) for more information.

If you would like to elaborate on your career path and / or share your CV with me that would be much appreciated.

markba@microsoft.com

Spoken like a true Solutions Architect. I like the fact the SA is at the top of the totem pole. lol.

If your intention was to poke fun at the assumption that I think the only architects are solution architects, then you may have missed the point. First off, the title was what does the career path of a "solutions architect" look like. Not what does the career path of an architect look like.

I wanted to know if you was doing your Architecture Course at University after you've done the seven year dgree course can you go straight into becoming a solutions architect and when doing the 2 year work experience within the University course do you have to do your work experience with a solution architect or can you do it with a normal architect firm. plus do you have to go throught the process like it shows above because i don't want to go through that way.

my email address is onaiksingh@gmail.com can anyone get back to me a.s.a.p.

Thank you

I do not really agree on the path that a Solution Architect may follow to achieve knowledge enough to be consider a SA, unless you just wnat to be consider a Software Solution Architect, but I think that a SA must have wider vision of the IT needs, SW is just a part of the hole, and usually it rest on hard and cold requirements definitions, i think AS must be the bridge between business and IT (as someone mention in some URL) that is why the path must include not only development side but infrastrucutre side, business side, consulting side, and a lot of market needs vision...

mine was something like this:

Project Engineer--> SW Solutions Specialist--> pre sales Specialist-->Project Manager--> HW Solutions Specialist-->Consultant-->Senior Consultant-->Datacenter and Telco Consultant-->Solutions Architect

Jcampos...
jairo_campos@yahoo.com

Senior UNIX and Network Adminstrator -> UNIX Architect -> solutioning architect
isn't that simple

I think that personality type is the key factor to be a SA. Plus you have to technically strong with management skills to provide solutions to the projects. I don't think we can define a definite carrier path for SA but definitely it needs lots of experience on all area and knowing the latest technology available or trend IT is going towards and be able to provide multiple options to move to successful end solutions by reducing cost and aligning business goals with IT goals.

Ten years may be too long to become a SA. What about if someone is brillant to learn multiple technologies and grasp the business vision quickly. I would like to hear if any people managed to become a SA from a developer within 5 years. Please share your experience.

I can speak from experience here that ten years is more of a guide than a rule. My first architectural title came at the tender age of 25 working on a $100 million bank project in Australia. Before that, I spent a few years in research and realized that a lot of those skills would be highly applicable to the business world.

Any person with the drive and intellectual capacity could easily skip ahead just as they do in most other endeavors.

Wow Mark...what is an amazing experience at age of 25. Can you share a bit of about your education background, learning curve of various technologies and how many companies you worked for?

Thanks in advance.

I'll post my bio up on the Microsoft Certified Architect website sometime in the next week. They've asked for it a few times so this should accomplish two tasks at once.

Quick snippet from my role hire email: (yes, I'm lazy and didn't type up something new)

Mark Baciak has been in the computer industry for over a decade working on a wide range of technologies during that time. His career starting off doing satellite and terrestrial communications for maritime vessels and eventually evolved into programming after being challenged to re-write a sat-comm protocol that was highly error prone. After that, he started working on software for the credit card, cruise, and hotel industry pioneering many new technologies now present in those industries. From there he worked at Hughes for a short time before moving to Avio, a medical software firm, doing R&D. One of Avio’s research partners was Microsoft Corporation and after Avio was bought he decided to see what MS was all about. The first stay here was short, working for CIT doing a research project on the inner workings of Siebel before moving on to Australia for a year as a Global Technical Architect. Once back from Australia, he resumed his career at Microsoft working in Windows and the Alchemy group before coming to Architecture Strategy.

My path:

Analyst>Operations & Help Desk Manager>Project Manager>IT Director>Solutions Architect

I Agree with Jairo Campos , its more to do with the knowledge level and how much you can understand the business problem.
In my case it has taken me arround 7-8 years to be a Solution Architect.

Trainer/Developer>Developer & Analyst >Team Leader>Project Manager> Technical Consultant>Solution Specialist>Solution Architect.

For me I have transitioned to a SA in 13 years of being in IT.

technical support>system administration>systems engineer>sr. engineer/mananagement/lead>solutions architect

will doin an MBA help to become a solution architect??

I have stumbed across this informative post as I have been investigating the pathway so I can become involved as a solutions architect. My career path has started off in very hands on roles, creating technology solutions for large telco companies and television/broadcast companies. As has been mentioned in this there is also the need to be aware of the business side of things to understand the business cases. I have taken 6 years to get here however this has been due to changing companies since it is difficult to first know what you want to do and get into the company that will support this type of experience. I'm completing a CCNP to get more knowledge in terms of networking / solutions and completing business courses and reading on industry to better untderstand things from that front. I'm excited to see where this will take me in a year or two down the track.

In my case it has been exactly 9 years to get to SA. I started my career as Programmer Trainee --> Developer --> Sr Developer/Team Lead --> Technical Manager --> Solutions Architect

Mark, your blog is a good thought provoker! Thanks to all the Archs out there !

The term Solution Architect can be interpreted in different ways as is evident from the above comments by virtue of individual experiences(due respect and credit). There are two questions to be answered here. 1. Who is a solution architect. 2. What does his career path look like.
A Solution Architect must possess deep technical knowledge on well known and well embraced technologies, and have a broad understanding of diverse technologies, current and cutting edge. In addition, he should have been exposed to various verticals/domains from which he can interpret business problems and devise technical solutions which are beneficial for the business not only currently, but also 'x' years in the future. He should also possess good thought leadership for driving solution adoption (biggest challenge Ive seen so far!).

My career has taken the following course:
Programmer->Programmer/Analyst->Team Lead->Assistant Manager->Consultant->Senior Consultant->Business Analyst->Integration Analyst->Integration Architect->Solutions Architect.

In my opinion more important than the deep knowledge in the technology is the ability to know a bit of everything, be always updated about new technologies, be able to learn fast and the most important, be able to put everything together and provide the best solution to any problem. And no, is not always about technology, is about organization, is about budget, is about people which have to operate it afterwards.

My career path:
Programmer/Teacher->System/Database Administrator->Fixed Network Designer->IP Network Designer->LAN Manager->Solutions Architect

I’m 27 now and have 10 years of experience. I did Electronic and Telecommunications Technical studying and a Cisco CCDP/CCNP certification.

Which track to take?

I'm an SA. My background was in a small organization wearing many hats until I moved to consulting. On my way to the SA role I was a network admin, desktop support, a programmer, a systems analyst, a webmaster, a tech manager, a director of IT, a VP of IT, a CIO and an IT PM.

I essentially created an IT department; EA, systems, people, policy, etc. from the ground up with next to no budget in a highly regulated and slim margined industry. Our small company produced higher net income than most of our large competitors and had all of the same technology, which is why we were acquired for a hefty price.

I have an undergrad in management and an MBA with an IT concentration. I’m studying for the PMP certification now.

To be an effective SA, you need a broad background in delivery of technical solutions to address the challenges of a business. You are involved in politics, you must communicate effectively - with BOTH business professionals AND technical staff. You are essentially a builder - a technology solution provider. You work with the business to craft a solution to a problem they are encountering.

It’s hard to say which “track” to take, but here is my 2 cents…

1. Get your MBA. Businesspeople respect those three little letters that cost you $40,000. More importantly, you will draw on what you have learned in the MBA program when communicating with C-level executives and defining your solutions. The MBA does not teach you a finite “bucket” of knowledge that you draw from (half the stuff you will forget in a few years anyway). A good MBA program will teach you a way of thinking and approaching problems – this is what you are really paying for. This is also how you learn to research your life away…
2. Work in higher visibility IT roles; director level or above. This is where you learn your political savvy, your understanding of using IT to address business challenges, and hone your communication.
3. Sign up for project work. Serve as PM or development lead on high visibility / high impact projects. When you are working on a project, you are essentially engaging in implementing a solution to a problem. Get a PMP certification if you can.
4. Stay current in technology. A year might as well be a century in IT. Always stay current on technology, its use, different methodologies, approaches, etc.
5. Try to get a job in an organization that is known for its SAs typically a large IT consulting firm.

I am reminded of the adage; “Leaders aren’t born, they are made”. The same can be said for SAs, but there are some personality tendencies that I personally have identified. They are;

1. Builders – these are people who are most gratified when “building”, whether it be building a network from scratch or a program from scratch we get bored easily with the same work day to day. We typically build, and move on, build, move on…
2. Problem Solver – do people come to you when they have a problem? If you are able to take a very complex and substantial problem and break it down into meaningful “bites” to craft a solution, you are a problem solver.
3. Effective Communication – SAs rely heavily on communication. We translate “business” language to “technology” language.
4. Technology Generalists – remember SAs don’t typically roll up their sleeves and actually do the programming, although the ones who have programmed in the past gain the respect of their programming team members much easier. An SA will typically have multiple lead developers reporting up to them in a project environment. So, don’t get TOO good and any one thing (other than building and problem solving!). SAs are typically generalists that draw on a broad range of expertise.

Oh, and I just turned 32.

Type "A" personality.....NAH!!!!

My track:

(Junior / Medior) Software Engineering / Computer Science lecturer (university) -> Systems Analyst -> Project Manager -> Software Architect -> Requirements Manager -> Solutions Architect.

Took me approx. four years (of *hard* work) from A to Z. I am now 31 years old, have a computer science degree (cum laude) and several certifications (SUN Java, Prince2, DSDM, Corba, DCOM).

Things especially went fast when I started working as a Software Architect, Requirements Manager and Project Manager for a very large and prestigious IT program (+/- 60 projects). Within this context, I assisted the Program Manager in identifying and defining new projects, as Project Manager I was responsible for initiating and managing several new (smaller) projects, as Requirements Manager I was responsible for a correct requirements elicitation and management process (within which I participated for several projects), and as Software Architect I was responsible for the high-level Architecture (conceptual designs etc.) within several projects.

Adding all these things up has made me a Solutions Architect I think.

I am a generalist with in-depth knowledge of several technical areas, learn fast, top-down approach, am more interested in concepts than in tools, technology, details, etc. (although these are the things that bring concepts to live).

If I weren't a Solutions Architect, I would do something in science / research.

FYI - mine looked like this.....

PC Support>Network Support>Network Manager>Operations Manager>Technical Operations Manager>Project Manger>Solutions Architect!

Ok so I start my new job as a solutions architect at the end of this month.. I'm 26, and live in Durban South Africa... I work for the largest IT outsource company in the country, in our regional office here...

my track looks like this

Developer (Contract) > Network Support > Business Owner > Senior SQL DBA > Solutions Architect

I don't have a degree, but I started my own company doing software development when I was 19, and ran that for 5 years with a partner. That company is still going, and my partner is still paying me out :)

Learn a lot doing everything yourself. Most of the software that we developed was an integrated debtors, stock and service application, primarily for the copier industry. A couple customers ditched Navision for it.

Also did some RFID apps as well. One particular app was used as a demo/pilot project app that has been used on factory floors of most major motor manufacturers, and also in various mines, within South Africa.

Did some good work on key accounts in the region, and due to being a loud mouth and being opinionated got noticed. Also taking advantage of circumstance, our solutions team went from 4 to 1 in the space of a month, for various reasons.

I'm a very quick learner, and can think on my feet. Don't have a degree, but am a member of Mensa :)

Your comments have all been extremely helpful everyone and even interesting too! This position is fascinating to me and I am just wondering where you all think the best and most accurate place to learn and keep updating yourself regarding the most up to date technologies. And also, if I wanted to hire an SA, where would I look? Should I be searching consulting firms or analysts or developers? Or simply finding individuals with the intellectual capacity and drive to build and problem solve?

Thank you all for your input.

I followed this path in about 8 years in industry:

Company1: Consulting Analyst->Consultant->Sr. Consultant
Company2: Solutions Development Engineer -> Sr. Solutions Development Engineer -> Lead Developer -> Development Manager -> Solutions Architect.

I think the key was to combine deep knowledge of my company's software while also maintaining responsibilities of a customer-facing role as Dev Manager, within a growing company.

web designer -> web developer -> system analyst -> Project Manager ->Solutions Architect.

Having perused this blog i find it amazing that people would just like to jump on the bandwagon as a Soltuions Architect.

All i can say about the career path is that you end up being between a rock face and a hard place as you are the go between. Customers don't trust you due to your involvement with contracting company & vice versa.

Sure the career path dictates that you gather and intepret a lot of information but the crucks of the matter is having the ability to intepret the business requirements into a business solution whether it is IT or Business related, doesn't matter this is only achieved by experience. Sure you can go and study for it but with out the business background you are a junior and only as you grow with experience do you get to the final zone.

Path followed.
Systems Engineer>Senior Systems Engineer>Consultant>Solutions Architect

Solution Architect my carrer path

Sofware Engineer > Sr software engineer> Pr
engineer> tech lead> Sr software Architect>
sr dev lead manager> Solutions architect

I am 38 years old now and I have seen it and
done it all

mine is Lecturer>Quality Analyst>Quality Manager>Requirement Manager> Engagement Manager> Solution Architect

Is it possible those who gravitate faster towards becoming SA have natural strengths that lend themselves nicely to the role?

Any SA's care to put forward there Strengthsfinder 2.0 results?

Career path is one view, personality traits may be another, but I suspect we'd see a strong correlation of 5-7 core strengths amongst respondents.

Mine are Command, Ideation, Learner, Analytical, Maximizer, and Relator.

In any career Path there are two roles: Individual Contributer and Management Roles

Solution Architect Fits into Individual Contributer role.

Nature of organisation and Business effects the career progression for this role.

Hirerchiely, Few Steps here or there, the profile remains the same with changed domain.

I would like to enter into this field of SA..i have done my graduation in commerce and an MBA..i would like to know ..whether not having a technical background affect my growth in the field of SA

Mine was something like this:

PC and Network Support -> Network Administrator -> Technical Support Specialist -> Freelance Consultant -> System Engineer/Subject Matter Expert -> Solutions Architect

Overall approx 10 years...

mine is
helpdesk > system admin > specialist > team lead > principal engineer > solutions architect.

but personally i always thought specialist are smarter than solutions architect becos in my previous job many solutions acchitect will consult to specialist to ask for advise before they execute their tasks. So i always thought specialist know better in terms of hands on experience, but if solutions architect without much experience than will be in trouble bcos they dun really have hands on experience on the real sw/hw

cheers

Hi guys,
this is my path:
Developer -> Sr Developer -> System Analyst -> Sr System Analyst -> Team Leader -> Project Manager -> Systems Architect -> Solutions Architect and next Enterprise Architect.

I started about 14 years ago. I've these certifications:

ITIL Foundation Certified
Sun Certified Enterprise Architect for Java(J2EE) Technology (SCEA)
Sun Certified Business Component Developer for J2EE 1.3 (SCBCD)
Sun Certified Web Component Developer for Java (SCWCD)
Sun Certified Java Programmer 1.4 (SCJP)
Sun Train-The-Trainers(T3) for Java - Instructor Java
IBM Certified Object-Oriented Analysis and Design with UML
IBM Certified WebSphere Application Server Administration

And Bachelor in Human Sciences(Teach Math and Bio), post-graduate in Enterprise Solution Provider in Java/J2EE.
In this moment I'm taking a Master's degree: Master of Science in IT (Information Security) at University of Liverpool (UK).

My next certification is Project+, as starting/training to PMP as I was approved by PMI in the first "phase" for the PMP certification.

Moreover, I've plan to take TOGAF and Prince2 certification next year.

Another Master degree in Australia called Enterprise Architect and finanlly a Ph.D if was possible.

I'm 33 y.o now(26/10/2007).
Then I want to retire as Enterprise Architect, as the salary isn't so bad. I don't wish a PM position/role, you get a lot of trouble and stay away of the technology.

Best Regards,

Adilson Dias

Hi Guys,

Recently i have been offered a position of Senior Solutions architect with one of the well know s/w company.

My career path had been as follows:

Engineer->Sr. Engineer-> Tech Lead -> Senior Tech Lead -> Project Manager (Changed to management role) -> Sr. Project Manager -> Sr. Solution Architect (New role offered).

Though I have changed my role in between from technical to management but being in a product company, I as a manager am hands on with the technology.

My biggest USP (as per my employer) had been that in my 11+ years of career i have worked with multiple technologies like Wireless, VOIP, IMS, Network Management. Due to which my employer chose me as Sr. Solution architect.

Personally i like technology and i like proposing end 2 end soltions to customers (i have done many in the past), every thing looks good but i would like to have a second opinion from the community that is it right and is there a growth in this path.

Cheers,
TM

What you just drank? The kool-aid...that's what