You cannot claim to value your engineering team while simultaneously laying off engineers mid-project on customer-committed work, terminating people over production incidents in a high-debt codebase, tracking AI token usage as a performance proxy, and ignoring the feedback your own managers are escalating.
Engineers talk to each other. They compare notes. They know when the feedback loop is performative. If you want to continue to build something great, start by treating the people building it as the strategic asset they are. Not a headcount number to optimize.
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.
I interviewed at BuildOps through recruiter who reached out to me on LinkedIn. The recruiter was incredibly helpful at every stage, providing clear guidance and quick follow-ups. The interview process itself was fast, straightforward, and well-struct
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.
I interviewed at BuildOps through recruiter who reached out to me on LinkedIn. The recruiter was incredibly helpful at every stage, providing clear guidance and quick follow-ups. The interview process itself was fast, straightforward, and well-struct