The company is progressive and diverse.
The company has better benefits than most others I've worked.
The QA org was dissolved about 10 months ago when they laid off 550 people.
They are pushing to remove QA as a role altogether with a focus on AI and automation, and have been moving that way for the last two quarters.
They don't care about their employees' opinions and have moved forward with a return-to-office mandate.
I was explicitly told that QA had no career growth in the company. There is no career growth at this company for QAs, managerial or otherwise.
The company also has a history of retaliating against dissenting opinions from that of the leadership.
The leadership fears criticism and will often deflect and deny that there are any issues, and make unreasonable demands and deadlines.
Eliminating QA altogether and focusing on AI are two mistakes that will degrade the quality of the product and the customer experience.
The leadership is out of touch with the reality of work within the company and is making decisions that the majority of employees disagree with.
The only reason I rated this as a negative experience was due to the lack of communication with the recruiter. I understand people get busy, but isn't the job of a recruiter to reply and interact with potential candidates? I went through the first i
I interviewed specifically for an Android role there. Typical process: * Initial phone screening * Onsite: * Two technical interviews: One looking at code and the other building a basic list. * Hiring manager round * Collaborating behav
Easy OA with 2 coding questions. Phone round with behavioral, which is essentially a chat with the recruiter. Straightforward graph question in the final round, which essentially tested traversal. The terminology was custom-made, making it a bit ha
The only reason I rated this as a negative experience was due to the lack of communication with the recruiter. I understand people get busy, but isn't the job of a recruiter to reply and interact with potential candidates? I went through the first i
I interviewed specifically for an Android role there. Typical process: * Initial phone screening * Onsite: * Two technical interviews: One looking at code and the other building a basic list. * Hiring manager round * Collaborating behav
Easy OA with 2 coding questions. Phone round with behavioral, which is essentially a chat with the recruiter. Straightforward graph question in the final round, which essentially tested traversal. The terminology was custom-made, making it a bit ha