Ever-increasing bureaucracy, process, and other tedious stuff. Probably par for the course with any big org.
Diluted focus and vision in some engineering areas. Can be frustrating finding and doing impactful work.
Strong drive "forward" means some legacy headaches are tolerated for too long.
Unrefined inter-department processes can cause headaches with security, infra, and "devenv" situations.
Great job on the whole. Please keep listening to the signals, feedback, and suggestions from engineers and keep fighting to keep things focused, fun, and productive for ICs.
Recruiter call, Tech screen, Recruiter call, Virtual onsite (coding 1, 2, behavioral). All in all, this process stretched out over two months, so it was the most extensive of any I had encountered.
It was quite long. I had several HR interviews and interviews with senior engineers before arriving at the technical test. This test was conducted by a senior and a junior who found my solution too complex, without really understanding its benefit, i
Only had the first coding exercise round. The problem was reasonable, and the interviewer was obviously interested in seeing people succeed rather than presenting an arbitrary problem to try and make people fail.
Recruiter call, Tech screen, Recruiter call, Virtual onsite (coding 1, 2, behavioral). All in all, this process stretched out over two months, so it was the most extensive of any I had encountered.
It was quite long. I had several HR interviews and interviews with senior engineers before arriving at the technical test. This test was conducted by a senior and a junior who found my solution too complex, without really understanding its benefit, i
Only had the first coding exercise round. The problem was reasonable, and the interviewer was obviously interested in seeing people succeed rather than presenting an arbitrary problem to try and make people fail.