Influitive logo

Influitive Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Influitive.

Showing 3 of 7
Influitive logo
Influitive

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Group

So the process started with a recruiter phone screen. After that, I met with the CTO. The next step was supposed to be an onsite with a technical part and then board games during lunch. The recruiter emailed me after talking to the CTO to see how I thought it went. I replied, but then heard nothing for a week and a half. I emailed twice, and he finally got back, saying they were swamped and offered a call, which he then missed because he had an interview. After another call, maybe two or three, I was told they decided not to move forward for their own reasons. I get it, but it was three weeks since I met the CTO. If they had decided, a quick email would have been fine, not three weeks. It felt really unprofessional and I was pretty appalled by the whole thing.

Confirmed questions2 questions
  • Can you tell me about your resume and your past experiences?
  • What are your career aspirations for your next position?
Influitive logo
Influitive

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Onsite Technical screen Panel
Interview formats
Behavioral Technical Coding

It was a 4 step interview process. First, an in-person chat with the VP Engineering, mostly to go over expectations and check for cultural fit. Second, a lunch with some of the team, also to check cultural fit. Third, a whiteboard technical interview to gauge architectural understanding and knowledge of HTTP. Fourth, a pair-programming session to see how I work daily and assess my problem-solving skills. The whole experience was great, and I appreciated how fast things moved. It was very thorough, expectations were set well, and the team seems great.

Confirmed questions2 questions
  • Can you describe how to implement a typeahead UI, like Gmail's, detailing API consumption and HTTP usage?
  • Given some complex, tightly-coupled jQuery and DOM manipulation code, how would you refactor it?
Influitive logo
Influitive

Software Developer

Engineering

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Group Presentation Offer
Interview formats
Technical Coding Behavioral Group Presentation

Had some chill chats over the phone and in person. It ended with a paired programming task. They were hiring for React, but I told them I didn't have much experience with it, though I'm solid with Javascript and other JS frameworks. They also had me spend about 3 hours with the team, including a one-hour paired coding challenge, some one-on-one chats, and lunch.

Confirmed questions2 questions
  • How would you refactor a javascript file?
  • Could you refactor this react file?

Influitive Software Engineer Interview Questions

Quoted word for word from Influitive interview reports.

Given some complex, tightly-coupled jQuery and DOM manipulation code, how would you refactor it?

Read reports

Can you describe how to implement a typeahead UI, like Gmail's, detailing API consumption and HTTP usage?

Read reports

What are your career aspirations for your next position?

Read report

Can you tell me more about a project listed on your resume?

Read report

Can you tell me about your resume and your past experiences?

Read report

Formats, difficulty and experience

Across all 7 Influitive interview reports.

Interview formats

Behavioral 26.3%
Technical 26.3%
Coding 26.3%
Group 10.5%
System Design 5.3%

Interview difficulty

Easy 14.3%
Average 85.7%
Difficult 0%

Candidate experience

Positive 57.1%
Neutral 28.6%
Negative 14.3%