Taro Logo

Module Reliability Engineer Interview Experience - Cupertino, California

November 1, 2016
Negative ExperienceNo Offer

Process

I contacted a recruiter via LinkedIn and was immediately approached by the hiring manager about this role. I went through two technical phone screens in the same week and then was called in for an onsite interview a week later.

From what the recruiter explained, it seemed that they were looking to hire for the same role in two different teams, which were again working pretty closely.

Instead of coordinating between themselves, both the teams decided to have their own full-length F2F interview on the same day! I ended up going through 13 very technical rounds of 1:1 interviews with different members of the teams. It started at 9 AM and went on until 6 PM.

To say it was tiring would definitely be an understatement. The questions were very bookish and knowledge-based. I understand that since I wasn't able to remember some of the mathematical formulas, I was not hired.

However, I was let down by the overall experience. Not only was the team unsympathetic towards grilling a candidate for nine hours, but the recruiter also did not even have the courtesy to let me know about their decision.

Questions

Questions on reliability modeling.

Weibull vs. lognormal distribution application.

How to determine the value of a Coffin-Manson exponent?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Apple Module Reliability Engineer role in Cupertino, California.

Success Rate

0%
Pass Rate

Apple's interview process for their Module Reliability Engineer roles in Cupertino, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Apple's Module Reliability Engineer interview process in Cupertino, California.

Apple Work Experiences