Pros: Awesome perks. Exciting and dynamic environment. Great learning experience. Very casual and friendly employees. Chance to work with the best in the world.

Cons: At every step, I have to learn by myself. Everything is mostly self-service. So, it's hard if you're not good with technology.

Pros: Good pay, on par with software engineers.

Cons: Subpar managers and leadership. Feels like a service-based company inside the Facebook org. Most teams are bloated and hardly have any meaningful work. Engineers often have to fend for themselves and find work. Managers are empire builders.

Pros: - Working on high-impact projects that are challenging and meaningful. - More flexibility with office locations than traditional SWE roles (e.g., there are EE teams in Austin but no SWE teams). - Hard to imagine a better place to learn and grow as an engineer. - A lot of EE teams are continuously finishing projects and beginning new ones, so you can have a lot more variety in what you're working on, which makes it much easier in my opinion to choose projects you find interesting or want to learn more about.

Cons: - It's hard to switch from EE teams to SWE teams (requires re-interviewing) if you're in one of the big engineering offices. - Since traditional EE roles dealt more with things like Oracle development, you can get the feeling that EE is looked down on by SWE orgs. I think this is changing quickly as the role evolves and people realize the complex problems EEs are solving, but we're not there yet in terms of having the same 'prestige' as SWEs. - Deadlines can be tight depending on business needs. - It's on you to determine how much you want to work. This is a double-edged sword because you can work a ton in order to drive quicker promotions, but you also have to be proactive in forcing work/life balance, as there's always more work you could be doing.