Business oriented - there's no engineering representation on Wayfair's leadership page!
Thrifty in spending - don't expect additional equity or any spectacular increase in your pay while you are employed here.
Absentee leadership - all decisions flow down from business without a care in the world about tech debt.
Tech debt - To give you an idea, Wayfair only has one real environment for developers, and almost all testing of features is performed in production. The cost for actually maintaining a development or staging environment is apparently too high. We'd rather have our website stop working for customers than fix a fundamental issue. But we are super business-oriented in cramming in as many features as possible!
Quantity over quality in code - Unit tests? Linting? They're turned off because engineering leadership decided that the key metric to target is increased speed to output.
Quantity over quality in engineers - The median tenure is under a year, and the turnover is extremely high. Absolute zero value is placed on time at Wayfair.
Stop selling new recruits that Wayfair is a tech company until engineering is represented on the leadership page.
Go after quality rather than quantity with engineers.
Tackle longstanding issues with tech debt by promoting a culture of higher code quality, with a strong directive from upper management rather than paying lip service to the underlying fundamental issues.
A recruiter reached out to me via Hired.com. We had a brief conversation about my experience and what they were looking for. The recruiter sent me an email later saying that I wasn't a good fit and wasn't enthusiastic about the company.
First Round: Online Assessment on HackerRank. Two questions, very easy. Second Round: Live interview. Asked to code an object-oriented style program in Java. Grilled with questions on design patterns. No response after the first two rounds.
The interview process was not properly structured. The recruiter was communicative most of the time and provided helpful prep materials. However, the interview scheduling coordinators lacked organization. First, they scheduled an interview and sent
A recruiter reached out to me via Hired.com. We had a brief conversation about my experience and what they were looking for. The recruiter sent me an email later saying that I wasn't a good fit and wasn't enthusiastic about the company.
First Round: Online Assessment on HackerRank. Two questions, very easy. Second Round: Live interview. Asked to code an object-oriented style program in Java. Grilled with questions on design patterns. No response after the first two rounds.
The interview process was not properly structured. The recruiter was communicative most of the time and provided helpful prep materials. However, the interview scheduling coordinators lacked organization. First, they scheduled an interview and sent