Not a good company for a QA Engineer
Not a good company for a QA Engineer
Good benefits and perks. Lot of free food. There are good entertainments, but you cannot participate due to the workload.
Base salary is low.
When I joined this company two years back, it had a good developer and QA ratio. Now, the developers have tripled, and no QAs have been hired in my team.
There is no scope for learning new technologies.
Work-life balance is very bad due to daily regressions and frequent production releases.
Was this helpful?
LinkedIn Interview Questions
LinkedIn Interview Experiences
Software Engineering Intern
A very nice process, including an OA, phone screen, and then a Technical/Behavioral final round. I genuinely enjoyed the process and met some great people, which led me to accept the offer. Just make sure you have knowledge of your projects and can s
Software Engineer
The phone screen was a combination of systems and coding. It was relatively straightforward, all things considered. The recruiters at LinkedIn were great and made me feel at ease. The process was overall very smooth.
Software Engineer
The interview was a 1-hour technical coding interview. The primary interviewer was being observed by another interviewer. We opened with mutual introductions, which took approximately 5 minutes, before the technical interview began. The question w
Software Engineering Intern
Mountain View, California, United StatesNovember 1, 2025A very nice process, including an OA, phone screen, and then a Technical/Behavioral final round. I genuinely enjoyed the process and met some great people, which led me to accept the offer. Just make sure you have knowledge of your projects and can s
Software Engineer
Mountain View, California, United StatesMay 23, 2025The phone screen was a combination of systems and coding. It was relatively straightforward, all things considered. The recruiters at LinkedIn were great and made me feel at ease. The process was overall very smooth.
Software Engineer
Mountain View, California, United StatesMarch 1, 2025The interview was a 1-hour technical coding interview. The primary interviewer was being observed by another interviewer. We opened with mutual introductions, which took approximately 5 minutes, before the technical interview began. The question w
