Excellent culture and benefits, very relaxed and welcoming atmosphere.
It can feel like you are stuck in application development using a proprietary language. The language makes development slower than it could be for apps teams. Pay is okay; they put a lot of emphasis on stock-based compensation, which doesn't vest until the year after you receive it. There's a tendency to reinvent the wheel with internal tools.
Give teams more scope to use the right tools for the job.
1. Hiring Manager: Give a brief intro about the company and a basic class diagram. 2. Technical Interview: - Asks for a UML diagram for a ridesharing app. - Later, there is a demo about their language.
Had multiple rounds of interviews. The technical interview was based on UMLs. Otherwise, it was mostly focused on behavioral questions. The recruiter was very responsive and kept me informed on all steps of the interview process.
I first had a phone call with the recruiter, which was mostly about the company, the position, and my qualifications. Later, I had almost five interviews. These were mostly focused on: * Behavioral questions * UML class diagrams (object-oriente
1. Hiring Manager: Give a brief intro about the company and a basic class diagram. 2. Technical Interview: - Asks for a UML diagram for a ridesharing app. - Later, there is a demo about their language.
Had multiple rounds of interviews. The technical interview was based on UMLs. Otherwise, it was mostly focused on behavioral questions. The recruiter was very responsive and kept me informed on all steps of the interview process.
I first had a phone call with the recruiter, which was mostly about the company, the position, and my qualifications. Later, I had almost five interviews. These were mostly focused on: * Behavioral questions * UML class diagrams (object-oriente