software engineer, architect, consultant. QA. ?

Express the business side of your digital lives. Share your experiences and/or your comments regarding a business or organization.

No advertising.

Moderator: General Moderators

Post Reply
jmut
Forum Regular
Posts: 945
Joined: Tue Jul 05, 2005 3:54 am
Location: Sofia, Bulgaria
Contact:

software engineer, architect, consultant. QA. ?

Post by jmut »

Hi,
I am just looking for some meaningful explanation of those positions: software engineer , software architect, software consultant, quality assurance.
What are these positions concerning...what's one responsibility...and what it takes to become one.
User avatar
feyd
Neighborhood Spidermoddy
Posts: 31559
Joined: Mon Mar 29, 2004 3:24 pm
Location: Bothell, Washington, USA

Post by feyd »

Engineers deal in the nitty-gritty. Architects deal in the overall design, more than the micro-level details. Consultants are often temporary, hired experts; they generally deal with specific pieces, but can be engineers or architects. Quality assurance people are basically testers; they make sure the product lives up to expectations and is solid enough for public use.

Technically, it takes almost nothing to become any one of those positions. Whether a company believes you, that's a different story. That's where your experience, work ethic and résumé/recommendations come in. Companies may have a variety of levels they expect for a position. Unfortunately, there is no norm that I know of.
jmut
Forum Regular
Posts: 945
Joined: Tue Jul 05, 2005 3:54 am
Location: Sofia, Bulgaria
Contact:

Post by jmut »

Yep I guess.
There are some standards like ISO something that recognize you as QA I think...or at least partly..but donno.
I mean it is hard to write code beyond age 30 I think. One starts thinking of a position where other responsibilities are required other than writing source code for life.
User avatar
feyd
Neighborhood Spidermoddy
Posts: 31559
Joined: Mon Mar 29, 2004 3:24 pm
Location: Bothell, Washington, USA

Post by feyd »

jmut wrote:I mean it is hard to write code beyond age 30 I think. One starts thinking of a position where other responsibilities are required other than writing source code for life.
I know plenty of programmers over 30 who are still simply developers, nothing more.
User avatar
CoderGoblin
DevNet Resident
Posts: 1425
Joined: Tue Mar 16, 2004 10:03 am
Location: Aachen, Germany

Post by CoderGoblin »

jmut wrote:Yep I guess.
I mean it is hard to write code beyond age 30 I think. One starts thinking of a position where other responsibilities are required other than writing source code for life.
Strongly disagree with that comment. Often you start as a software engineer/programmer (I'll stick with programmer here) and the only option for pay advances is to become "management" which is not a situation I agree with. Not all programmers make good managers and vice versa. Its a bit like saying all programmers make good web designers. Being good at any job often means learning new things so life should never get boring. The main point is getting a feeling of satisfaction from your job whatever you do. Take a look at the site cssplay.co.uk. The writer is in his 60's.

To answer the question though I feel most of those position "labels" are a matter of experience, although feyd defined the basic logic behind the names. Coming straight of of uni or college is one thing. Learning how to do things is the real world is another just as you learn to pass a driving test then learn how to survive driving everyday. Also bear in mind a lot of company personnel departments use labels like this to pigeon hole people and determine pay scales.
Post Reply