iRhythm has a legitimate business case in interpreting heart rate records for cardiac patients. They also have a concrete international business expansion plan as well as the resources to scale their data architecture.
iRhythm has always been cruising on that initial business case while trying to figure out the hardware to support it. Unfortunately, startup management grew the team based on social fit and communication skills - even preventing managers from performing technical evaluations of candidates. As a result, much of the Director level and under "organic" middle-management is technically under-skilled, and, for the most part, has spent most of their career at iRhythm.
There are very few technical challenges at iRhythm, but many procedural and political ones. Decision making is terrible. Inconvenient truths are hidden under Directors and hand-waved away to be fixed later, and the result is significant technical debt in the core products while trying to scale. These problems are surmountable, but not with current leadership, and not without holding middle-management accountable for performance.
Many times I saw "narrative" win out over facts and data, with socially-connected resources being protected and groomed for their loyalty, not for their ability or achievement. "Failing upwards" is very common, with most leaders leaving behind failing projects before they are finished, and those projects are often "pain points" forever for good technical resources to fix, but those people tend to burn out and quit.
iRhythm is still a place where early-stage medical device engineers can learn and grow, but if you spend longer than 2-3 years here, you are wasting your time and not learning crucial skills; you will find it difficult to obtain a role at the same level at another company.
Hire for technical skill, not for social fit. Focus less on seniority and more on performance. Develop a product pipeline and do it. Actually follow the phase-gate process. Stop promising things you don't understand. Stop doing the bare minimum "easy path" and do what's hard when it's necessary to do it right.
A recruiter went through generic questions and asked how experienced I was with each skill. They had very little information they could provide about the specifics of the role and company/team in general.
I received a call from HR, and they scheduled a manager round to check if my expectations and theirs were aligned. After the discussion, we moved to the next onsite interview rounds. Rounds: 1. HR explained the process and feedback system. 2. In
The onsite interview experience was positive, but unfortunately, communication afterward was lacking. Despite efforts to follow up with both the recruiter and hiring manager, there was no response. This left me feeling disappointed and uncertain abou
A recruiter went through generic questions and asked how experienced I was with each skill. They had very little information they could provide about the specifics of the role and company/team in general.
I received a call from HR, and they scheduled a manager round to check if my expectations and theirs were aligned. After the discussion, we moved to the next onsite interview rounds. Rounds: 1. HR explained the process and feedback system. 2. In
The onsite interview experience was positive, but unfortunately, communication afterward was lacking. Despite efforts to follow up with both the recruiter and hiring manager, there was no response. This left me feeling disappointed and uncertain abou