Job Title for a person who writes tests and manages source code? [duplicate]

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
-1
down vote

favorite

This question already has an answer here:

• 
  How do I choose an appropriate job title?
  
  3 answers
  
  

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?

startup title

share|improve this question

asked Sep 2 at 9:09

user2022716

81

marked as duplicate by Philip Kendall, gnat, Dukeling, Community♦ Sep 2 at 13:06

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  whats wrong with Project Manager?
  – Kilisi
  Sep 2 at 9:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
  – Philip Kendall
  Sep 2 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
  Sep 2 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.
  – Dukeling
  Sep 2 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".
  – Chan-Ho Suh
  Sep 2 at 18:30
  

  
  
  
  

 | 
show 3 more comments

up vote
-1
down vote

favorite

This question already has an answer here:

• 
  How do I choose an appropriate job title?
  
  3 answers
  
  

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?

startup title

share|improve this question

asked Sep 2 at 9:09

user2022716

81

marked as duplicate by Philip Kendall, gnat, Dukeling, Community♦ Sep 2 at 13:06

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  whats wrong with Project Manager?
  – Kilisi
  Sep 2 at 9:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
  – Philip Kendall
  Sep 2 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
  Sep 2 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.
  – Dukeling
  Sep 2 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".
  – Chan-Ho Suh
  Sep 2 at 18:30
  

  
  
  
  

 | 
show 3 more comments

up vote
-1
down vote

favorite

up vote
-1
down vote

favorite

This question already has an answer here:

• 
  How do I choose an appropriate job title?
  
  3 answers
  
  

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?

startup title

share|improve this question

asked Sep 2 at 9:09

user2022716

81

This question already has an answer here:

• 
  How do I choose an appropriate job title?
  
  3 answers
  
  

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?

This question already has an answer here:

• 
  How do I choose an appropriate job title?
  
  3 answers
  
  

startup title

share|improve this question

asked Sep 2 at 9:09

user2022716

81

share|improve this question

share|improve this question

asked Sep 2 at 9:09

user2022716

81

asked Sep 2 at 9:09

user2022716

81

asked Sep 2 at 9:09

user2022716

81

81

marked as duplicate by Philip Kendall, gnat, Dukeling, Community♦ Sep 2 at 13:06

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

marked as duplicate by Philip Kendall, gnat, Dukeling, Community♦ Sep 2 at 13:06

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  whats wrong with Project Manager?
  – Kilisi
  Sep 2 at 9:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
  – Philip Kendall
  Sep 2 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
  Sep 2 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.
  – Dukeling
  Sep 2 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".
  – Chan-Ho Suh
  Sep 2 at 18:30
  

  
  
  
  

 | 
show 3 more comments

• 
  
  
  

  
  

  
  
  
  
  
  

  
  whats wrong with Project Manager?
  – Kilisi
  Sep 2 at 9:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
  – Philip Kendall
  Sep 2 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
  Sep 2 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.
  – Dukeling
  Sep 2 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".
  – Chan-Ho Suh
  Sep 2 at 18:30
  

  
  
  
  

whats wrong with Project Manager?
– Kilisi
Sep 2 at 9:22

whats wrong with Project Manager?
– Kilisi
Sep 2 at 9:22

Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
– Philip Kendall
Sep 2 at 9:25

Project managers should be kept as far away from git as possible :-) Let the technical team manage git.
– Philip Kendall
Sep 2 at 9:25

1

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
Sep 2 at 9:43

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
Sep 2 at 9:43

2

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.
– Dukeling
Sep 2 at 11:36

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.
– Dukeling
Sep 2 at 11:36

2

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".
– Chan-Ho Suh
Sep 2 at 18:30

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".
– Chan-Ho Suh
Sep 2 at 18:30

 | 
show 3 more comments

3 Answers
3

active

oldest

votes

up vote
1
down vote



accepted

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.

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

add a comment | 

up vote
0
down vote

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...

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

up vote
0
down vote

"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".

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

add a comment | 

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
1
down vote



accepted

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.

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

add a comment | 

up vote
1
down vote



accepted

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.

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

add a comment | 

up vote
1
down vote



accepted

up vote
1
down vote



accepted

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.

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

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.

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

share|improve this answer

share|improve this answer

answered Sep 2 at 12:59

gnasher729

72.8k31135229

answered Sep 2 at 12:59

gnasher729

72.8k31135229

answered Sep 2 at 12:59

gnasher729

72.8k31135229

72.8k31135229

add a comment | 

add a comment | 

up vote
0
down vote

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...

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

up vote
0
down vote

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...

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

up vote
0
down vote

up vote
0
down vote

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...

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

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...

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

share|improve this answer

share|improve this answer

answered Sep 2 at 9:45

bharal

11.4k22453

answered Sep 2 at 9:45

bharal

11.4k22453

answered Sep 2 at 9:45

bharal

11.4k22453

11.4k22453

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

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

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

add a comment | 

up vote
0
down vote

"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".

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

add a comment | 

up vote
0
down vote

"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".

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

add a comment | 

up vote
0
down vote

up vote
0
down vote

"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".

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

"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".

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

share|improve this answer

share|improve this answer

answered Sep 2 at 12:35

YElm

5,18131226

answered Sep 2 at 12:35

YElm

5,18131226

answered Sep 2 at 12:35

YElm

5,18131226

5,18131226

add a comment | 

add a comment |