Software Engineer(Internship) applicants have rated the interview process at Enova with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 56.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer(Internship) roles take an average of 26 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Enova overall takes an average of 14 days.
Common stages of the interview process at Enova as a Software Engineer(Internship) according to 6 Glassdoor interviews include:
One on one interview: 29%
Phone interview: 29%
Group panel interview: 21%
Background check: 7%
Skills test: 7%
Presentation: 7%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Enova (Chicago, IL) in Oct 2018
Interview
First step was a brief phone interview with a recruiter. Second step was an online coding technical challenge. Third step was an onsite interview consisting of a behavioral, technical and group interviews.
Interview questions [1]
Question 1
Typical behavioral questions like how you work in teams, name a time when you failed and how you dealt with it, etc.
Technical interview and tests were pretty basic. String manipulation type stuff, control flow.
For the group interview they gave a technical-type question and a couple candidates and I discussed potential ways to solve the problem on a broad scale.
Introductory phone call with no technical questions, then all day interview with multiple rounds, including several behavioral rounds, technical rounds, and collaborative problem solving round with other prospective interns. Not crazy challenging but very tiring
I applied online. The process took 4 weeks. I interviewed at Enova (Chicago, IL) in Oct 2023
Interview
Pretty smooth process, contacted by the recruiter week after applying for an OA, then recruiter screen, then superday with 3 rounds consisting of 1 easy LC, 1 behavioral, and 1 system design scenario
There were many parts, like an info session, technical, behavioral, and group interviews followed by informal question time. The group interview was focused on outlining a solution to a hypothetical situation, rather than coding.
Interview questions [1]
Question 1
Lots of questions about challenges you have faced or goals you have failed to meet in the behavior interview