Candidatei-me online. O processo levou 3 dias. Fui entrevistado pela Klaviyo em abr. de 2022
Entrevista
Don't waste your time with the Java interview/test. The Klaviyo guys that interview you have no clue about Java. Just go for the Python jobs and watch your stuff blow up at runtime. They talk about how tech savvy they are, but cannot answer basic questions about best practices or principles.
Perguntas de entrevista [1]
Pergunta 1
JDBC API from 20 years ago and GSON payload mapped to Maps. No one codes like this anymore. Plus you cannot compile/run the code. These Klaviyo folks are geniuses.
We’re sorry to hear about your negative interview experience, and appreciate the time you took to interview with us.
Candidatei-me online.
O processo levou 1 semana.
Entrevista
Typical interview process. Recruiter call, online assessment, and then supposed to have a hiring manager round. I cleared the online assessment but was ghosted after that round. No response from recruiter.
Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fiz uma entrevista na empresa Klaviyo.
Entrevista
The recruiter reached out via linkedin, then set me up for an OA which I aced, and then arranged a 45 mins conversation with the hiring manager. After this they ghosted me. Totally unprofessional.
Round 1: Coding Assignment (CodeSignal)
A take-home or timed industrial coding challenge from code signal
Round 2: Hiring Manager Interview
A conversation with the hiring manager to discuss your background, interests, and alignment with the role.
Onsite Rounds:
Round 3: Deep Dive – Work & System Design Discussion
A technical deep dive into your past projects and contributions.
Be mindful of not just the architecture, but also why some decisions were made.
Round 4: Leadership & Behavioral Round
A structured behavioral interview to assess leadership, teamwork, and problem-solving in complex situations.
Focuses on past experiences, conflict resolution, and decision-making skills.
Round 5: API Design & Best Practices (Coding Round)
A practical coding session, not purely algorithmic but focused on designing and building a small API/system from scratch.
Asked about scalability, maintainability, and software design principles.
Round 6: System Design Enhancements
Given an existing system design, you’ll be asked to analyze it and propose improvements.
Expect discussions around scalability, reliability, trade-offs, and edge cases. I guess I failed at this step, since it was an unknown with this style of interview.
Great people involved and were very accommodating.
Perguntas de entrevista [1]
Pergunta 1
Conflict was asked twice, how did you resolve conflict.
