iHerb logo
iHerbSoftware Engineer
Updated May 4, 2023

iHerb Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at iHerb, newest first and distilled into what to expect across the loop.

Get your personalized iHerb Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
> 1 year
Average Negative New York, NY

My experience started normally enough: I went through multiple rounds and the interviews themselves were pretty casual in tone, with the team members acting cordial and transparent. I got through what looked like the expected progression—early discussions and then interviews with people in the org—so I assumed things were on track.

What threw everything off was the recruiter coordination and how I was treated afterward. One interviewer-related reschedule happened at the last minute, and it felt tied to the recruiter not verifying availability properly. During at least part of my process, questions didn’t always get meaningful engagement from the recruiter side, and after I completed the rounds I basically didn’t hear anything. I received no real status updates and I even sent follow-up emails that went unanswered, which made the silence feel intentional rather than accidental.
> 1 year
Average Neutral Shanghai, Shanghai

My interview journey followed a classic multi-stage flow and felt steadily technical. I started with an intro-style conversation and then moved into a panel-style interview that included quick-fire questions about different technologies and applications, followed by deeper dives into specific tech and how I’d used it. There was also a coding challenge where I worked in my preferred language, and it ended with the usual opportunity to ask questions.

After that, I had an additional longer technical pass that leaned heavily on design thinking. I remember there being lots of design-related questions, and the format included a mix of interviewers: a manager discussion, followed by a couple of hours with technical staff, and then a final segment with a solution architect. The process was demanding but in a way that felt fair—until one round introduced questions tied to a technology I hadn’t actually used hands-on in my career. Even though that topic wasn’t listed as a requirement in the job description, I got hit by the last questions and it ended with a rejection.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Flow

The interview process typically follows a multi-stage structure, starting with a recruiter call, followed by a technical screen with the hiring manager, and then an onsite interview with multiple team members. Candidates noted that while the flow was generally straightforward, scheduling and communication could sometimes be inconsistent.

Recruiter callTechnical screenOnsite interview

Technical Evaluation Focus

Interviews often emphasize practical technical skills and knowledge relevant to the role, with a mix of coding challenges and system design questions. However, some candidates experienced unexpected questions on technologies not listed in the job description, which led to frustration.

Coding challengeSystem designTechnical skills

Behavioral & Experience Questions

Candidates reported a strong focus on behavioral questions and discussions around past work experiences, especially during the initial stages of the interview process. This conversational approach was generally appreciated, but the depth of technical questioning varied.

Behavioral questionsExperience discussionConversational tone

Communication & Coordination Issues

Several candidates highlighted issues with communication and coordination throughout the process, including last-minute reschedules and lack of updates after interviews, which contributed to feelings of frustration and uncertainty about their status.

CommunicationCoordinationStatus updates

Interview Environment & Atmosphere

The atmosphere during interviews varied significantly, with some candidates experiencing a professional and engaging environment, while others noted distractions and a lack of focus from interviewers, which negatively impacted their performance.

Interview atmosphereEngagementDistractions

Pacing & Decision Timeline

The pacing of the interview process can fluctuate, with some candidates experiencing quick turnarounds and others facing lengthy delays in decision-making, leading to uncertainty about the outcome and overall experience.

PacingDecision timelineTurnaround time