My job title is currently Junior Software Engineer.

When I sent out my CV with the title Software Engineer instead, I received a much better response.

If I get offered a role I applied for with that CV, and reference checking comes back with the Junior title, is that likely to lose me the role?

Additionally - If you saw Junior Software Engineer vs Software Engineer on a CV, would it change the type of work, experience, and competence you expected from the applicant?

  • 1
    Lots of related information here (not a duplicate).
    – enderland
    Commented Jul 21, 2014 at 18:07
  • 2
    The word "Junior" in your job title isn't necessarily a bad thing. Have a listen to Hanselminutes #427
    – alroc
    Commented Jul 21, 2014 at 18:07
  • 2
    Nothing wrong with a "Junior" applying for the next rung - particularly if you have a couple of years experience and can show that you have become more independent in your junior role.
    – HorusKol
    Commented Jul 22, 2014 at 0:55
  • 1
    I think this is a very good question. Unfortunately I think the answers are largely conjectural and based on ethics they made up on the spot. You really need an answer from someone in HR who has made this kind of employer-side decision before. Me? as a hiring manager at a startup? I wouldn't care provided you accurately represented yourself in conversation and interview.
    – user1084
    Commented Jul 22, 2014 at 0:59
  • 2
    Are you looking for another junior job, or not? Commented Jul 22, 2014 at 2:41

7 Answers 7


Titles can be important for both you and a potential employer. It benefits you to have a title that realistically shows your current position because it relays what a potential employer can expect from you.

If you CV has your last position as a Junior level and you held that position for a year, a prospective employer will make the assumption that you are still Junior and will put you in a position where you can grown into a more experienced developer. However, if your skillset is still Junior, but you change your title by dropping the "Junior" your prospective employer will have an expectation of your ability and will task you accordingly.

I've seen this play out a couple of ways. When a Junior applies and gets a position that is beyond thier experience to handle, they usually get fired and don't get a good recommendation. The employer will normally attribute this to lying on a CV. This is really the big problem with your approach. If you "reword" or otherwise alter your CV entry to make yourself appear to be more qualified than you actually are, you have committed fraud. This happens more than you'd expect with credentials like CPA, PMP or BS/BA. When someone applies for a job and lies about thier degree or credential they are fired. Nobody wants to have an employee that will lie to them.

The fact is, "Juniors" are in pretty high demand and a "Junior" with some experience can command up to a 10% increase when they switch to a new employer. And, you get the raise without creating a false expectation of your ability or committing fraud. Both really good things!

  • Thank you for a well thought out and ethically sound response.
    – DryShirt
    Commented Jul 21, 2014 at 17:51
  • What happens if your current position is officially Software Engineer, but you only have almost four years of professional experience in total? Are you technically a junior?
    – Ogre
    Commented Jul 22, 2014 at 6:15
  • 3
    @Ogre - The experience required to no longer be a Junior is different for everyone.
    – Donald
    Commented Jul 22, 2014 at 14:22

The answer depends on two factors:

1) If you effectively performed as a software engineer, then you should write something like this:

XYZ Company

Junior sofware engineer (14 Jul 2013-Present) xxx xxxx bla bla bla ... Last sentence: effectively performed the duties of a software engineer within six months of being hired. Salary raised twice. Promoted twice. And you pretty much answered the question ":You had the job title. What did you do with it?" The preferred answer is, of course: "A lot"

There is a downside to telling the truth. On the other hand, there is an upside to saying that you worked your way up from knowing very little, you worked your way up fast and did not let the grass grow under your feet, and you gained the professional trust and respect and respect from the staff and management on the way up. And yeah, you're looking for the money, too.

2) If you did not perform your duties beyond junior level, then you crossed an ethical line and you have a clear resume accuracy problem.


If I get offered a role I applied for with that CV, and reference checking comes back with the Junior title, is that likely to lose me the role?

The outcomes can vary, from no reaction to immediate termination / withdrawal of an offer, but likely it'll be closer to the latter.

It's possible you'll find a company that doesn't care, but I would wager more companies would consider this to be a fabrication of your qualifications and would not consider you for a role. With a large enough number of candidates, it's hard to justify keeping someone in the "in" pile when there are other qualified candidates who didn't embellish their resumes.

Additionally - If you saw Junior Software Engineer vs Software Engineer on a CV, would it change the type of work, experience, and competence you expected from the applicant?

Typically with a junior person in a role, I would expect they'd require more constant supervision, I'd need to review their work more frequently, and I'd need to assign them easier tasks. As time goes on, the amount of each would lessen as I gained more confidence in the employee, until eventually they reach "mid-level" status where I didn't need to give them any special treatment.

So yes, seeing "junior" on a resume would make me wonder whether or not you were ready for a more hands-off role, or whether I'd need to make sure I had enough time to watch more closely.

  • That first part is a little worrying. I had taken an interview with one of those employers, but will cancel now. I had hoped that removing a word was regarded differently to adding one.
    – DryShirt
    Commented Jul 21, 2014 at 18:01
  • 4
    Whether you remove the word or add it, you're still presenting false information on your resume.
    – alroc
    Commented Jul 21, 2014 at 18:06
  • @Adam Is it possible that a "junior" member would be trying to move into a less junior position after learning everything they needed to from that role?
    – kleineg
    Commented Jul 21, 2014 at 19:05
  • @kleineg - yes, of course; it's entirely possible the employee [wants to be / is ready to be] a mid-level and their company is treating them as a junior, so instead of waiting to be promoted at their current company, they're looking elsewhere. However, that informs how you frame your job search ("I'm a junior looking to take the next step at your company!"), but it doesn't change what you put on your resume.
    – Adam V
    Commented Jul 21, 2014 at 19:32
  • Citation please. Because I would totally wager that it's just automated screening caring about the "junior" in phase 1, and human beings who would far value their impression of you in an interview over six characters in phase 2.
    – user1084
    Commented Jul 22, 2014 at 0:57

Job titles vary wildly from company to company. There is absolutely no guarantee that a "junior" in one place is the same as a "junior" in another. Same thing goes for "senior", "staff", "lead", "1,2,3", "3,2,1", or even "VP" (a title which means virtually nothing in this era of fleeting technology start-ups)

If you're talking about certifications and degrees, those are relatively fixed credentials.

I have never heard of anyone getting an offer withdrawn because they failed to very exactly indicate the company-specific title on their resume. No one cares about the difference between a "Associate level 2" and a "Level 1 staff engineer".

On the other hand "junior" usually implies a vague sort of rank, it suggests more than just a meaningless level number. Some people really get hung up on silly inconsequential details, and as you can see, it can cost you the chance.

However, as you noticed, you got more response without the "junior" keyword-- so you might have lost a chance because of that too.


If I get offered a role I applied for with that CV, and reference checking comes back with the Junior title, is that likely to lose me the role?

As always - it depends.

If I were doing your reference check, and I learned that the title you reported wasn't the title you held, I might categorize that as a "lie".

I don't hire people who lie, so that would lose you the role.

In other scenarios (perhaps other hiring managers or other companies), they might not consider this important, and that wouldn't cause you to lost the role.


First of all... and this is covered elsewhere, omitting part of your title to make it appear better will not fly, and I would recommend against it.

However, on your resume you have a chance to list things you have accomplished at that job and roles you have undertaken. Use that to your advantage! People are more likely going to look at what you have done than what you were called when you were doing it. For example in a previous job I was listed as an "analyst" but was in fact a software developer, all of my bullets reflected this and I had no trouble being hired as a developer.

The fact that you are "junior" might make your employer expect to train you and direct you a bit more, however it is possible that if you prove to your prospective employer that you have matured enough in that role you might be hired into a more senior role.

Lastly, if you are at a small company and your boss has a lot of control over your title you may want to work out with them what you can and cannot call yourself when applying for jobs. You may not get permission to move up a level, but if instead of a junior developer you actually did the work of a junior engineer you may want to work something out so that your title and role match better.

  • 1
    +1 - if you write "Junior" but list the dates and achievements/responsibilities, a potential employer will be more considerate than if you omit the "Junior" with the same dates and achievements, and they call for references and find out that you were not entirely truthful about your title. The next question in the recruiter/interviewer's mind is "what else were they not truthful about"
    – HorusKol
    Commented Jul 22, 2014 at 0:53
  • taking "omitting for better appearance" to the next level: assistant to the regional manager -> assistant regional manager -> regional manager
    – Flo
    Commented Jul 22, 2014 at 10:45

I would like to put a slightly different spin on this. I have had a fair number of jobs where the job title was not less senior sounding than I liked, but merely a completely incomprehensible internal name for the role (often very long and abbreviated to some acronym).

My personal opinion on the matter is that the job name you should write on a CV need not be the official job title but should reflect what you actually did. For example if a fictitious job title was "Architect, software, band 3, test" I would feel no issues just writing "Software Architect" or even "Software Developer", or maybe even "Test Engineer" perhaps, depending on what I actually did day to day in the role. I feel the most important part is that the reader of the CV will gain a reasonable and accurate expectation of your role and experiance. Not that they know the precise formal job title.

So if you can in honest and good conscience say an average reader in your field would consider your job to have been "Software Engineer" by all means write it, but it you feel that would truthfully be deceptive or exaggerate your skills unreasonably add junior or some other descriptor to explain that.

As a short test of what would be reasonable, I would say if you feel that if a friend could go to your previous manager and team from the former job and refer to you as a "Software Engineer" or whatever else without annoying them or being rebuked or corrected, or them suspecting you had been deceptive I would consider it OK to put on a CV, otherwise rethink.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .