
Kenect Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Which role are you interviewing for?
10 roles · 20 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Kenect.
Sales Development Representative
The interview was pretty straightforward. They asked about my sales experience, if I'd be a good culture fit, and had me do a live call. Nothing too hard, pretty standard stuff. Everyone was easy to talk to and professional, and they did a good job of letting me know what to expect next.
- Can you tell me about your sales background and experience working in fast-paced environments?
UX Designer
The interview process was pretty straightforward. I was expecting a second interview and had scheduled it. But, the scheduling email was missing some information. I tried to follow up several times but never got a response. It was disappointing to get ghosted. I really don't think it's a good practice for companies to ghost candidates; most people would prefer to know if they weren't selected or if something changed.
- Can you tell me about your experience with mobile apps, specifically iOS or Android?
Recruiter
The interview process was stellar, for the most part. The hiring manager and hiring team kept me updated and moving forward in the interview process in a consistent and timely manner. I never waited too long, or wondered where things stood in the interview process. They were very aware of the candidate experience, and conducted interviews in a friendly and conversational way, which I appreciated. The last interview, with a senior leader and the team I would be supporting, felt long and like I was being drilled. Neither the team nor the senior leader left time at the end for me to ask questions. Overall great company, and good interview process, but some team members and decision makers need to be trained on how to interview.
- Can you tell me about the size of the departments you previously supported?
Back-end Software Engineer
So, there were three interviews. First, a 30-min screen, then a 90-min technical interview, and finally a 60-min cultural-fit interview. The first one was cool, talked to a nice person. The technical part was alright. The code challenge itself was demanding due to a lot of technical requirements to process quickly. It was tough to code effectively when I felt like I was missing some of the many requirements. I got the vibe that the interviewer was a Java guy who prefers other Java folks, even though the job required 3+ years of Java + Spring Boot experience, which I have. My main expertise is in Spring, but they didn't ask me anything about it. The weirdest part is they still proceeded with the third interview even though I apparently didn't pass the technical one. The culture-fit interviewers were nice and interesting, but it felt like a waste of my time and PTO when they already knew I wouldn't be hired.
- Can you explain the difference between inheritance and composition?
- Could you define what a generational garbage collector is?
- What is the recommended approach for abstracting a microservice?
Kenect Interview Questions
Quoted word for word from Kenect interview reports.
“What are React Hooks?”
Read reports →“Could you define what a generational garbage collector is?”
Read reports →“Can you explain the difference between inheritance and composition?”
Read reports →“What is the recommended approach for abstracting a microservice?”
Read reports →“Can you explain what measures are in PowerBI?”
Read report →“Can you explain what functional components are?”
Read report →“Could you draft an example email for a webinar campaign targeted at our existing customers?”
Read report →“Which do you prefer most: praise, promotion, or money? Rank them.”
Read report →“What's your current strategy for handling renewals?”
Read report →Formats, difficulty and experience
Across all 20 Kenect interview reports.