5 ms·
Being downleveled for "years of experience" is obviously silly. There's a common adage: You can have 10 years of experience, or 1 year of experience repeated
by dijit 5y ago
Being downleveled for "years of experience" is obviously silly.
There's a common adage:
You can have 10 years of experience, or 1 year of experience repeated 10 times.
--
I don't know the author, and it's possible that Shopify used this as an excuse because the authors talents did not meet expectations or claims: but "years of work experience" is a very poor marker for ability and experience, since years are not equal between people or roles.
- xibalba 5y ago> obviously silly No. You've drifted into believing your opinions are facts. Reasonable people can disagree. Having hired many people, I understand that everything in the hiring process, no matter how well calibrated and tightly looped, are rough heuristics for how well a person will do in a role. So years of experience in the relevant activity gets at least equal weight to responses to relevant technical questions, coding challenges, etc. Yes, FAANG experience carries extra weight in opening the door because FAANGs are known to set high bars and have (overly) intense filtering. Etc. Etc.
- dijit 5y ago> No. You've drifted into believing your opinions are facts. Fair enough. I've also hired "many" people (many in my case being about 12, so that may not be "many" by other definitions). I think it's fine to disagree, maybe my overall sentiment was much too strict, but let me just say that in my experience years != years, even people in the same roles at the same company can have wildly different experience levels from the same years of being there. This isn't really accidental either, a good example was.. me.. actually, I had a colleague who had the same number of years experience and for all intents and purposes we actually matched super well in our abilities and mentalities. However, we worked together for 7 years, on the same projects, same deadlines, same tech, same responsibility. That man knows far more about influxdb than I possibly can: despite both of us having "7 years influxdb" on our resumes. I know more about postgresql than he likely ever will, but we both have "7 years postgresql" on our resumes. Aptitude is one thing, attitude is another, and at the end of the day: the only thing that works is to set your standard and see if people hit it. For me, senior means that you're able to teach, are self motivated, can speak at a high level to leads or directors and understand business need, regardless of technical competence in specific technologies or years experience. If you hit that bar, you get the title, if you don't, you don't.
- Consultant32452 5y agoI feel like it's reasonable to hire someone at a lower level due to lack of years of experience. Down-leveling after the fact is a punitive act. My guess is the years of experience thing was just an excuse for some business initiative to cut costs or was a personal attack on the OP.
- ewidar 5y agoExcept it was not "after the fact"? He got interviewed for a senior position, got offered a mid-level position. Seems to fit exactly the case that you find reasonable.
- krob 5y agoYears of experience is relative to the company, and software type. Companies like Google, production products are likely on a totally different level than almost any other product in existence. So 10yrs at none google company is not equal to Google engineering. What plays into all of this is the complexity of the problems they solve at scale, and level of academic sophistication. Map software, search engines, Google app suite gui products are not simple or easy to build.
- deleted 5y ago[deleted]
- wpietri 5y agoYou contradict your own point. Even that adage accepts that the upper bound on the amount of experience you have is based on the time you spend. You can have 1 year's worth in 1 year, or 1 year's worth in 10. But you can't get 10 years' worth in 1 year. I think experience is vastly overused in hiring; it's a classic example of picking the easy thing to measure over something meaningful. But experience really does matter. Living with a code base for an extended period teaches you about consequences that just aren't obvious.
- onion2k 5y agoYou can have 10 years of experience, or 1 year of experience repeated 10 times. This is a good adage for why 'time served' is not a particularly useful way to judge someone's level of experience, but you can't invert it and say it means time served isn't important at all. Someone with 1 year of experience might have the same experience level of someone with 10 * 1 year, but they obviously don't have the same experience as someone with 10 years of real experience. "You can have 10 years of experience, or 1 year of experience repeated 10 times." is only useful as a way of differentiating between two candidates with 10 years experience; it can't be used to suggest someone with 1 year of experience is as experienced as someone with 10 years. They're only as experienced as the bad 10 years experience.
- dijit 5y agoI think that's completely fair, but are we really talking about people with 1 year of experience as if they have 10 years? I'm not saying experience doesn't matter at all, just saying that it's a poor marker for seniority. FWIW when hiring I tend to avoid thinking about years of experience; else I allow some implicit ageism into my assessment; my definition of senior has very little to do with actual technologies and is more to do with how you use those technologies and if you have experience being self-motivated to deliver something with business value.
- adriand 5y ago> I'm not saying experience doesn't matter at all, just saying that it's a poor marker for seniority. In many contexts seniority is literally defined as years of service. I take your point to mean that experience isn't everything, and that there are many people with less experience than others but with more talent or skill, but I think there is a reasonable expectation that a senior developer (in terms of years served) ought to have certain qualities that one cannot expect in someone with far fewer years of experience, regardless of how intelligent/skilled/talented they might be. Wisdom is one quality that takes years to arrive at. In a developer, wisdom is the quality that leads to questions like, "Yes, we could do that...but should we?" It's the lived experience of writing enough code that never got used to be able to call YAGNI. It's knowing when to be cautious about adopting new technology, because of all those times someone picked the wrong new thing that they still had to maintain five years later.
- dkarl 5y agoThey might have said "years of experience" because the candidate was lacking some important skills that Shopify needs in their senior engineers, and Shopify felt that the candidate was plenty smart and the only reason they hadn't learned those skills was a lack of time and opportunity, which a few more years in the industry would likely cure. Sometimes the handful of words that filter through on the internet don't do justice to the reasoning behind them.
- deleted 5y ago[deleted]
- tppiotrowski 5y agoCouldn't you be fooled by someone that meticulously studied Cracking the Coding Interview but has never opened an IDE in real life?
- dijit 5y agoGiven that I don’t at all ask the kinds of questions in that book I think it’s unlikely. My questions are usually: “tell me about a time you x” “Who helped you, what did you like about them” Or “nobody helped you? Was that by choice, how did that feel”. You get the gist.