Candidatei-me de outra forma. Fui entrevistado pela Binti (San Francisco, CA) em fev. de 2026
Entrevista
Reached out on my own on LinkedIn. Interview took a month. 8 rounds of interview.
Recruiting and leadership interview, Take home, leadership philosophy, PM collaboration, values interviews, 3-in-1 (technical/design/behavioral) with CTO and one additional round.
Overall my experience showed that the company does not have a decision framework that enables a good candidate experience. The previous glassdoor reviews track with my experience. There was a lot of scheduling chaos, no defined interview process, lots of readjustments and ultimately no feedback for rejection.
Perguntas de entrevista [1]
Pergunta 1
What are the qualities in the next engineering team you lead, aspire for?
-First interview with CEO, which was great to get an understanding of the culture & company journey
-Offline customer-success related exercise, then presented in front of a panel of 3 employees
-Live problem solving exercise
-Culture interview with Executive
-References
Perguntas de entrevista [1]
Pergunta 1
Tell me a story about how you dealt with a challenging customer/client situation
Candidatei-me de outra forma. Fiz uma entrevista na empresa Binti.
Entrevista
The CEO reached out to me, which initially made me very interested in the opportunity because I really valued the company’s mission. So, I decided to go through the process — starting with a recruiter call, then an async technical interview, and finally an in-person onsite.
Unfortunately, the interview process felt extremely disorganized and improvised. I was told I had advanced to the final onsite before they had even figured out what that round would include. The onsite itself wasn’t great — one of the interviewers seemed disengaged, not very responsive, and started typing every time after I asked a question. I couldn’t tell if she was doing her own work or taking notes on me. It felt uncomfortable and unprofessional.
The technical evaluation focused heavily on Ruby on Rails, which surprised me given that my background is primarily in infrastructure and backend systems. It felt like they were expecting deep Rails expertise for a role that wasn’t clearly defined that way — and I personally think the stack is a bit dated for what they’re trying to achieve.
Afterwards, I was told they wanted someone with more tenure and more full-stack experience. That feedback didn’t make much sense considering my resume clearly shows a strong infrastructure and backend background, and that could have been identified much earlier in the process. It felt like expectations weren’t aligned from the start and was a huge waste of my time.
On a positive note, I still think highly of the company’s mission and the work they’re doing, but the interview experience was highly disappointing and felt like a huge waste of time, and it was a reflection of how poorly they operate internally.
Perguntas de entrevista [1]
Pergunta 1
Implement a feature for a Ruby on Rails application