Web Engineer or Software Engineer

[evergreean43]

I always wondered if I developed ASP Web applications, Database models and SQL scripts, I should be called a Software Engineer instead of a Web Engineer?

Please advise if ASP Web Development, SQL Server and Oracle Database Development and sometimes developing system scripts would qualify my job title as a Software Engineer and not a Web Engineer which seems to tie the person to web development only.

 

[damber]

Sorry to burst your bubble, but neither, you're not an engineer (not in this context anyway).

Web Developer is probably the most accurate. You develop web applications. Web applications 99% of the time need a database (which includes the SQL scripts) - therefore web developer accurately portrays what you do. Don't confuse this with Web Designer, which is very different, as it's mainly about the aesthetics.

You could push that a little and call yourself a software developer, or web application developer.

There are lots of debates about the word Engineer as it is so often misused.. e.g. refuse engineer (garbage collector), sanitation engineer (toilet cleaner) and so on, just a word used to make a job sound more important than it is, but when used incorrectly makes the employee sound like their faking it and hiding their inadequacies..

Cited in one dictionary as:

a person who uses scientific knowledge to solve practical problems
synonym: Applied Scientist

That seems a bit of a grandiose title for someone who codes everyday web applications.

Other misused titles: Manager, Architect, Consultant

Everyone manages something in their job, if even only their own time. They also generally provide advice or views like a consultant would and some even design things, kind of like an architect... but that doesn't mean you can honestly say you are a manager, consultant or architect, does it ?

Anyway, what's in a name ? Any hiring manager with any reasonable understanding of IT should know the difference. Focus on achievements, skills and experience - and impress with what you are.. not with some made up title that wont actually make your work any better.



A smile is worth a thousand kind words. So smile, it's easy!

 

[Tarwn]

I would agree to a degree...err, moving on.

I actually am in the camp that believes there is and should be a job title called "Software Engineer" even if most certified engineers have a problem with that. However, I think that in order to be able to use that title you need to have a skill set beyond the ability to develop an application.
Engineers basically are applied scientists (as mentioned above), ie, they take theory and apply it. My preference would be to include processes (Software Lifecycle, Documentation and planning skills, etc) in that definition, but apparently that isn't part of the definition.

My official job title is something like "Systems Developer II" in my current organization. Does that mean that if someone else is looking to fill an Architect position, that I wouldn't qualify? Nope. It means that based on what my company requires from the position I am filling and how the meshes with the skillset I currently have, I am a "Systems Developer II". I've also been a Senior Developer, a Project Leader/something technical I've forgotten, once even a VP of Development, and a couple other similar titles.

The most useless title I have had was probably the VP title. While it does get people to remember my resume, it also makes them wonder if they can trust me. Which is why it's the only title on my resume with quotes around it and a second title next to it It's hard to explain that your sales guy (VP of Sales and Business Management) gave you a title to impress people with his own importance that was not related to the size of your skillset, duties, or tasks (I had one subordinate).


So my own thoughts are in line with Dambers, it is not your titles that sell potential employers, it's your skillset and achievements. Overselling yourself with a job title can actually hurt you, as it can cause potential employers to assume you know things you do not, making for a fairly painful fit in a new company as you try to catch up with everything normally associated with an ill-fitting title.

 

[damber]

I actually am in the camp that believes there is and should be a job title called "Software Engineer"

me too - Software Engineer is a valid title, and I have several friends / colleagues that wear that badge with conviction - but they don't develop web applications ;-)

So my own thoughts are in line with Dambers, it is not your titles that sell potential employers,

Thinking about it - maybe a title WOULD sell to some employers - but is that an employer you would want to work for ? And it might get you to the interview, but what do you do then ? If they're of any quality they will soon see that you are not what you initially appeared to be. And even if you get into the role by some fluke.....

making for a fairly painful fit in a new company as you try to catch up with everything normally associated with an ill-fitting title.

A smile is worth a thousand kind words. So smile, it's easy!

 

[damber]

That reminds me... I should really update my CV !

A smile is worth a thousand kind words. So smile, it's easy!

 

[onpnt]

First there are full blown threads on this in forum656 and other water cooler forums...

A few comments from quickly reading through

You could push that a little and call yourself a software developer, or web application developer.

Not really. If you did it would really be pushing it. If your skill set and or job is restricted to web enabled applications be it internal or external you're not a software developer. In order to get into that side of things you should be developing on far more than just a web based platform.

As for engineer everyone is spot on that it is a gray title. There have been heated discussions over people being called an engineer with an engineering degree or certification. Yes, even if you have that ridiculous MCSE cert MS does consider you an engineer. Even knowing that absurd cert can be obtained by any moron given $7000 and a boot camp. Trust me I have one working in our operations grouped and e hasn't a clue on any part of win 2003 which is what his MSCE is for. My last position was titled Systems Engineer. I do not have any certifications or an engineering degree however. I was given the title due to experience. I wasn’t sure if this was correct but I took it without thinking twice about it as I have seen this title can help you in other opportunities. This can only be obtained given the management views of engineering though and experience level along with years of experience. So put that title next to software needs to be far over what you’ve listed there though. You need to go way deeper than some ASP scripts and SQL dev. That is to me no farther than a web programmer. Even saying developer can be a stretch.

After all of that you have to remember the title game is nothing more to me than that. A game! If your employer gives you something like software engineer or the likes and that gets you a higher level job somewhere else I hat to burst your bubble but you may have set yourself up for failure. You will be found to be severely lacking the required skills that a real engineer or developer needs to satisfy the business. That will only hurt your career path then and may take you far longer to get back in line than it took you complaining to your employer to get that title in the first place

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[onpnt]

my job title as a Software Engineer and not a Web Engineer

Honestly you shouldn't even have web engineer from what you've given us. That would mean you are to me doing far more than development. You should be designing the infrastructure, configuring the devices, development and pretty much everything else that lies behind the web environment that your business has.

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[Sheco]

A Real Engineer is a someone that operates an engine.

The engineer manages details like fuel intake, lubrication, cooling, and power output. The engineer is able to diagnose problems that arise with the engine and perhaps even make repairs.

Those people using science to solve practicle problems are just trying to make their job sound more important by misusing the term "engineer.

 

[damber]

http://en.wikipedia.org/wiki/Engineering

Read the etymology section...

A smile is worth a thousand kind words. So smile, it's easy!

 

[evergreean43]

I always thought of software engineer was someone who could develop solutions for databases, systems and web pages.

If someone can develop system scripts using Perl and Unix Shell scripts. Also create SQL scripts and build database models. Develop server side (ASP, J2EE etc..) and client side (JavaScript) languages. And configure server containers such as Tomcat.

The above skills seem to lean toward Web Engineer only???

 

[onpnt]

Everything you listed means nothing more than a Web Developer. Even adding the config of Tomcat really doesn't apply to more than that IMHO

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[Sheco]

en.gi.neer [en-juh-neer]
–noun
1. a person trained and skilled in the design, construction, and use of engines or machines, or in any of various branches of engineering: a mechanical engineer; a civil engineer.
2. a person who operates or is in charge of an engine.
3. Also called locomotive engineer. Railroads. a person who operates or is in charge of a locomotive.
4. a member of an army, navy, or air force specially trained in engineering work.
5. a skillful manager: a political engineer.

–verb (used with object)
6. to plan, construct, or manage as an engineer: He's engineered several big industrial projects.
7. to design or create using the techniques or methods of engineering: The motor has been engineered to run noiselessly.
8. to arrange, manage, or carry through by skillful or artful contrivance: He certainly engineered the election campaign beautifully.

 

[tsdragon]

What's the problem with simply "Programmer". I'm quite proud to be one. I worked for contracting companies for so many years that I'm of the opinion that a job title is entirely arbitrary and meaningless. Mine has been whatever was necessary to get the contract, impress the client, or make the employee feel more appreciated without actually giving them a raise. I've seen egos get prickly over whether one was called a "programmer" or a "senior programmer" even when existed no standard to determine which was which. I conclude the whole area is essentially an ego trip more than a useful designation.

When asked what I wanted on my business card at the last 4 or 5 jobs I've had my reply is "programmer or technical staff", whichever you prefer. I'm not really into titles."


Tracy Dryden

Meddle not in the affairs of dragons,
For you are crunchy, and good with mustard.