RepostedMeta logo

Meta · OA → Phone screen → Onsite

In process

Meta Production Engineer Intern Questions: 6 Experiences

Production Engineer Intern Roundup · InternshipNov 2024
Shared by

Meta Production Engineer intern reports, 2019–2025: a Linux quiz, a 45-minute coding round on files, CSV or streams, then a Linux and OS systems round.

At a glance

  • Process: an 18–20 question Linux and OS quiz (sometimes due within three business days), a 45-minute coding interview with two tasks, then a 45-minute systems or "PE basics" interview (01, 02, 03).
  • Asked recently: file or stream processing in all 3 current reports: top N words in a file (02), the fastest-dinosaur CSV join (01) and a vmstat threshold alert script (03). Systems rounds covered virtual memory, processes, signals and system calls; two had a design question (01, 02).
  • Difficulty: the coding was approachable; the follow-ups in the systems round were what candidates found hard. Two of three current candidates were rejected (01, 02).
  • Practise first: Fastest Dinosaur CSV, Top N Words in a File and Column Threshold Stream Alert.

Coverage: Meta Production Engineer internships in Tel Aviv, London/Dublin, Menlo Park/Bellevue and the UK. Six reports: three current (early 2024 to September 2025) and three older ones in History (November 2019 to February 2022).

What came up

Production Engineering coding is practical: read a file or a stream, count or join records, and print a result. The systems interview goes deep on Linux.

Topic Reports Last seen
File, CSV or stream processing 3 of 3 Sep 2025 (report date)
Linux and OS concepts 3 of 3 Sep 2025 (report date)
Linux and OS quiz 3 of 3 Sep 2025 (report date)
Design (Reddit-like or system and schema) 2 of 3 Sep 2025 (report date)
Classic algorithm (parentheses, friend requests) 2 of 3 Dec 2024

A candidate can appear in more than one row.

Questions we found

Algorithms and scripting

Question Reports Last seen
Fastest dinosaur from two CSV files 1 Sep 2025 (report date)
String manipulation (not specified) 1 Sep 2025 (report date)
Top N words in a text file 1 Dec 2024
Centaur friend requests by age rules 1 Dec 2024
Valid Parentheses 1 Feb 2024 (report date)
Alert on a streaming column above a threshold 1 Feb 2024 (report date)

Systems and design

Question Reports Last seen
Design something like Reddit (practice) 1 Sep 2025 (report date)
OS concepts, signals and how Linux works 1 Sep 2025 (report date)
System design and database schema 1 Jan 2025
Virtual memory, context switches, process lifecycle, paging, copy-on-write, and vmstat, iostat, strace, pidstat 1 Feb 2024 (report date)

3 detailed candidate timelines, loops, and screens

01: Tel Aviv: dinosaurs, strings and a Reddit-like design

Report date: Sep 2, 2025 · Role: Production Engineer Intern · Location: Tel Aviv-Yafo · Result: No offer

  1. A referral, then 18 operating-systems questions, then two online interviews.
  2. Coding: the dinosaur CSV problem and a straightforward string question.
  3. Systems: OS concepts, signals and how Linux works, plus a design-pattern question on something like Reddit. They still called it a positive experience.

02: London/Dublin: word counts, centaurs, then design

Interview date: Dec 2024 – Jan 2025 · Role: Production Engineer Intern (undergraduate) · Location: London/Dublin · Result: Rejected (Feb 5, 2025)

  1. Applied in November; recruiter call November 27 on graduation, availability and interest in PE. A 20-question Linux fundamentals test due in three business days, taken December 2, with good feedback the next day.
  2. Coding (Dec 12, 45 min): print the N most frequent words in a text file, with filename and N from the command line. They asked about missing files, errors and fewer than N distinct words, then counted and sorted (a heap would be faster). The interviewer moved on, so they asked to state the complexity themselves.
  3. Second task: count friend requests between centaurs. The recipient must be at least sender_age / 2 + 7, not older than the sender, and a sender over 100 cannot message anyone under 100. Brute force, checked on an example; no time for complexity. Positive feedback a day later.
  4. PE basics (Jan 10, 45 min, after two reschedules): more system design and database schema than the OS questions they expected; conversational, with hints (the interviewer reminded them of the listen system call).

03: Menlo Park/Bellevue: parentheses, a vmstat script, deep OS

Report date: Jan – Feb 2024 · Role: Production Engineer Intern · Location: Menlo Park/Bellevue · Result: Not shared

  1. Quiz: multiple-choice and multiple-select, including networking (which did not come up later).
  2. Coding: Valid Parentheses, and a script that watches streaming input such as vmstat 1 | yourscript 7 5 200: track one column and alert after enough consecutive readings over a threshold, skipping repeated header rows. Whether the alert fires on the fifth or sixth reading was unclear.
  3. Final (conceptual): virtual memory and allocation, context switches and system calls, process lifecycle (zombie and orphan), paging, demand paging and swapping, the kernel, copy-on-write, filesystem memory, and tools such as vmstat, iostat, strace and pidstat.
  4. They studied four to six hours a day for a week; a mock interview helped.

History (before November 2023)

These three reports are more than three years old, so they stay out of the counts and tables above.

04: London/Dublin: equal-sum split and dinosaurs

Interview date: Jan – Feb 2022 · Role: Production Engineer Intern (undergraduate, India) · Location: London/Dublin · Result: Rejected

  1. A referral; recruiter a week later; a 20-minute quiz on Linux internals, OS and networking.
  2. Coding (45 min): can the array split into two contiguous parts with equal sums (total sum, then scan for half)? Then rank bipedal dinosaurs by speed from two CSV files with a map and a priority queue. Both solved; advanced within a week.
  3. Systems (45 min, Feb 15): processes and threads, fork–wait–exec, what happens on ls -l *, reading Linux command output, swap, virtual memory, buffers and cache, with relentless follow-ups. Rejected two or three days later.

05: UK: a ten-week process ending in troubleshooting

Interview date: Jan – Feb 2021 · Role: Production Engineer Intern · Location: UK · Result: Rejected

  1. A 20-question Linux quiz; coding with the dinosaur parsing problem and an equal-sum array split; then a Linux troubleshooting interview they found hard to explain smoothly. Rejected over a week later.

06: Menlo Park: a 70% quiz and no code execution

Interview date: Nov 2019 · Report date: Jan 2020 · Role: Production Engineer Intern · Location: Menlo Park · Result: Rejected

  1. About 20–25 Linux MCQs in 18 minutes (ls -lSh, log locations, signals, debugging tools); they scored 70% and advanced.
  2. CoderPad (45 min, execution off): an equal-sum split, O(n²) first, then O(n) with hints; then the fastest dinosaur of a type from CSV, with questions on memory and why a dictionary. About half finished. Rejected a week later.

Patterns across the reports

  1. The dinosaur CSV task keeps coming back. It appears in 01 here and in three older reports (04, 05, 06).
  2. The systems round goes deep. Candidates described follow-ups well past definitions (03, and older 04, 05).

Common questions

What is on the Meta Production Engineer intern quiz?

18–20 questions on Linux, operating systems and sometimes networking, with some multiple-select (01, 02, 03).

What coding does Meta ask Production Engineer interns?

File and stream tasks: top N words in a file (02), the dinosaur CSV join (01) and a vmstat alert script (03), plus classics like Valid Parentheses (03).

What is the Meta PE systems interview?

Linux and OS concepts: memory, processes, system calls, signals and tools like strace (01, 03), sometimes with design (02).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.