Timeline for How to portray "senior" levels of experience in relatively young technologies?
Current License: CC BY-SA 3.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2017 at 2:57 | comment | added | Fattie | just use the words "expertise" or "leading expertise". | |
| Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://workplace.stackexchange.com/ with https://workplace.stackexchange.com/
|
|
| Oct 6, 2014 at 17:17 | comment | added | Brandon | You claim that you are senior due to years of experience, then argue that employers are making a mistake by using # years of experience to judge seniority. Yet you want them to judge you as senior. That seems like a contradiction. | |
| Sep 10, 2014 at 16:10 | answer | added | David Navarre | timeline score: 2 | |
| Aug 22, 2014 at 14:43 | comment | added | user2813274 | I have seen positions (in 2000) that "required" 8 years of java experience , and the HR would toss any resume that didn't have it - needless to say they never got their "ideal" candidate. | |
| Jul 28, 2014 at 3:52 | answer | added | Michael Lai | timeline score: 0 | |
| Sep 13, 2012 at 22:06 | review | First posts | |||
| Sep 14, 2012 at 14:15 | |||||
| Aug 20, 2012 at 13:33 | comment | added | IDrinkandIKnowThings | @user2343 - I just meant that it was a common blow off from an interview. If you were willing to take the IC position then they get someone with senior (or at least approaching senior) level skills for bargain price. Some companies are good at promoting when you show the skills but they want you to prove yourself for 2 or 3 years first. | |
| Aug 19, 2012 at 2:00 | history | edited | Zelda | CC BY-SA 3.0 |
I don't think that bit's necessary to the question
|
| Aug 18, 2012 at 14:56 | history | tweeted | twitter.com/#!/StackWorkplace/status/236839067659153408 | ||
| Aug 18, 2012 at 14:28 | comment | added | maple_shaft | ... because in the end it is certainly a trust issue and an enormous investment of time and money. Management needs to trust the solutions being proposed by the architects, and they would rather hire the senior SE who has been there loyally for 6 years and where they truly know that persons abilities and limitations. Senior SE positions are nothing to shake a stick at, and are the stepping stone to the next level of your career. | |
| Aug 18, 2012 at 14:24 | comment | added | maple_shaft | @user2343 I think you are setting your sights a little high. The bar for experience to come into such an important position as Principal Architect is absurdly high because hiring somebody off the street is inherently risky. We have all hired that guy who seemed perfect on the interview then turned out to be a complete joke of a human being. Positions like Principal Architect are inherently political, so unless you were an Architect at Google or you are Jon Skeet, they are probably going to look internally for aptitude loyalty and trust... | |
| Aug 18, 2012 at 4:58 | comment | added | user2343 | @DBM Of course. Here's a concrete example. Well-known company had third-party recruiter contact me about Principal Architect in a fairly small group. HR dropped me down a notch to be interviewed for Senior Front-end Engineer before interviews (without telling me). The resulting interviews were all about Javascript and the interviewers skipped to the end because I had answered the questions so far so easily. Then they invited me on-site and told me it was for Senior SE (4 yrs JS/front-end), not Principal Architect. I declined. | |
| Aug 18, 2012 at 4:50 | answer | added | Erik Reppen | timeline score: 6 | |
| Aug 18, 2012 at 3:12 | comment | added | Daniel Mann | Have you considered the possibility that people are passing on you for these roles because you're not actually qualified for them? | |
| Aug 18, 2012 at 3:00 | answer | added | Permas | timeline score: 16 | |
| Aug 17, 2012 at 22:01 | history | edited | gnat |
edited tags
|
|
| Aug 17, 2012 at 21:26 | answer | added | JasonTrue | timeline score: 32 | |
| Aug 17, 2012 at 21:07 | answer | added | HLGEM | timeline score: 9 | |
| Aug 17, 2012 at 20:50 | comment | added | user2343 | @Chad Several times they have actually offered me an individual contributor position, instead. | |
| Aug 17, 2012 at 20:46 | comment | added | IDrinkandIKnowThings | "we're looking for someone with a bit more 'senior' experience in ..." is the "Its not you its me!" speech hiring. It probably tells you very little about the actual reason you did not get the position. | |
| Aug 17, 2012 at 20:38 | history | edited | Zelda |
edited tags
|
|
| Aug 17, 2012 at 20:33 | comment | added | user2343 | @Chad Thanks for the feedback. I struggled to get the point across without removing important detail. I will try to think about it. I would also welcome any editing. As for the note -- just wanted to say I am familiar with some rules of this site, and am happy to integrate feedback to improve the question since I know it's not perfect as-is. | |
| Aug 17, 2012 at 20:29 | comment | added | jcmeloni | I agree with the comments here about the question needing some help; Chad's suggestion about asking for qualities & skills (etc) that match with the position you are looking for (which you answered in your comment to Oded) would be a much better starting point. The goal doesn't seem to be how to figure out how to show you are "senior" for some value of "senior" but rather how to get the position you want with the skills & experience you can prove. | |
| Aug 17, 2012 at 20:14 | comment | added | user2343 | @Oded My question was already getting a bit long, but here's a little more detail. I've led a team for two years in the past and left that company for a company that did bigger/better things where I could actually get more advanced experience. I've done that now but actual teams are small and don't need developer-managers. As for what I'm looking for -- any/all of the above: 3-6 direct reports (junior-mid engineers) and/or complete product technical ownership. | |
| Aug 17, 2012 at 20:10 | comment | added | Oded | It is not clear to me what kind of position you are looking for - senior, yes, and the jobs you listed are usually that, but with the added requirement of leading/managing/running a development team. Nothing you have posted tells us about your experience with team leading. So, are you trying to get that added responsibility or not? | |
| Aug 17, 2012 at 20:03 | history | asked | user2343 | CC BY-SA 3.0 |