Human API reviews

4.1

77% would recommend to a friend

(29 total reviews)
avatar

Andrei Pop

85% approve of CEO

70% positive business outlook

Human API has an employee rating of 4.1 out of 5 stars, based on 29 company reviews on Glassdoor which indicates that most employees have an excellent working experience there. The Human API employee rating is in line with the average (within 1 standard deviation) for employers within the Information Technology industry (3.9 stars).

Reviews by job title

29 reviews
1.0
Sep 5, 2017
Recommend
CEO approval
Business Outlook

Pros

- A good idea (but poorly executed) - Early employees who joined the company with the purpose to change the state of healthcare. - The company is sitting on a product that could potentially work well (wellness/devices) but is putting close to ZERO effort into making it great. Done right, this could be a key differentiator in the market.

Cons

Most of the reviews have already covered. My experience was similar. Your mileage might vary, but it won't be far from the median of the poor experience. The TL;DR: - The biggest challenge is the management. Starts with the CEO wanting to micromanage every aspect of the company. - The decisions get made behind closed doors but retold in a narrative in the guise of transparency. This is one place where management gets in the way. - The pay is well below valley average - so negotiate hard, and do not fall for the "we are doing something special crap". Since one of the "positive" reviews mentions that potential candidates ask a lot of questions, I wanted to provide a framework on how to evaluate this company. There are both merits and demerits in joining Human API, but most importantly the decisions have to be made with some data (if it is even possible to gather them during your interview process!): (1) Business - Why have they not raised Series B (as of this writing)? Ask for the growth of their revenue (not just a final number). (2) Product - How do they get the clinical data? This is probably THE most important question you should be asking up front. You should be aware of the practice and evaluate the pros/cons. - How much is the user kept in the loop of the data pull? Read their end user terms of service - which you can find at their corporate website in the footer. - How much "medical" (non-device) data do you have and yoy/mom growth of these specific users? Evaluate whether the product is working. The future is less predictable than it is made out to be. (3) People - What is the total churn of employees that have (voluntarily) left in 2017? (P.S you can verify on LinkedIn) Watch out of hand wavy answers.

avatar
Human API Response
8y
Thank you for your feedback -- I always have, and still do, value your perspective. I’m sorry we parted ways with you harboring these frustrations. To the extent that there are still hard feelings, I’m always willing to hear them out. Since you departed, we’ve placed a strong emphasis on building the infrastructure to mature the product team and the broader organization. Your feedback provides us with the opportunity to reflect on the processes we’re building, so thank you. To anyone reading these comments: please do ask me, or anyone else on the leadership team, any of the questions mentioned; I am more than happy to answer them. - Andrei
1.0
Sep 1, 2017

Mixed experience, weak management and culture

Anonymous employee
Recommend
CEO approval
Business Outlook

Pros

Pros: 1. The domain is very interesting, there is great potential to learn and grow. 2. At the time of my leaving, there were still lingering elements of an erstwhile attempt at building a great team. 3. The company allowed flexible work arrangements such as working from home and flexible work hours.

Cons

1. (a) The work environment was mired in internal politics, conflict resolution was absent, and distrust between coworkers seemed to be fanned. There was insincerety in communication and action from the leadership, all perhaps in an attempt to maintain a management-approved narrative of an underwhelming state of affairs. (b) There was a critical lack of competence at managing (and acquiring) talent. The culture fostered disingenuity and sophistry over expertise and honest assessment. Routine manifestation of the Dunning Kruger effect had free reign and was a key driver of the organization. Favoritism was rampant. Legitimate performance evaluation was absent. 2. (a) Re-organizations were frequent and org structures followed agendas that seemed independent of product functionality and skill sets more often than not. Per Conway's law, the clutter in the product was reflective of such organization and flux. (b) Product teams were expected to ideate features flying blind, in isolation from customer feedback, market research and user experience. There was also a policy of design by committee and decisions were made by consensus, perhaps because of a lack of technical competence of the upper management coupled with a strong compulsion to micromanage every function. There was no honoring of ownership or of actual delegation. (c) Few ideas were realized as complete working implementations (even v1s) - the resources invested wouldn't be nearly sufficient, improvements and iterations would not be prioritized, and experts wouldn't be allowed to do their job without micromanagement. The productive would be vilified for not meeting unnecessarily aggressive (if not simply uninformed) expectations, prematurely, over partially developed solutions. (d) Product and company objectives were vague and seemed intentional (as were perf evals and feedback). (e) The primary objectives for PMs seemed to be to fill backlogs and for engineers to clear them, there was really no seriousness in delivering anything of value. 3. The upper management consistently engaged in misrepresentation and character assassination instead of genuinely admitting to lapses and addressing feedback from departing (and present) employees, writing off even key veteran contributors as "cultural misfits" (!!!). 4. There was no interest in investing in employees and their growth, even in manners that would benefit the company. This was in keeping with the lack of respect for employees (as with the disrespect towards customers and their mockery).

avatar
Human API Response
8y
Thank you for your feedback and thoughts. We’ve continued to grow as an organization thanks, in part, to constructive feedback from you and others on the team. I am very sorry you feel the way you do. The environment you describe is far from what I personally want to foster at Human API. Since you departed, the leadership team and I have focused on growing the organization and maturing our processes to address some of the concerns you brought up. Creating the required management structures to support us through our next phase of growth and foster a great environment is a big area of focus for us. Good luck in your next adventure, wherever it might take you. - Andrei
2.0
Nov 7, 2018

Interesting idea, limited execution

Anonymous employee
Recommend
CEO approval
Business Outlook

Pros

Could be a game changing idea within healthcare by allowing people to control their health data. Great work atmosphere, people, and work flexibility. Truly enjoyed the team and environment. Smart people behind the scenes that are working on building a healthcare data exchange. Have recently been building out the data team to better the product

Cons

The product doesn’t matchup with the needs in the market currently. There are too many steps to allow a user to connect their data sources. Being a startup, they haven’t been able to take advantage of being nimble and flexible within development. When customers said they needed features it would take far too long to have them implemented. The product is in very early stages and needs to mature to make an impact. The market is highly limited, much more than the management will accept.

Viewing 1 - 3 of 29 Reviews

Glassdoor has 33 Human API reviews submitted anonymously by Human API employees. Read employee reviews and ratings on Glassdoor to decide if Human API is right for you.