Software Engineers of the Enterprise World
Software Engineers of the Enterprise World
- 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.
-
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.
- Continue to take engineers' input in roadmap planning, as we're often the front lines who see inefficiencies or problems firsthand.
- Do a better job advertising what Enterprise Engineering is and where open roles are, so SWE candidates who want to live in places like Austin know that Enterprise Engineering is an option.
Was this helpful?
Meta Interview Questions
Meta Interview Experiences
Enterprise Engineer
The process started with an invitation to speak with a technical recruiter. That was a 30-minute conversation with questions about myself and my goals. The next interview was a technical one featuring LeetCode questions. After that, I had an onsite
Enterprise Engineer
- Multiple calls with recruiter - Mock call with Enterprise manager Everything was scheduled as per my availability. No pressure from Meta. The interview was held in two days. First day: 2 system design and behavioral. Second day: 3 coding. Yes,
Enterprise Engineer
The whole process had 4 interviews in my case: * 2 technical * 1 behavioural * 1 system design All the interviews were remote and performed on 3 different days. Technical rounds involved 2 LeetCode problems (medium difficulty) to solve withi
Enterprise Engineer
Austin, Texas, United StatesJuly 1, 2020The process started with an invitation to speak with a technical recruiter. That was a 30-minute conversation with questions about myself and my goals. The next interview was a technical one featuring LeetCode questions. After that, I had an onsite
Enterprise Engineer
Durham, North Carolina, United StatesAugust 1, 2022- Multiple calls with recruiter - Mock call with Enterprise manager Everything was scheduled as per my availability. No pressure from Meta. The interview was held in two days. First day: 2 system design and behavioral. Second day: 3 coding. Yes,
Enterprise Engineer
PolandMay 12, 2022The whole process had 4 interviews in my case: * 2 technical * 1 behavioural * 1 system design All the interviews were remote and performed on 3 different days. Technical rounds involved 2 LeetCode problems (medium difficulty) to solve withi
