Enova Software Engineering Intern Interview Questions

5 Interview Reviews

Interview Experience

Interview Experience

80%
20%
0%

Getting an Interview

Getting an Interview

100%

Interview Difficulty

3.4
Average

Interview Difficulty

Hard

Average

Easy

5 Candidate Interview Reviews Back to all Interviews

Sort: Popular Date Difficulty

 

Software Engineering Intern Interview

Anonymous Interview Candidate in West Lafayette, IN
No Offer
Neutral Experience
Average Interview

Application

I applied through college or university. The process took a week. I interviewed at Enova (West Lafayette, IN) in January 2014.

Interview

Met them at my school's career fair. Scheduled an interview for the next week. It was a 30 minute interview, two questions. First one was to see our written communication, I was asked to write the rules of a very simple game to someone who had not played that game before. Second question was to read a program in Ruby and explain the code.

Interview Questions

  • Ruby program is very tricky if you have no experience. 5 or 6 methods were just chained to each other in one line and the interviewer admitted it was on purpose even though the actual code would be simpler.   Answer Question

Other Interview Reviews for Enova

  1. Helpful (2)  

    Software Engineering Intern Interview

    Anonymous Employee in Chicago, IL
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through college or university. The process took 4 days. I interviewed at Enova (Chicago, IL).

    Interview

    I applied through a campus career fair and online, and received an invitation to interview two weeks later. The first round consisted of two problems, which lasted a total of 30 minutes. One was a written communication problem, the other code reading (I'll explain below). After a week, I was then contacted again to travel to their Chicago office for a full day interview. It consisted of four parts, and though I can't tell you exactly what they were due to an NDA, I can tell you the different types of problems. Each session was about an hour. 1. A code reading problem. They expect every engineer to be able to read other engineers' code, which is what you'll be doing 90% of the time. The CTO told me that rarely will you ever start with a blank file. The code was taken live from production, and although I didn't know Ruby at the time, I was able to apply concepts from other languages to decode it and tell the interviewer what it was doing. 2. A code writing problem. This is much like what you'd run in to in other interviews. These tend to rely on your problem solving skills, but unlike a lot of bigger tech companies, they do not expect you to know specific algorithm/data structure questions, which I really appreciated. 3. A written communication problem. They believe in a strong correlation between taking complex ideas and communicating them to others, and taking complex ideas and coding them as well. You're given a general problem, and expected to write a solution or a set of instructions. 4. A team problem. I'm not sure if this is different for full-time hires, but every intern interviewing that day (there were about 7 of us) gathered in a room with several engineers and were expected to solve a technical problem on the whiteboard. They want to test your ability to work in a team and make sure you can listen to others' ideas as well as contribute your own. A week after I returned to campus from Chicago, I received an offer. I think it was one of the best interview processes I had ever been through. I really respect the fact that they try to get to know you as a person and as a teammate, and to see what your critical thinking skills are as a whole rather than your knowledge of a specific algorithm or data structure. It's a bit frustrating interviewing at larger tech companies due to the fact that you have to cram reading an interview book the night before studying trivial algorithm questions, or having to worry about stupid brain teaser-type problems.

    Interview Questions

    • Again, I can't be too specific, but one of the most challenging aspects was either the code reading or code writing. I had never seen/written a line of Ruby in my life before that point, so getting past Ruby's syntax and language features to find the core purpose of the code was a bit difficult. In code writing, I made the initial mistake of beginning to code a solution without fully thinking it through first. Take your time and don't panic.   Answer Question

    Negotiation

    Intern positions are largely non-negotiable.

  2. Helpful (1)  

    Software Engineer Intern Interview

    Anonymous Employee in Chicago, IL
    Accepted Offer
    Positive Experience
    Average Interview

    Application

    I applied through college or university. The process took 4+ weeks. I interviewed at Enova (Chicago, IL) in October 2013.

    Interview

    I had a 30 minute on-campus interview followed by an all day on-site interview. The 30 minute interview was a pretty short get to know you sort of thing. I had to read Ruby code and explain what it did. I had never read Ruby before, but there were some printed out pages of the api as a reference. The on-site interview was longer. It started with a dinner the evening before. The day of there were three main sections, code reading, technical writing, and code writing. Each segment lasted roughly an hour. After those three interviews were completed, everyone interviewing participated in a team interview and worked together to complete a challenge. I have interviewed at Microsoft, SpaceX, HP, Google, TI, etc. I've hit all of the big name companies. I never was introduced to the atmosphere of the company though. This place is really cool. Throughout the interview process I knew that I didn't want to continue my job search.

    Interview Questions

    • The most difficult part was the scrutiny of the interviews. Because so much focus was spent on getting to know the people (you them and them you) before the interviews, they didn't need that time to meet me. It was time to evaluate my abilities. There was little discussion in mine, and instead they simply watched me work.   Answer Question

    Negotiation

    It was for an internship, so there was little negotiation. I did heavily discuss dates though.

  3.  

    Software Engineer Intern Interview

    Anonymous Interview Candidate in Urbana, IL
    No Offer
    Positive Experience
    Average Interview

    Application

    I applied through college or university. The process took a week. I interviewed at Enova (Urbana, IL) in October 2013.

    Interview

    Talked to them at the career fair at the college campus, they held on campus interviews the following week.

    Interview Questions

    • Was handed Ruby code and asked to decode it and tell what its saying. Was also handed Ruby documentation in case I didn't know Ruby (which I didn't)   Answer Question
  4. Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review


  5. Helpful (1)  

    Software Engineering Intern Interview

    Anonymous Employee in Chicago, IL
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through college or university. The process took 2 weeks. I interviewed at Enova (Chicago, IL) in October 2011.

    Interview

    Talked to a dev and recruiter at a career fair. Had an on campus interview the next day, after which I received a call asking me to come to Chicago for an interview there. Got there on a Thursday night and went out to dinner after checking into the hotel. They had us interview with a few different people throughout the day on Friday and finished with a big group problem solving interview. Everything was paid for by Enova, including transportation to and from.

    Interview Questions

    • The most unexpected question was an open ended question/discussion on how to solve a slightly crazy problem. Working through all the details and methods was a bit weird.   Answer Question
Don't Miss Out On a Job You Love
Upload a resume to easily apply to jobs from anywhere. It's simple to set up.

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.