Clear Vision & Leadership: The leadership team is transparent and has a clear vision for where the company is headed. There's a strong sense of shared purpose, and it’s genuinely exciting to be part of a company that is solving real problems and poised for future growth.
Open, Feedback-Driven Culture: This is one of the best parts of working here. Management actively solicits feedback and, more importantly, acts on it. This commitment to continuous improvement creates a culture of trust and makes you feel like your voice truly matters.
Opportunities for Growth: I have been able to work with a wide variety of technologies, which has been incredible for my professional development. The work is always engaging and provides constant opportunities to learn new skills, which keeps me motivated.
As the company and engineering team have scaled, cross-team communication can be challenging at times. Managing cross-cutting concerns that affect multiple teams requires significant coordination, which can occasionally slow down development velocity. It's a natural challenge for any organization, and its good to see steps being taken in the right direction.
The first step in the interview process was a call with an HR representative to discuss my background and the role. This was followed by a technical interview, which I found straightforward. I was tasked with creating a simple spreadsheet class, imp
I had a call with a recruiter. The call was really relaxed. The recruiter himself was recently hired and made it clear at the beginning he was still trying to find his footing. He took the time to describe the company and asked common questions. The
First round with recruiter. Two technical rounds: * First is a CoderPad programming exercise with a developer, followed by a technical background discussion with a VP. * Second is an architecture design round and a chat with the product team.
The first step in the interview process was a call with an HR representative to discuss my background and the role. This was followed by a technical interview, which I found straightforward. I was tasked with creating a simple spreadsheet class, imp
I had a call with a recruiter. The call was really relaxed. The recruiter himself was recently hired and made it clear at the beginning he was still trying to find his footing. He took the time to describe the company and asked common questions. The
First round with recruiter. Two technical rounds: * First is a CoderPad programming exercise with a developer, followed by a technical background discussion with a VP. * Second is an architecture design round and a chat with the product team.