What job title should I give myself (software engineer)
03-22-2007, 07:04 AM
#1
Burning Brakes
Thread Starter
Join Date: Dec 2004
Location: Boston MA
Age: 44
Posts: 1,078
Likes: 0
Received 0 Likes
on
0 Posts
What job title should I give myself (software engineer)
I need a job title for resume purposes...
Some background --
I'm a software engineer, 5 years experience...
I work for a startup (about 20 ppl now)...There are 4 developers, plus the cto (who does some dev work). Each developer is working on a different product, but most products have common code between them.
Alot of ppl have inflated titles..like the director of marketing, the manager of customer service, and the manager of software quality assurance all have 0 ppl working under them...that may change as we hire more ppl, but right now they're the manager/director of absolutely no one...
I need to fill out the title portion of my resume (so I can give it to someone)...I dont have an official title, my boss (the cto) doesn't really care what we call ourselves...Whatever title is on my resume won't get back to my employer to accept or reject...I'm looking for a nice, yet honest title...
The most obvious title is
Senior Software Engineer...
Would it be okay to call myself a Software Architect instead? In a sense I am the architect because I make all the design decisions for the product I'm working on, except when it comes to the use of the common code. But then there's no-one working under me, and in most situations an architect has peons below them..Also its not like a 1 person software program is going to have complicated architecture...
Likewise, it would be nice to call myself a software lead, since I am the lead engineer on the areas I work on...but again, I have no one under me so is that okay?
Any opinions? other useful titles I could call myself?
Some background --
I'm a software engineer, 5 years experience...
I work for a startup (about 20 ppl now)...There are 4 developers, plus the cto (who does some dev work). Each developer is working on a different product, but most products have common code between them.
Alot of ppl have inflated titles..like the director of marketing, the manager of customer service, and the manager of software quality assurance all have 0 ppl working under them...that may change as we hire more ppl, but right now they're the manager/director of absolutely no one...
I need to fill out the title portion of my resume (so I can give it to someone)...I dont have an official title, my boss (the cto) doesn't really care what we call ourselves...Whatever title is on my resume won't get back to my employer to accept or reject...I'm looking for a nice, yet honest title...
The most obvious title is
Senior Software Engineer...
Would it be okay to call myself a Software Architect instead? In a sense I am the architect because I make all the design decisions for the product I'm working on, except when it comes to the use of the common code. But then there's no-one working under me, and in most situations an architect has peons below them..Also its not like a 1 person software program is going to have complicated architecture...
Likewise, it would be nice to call myself a software lead, since I am the lead engineer on the areas I work on...but again, I have no one under me so is that okay?
Any opinions? other useful titles I could call myself?
03-22-2007, 08:32 AM
#2
Senior Moderator
SSE works for me... I usually use the old P/A (programmer/analyst) title but it says software development specialist on my business cards (and resume).
03-22-2007, 08:38 AM
#3
Senior Moderator
iTrader: (2)
Join Date: May 2000
Location: where the weather suits my clothes
Age: 55
Posts: 27,921
Received 1,080 Likes
on
661 Posts
Honestly it doesn't really matter what the title is. As you mentioned your boss really doesn't care, as do the people reading your resume.
Make sure you focus on the meat of your resume, your responsibilites AND most importantly quantify your importance to the organization.
Saying "I programmed XYZ system and it was a big success" means nothing and will probably get your resume tossed in the same pile as all the other applicants.
Saying, "the XYZ application improved employee productivity by 25%, was delivered under time and under budget and will save the organization $25,000 in training costs" is what recruiters want to see.
Make sure you focus on the meat of your resume, your responsibilites AND most importantly quantify your importance to the organization.
Saying "I programmed XYZ system and it was a big success" means nothing and will probably get your resume tossed in the same pile as all the other applicants.
Saying, "the XYZ application improved employee productivity by 25%, was delivered under time and under budget and will save the organization $25,000 in training costs" is what recruiters want to see.
03-22-2007, 09:04 AM
#4
Suzuka Master
NSXNEXT has hit the nail on the head. Don't just say what you did, say what it impacted, how you were on time completed vs time allowed, and give some statistics behing it (solid stats).
Employers want to see IMPACT, not just a bland statement.
Hell, titles really don't mean much anyways, I have about 5 of them in my job, and they are all valid titles.
For example, my official Air Force career title is-
F-15/A-10/U-2 Communication, Navigation, and Penetration Aids Systems Journeyman
But really I'm just an Avionics Specialist, or Spec for short.
Sounds cool, but in reality it's not that complex. So go with whatever you choose, as long as it's within a realistic boundary.
Employers want to see IMPACT, not just a bland statement.
Hell, titles really don't mean much anyways, I have about 5 of them in my job, and they are all valid titles.
For example, my official Air Force career title is-
F-15/A-10/U-2 Communication, Navigation, and Penetration Aids Systems Journeyman
But really I'm just an Avionics Specialist, or Spec for short.
Sounds cool, but in reality it's not that complex. So go with whatever you choose, as long as it's within a realistic boundary.
03-22-2007, 09:31 AM
#5
Senior Moderator
iTrader: (2)
Join Date: May 2000
Location: where the weather suits my clothes
Age: 55
Posts: 27,921
Received 1,080 Likes
on
661 Posts
Originally Posted by saiko_cl_duck
F-15/A-10/U-2 Communication, Navigation, and Penetration Aids Systems Journeyman
But really I'm just an Avionics Specialist, or Spec for short.
Sounds cool, but in reality it's not that complex. So go with whatever you choose, as long as it's within a realistic boundary.
But really I'm just an Avionics Specialist, or Spec for short.
Sounds cool, but in reality it's not that complex. So go with whatever you choose, as long as it's within a realistic boundary.
I really don't wanna know.
Trending Topics
03-22-2007, 12:31 PM
#8
Smoke free since 2/26/07
Originally Posted by CLpower
I'm about to go from Account Executive to Regional Senior Manager 
(just a title change)
(just a title change)Congrats man...I remember reading a while back that you weren't happy with Xerox. I guess everything did work out in the end huh? Good for you. Are you responsible for the Ontario area? That's where my company is based out of.
03-22-2007, 02:58 PM
#9
Senior Moderator
Originally Posted by saiko_cl_duck
NSXNEXT has hit the nail on the head. Don't just say what you did, say what it impacted, how you were on time completed vs time allowed, and give some statistics behing it (solid stats).
03-22-2007, 03:06 PM
#10
Moderator Alumnus
Originally Posted by Slinks
I need a job title for resume purposes...
Some background --
I'm a software engineer, 5 years experience...
I work for a startup (about 20 ppl now)...There are 4 developers, plus the cto (who does some dev work). Each developer is working on a different product, but most products have common code between them.
Alot of ppl have inflated titles..like the director of marketing, the manager of customer service, and the manager of software quality assurance all have 0 ppl working under them...that may change as we hire more ppl, but right now they're the manager/director of absolutely no one...
I need to fill out the title portion of my resume (so I can give it to someone)...I dont have an official title, my boss (the cto) doesn't really care what we call ourselves...Whatever title is on my resume won't get back to my employer to accept or reject...I'm looking for a nice, yet honest title...
The most obvious title is
Senior Software Engineer...
Would it be okay to call myself a Software Architect instead? In a sense I am the architect because I make all the design decisions for the product I'm working on, except when it comes to the use of the common code. But then there's no-one working under me, and in most situations an architect has peons below them..Also its not like a 1 person software program is going to have complicated architecture...
Likewise, it would be nice to call myself a software lead, since I am the lead engineer on the areas I work on...but again, I have no one under me so is that okay?
Any opinions? other useful titles I could call myself?
Some background --
I'm a software engineer, 5 years experience...
I work for a startup (about 20 ppl now)...There are 4 developers, plus the cto (who does some dev work). Each developer is working on a different product, but most products have common code between them.
Alot of ppl have inflated titles..like the director of marketing, the manager of customer service, and the manager of software quality assurance all have 0 ppl working under them...that may change as we hire more ppl, but right now they're the manager/director of absolutely no one...
I need to fill out the title portion of my resume (so I can give it to someone)...I dont have an official title, my boss (the cto) doesn't really care what we call ourselves...Whatever title is on my resume won't get back to my employer to accept or reject...I'm looking for a nice, yet honest title...
The most obvious title is
Senior Software Engineer...
Would it be okay to call myself a Software Architect instead? In a sense I am the architect because I make all the design decisions for the product I'm working on, except when it comes to the use of the common code. But then there's no-one working under me, and in most situations an architect has peons below them..Also its not like a 1 person software program is going to have complicated architecture...
Likewise, it would be nice to call myself a software lead, since I am the lead engineer on the areas I work on...but again, I have no one under me so is that okay?
Any opinions? other useful titles I could call myself?
If you are able to set your own title, I would tailor it to what the other company is looking for.
If they want a software engineer, then use that as your current title and if they want a software architect, then use that. It will give you an advantage when someone is quickly going through a stack of resumes
Thread
Thread Starter
Forum
Replies
Last Post
BlkTxAcuraTypeS
Member Cars for Sale
3
10-18-2015 08:05 PM
asahrts
Member Cars for Sale
0
09-04-2015 05:55 PM
Charlespsu
2G RDX (2013-2018)
3
09-02-2015 09:54 AM
