What was the onboarding process for your tech job, Any Forums?
Don't reply if you're a neet.
What was the onboarding process for your tech job, Any Forums?
Don't reply if you're a neet.
A lot of waiting for my accounts.
They made me watch a bunch of videos and PowerPoint slides and set up my ide.
Basic stuff really
>This is our business
>We work like this
>There are your tools
>???
>Profit
What's there to explain?
this
who is she
I am NEET, fuck you.
Read 200 pages of wikis.
I said I did. I didnt.
>female ben shapiro
>way less annoying
i want to fuck her tight, small frame and NAKADASHI, get her pregnant
brett cooper
>onboarding
why do stupid soidevs have to have cringe buzzwords for literally everything?
>wft job
>get corporate laptop
>also some gadgets
>take them home
>talk to the guy tasked with getting me in
>get put in some project
>the team gives me an overview of the project
>start working
>change projects later because it sucked dick
I remember being given the manual to how my first project at the company worked.
Never read it either and was surprised someone actually wanted to update that trash.
>soidevs
This is more in the domain of HR cucks, tbqh.
>So hypothetically speaking, cereal is soup
wish there was leaks or deep fakes of her so fuckin hot
Read the product training material. First job task? Update the product training material.
Log in. Btw this thing says you use rsa but idk anything so you can just use a password. Here is git. Here is link to kanban board. Here is (shit) wiki where there's like 5 different pages for the same thing, by separate people. Here is your first task of replace X logger with Y logger. Couple 30m presentations on how stuff works. Btw poor automated testing. Here is how you copy default server configs onto test env, and it spawns a gorillion server processes. To test this particular client you need login credentials for connection. Oh, can't actually test in test environment because IT stuff prevents us sharing connection with prod and we are cheap to pay for test connection. Whatever, push it anyways. Btw, we have code reviews but nobody really does more than a cursory look. Didn't have sudo for first couple days so I was using plain vim. Scp'd coworkers clion to my home and still use that. Tried installing emacs but rhel7 and issues compiling, plus company has weird custom dependency management by a global shared NFS mount in PATH.
Previous place, guide through initial setup of machine w credentials + rsa, svn + git, visual studio, blah installs. The IT stuff took whole day, slow. Eod get assigned. Some long convos/lectures to get an idea of the task and understand things. Absolutely beautiful wiki, code, testing.
>Our last IT guy left, you know IT stuff right?
>Here is a list of passwords
And that was it.
>0 Documentation on everything
Some boring nonsense
But i got a water bottle and a cap so pretty cool, i guess
Sitting on my ass and having a bunch of meetings that only serve as a means for me to mentally afk to get the check.
Also a fair bit of reading
this, and witnessing the complete shit show of a network engineer they had.
> 2 Days of presentations about the company
> 2 days setting up my dev environment on the machine they lend me
> And then started working for good
Better than my last employer, my machine took a whole month to get to me
They made me watch a series of videos that simulate a manager asking me questions about typical work scenarios, then i had to respond by voice to these questions and my responses were recorded and processed by a speech-to-text algo and scraped for certain key phrases and language. I was then told that i did not answer the questions in the right way so I could not continue in that role.
Phone interview
Panel interview
One on one interview with big boss man
Hired