Enterprise Engineer Interview Experience - London, United Kingdom
Process
A recruiter reached out to me on LinkedIn. We then had a phone call about the role, and subsequently set up the screening interview.
Screening Interview: The technical interviewer seemed uninterested in learning about me or my experience. After explaining the interview format, they proceeded directly to the questions. I even asked at the end what to expect in the next round if I passed, but they refused to answer and did not offer any general tips.
Overall, the interview was fairly easy, but I wasn't able to complete the questions within the allocated 20 minutes per question.
My advice is to strictly limit your answers to 20 minutes during practice sessions and ensure you get a good amount of sleep.
Questions
2 questions:
-
A function that would work as
cdin Linux. It accepts a path and, according to the input, should output the correct path. -
BST: Find the nearest node to a given node.
Was this helpful?
Interview Statistics
The following metrics were computed from 4 interview experiences for the Meta Enterprise Engineer role in London, United Kingdom.
Success Rate
Meta's interview process for their Enterprise Engineer roles in London, the United Kingdom is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Meta's Enterprise Engineer interview process in London, United Kingdom.
Meta Work Experiences
- 4.0Smart Team, Average ProjectEnterprise Engineer • Former EmployeeFremont, California, United StatesNovember 18, 2024Pros: - Smart People - CaringCons: The project or team wasn't super interesting.
- 5.0Software Engineers of the Enterprise WorldEnterprise Engineer • Current EmployeeAustin, Texas, United StatesFebruary 20, 2020Pros: - 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.
- 5.0Excellent Tech, Team DependentEnterprise Engineer • Current EmployeeMenlo Park, California, United StatesSeptember 16, 2021Pros: Tech stack is the best.Cons: Too big, experience depends on the team.
Meta Interview Questions
