I run a small startup team and we are about to hire a person who would hopefully take care of testing (writes and executes) and manage our git source code (like a project manager). What do you think would be the best job title to describe this position?

  • whats wrong with Project Manager?
    – Kilisi
    Commented Sep 2, 2018 at 9:22
  • Project managers should be kept as far away from git as possible :-) Let the technical team manage git. Commented Sep 2, 2018 at 9:25
  • 1
    while I disagree with the overly smug attitude of @Phil (git is hard only clever IT ppl can use it ho ho ho) I do wonder about the wisdom of describing a project manager as one who "manages a git repository". You imagine that "tester" would be a more normal description here...
    – bharal
    Commented Sep 2, 2018 at 9:43
  • 2
    You have two non-overlapping sets of responsibility there - there isn't really a job title that covers both. Either go with the "more important" one or just call it "Tester and Project Manager". Although a project manager doesn't really manage code and, as a developer, it's not really clear to me why you need someone to specifically manage your source code (it really makes more sense to have one / all of your developers take responsibility for it). Also, questions asking what the best job title would be are a bit too opinion-based and not really useful to others to be on topic here. Commented Sep 2, 2018 at 11:36
  • 2
    If "managing" the source code, means tagging releases and approving deployments, then "release manager" or "release engineer" are titles I've heard. If this person also does testing, you can say "Testing and release engineer". Commented Sep 2, 2018 at 18:30

3 Answers 3


The normal way to handle git is that the developers manage the source code. Not anyone outside the development team. You will have someone responsible for setting up the repository, setting up permissions, making backups etc., but managing the source code is purely the developers' business.

In a very small company, you might have one person responsible for QA (Quality Assurance) and general IT.


Tester would be my choice.

You can train someone to use git, it's not hard just very dull.

Is harder to train a tester. So find a good tester, and then just train them to use git commands. Although why your developers don't know how to use it is a little odd...

  • Thanks, I think this is what I will do. The responsibility for the source code management will be the developers. Commented Sep 2, 2018 at 13:05

"Test engineer" sounds like a good start. It's basicly the default title for someone writing and executing software tests.

If you want it to sound very important you could go for "quality management officer", but that title usually involves making sure that a product meets quality standards set by norms, standards and laws (for example in medical products).

In your case "code quality manager" could be a compromize between the non-technical "quality management officer" and the more technical "test engineer".

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