The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I have a question: does it matter what you put down [on the resume] as your current title? If you want to be a Senior Code Monkey, can you not list that as the current title? Point being: do prospective employers get to call and check up on you at the current job while you're still working there? What is the point of the [checkbox] for "May we contact your current employer?"?
Most large corporations I worked for had it Programmer Analyst, appending Roman numerals or prepending Junior or Senior.
The last large corporation I worked for decided to shake things up (to make us less employable elsewhere was the suspicion) and changed them to Associate Member Technical Staff, Junior Member Technical Staff, and Senior Member Technical Staff. I believe there was another one, but I forget what it was, simply Member Technical Staff?
I preferred the places where I had R&D Programmer or Software Engineer.
My current title is Manager of Software Application Design, which I think is too wordy and I would have preferred Development over Design.
However, my desk plaque reads Universal Genius.
Psychosis at 10 Film at 11
Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
Software Engineer, or Senior Software Engineer if you think your experience level justifies it. If you're not sure, stick to SW engineer -- better to have a too-low title and appear to be looking for an upgrade, than to claim to be a senior level engineer and not meet their expectations. You might miss out on an interview or two without a sufficiently lofty title, but you'll immediately fail the interview if your experience level can't justify the lofty title to them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
Whenever somebody asks me what I do for a living, I do not answer with "I'm a computer programmer", even though that is one of the main activities that justifies my paycheck. For me, "computer programmer" conjures up an image of a sun-deprived subterranean creature -- a go-between who accepts requests from the computer ignorants and performs the necessary incantations over a computer keyboard to make it happen. In "the old days" it really was that mystical. The programmer was like a priest who took your petition to the Great Mainframe. After a ritual sacrifice of punch cards and green bar paper, your prayers might be answered with a result that you could use.
I'd rather be seen as a team member who just happens to specialize in software. It's a lot like the film Oceans Eleven, where a team of specialists all work together to achieve a noble goal. (Their team also has a software specialist, albeit one with some ridiculous skills.)
I feel your pain; I work at a startup, so technically I am:
Programmer in .NET and Crystal Reports
Director of Design
Director of QA
Director of Customer Support
SQL Server DBA
Net effect, I don't have an official title. I don't care so much about that (most people know what I do), but if I were to look for another job, it'd be difficult to explain that in a nice corporatespeak title. So, I enjoy occasionally making up titles for my e-mail signatures (see below).
My advice: something simple that's roughly all-encompassing; in my role, I'd rock out with "Nonsense Title - Software Development".
Senior Assistant VP Director of Byte Procurement II
Wjousts - I've been battling the same issue for years; titles created by previous employees that seem to have stuck to the corporate position title list.
To resolve this issue, my resume states the normal segments (e.g. position title, date range, accomplishments, & bullet points) but also includes the job description for each position held. The job description can be laid out similarly to the descriptions you find on the salary research sites.
Recruiters and HR personnel understand the typical corporate position title issues, so as long as you state what it is you do at the current position and highlight the important aspects, you should be get the point across to anyone reading your resume. Truthfully, all the resume is good for is to get your foot in the door, so create it to attract potential employers. Once you're at the table, you can explain what you did at your previous position regardless of the title they bestowed upon you.
Many places have their own terminology so it isn't so surprising.
I wanted to point to this wikipedia article Battel[^], which we had to pay termly for lodging and food. When reading the article, it turns out that Battels was distinct to Commons (the latter being the name of the bill the student gets for the standard meals), and that some [other] Durham/Oxford colleges continue to use it in the way my college used Battel. You live and learn!
I use my email client to actively block spam. I usually block the entire domain.
Of course, that doesn't slow down the absolute asshats that run spam sites.
From my history: blocked 6/18/2012 executivebizbriefings.com blocked 7/10/2012 executivebusinessbriefings.com blocked 8/22/2012 executivebusinessreports.com
I've numerous examples of this sort of thing in my history. It's the sort of thing that gets me fantisizing about hunting some people down and giving them a really good real life beating. I'm so tired of the persistent nagging.
PRO-TIP: Legitimate businesses don't have to change their IP address on a monthly basis.