
Kenandy Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Which role are you interviewing for?
8 roles · 12 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Kenandy.
Software Engineer
So first there was this phone screening interview that lasted like 30-45 minutes. They asked me about my past projects and why I wanted to be an integration engineer, and how I'd be a good fit for the role based on my experience. Also, some questions about web services. Then, about a week later, I went onsite and had 5 interviews back-to-back, each 30 minutes long, with 10 different people in total (2 people per interview). The first two interviews were strictly technical. I had to show them an app I built on Salesforce and also work through some algorithmic and coding questions. The other three interviews were more about how things are done at Kenandy, my past work, and team-related processes.
- Could you write an algorithm to perform a level-order traversal on a binary tree using a whiteboard?
Product Marketing Director
I spoke to HR/hiring manager and got a good impression. Then I met with a C-level executive who seemed biased against my current company, and the conversation felt like it was full of bias. I didn't get the job because of where I work. The hiring manager and HR were aware of the bias the whole time, so I'm unsure why I was even interviewed. My interactions with the C-level executive weren't based on principles I use, but on theories from experts. I would have considered declining an offer anyway, so I guess it's good it didn't work out. It seems like the company is top-heavy and not open to new ideas, which isn't ideal for a startup.
- The questions asked were not challenging.
Administrator
The interview process was standard with four steps. First a recruiter screen, then HR, then the hiring managers, and finally an offer. Both the company and I knew exactly what we were seeking from both ends (as employee and employer). At the end of the day, after experience, education, and skill set are assessed, it's about chemistry -- how well you can work with the other person. People work for people!
- What are the most important qualities you look for in a potential manager?
Applications Engineer
This was about a 2-hour interview with 4 Lead engineers. It involved Modeling/White boarding and Coding samples. Topics covered included Algorithms, JS Remoting, Triggers, Apex testing, and OOPS.
- Tell me about Algorithms.
- Can you explain JS Remoting?
- What are Triggers?
Kenandy Interview Questions
Quoted word for word from Kenandy interview reports.
“What are Triggers?”
Read reports →“Could you write an algorithm to perform a level-order traversal on a binary tree using a whiteboard?”
Read reports →“Can you explain JS Remoting?”
Read reports →“How would you test the presented website?”
Read reports →“How would you handle Apex Batch jobs for processing large amounts of data, specifically regarding retaining state across batches by implementing the stateful interface?”
Read report →“Can you explain one or two sorting questions related to the comparable interface?”
Read report →“Tell me about Algorithms.”
Read report →“How do you approach Apex testing?”
Read report →“What questions do you have regarding the data model?”
Read report →Formats, difficulty and experience
Across all 12 Kenandy interview reports.