A friend put me in touch with a recruiter, and I had a brief intro call to learn about the company. She then connected me to the relevant PM for the team I'd be interviewing with. I had an intro call with the PM, which was followed by a HackerRank takehome - an algorithm to solve, and a frontend assessment that hinged primarily on CSS. After that, I went on-site, and interviewed with 4 people on the team I'd be joining. If I get called back, I'll interview with the PM again, and with the CTO.

I was reached out to by an employee at HealthTap who scheduled a phone interview with me. After reading other reviews on Glassdoor, I was hesitant, but I decided to proceed. During the phone interview, the interviewer had no idea what the tech stack for the product was, and couldn't tell me the exact job description (it was all very vague). He said I'd be working on implementing new features on their new codebase, and it was somehow tied to product quality. They sent me a coding challenge which was fairly straightforward. After that I was invited for an onsite interview. I got a tour of the place and it's true - all the engineers are in the basement, separated from everyone else. The whole place was really crammed. I spoke with the same person from the phone interview for a bit, and he again couldn't really tell me too many specifics about the job. Next I spoke with an engineer on the team, who clarified a lot of questions I had. The job description that the first person had described was entirely false - what I would have been working on was an endless list of bug fixes on their legacy codebase, while also doing client-facing IT. Nothing to do with the new product at all. I asked questions about culture, and the engineer let me know these details: -The hours are tough. They do enforce their hours, but they're long - at 9:30 all the engineers have a meeting with the CTO, and when Munchery is delivered between 6-7 they're allowed to leave. That doesn't sound like the worst hours, but combined with the rest of these facts, they are not easy. -The CTO is quite rough and very much micro manages. He breathes down the engineers' necks since everything is incredibly deadline-driven. He's way more hands on than any typical CTO. -There are communication issues across the company, and they're planning on opening an office in San Francisco with no foresight about how to fix the inevitable communication issues across different campuses, let alone within the same campus. -There's no real company vision. They just have a series of "values" that they don't really hold to. -There's no real motivation for staying except that a few people on the team are nice. This is about what I can remember - everything was a glaring red flag. All the other negative reviews here seem pretty accurate. If you're considering working for them, try to get as much information as possible before making a decision.