It's good to work with this organization.
Workload pressure is there, as business requirements dictate.
Fine
I was called in for an on-campus interview by a recruiter. The interview lasted for 45 minutes. He asked one technical question, described his role in the company and what his team does, and finally, we discussed any questions I had.
After HR reaches out and an initial 15-minute phone interview, there follows a 1-hour technical interview with an engineer in the team. Overall, I think HR is pretty hard to get in touch with, for example, not replying to emails.
Two back-to-back 30-minute interviews. These were mainly coding, but there were some general knowledge questions too, such as: * What is MVC? * What is OOP? * What is BFS? * What is DFS? Verbal programming questions seemed geared towards C++ and Ja
I was called in for an on-campus interview by a recruiter. The interview lasted for 45 minutes. He asked one technical question, described his role in the company and what his team does, and finally, we discussed any questions I had.
After HR reaches out and an initial 15-minute phone interview, there follows a 1-hour technical interview with an engineer in the team. Overall, I think HR is pretty hard to get in touch with, for example, not replying to emails.
Two back-to-back 30-minute interviews. These were mainly coding, but there were some general knowledge questions too, such as: * What is MVC? * What is OOP? * What is BFS? * What is DFS? Verbal programming questions seemed geared towards C++ and Ja