Personally, I set work-life balance boundaries early on (literally 7-hour workdays), made competent software engineering decisions, and stayed engaged while in the office. I learned from those around me, and it pays off. I've received, on average, a 9% annual raise. I am not advancing as quickly as some around me. There is still growth and a need for people to step up, and individual contributors can be greatly rewarded for growing and contributing. There is so much room for improvement and ideas, too.
Also, moms and dads both get great, fully paid maternity and paternity leave.
I like the PTO system, which includes unlimited unpaid time off if you accidentally go over. That is, if you feel like you don't have enough time off or holidays and book a little too much time off, you won't get fired for not coming to work; you just won't get paid for a couple of days. That is fair to those who work more.
You have to be receptive to change and adaptation as teams split, grow, move desks, tools change, we adopt better frameworks and libraries, and coding practices.
It depends on what software team you are working on as to what the specific culture, work, and tech stack is like. But I see that all teams are heading in the right direction, some more slowly than others.
Don't stop being afraid. Stay ahead of the world innovating. Your next step is toward bringing all of the world buying all things home from Wayfair. Only you can do this.
Fairly standard for the industry. A phone screen is used to judge minimum qualifications. An onsite interview involves meeting with a number of the current software engineers. Some interviews were with two or three interviewers at once, while other
Applied online. I received an email the next day asking for my availability for a half-hour phone interview. I provided it, and the recruiter and I agreed on a date a couple of days in the future. The day arrived, and I waited over half an hour. I r
Once they received my referral, the recruiter set up a preliminary phone screen, which went fine. I was then asked for a code sample and sent a 24-hour coding challenge, which I completed within the allotted time. At this point, the recruiter confi
Fairly standard for the industry. A phone screen is used to judge minimum qualifications. An onsite interview involves meeting with a number of the current software engineers. Some interviews were with two or three interviewers at once, while other
Applied online. I received an email the next day asking for my availability for a half-hour phone interview. I provided it, and the recruiter and I agreed on a date a couple of days in the future. The day arrived, and I waited over half an hour. I r
Once they received my referral, the recruiter set up a preliminary phone screen, which went fine. I was then asked for a code sample and sent a 24-hour coding challenge, which I completed within the allotted time. At this point, the recruiter confi