7 ms·
Like you say, they left after a year. Maybe they really tried to make it work, and now, in retrospect, can see the red flags. And yeah, they're being blunt abou
by sverhagen 5y ago
Like you say, they left after a year. Maybe they really tried to make it work, and now, in retrospect, can see the red flags. And yeah, they're being blunt about it now. But in the moment they may have done a decent enough effort.
Myself, I am very "getting my hands dirty"-oriented, and the corporate onboarding goes over very poorly with me too. Sit through multiple days of material that is dumbed down to the company's lowest common denominator. Having to be giddy with other new hires in departments that you will never have any interaction with anymore. Kill me now. So, if the trainers just go through the motions, why wouldn't the original poster and I just put in the mere minimum to get through it, and start my real job...?
Oh, my real job... in the cafetaria with no desk? So, sure, the manager can forget to put the request in. But would a manager not know that you start, schedule a welcome meeting with you on the first day, touch base a few times in your first week? Plenty of chances, still no desk! It's ridiculous, but I am not surprised. If you don't think that is ridiculous, then, I don't know, maybe you've been conditioned to that sort of environment. With no snark I wish you much joy in your employment there, but then please let the original poster and myself move on^H^H^H^H^H^H^Hrun for the hills.
Here's what onboarding should look like for an Engineering role: you come in at 9:00, do the bare minimum with HR, meet your team, set up your computer, and before the end of your first day, you have your first code changes in production. Then you go home with a feeling of accomplishment. Then, during the rest of the week, some onboarding meetings will happen, but at least you have started with the most important place: your team.
- ChrisMarshallNY 5y ago> Here's what onboarding should look like for an Engineering role: you come in at 9:00, do the bare minimum with HR, meet your team, set up your computer, and before the end of your first day, you have your first code changes in production. Then you go home with a feeling of accomplishment. Then, during the rest of the week, some onboarding meetings will happen, but at least you have started with the most important place: your team. That pretty much describes my department, for the 25 years I ran it. Of course, it was a fairly small team of experienced, high-functioning, engineers, so I doubt it represented the “industry standard” shop. We hired people with many years of experience, and I found it productive to let each one have a great deal of agency and control of their development environment.
- Redoubts 5y ago
- rythmshifter03 5y ago>you people
- Aeolun 5y agoHow so? I think this is more or less correct. I never even considered how people could fail at those tests (e.g. privacy procedures) until I saw someone that was truly not interested in them take them. Now I understand why the stupid things require you to spend at least 2 seconds looking at the answer slowly fading in before they allow you to click. For some people the solution is not understanding the material. It’s just clicking every answer in rapid succession until they get the magic combination.
- rightbyte 5y ago> before the end of your first day, you have your first code changes in production. Like adding yourself to a maintainer list or some prepared token handholding task? Or what could you possibly do in the first day before having the time to read the code.
- icedchai 5y agoAt an early startup I worked at (about 10 years ago), it was fixing a small bug. You updated a couple lines of code and got familiar with the deploy process.
- bitcharmer 5y agoYeah, their statement about expecting to push changes to prod on day 1 is hilariously unrealistic. The sense of entitlement is strong in this one. Glad we don't hire people like this.
- Aeolun 5y agoDepends on how large your app/org/process is. I have worked in places where it would be expected (6 people org), and absolutely laughable (10k+), not least of which is that any release takes at least two months in the first place.
- eutropia 5y agowe have our new engineers update the “our team” wall of faces with their photo on day 1 in prod. Not sure why that’s unrealistic if your deploy process doesn’t suck?