Test Engineer Interview Experience - San Francisco, California
Process
I submitted my resume to a job board and was set up with an interview through a recruiter.
The phone screen was scheduled within the first week.
After the phone screen, an in-person interview was arranged in the SF office for the following week. The in-person interview consisted of three rounds:
- Q&A and coding
- Test strategy
- A final round of coding and testing
The interviewers were mostly friendly, except for one person who was completely disinterested from the start, as though they had somewhere else to be.
Questions
Examine the inbox feature of LinkedIn. Read over the given spec and design a test suite for it.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the LinkedIn Test Engineer role in San Francisco, California.
Success Rate
LinkedIn's interview process for their Test Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for LinkedIn's Test Engineer interview process in San Francisco, California.
LinkedIn Work Experiences
- 5.0Company Is Good, No ConsTest Engineer • Current EmployeeWarsaw, Masovian Voivodeship, PolandOctober 15, 2025Pros: Company is fine and good.Cons: No cons. Nothing bad. Etc.
- 4.0Moving to more technical QATest Engineer • Current EmployeeCalabasas, California, United StatesFebruary 26, 2016Pros: Fantastic co-workers, lunch served M-Th, and an interesting product if you're on the right teams.Cons: Specific to QA, they are moving away from any manual testing and to full automation, as per the LinkedIn way (bought in May 2015). This can be seen as positive in some ways, but most of the QA folks are manual testers and will need to quickly ramp their skill sets to keep their jobs.
- 3.0QA here is not like everywhere elseTest Engineer • Current EmployeeMountain View, California, United StatesJanuary 17, 2016Pros: Great benefits, free food, flexible hours, a decent workload, great perks, and a good salary. For developers, working here would be a dream job, as long as they don't mind being responsible for the testing as well (see below).Cons: Testing is done by developers, which means as a QA your main job is to come up with scenarios and hand those to them. As a result, the priority is to hire more developers and (to put it nicely) employ less QAs. While this makes developers be more disciplined in designing with testing in mind, it also means less chances for QAs to learn and do new things.
LinkedIn Interview Questions
