3 ms·
With most employees not staying at a job for more than two years, why wouldn’t you hire someone who can hit the ground running? If they spend six months doing n
by scarface_74 3y ago
With most employees not staying at a job for more than two years, why wouldn’t you hire someone who can hit the ground running? If they spend six months doing negative work ramping up and leave in two years, your investment in them didn’t go far.
Yes, I know the answer is to keep them at market wages and don’t fall into the salary compression trap.
But often that isn’t under your control as a hiring manager. HR won’t give you a budget for raises. But will give you the budget to hire at market rates.
- solarmist 3y agoBecause, as mentioned, it’s a fantasy that someone can step in and understand the peculiarities of a new company(’s technology) without ramp up time. Edit: specified its specifically about the tech. The business side is a whole other thing.
- scarface_74 3y agoThere are two things to ramp up on - the technology and the business. If they know the technology that’s one less thing to worry about.
- solarmist 3y agoAnd you can know 100% of the technologies they use; open the repo and still say, “what the hell were they thinking using X like Y!” “Why didn’t they use Y here” “Oh man, this looks like monkey patched code from 2 full versions ago, the right way to handle this now would be 1/3 the code, but oh they can’t update it because they’re mutating the data structure in order to Z… Fuck…” Edit: Eventually, you'll come to an understanding of why it's that way, but it takes time and often experimentation.
- scarface_74 3y agoEveryone thinks what came before then was done stupidly. With maturity, you realize whatever they did worked well enough to get the company to a position where they were able to hire you. As Corey Quinn (a well known “cloud economist”) says, “legacy software is software that generates revenue”.
- solarmist 3y agoThat wasn't the point. You missed the context or something. Those were just examples of initial thoughts that come up when starting to understand a new codebase. My point was exactly the opposite and parallel to what you said. But even with experience it takes time to decode those decisions. The point is that it takes time to understand the whys of code that is counterintuitive at first. Even if you are a 100% match for the technology.
- eulers_secret 3y agoIt depends on domain, and we have mostly webdevs in this thread. When I joined a kernel gfx driver team, the expected ramp time was ~6 months. My friend working on Mesa had a >1 year ramp time! If I open the source for a Django or React app, I can get to fixing bugs in a few days or less. It just depends.
- solarmist 3y agoSure, it's most dependent on the age of the company/software. The older, or lower level the code, the more hacks and workaround that appear in a codebase.
- epicureanideal 3y agoSounds like HR shouldn’t be in charge of deciding engineering salaries and raises. Seems like HR creates more problems than it solves. Time to reduce the scope of their roles.
- isbvhodnvemrwvn 3y agoIt's not HR that decides that, it's management. HR just enforces it.
- redditor98654 3y agoYeah, upper management and the finance department.
- ahoka 3y agoDo you think HR decides salaries? Do yo also think cashiers set the price of bread?
- goostavos 3y agoReading comprehension: the person you're replying to is replying to the statement: "HR won’t give you a budget for raises"
- isbvhodnvemrwvn 3y agoThinking comprehension - who determines budget?
- ren_engineer 3y agoif "most" engineers are staying for less than 2 years you either have a culture problem or aren't matching market rates for compensation
- esafak 3y agoThat's twice as long as Google's average tenure.
- ren_engineer 3y agothat number comes from their hiring spree when around 20% chunk of their workforce had 0 years of tenure, the data was pulled from LinkedIn and includes all employees or people claiming they are employees