iHerb Employee Job Reviews in the United States

"Great company culture. Much of the development work is done off-shore which makes for long days due to time zone differences."

"IHerb in Hebron, KY has a physical harassment problem coming from people in Supervision, Management, and Lead roles in the warehouse, there have been 2 harassment situations where two different subordinates had to quit or were forced out of a job because the H.R. Department wouldn't investigate either past employee's allegations in late 2019 and in late 2020. If you work there, please document every time an authority figure there touches you or says something, they are ruining people's lives because they won't investigate authority figures' inappropriate and unprofessional behavior towards subordinates in the workplace."

"Good company for begging mechanics."

"full of innovation which brings tremendous amount of challenges to your day-to-day operations. Everyone is a fighter and thats what stand out about this company."

"Good opportunity to learn about what it takes to drive KPI's forward in a global ecommerce company. Great exposure to personalization, mobile apps, mobile web, and desktop experiences. The product experience still needs improvement, but it's a good place to suggest new methods and practices to level-up the product team."

"Very challenging and rewarding at the same time."

"Pros: My former coworkers are fantastic! I've never been around such a smart, talented, enthusiastic, and ambitious group. They had really been there for when I needed guidance, advice, or even moral support. I had learned working here than any other company in recent memory. The Development teams are awesome. Cons: One word: Management. Avoid working in IT Ops like the plague. Allow me to elaborate. These "New Feature" projects are held in much higher regard than improving internal systems to streamline the chasm between Ops and Dev. The situation that results from this mentality is that DevOps has to support an exponential number of systems without any sort of automation to help maintain it. Point-click-point-click. No one knows how it was set up because documentation is non- existent. Be ready to ask about 3 other teammates to figure out how so-and-so set it up because you'll also be held accountable for maintaining this system, in addition to your regular projects. You're expected to spontaneously understand all the systems in an arbitrary amount of time after a short meeting where the speaker presents a series of mouse clicks, completely lacking any kind of automation or integration into existing systems. (Isn't this what DevOps is about?) There's no script, you'll just have to figure it out. If you don't finish your projects because of persistent production emergencies and offer this explanation, management doesn't listen and assumes that you're not up to the task in the project. Get ready to be a perpetual firefighter in IT Ops. Management prefers to accept that fires in production are going to happen and that we have to deal with them, as opposed to looking for solutions to nip these issues in the bud. Additionally, you'll have to be on-call, and any work done while resolving production issues is not counted for overtime."

"10 years of employment and every year the company manages to turn a higher profit."

"I have worked for iHerb Inc. since for some time now. The benefits are exceptionally good and the CEO cares a lot about the company. Although I have heard rumor of a progression system and an annual review system, they are non-existent. The overall environment is good but the department I work in has its issues. Unless some sees the issues that can do something about it there is no hope for these things to be fixed."