[ale] Titles

[Pete Hardie]

An amusing factor in titles I've seen in online job postings - a "Senior"
software developer needs 2-5 years of experience


On Tue, Dec 23, 2014 at 9:33 AM, Lightner, Jeff <JLightner at dsservices.com>
wrote:

>  My title has been a “Senior” at most of my jobs.   The only time I was
> called “Principal” was when the parent company was British so it seemed to
> me that “Principal” meant top level in the role for them like “Senior” does
> in US.
>
>
>
> Of course titles sometimes don’t really tell you much.   At a prior job I
> was “Operating Systems Programmer II” then “III” and finally
> “Consultant”.   The “III” was original senior most level and the
> “Consultant” was a bump up from that just because it allowed for a higher
> pay scale – my work didn’t actually change.   Note that in none of those
> roles was  I actually a “programmer” or developer.   (Though of course
> Admins do a fair amount of script “coding” it isn’t really the main point
> in the job.)   I think the titles were hold overs from the old mainframe
> only nature of that particular company.
>
>
>
>
>
> *From:* ale-bounces at ale.org [mailto:ale-bounces at ale.org] *On Behalf Of *Charles
> Shapiro
> *Sent:* Tuesday, December 23, 2014 9:15 AM
> *To:* Atlanta Linux Enthusiasts
> *Subject:* Re: [ale] Titles
>
>
>
> Or you could just go here (
> http://siliconvalleyjobtitlegenerator.tumblr.com/ ).
>
> -- CHS
>
>
>
> On Tue, Dec 23, 2014 at 8:24 AM, Leam Hall <leamhall at gmail.com> wrote:
>
> On 12/23/14 08:00, Brandon Colbert wrote:
>
> Thanks for the feedback.
>
>
> The main thing to ask is "did the person who wrote the title really
> understand the job?" In some places that's a "yes", in other places no. If
> it's a resume title then it gives you a lead to discuss your strengths and
> accomplishments.
>
> A recruiter called me about an Oracle DB/Solaris support job. The hiring
> manager really needed someone to lead the growth of the entire Unix
> infrastructure. Same job, two very different perspectives.
>
> If this is for a resume, define the job you want and show how you've been
> working towards that for some time. Everything on my resume is true, but
> it's not everything I've done. My resume does show those things that
> demonstrate the type of work I really want to do. I don't talk about
> supporting HP/UX or SCO because I don't want to do that anymore.
>
> For folks transitioning into a new area, the same applies. Find the best
> "industry standard" you can for the role. Highlight what your background
> already shows and find ways to build the skills you don't have. This is a
> great time to help with an Open Source project; you build skills, resume
> bullets, and the community.
>
> Leam
>
> --
> http://31challenge.net
> http://31challenge.net/insight
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
>
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
> information and is for the sole use of the intended recipient(s). If you
> are not the intended recipient, any disclosure, copying, distribution, or
> use of the contents of this information is prohibited and may be unlawful.
> If you have received this electronic transmission in error, please reply
> immediately to the sender that you have received the message in error, and
> delete it. Thank you
>
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>


-- 
Pete Hardie
--------
Better Living Through Bitmaps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20141223/193ca923/attachment.html>