BuildOps has been a great place for me to grow professionally. Engineers are trusted to take ownership of meaningful projects, solve challenging technical problems, and make a real impact on the product and business.
One of the biggest strengths is the people. I've had the opportunity to work with talented, supportive teammates and managers who genuinely care about professional development. Strong performance and initiative are recognized, and there are opportunities to take on more responsibility as you grow.
The engineering culture encourages collaboration, autonomy, and continuous learning. For engineers who enjoy building products, tackling complex problems, and having a direct impact, BuildOps offers a lot of rewarding opportunities.
As with many fast-growing companies, the pace can be intense, and priorities sometimes shift quickly. Work-life balance can be challenging during busy periods, especially when working on high-impact projects.
Organizational changes can also create uncertainty, and more consistent communication and long-term planning would help teams navigate those transitions.
These are areas where I believe the company can continue improving as it scales.
Continue investing in the people and engineering culture that make BuildOps a great place to grow. As the company scales, maintaining transparent communication, clear priorities, and sustainable workloads will be increasingly important for long-term success.
This experience has been disappointing and one of the worst interview experiences I have had for several reasons: * The recruiter was rude and strictly followed a script that lacked important context about the role, company, or teams involved. * No e
The interview process started with a recruiter call, followed by a Carat online interview (JavaScript + LeetCode). Then, the interview process continued with a 3h round of interviews including coding and system design.
Call with recruiter -> Coding challenge -> 4 in person interviews. The in person interviews were streamlined and fast, about 30m each. Have coffee beforehand, but the nice thing is you go through them pretty fast. That said, don’t rush things - just
This experience has been disappointing and one of the worst interview experiences I have had for several reasons: * The recruiter was rude and strictly followed a script that lacked important context about the role, company, or teams involved. * No e
The interview process started with a recruiter call, followed by a Carat online interview (JavaScript + LeetCode). Then, the interview process continued with a 3h round of interviews including coding and system design.
Call with recruiter -> Coding challenge -> 4 in person interviews. The in person interviews were streamlined and fast, about 30m each. Have coffee beforehand, but the nice thing is you go through them pretty fast. That said, don’t rush things - just