Good pay. Excellent resume eye-catcher. Best practices in data engineering and some good documentation that can be learned from.
You are a small moving part of a big engine. Leadership doesn't know you exist as an IC. Try hard enough to prove your impact to get into the cult. Too much empire building. Job specific - even though you would learn a lot about Data Engineering, the learning you get exponentially decreases. You learn more how to communicate rather than technical stuffs.
Stop empire building. Listen to ICs and treat them nicely. Good layoff, as I agree there are lots of people that don't do work or just do fake work.
First is the recruiter round, then a one-hour technical interview which included questions around SQL and Python. After that would be behavioural and other technical rounds. Other technical rounds would cover system design, etc.
Bad interviewer. Did not respect interviewee. They were late, shut down the camera in the middle, and did not let me finish my interview despite having enough time. A really bad experience.
The interview process typically begins with an initial phone screen, where background and overall fit are assessed. This is followed by one or more coding interviews to evaluate technical problem-solving skills. Finally, candidates usually particip
First is the recruiter round, then a one-hour technical interview which included questions around SQL and Python. After that would be behavioural and other technical rounds. Other technical rounds would cover system design, etc.
Bad interviewer. Did not respect interviewee. They were late, shut down the camera in the middle, and did not let me finish my interview despite having enough time. A really bad experience.
The interview process typically begins with an initial phone screen, where background and overall fit are assessed. This is followed by one or more coding interviews to evaluate technical problem-solving skills. Finally, candidates usually particip