Management and leadership is open to suggestions and really work on implementing genuine requests.
Snacks on the house.
Engineering culture is towards the latest tech stacks.
Engineering teams are very open to discussion and prioritize what works best for the students.
Never seen a single instance where an individual puts his own interest above the end user or group's interest. This is really a big plus one for me.
It is very easy for an entry-level engineer to reach out to the engineering leadership and pitch their ideas. This is the first time I have seen this in any medium-scale organization.
The leadership shares a lot of context on why we are working on an engineering or product problem, which helps us understand the impact of our work and also helps us take decisions more effectively.
Product decisions are data-driven, which helps us identify where we are going and where we need to go in the future. Data-driven decisions are very strong within the community, which helps us take the right decisions for our students.
A lot of benefits for the employees are regularly reviewed to make sure the employees stay healthy and have the best facilities to work.
Fun Fact: We recently had a one-week off for the entire organization to relax ourselves, disconnect from work, and focus on what we want to do.
In terms of engineering processes, the teams are not very strongly aligned. But the leadership is already working on aligning it, so hopefully, this should be better with time.
Sometimes it takes a while to come to a decision, and in the short term, it might feel that the needle is not moving.
Keep doing the great work for the teams!!!
1. HackerRank round with MCQs related to API testing, Selenium, and Python coding. 2. Technical round with two interviewers, covering questions on Python coding, API testing, Selenium, and project framework-based questions, including BDD.
First round: DS and Algo test with a system design problem. No feedback was provided on the test. Second round: The interviewer copy-pasted two Amazon problems from GeeksforGeeks and also copied the GeeksforGeeks URL into the coding editor while int
Round 1: Solve problems on paper. Round 2: Discussion with a person on another set of problems based on DS, Algo, and Java. The process was okay; the people were not. I answered every question that the interviewer asked, and on my way home, I figur
1. HackerRank round with MCQs related to API testing, Selenium, and Python coding. 2. Technical round with two interviewers, covering questions on Python coding, API testing, Selenium, and project framework-based questions, including BDD.
First round: DS and Algo test with a system design problem. No feedback was provided on the test. Second round: The interviewer copy-pasted two Amazon problems from GeeksforGeeks and also copied the GeeksforGeeks URL into the coding editor while int
Round 1: Solve problems on paper. Round 2: Discussion with a person on another set of problems based on DS, Algo, and Java. The process was okay; the people were not. I answered every question that the interviewer asked, and on my way home, I figur