I'm negotiating a new job and need some advice on titles. I'm normally a senior-level software engineer (about 9 years exp), but this new role will be non-coding. The company doesn't have an engineering group, but instead contracts out heavily. They want me to be the technical go-between... software requirements generation, design reviews, and regulatory stuff (medical device).

Basically, very close to the software, but not writing code. What would you call this?

closed as too localized by enderland, IDrinkandIKnowThings, yoozer8 May 21 '13 at 16:43

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • You can try using the following term which is used very loosely to describe what you are looking for: Specialist: As the primary assignment, performs a specific quality related function within the company’s quality program. Examples include management representative, statistician, and testing expert. Has received direct training or has been performing the activity for a number of years. Shows a high degree of skill performing that specific activity. – Michael Grubey May 21 '13 at 16:02
  • 2
    See here for a discussion on questions like this. – enderland May 21 '13 at 16:19
  • 2
    A Business or Systems Analyst – IDrinkandIKnowThings May 21 '13 at 16:35

There are a couple of possible ways I'd describe this role:

Business analyst - If you are getting into the domain knowledge of software and handling the translation back and forth with requirements and some basic design.

Solution architect - This would be the more technical title I could see. This is the high level planning and overall structure person that lets others handle the technical details.

  • They were the two titles that leapt to my mind when I read the question, also. – Carson63000 May 22 '13 at 2:54

I had a similar role as a member of a team. I was a computer engineer between a team of mechanical engineers and electrical engineers.

I had to speak both languages, essentially, knowing what a fifth wheel was and what a zener diode was.

This was a research position, so my actual title was Research Assistant, but when people asked what I did (more than just being a research assistant), I considered myself a technical engineering liaison.

This puts an emphasis on people skills AND the ability to speak technically.

I would check with the company, as it's likely they have had similar roles in the past. Your title could be solutions architect as JBKing suggested, or it could be lead developer, or business analyst.

At Microsoft, lead developers tend to take on more architect and management focused roles, so this would not be without precedent.

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