Great food, free drinks stocked in the break room. You get your own office. Good pay. Good benefits if you're there for a long time. Smart co-workers who are generally passionate about pushing out a good product. Looks good on a resume.
Your experience can vary widely depending on the team and manager you are assigned. As for me, I was on the bad end of the spectrum.
Revolving door work culture and high turnover rate. Their philosophy seems to be hire fresh graduates, burn them out, and hire more when they quit. This leads to no ownership of existing code and just adding to the mountain of technical debt.
Of course, I have to mention the outdated technology. Even though my training consisted of C# and ASP.NET, the constant poor state of quality of the application I was working in often led to working on VB bug fixes. Very frustrating work. Even when doing web development, you are pretty much restricted to using in-house developed libraries and controls which have poor support and functionality, and the web pages still have to work in the VB application. Some of the web applications are even written with VB... What a nightmare that was. I don't think the full transition to web will happen any time soon.
Project management was especially bad on my team. Even with the mountain of technical debt, managers constantly promise new projects to customers with unrealistic deadlines, and it's left to the developers to deliver. Now it's up to us to work on the project with short deadlines, lack of vision, and constant scope creep while juggling an endless amount of VB bugs found in incomprehensible code. I was constantly overworked and stressed out. 45 hours a week was the norm; we had team-wide weekly/monthly late nights, and working weekends was not uncommon close to deadlines.
Add many pointless but required meetings on top of that.
I could give advice, but would they listen? I think they are aware of the problems, but they are too ingrained in their ways to do anything about it at this point.
30-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
Quick 30-minute phone call (nothing technical). Then the long exam over webcam. Problems weren't super difficult, but definitely be familiar with DP and do some practice problems on LeetCode. 3 weeks later, I got the on-site. This was very well run
One round of phone screening, then an online coding test which includes algorithm questions that are not too difficult. If you do well on the online exam, then you will be flown out to Wisconsin to have an onsite interview, where not a lot of technic
30-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
Quick 30-minute phone call (nothing technical). Then the long exam over webcam. Problems weren't super difficult, but definitely be familiar with DP and do some practice problems on LeetCode. 3 weeks later, I got the on-site. This was very well run
One round of phone screening, then an online coding test which includes algorithm questions that are not too difficult. If you do well on the online exam, then you will be flown out to Wisconsin to have an onsite interview, where not a lot of technic