I am surprise nowadays the solution architect title had been abused in such..

p/s: sorry no offence to you, it was mainly the company and industry fault.

Hi, i did saw your early post, no worry wont do silly things like asking questions here, take it easy

Well, normally when one call himself solution architect, he should actually has a very deep and BROAD knowledge of system architecture. He needs a lot of exposure, hands-on and experiences, eventually in the technical side, ability to integrate business idea into a full fledged system design. He also needs to equipped with strong people skills such as coordination, influencing, leadership, interpersonal etc.

In short, it meant to be a lead/managerial/director level position, most of them have people responsibility (which team leads/seniors reporting to him), with probably at least 5 to 10 years of exposure in IT technical/System design/Integration. In fact these are what similar requirement to reach whatever (true) architect position in IT industry.

For a junior which doing system/solution design, usually a much appropriate title would be system designer/analyst/software engineer/solution consultant (hate to say i do not agree that consultant to be use in junior post as well, but sadly this seems to be the trend too...).

Anyway is good for you to be in the same team with those 6-10 years old birds in such a young age. Work hard and absorb their knowledge, very soon you will become a respectable industry expert!