iFIT Fullstack Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at iFIT.
iFIT
Fullstack Developer
Mid Easy Positive experience Accept offer 4 rounds
Interview process
Take home Technical screen Recruiter call Onsite Offer
Interview formats
Coding Technical Behavioral
So I started with this coding challenge online, it was pretty simple and took like 20 minutes. Then about a week later, HR reached out to set up a technical interview with two lead developers. That was about 45 minutes, first 15 minutes were about my coding background, then a 30 minute live coding challenge. The problem was tough, I didn't finish it on time, but they said they cared more about how I tackled it than finishing. A few days after, I got contacted for a second interview. This one was more of a quick chat with senior leads to see if I'd fit the team culture, only 15 minutes. The third interview was with the technical director, another chat for about 45 minutes. During this chat, we talked about salary expectations, and they mentioned an offer might be coming. An offer did come a few days later. Overall, it was a really good experience.
Confirmed questions1 question
- How do you teach yourself new things related to coding?
iFIT
Full Stack Developer
Entry Average Negative experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Coding Other
You won't talk to anyone unless you pass their HackerRank coding challenge. You'll get emails from their HR bot. This whole thing felt really random and cold. I got a standard email back because I didn't get 100% on the test. Honestly, I feel like I avoided a bad situation because any place that uses weird, unnecessary steps like this is probably not a great place to work.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
iFIT
Full Stack Developer
Mid Average Positive experience Accept offer 5 rounds
Interview process
Technical screen Take home Technical screen Recruiter call Technical screen Recruiter call Technical screen
Interview formats
Technical Behavioral Behavioral Behavioral
The interview experience started with an automated technical screening, followed by an automated culture screen. Then there was a technical interview, then a culture interview, and finally a CTO interview. The whole process moved really quickly once it got going.
Confirmed questions5 questions
- Two programming questions that act as a litmus test were asked in the pre-technical screen.
- The pre-culture screen involved 5 questions focused on your perspective on work.
- The technical interview was like whiteboarding but conducted in an automated IDE, requiring a good programming background.
iFIT Fullstack Engineer Interview Questions
Quoted word for word from iFIT interview reports.
“For an input array, determine if there are three consecutive numbers present and return '1' if so, and '0' otherwise.”
Read reports →“With small bags (1kg) and big bags (5kg), and given counts for small and big bags along with a target goal, figure out how many small bags are needed to meet the goal, starting with the big bags. If it's impossible, return '-1'.”
Read reports →“Can you explain what object deconstruction is in JavaScript?”
Read reports →“How do you teach yourself new things related to coding?”
Read reports →“The culture interview was a standard HR-style interview.”
Read report →“When are you available for the interview?”
Read report →“The CTO interview was a more focused culture interview, suited for those aligning with the company's mindset.”
Read report →“The technical interview was like whiteboarding but conducted in an automated IDE, requiring a good programming background.”
Read report →“Two programming questions that act as a litmus test were asked in the pre-technical screen.”
Read report →Formats, difficulty and experience
Across all 6 iFIT interview reports.