- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Requirements From Software Developer To Software Architect
Posted on 8/16/15 at 9:41 pm
Posted on 8/16/15 at 9:41 pm
What are some suggestions and requirements for a software developer to be elevated to a software architect role? For board members that have experienced this career change, what are some of the pros and cons of being an architect versus a developer?
3
Posted on 8/16/15 at 10:22 pm to RickAstley
Been in the software engineering game as a consultant for a variety of companies for 15 years and these terms are all interchangeable. Most places use "architect" to denote a journeymen level position with enough experience to make high-level decisions in the initial design and decision making process, where as a developer may just stick to writing code and solving problems at a more micro level.
This post was edited on 8/16/15 at 10:24 pm
Posted on 8/17/15 at 7:16 am to RickAstley
An architect has to be able to work in a brightly lit room in front of a whiteboard and wear snappy business casual. He can also use buzzwords fluently. A developer is more comfortable in jeans working in a dark room.
Posted on 8/17/15 at 7:58 am to RickAstley
In the companies I have worked for, Architect generally means more years of experience mostly. An architect, again in my experience, generally creates the initial high-level design will the developer/engineer generally does micro-level coding.
For example I've seen companies do it like this:
Software Engineer/Developer -> Sr. Software Engineer/Dev -> Software Architect -> Sr. Software Architect
Same goes for Infrastructure side:
Systems/Network Admin -> Systems/Network Engineer -> Network Architect -> Sr. Network Architect
Generally the architects had 5-10 years experience at a minimum.
For example I've seen companies do it like this:
Software Engineer/Developer -> Sr. Software Engineer/Dev -> Software Architect -> Sr. Software Architect
Same goes for Infrastructure side:
Systems/Network Admin -> Systems/Network Engineer -> Network Architect -> Sr. Network Architect
Generally the architects had 5-10 years experience at a minimum.
Posted on 8/17/15 at 9:21 am to Asgard Device
Thanks for the reply. What kind of experience would you expect that separates an architect from a developer?
Posted on 8/17/15 at 9:23 am to WavinWilly
quote:
For example I've seen companies do it like this:
Software Engineer/Developer -> Sr. Software Engineer/Dev -> Software Architect -> Sr. Software Architect
This is a progression that my company offers. I am curious though if it is just a matter of years of experience for most companies, or is there certain criteria that the developer most meet to become an architect. What would be the next point beyond Software Architect for that career path?
Posted on 8/17/15 at 9:30 am to foshizzle
quote:
An architect has to be able to work in a brightly lit room in front of a whiteboard and wear snappy business casual. He can also use buzzwords fluently. A developer is more comfortable in jeans working in a dark room.
The terminology doesn't really matter. But, there is a huge difference between the guy who is a great coder and the guy who is capable of seeing the big picture from design to implementation.
There are great coders who will NEVER be capable of doing the latter.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News