tags:

views:

493

answers:

10
+2  Q: 

Job Titles

I consult for a small company and need to get some business cards with the client's logo.

I have free range to suggest an appropriate title for myself.

My roles in the organization:

  • lead IT initiatives (from automation to office infrastructure)
  • design software solutions
  • develop software solutions
  • lead small dev team
  • work with ceo/coo/customers
  • organize everything IT related (T1's, AD setup, etc.)

I've never given any thought to titles. I just care about the work I do and the money I make, but I suppose I should give this some consideration.

Given that the company is less than 50 employees; has about 4 developers; and does less than 20 million a year, what is an appropriate title?

EDIT:

The CEO wants to me to take an internal title, so consultant is sort of nixed. My favorites so far is Markle's suggestion:

Minister Plenipotentiary to High Lord Xenu?

A: 

I would be inclined to simply put...

Consultant

EDIT: Well in that case (internal looking title) and you are required to give this out to your clients custs I would still keep it simple and say something like

IT Manager

Tim Jarvis
A: 

IMO it depends on what others' titles are. Are you at the top of the org chart for developers, or are there others above you?

Here's what comes to my mind as being acceptable:

  • Lead Consultant (are you one of many?)
  • Senior Consultant (if there is a consultant over you on the org chart that calls design shots)
  • Consultant

Unacceptable:

  • Vice President of [Anything]
  • [Anything] Architect
  • Chief of [Anything]
  • Minister Plenipotentiary to [country]
Dave Markle
+1  A: 

I agree with Tim J - if you are not an employee, then you are a consultant. if you were an employee, i'd put "IT Director" or CIO or similar.

why do you want/need a business card with the client's logo et al on it? that makes it look like you are an employee - would it not make more sense to have a business card with your logo on it instead?

Steven A. Lowe
+6  A: 

The answer at least partially depends on who is going to be looking at the cards. The title is most likely for imparting to the customer what your role is. In a smaller company you typically want something that implies a larger organization and more complex structure. I would suggest something like Senior Architect which is appropriate to your development and design roles. However, if you want to focus more on your IT role, then I would instead go with something like Director, IT Operations. I'm assuming you have a fairly extensive role, and you're portraying yourself as a direct employee of the company rather than a third-party contractor. If your role as a contractor is open, then I would simply go with Architecture & Operations Consultant or something similar.

Jay
Does Application Architect work?
mson
Application Architect will work, but Senior Architect is more standard and most people would recognize it and have a good idea of your general duties (lead a dev team, design product feature implementations)
Jay
Thanks - I think I'll go with Senior Architect.
mson
+1  A: 

Forget about ranks and ladders and describe what you do.

Software Developer

eed3si9n
A: 

That's a wide range of responsibilities. I agree that consultant fits best, but if it has to be an internal title, maybe ...

IT Analyst / Developer

Or possibly something like ...

Information Technologist

John MacIntyre
+1  A: 

You've already expanded way too much energy on this topic. Use "Engineer". Now get back to work.

Terry Lorber
in some states you can't use the title 'engineer' unless you are licesned as one...
Steven A. Lowe
Good point, know your jurisdiction.How about, "Unlicensed Engineer", like Joe the Plumber.http://en.wikipedia.org/wiki/Controversies_over_the_term_Engineer#United_States
Terry Lorber
+2  A: 

I've been in the same kind of boat and I had to come up with a title. You don't want to step on anyone's toes so don't pick something that could put someone else's nose out of joint - especially if you report to that person. i.e. if your "boss" is in middle management, don't put Director, Management Information Services or Chief Technical Officer. When picking a title you need to take under consideration the following things:

  • It should be representative of your responsibilities within the company
  • It should be representative of your political position within the company.
  • It should also be something that you can be proud to have on your resume.
  • It should not get you laughed out of the door when being interviewed for future positions.
  • It should put you in the best position for negotiating future contracts.
  • It should be concise and descriptive ie don't use three words when two will do.

Some of the titles that immediately spring to my mind that describe the software design part of your position are:

  • Lead Systems [or Solutions depending on your taste] Architect
  • Senior Systems Architect
  • Application Design Consultant
  • MIS Solutions Consultant
  • I.T. Solutions Consultant

Or you could go way out there and use something out of the ordinary like Disney use: Lead Systems Imagineer.

Otherwise if you want something general that incorporates the I.T. side too then something more generic like: Information Systems Manager - I personally think that's kind of bland though.

BenAlabaster
+1  A: 

Any of these will help you:

http://www.cubefigures.com/job.html

http://dithered.chadlindstrom.ca/attic/job_titles.html

http://www.bullshitjob.com/titles.html

I prefer Director of Intellectual Property myself

Scott Evernden
+1  A: 

The answers posted here seem very developer centric. In some cultures, the title matters a lot.

Even though it's a bit 'playing the game', you might want to consider trying to get as important a title as possible.

It seems the company you consult for should give you your title.

botty