Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I don't know if "Junior" is a useful title. Can the title Jr. Developer be used in a resume? I want to be a good fit for something that is entry level, but still challenging.

Examples: Jr. Web Developer, Jr. Developer, Jr. Software Engineer

share|improve this question

closed as off-topic by MichaelT, Thomas Owens Mar 13 '14 at 16:31

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking career or education advice are off topic on Programmers. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most cases, any answer is going to be a subjective opinion that may not take into account all the nuances of a (your) particular circumstance." – Community, Thomas Owens
If this question can be reworded to fit the rules in the help center, please edit the question.

Are you saying in terms of a job title you held, or for a job you want to find? If I get resumes where people have an objective section, they don't say 'entry', 'associate', nor 'junior' in what they want. – birryree Mar 24 '11 at 17:38
I want to find a Jr OR associate position. I'm not sure what title I've had before. – DisEngaged Mar 24 '11 at 17:44
@FXquincy - In that case, I wouldn't mention you are explicitly seeking junior/associate/entry-level stuff if you are going to have an 'Objective' section. Say what kind of position/work you're looking for, and companies will make their decision about you and where you fit during interviews. – birryree Mar 24 '11 at 17:50
I would eliminate the objective section altogether, it is used only to eliminate people from consideration. – HLGEM Mar 24 '11 at 18:04
@HLGEM - that's why I like it. I want employers to eliminate me if the position doesn't match my objective. It cuts down on poor fit interviews. – Ethel Evans Mar 24 '11 at 19:45
up vote 19 down vote accepted

With the fact that there's no universal standard between what is considered a 'Junior' Developer vs. a Developer vs. A Senior Developer, I would always put Software Developer, even if the position called for a Senior Software Developer. My experience tells them what level I'm at, not a job title.

Shameless Plug: As someone who has spent a lot of time recruiting, interviewing (and being interviewed), and hiring developers, I have quite a few blog posts on the subject of trying to get hired:


Three years after this post has been written, there are a number of tips that will help you determine when you need to put a discerning title on your resume:

  1. What type of Company are you applying to? Is this a 'hacker' oriented company? Are technologists valued? Or are they a means to an end? If it's the former, you don't need to emphasize your title. If it's the latter, you do.

  2. Is it an internal or external recruiter? This tells you a lot about the company. An external recruiter will have a relationship with the company and know what they want to see -- recruiters only get paid for placement. Also, if it's an external recruiter, they likely don't value programmers as much as they probably should. We're tough to hire. It takes knowledge of a company's culture + where they're going in order successfully hire a programmer. An external recruiter looks for the 'right now', and if a company is focused on that, that means they aren't as focused on what really matters.

  3. Are you sending your resume directly to the hiring manager? This is a sign, that unless that manager's title is a business-y title, they [should] know that experience is not always reflected in someone's title.

  4. What is the manager's title? Is it simple? "Team lead", "Tech Lead"? Or does it sound unnecessarily pompous? "Deputy Project Manager for Operations"? The more pompous it sounds, the more weight they put on titles. Plan accordingly.

  5. Dovetailing #4, what are some titles of their employees on Linked In/Glassdoor? Someone from a company that has the title "Chief Rabble Rouser of the Highest Order" (an actual title I've seen) probably doesn't care as much about titles as the aforementioned pompous title.

share|improve this answer

It all really depends on your development experience.

When I was searching for my first job, I put on my resume that I was a developer. Everything is relative, I had dev experience in college and that was clear through the other parts of my resume so there was nothing misleading.

Now, if a previous job position's official title was Jr. Developer, put that. You don't ever want to be misconstrued as trying to mislead a potential employer. Fraud, or the whiff of fraud (intentional or unintentional) will kill any prospects and possibly a new job that you have already started.

share|improve this answer
Programmers will throw people under the bus that don't know their stuff. That's why I'm looking for a position where I won't unintentionally be a fraud. I have a high-level knowledge to get through interviews, but I want to be honest. – DisEngaged Mar 24 '11 at 18:02

Don't mention Jr. Most Recruiters would be smart enough to figure that out from your resume. Your objective section in the resume would satisfy this requirement by specifying the level of career you are seeking i.e entry ,intermediate,senior .

share|improve this answer

If possible, spell the whole word out please. "Junior" may seem a little better than "Jr." as using an abbreviation isn't often a good thing on a resume, at least to my mind. "Junior developer" is fine but "Jr. Dev." may seem a bit too short and could appear lazy in some ways.

share|improve this answer

I would't put Jr. Dev unless even though you have a lot of experience you still consider your skill level to be on par with those of a more junior developer.

share|improve this answer

Yes, I would say. Since recruiters are getting smarter nowadays especially for companies who would want to use the latest technologies available. These companies prefer Juniors for the reason that most of them are into the latest technologies, aggressive, and more importantly, willing to learn and discover new things. An engineer who just graduated oftentimes are well equipped with the state of the art tools than engineers who graduated 5 years ago who failed to to keep themselves updated. So why not if it fits you?

share|improve this answer
Young programmers may be preferred because they are cheaper, but I wouldn't want to work for someone that didn't value experience. – Eric Wilson Mar 24 '11 at 20:51
I just answered the question here i.e. it's ok to use Jr. Developer as a title, I didn't mention anything that these type of companies do not value experience. – eradicus Mar 25 '11 at 2:11
I guess I disagree with the premise that "smarter" recruiters prefer younger developers. I found your answer not helpful. – Eric Wilson Mar 25 '11 at 2:15

Not the answer you're looking for? Browse other questions tagged or ask your own question.