iHerb logo

iHerb Software Engineer Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at iHerb.

Showing 3 of 22
iHerb logo
iHerb

Principal Software Engineer

Engineering · more than a year ago

Staff Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Coding

I was contacted by a recruiter from LinkedIn and we set up a video interview with the hiring manager for the next week, which lasted an hour. The first half hour was spent discussing the role and my background, and the second half hour involved solving two programming problems that weren't too tough. I got positive feedback a week later and scheduled another video interview, but I withdrew because I had already accepted another offer. Overall, it was a good experience. The recruiters, Darren and Kimi, were professional and responsive, and the hiring manager was very pleasant and didn't make things difficult for candidates. It seems like iHerb is expanding in the US, and it's a good place for engineers who enjoy learning and taking on challenges.

Confirmed questions4 questions
  • Can you discuss your previous work experience?
  • Some basic questions about data structures.
  • Questions about finding data.
iHerb logo
iHerb

Software Developer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical

I applied online and got contacted by Michael Mandell about a week later. We had a 30-minute call to go over my resume and projects, and I also learned about the company. Then I had two on-site interviews with the Director of New Technologies and the team lead. They were really smart and nice, and we had great discussions. It was cool how they helped me improve a past project. I also met Michael before an interview, and he gave me a tour. Michael kept me updated on the next steps, so I always knew what was going on. He was really responsive by phone and email and answered all my questions, which made me less nervous and more able to focus on the interviews. He's easy to talk to and made the whole thing a good experience.

Confirmed questions3 questions
  • Can we discuss your resume and any projects you have worked on?
  • Let's talk about the projects you've worked on.
  • Can you walk me through your experience with your past projects?
iHerb logo
iHerb

Software Engineer

Engineering

Mid Average Neutral experience Accept offer 1 round
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding

It was a panel interview. Started with introductions, then a quick round of experience questions on various technologies and applications. Then they dove deeper into technical and application-specific questions. Finished with a coding challenge in my preferred language. I was also given a chance to ask them questions.

Confirmed questions3 questions
  • Could you explain HTTP caching?
  • What's a linked list?
  • How would you find the longest substring?

iHerb Software Engineer Interview Questions

Quoted word for word from iHerb interview reports.

Solve a variation of the knapsack problem where candies of equal value must be distributed equally among three people.

Read reports

How would you remove duplicate lines from a file, similar to the uniq unix command?

Read reports

Could you state the three defining characteristics of OOP?

Read reports

How would you optimize a generic web API system when faced with a sudden 10x increase in input data?

Read report

How would you go about naming methods and organizing namespaces?

Read report

Formats, difficulty and experience

Across all 22 iHerb interview reports.

Interview formats

Behavioral 39.2%
Technical 35.3%
Coding 17.6%
System Design 7.8%

Interview difficulty

Easy 27.3%
Average 72.7%
Difficult 0%

Candidate experience

Neutral 13.6%
Positive 50%
Negative 36.4%