eBay

Really good work/life balance.

If you want to work somewhere from 10 to 5, have frequent days off, don't need to learn anything new, and complete 2 things in an entire year, this is the place for you.

Tech stack is atrocious.

Politics of a large company.

Lack of credibility of higher management.

Legacy Java stack with domain-specific reinventions of open-source libraries that are worse in every way. Attempts to improve the stack get lip service but no competent infrastructure support. There is no serious movement to update the stack and fix things. New libraries and wrappers are written to interface with broken and dysfunctional legacy systems, so even using the new stack doesn't actually increase code productivity.

Almost all of the smart engineers have left or are leaving, so you won't get significant mentorship. As a junior engineer, I am actually reverse-mentoring senior engineers, architecting the entire project, and implementing a supermajority of everything on my project. Also, promotions and wages aren't matching what startups are offering to pay now. Due to constant reorgs, promotions are hard to come by, while less qualified individuals get hired at higher ranks due to age.

Something which would take you 2 days to complete takes 2+ months at eBay due to the stack and process.

Build credibility by sticking to what you say instead of constant reorgs and strategy changes every 3 months. Be truly open and honest instead of just preaching it.

Work on a complete reinvention of the site from the ground up; throw away all of the legacy systems.

Use open source technologies and ONLY open source technologies in the rewrite; don't make Inc-specific wrappers or variations of those libraries which are worse.

Don't reinvent things like CSS, logging, or server frameworks!

Reduce management and meetings, and just let competent engineers get things done. Senior engineers go to meetings almost all their time and contribute little or nothing to the company as a result, even if they wanted to code. Focus on what people get done rather than how visible they are or how good the presentations look. Favor succinct code rather than millions of copy-pasted code.

Do something about the fact that at least one internal system is always down every Friday.