Coworkers are open and kind. Development tools are surprisingly good. The office environment is a good mix between quiet and collaborative, and the hybrid 3/2 works well for me. Customers love the product!
You have to like using the product internally for everything (it can take some getting used to). The company is working toward profitability, which means there's a need to be disciplined around spending, which projects you take on, etc.
I had the same experience as one of the candidates mentioned below. I'm a bit flummoxed because it seems like my answers to the code screen were correct, but they said they were wrong or that I solved the wrong problem. I also tested the solution f
The phone screen consisted of an evaluation of runtime/memory complexity and an OOP design question (though the interviewer already hinted at a third coding part). From reading other interview experiences here, I thought this interview would be less
The interview process involved a behavioral phone screen, a coding challenge, a tech phone screen, and then an onsite interview. I only reached the coding challenge stage. Someone I hadn't corresponded with via email called me for the behavioral pho
I had the same experience as one of the candidates mentioned below. I'm a bit flummoxed because it seems like my answers to the code screen were correct, but they said they were wrong or that I solved the wrong problem. I also tested the solution f
The phone screen consisted of an evaluation of runtime/memory complexity and an OOP design question (though the interviewer already hinted at a third coding part). From reading other interview experiences here, I thought this interview would be less
The interview process involved a behavioral phone screen, a coding challenge, a tech phone screen, and then an onsite interview. I only reached the coding challenge stage. Someone I hadn't corresponded with via email called me for the behavioral pho