← Back to Directory

Apple interview notes, page 15 of 38

FAANG / Big Tech

Most of these Apple write-ups come from Software Engineers (212), then Machine Learning Engineers (85) and Data Scientists (32). The most reported rounds are the technical phone screen (217), the system design round (48), the product sense round (29) and the behavioral / leadership round (22).

372 interview notes · updated Oct 2026

Apple·Machine Learning Engineer·Technical Phone Screen

May 2026
Apple ML engineer interview, got a pretty standard machine learning fundamentals question about logistic regression. Nothing too wild but it required more depth than I expected.
  • Walk me through how you would fit data using logistic regression.

“I started with the loss function and gradient descent which felt right, but then they pushed on convergence criteria and regularization and I got a bit fuzzy.”

View Post

Apple·Software Engineer·Technical Phone Screen

May 2026
Apple SWE interview where the main coding portion was followed by a follow-up question that reused the same data structure. Short session, not a lot of detail to go on.
  • After completing the initial coding problem, solve a follow-up question that builds on the same data structure used in the first part.

“The follow-up came right after I finished the first problem.”

View Post

Apple·Software Engineer·Onsite - System Design / Architecture

May 2026
Apple infrastructure or hardware-adjacent design interview, single question about designing a port in San Francisco. Not a lot of context given so I had to figure out on my own whether this was a physical port, a software port, or some kind of networking thing. Weird one.
  • How would you design a port in San Francisco?

“I stared at this for a second because I genuinely wasn't sure if they meant a physical shipping port, a network port, or something else entirely.”

View Post

Apple·Software Engineer·Technical Phone Screen

May 2026
Apple SWE coding round, one matrix problem that sounds straightforward until you actually think through all the diagonal cases.
  • Given an m by n boolean matrix, determine whether any row, column, main diagonal, or anti-diagonal (at 45 degrees) consists entirely of true values.

“Rows and columns were fine, I had that part coded up pretty fast.”

View Post

Apple·Software Engineer·Technical Phone Screen

May 2026
Apple SWE coding round, one question based on a graph problem. Pretty light on details but the core challenge was working with a graph represented as a list of nodes rather than the usual adjacency matrix setup.
  • Given a graph represented as a list of nodes, solve a variant of a classic graph traversal problem.

“The twist was the input format.”

View Post

Apple·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Apple system design round, one question about building a shape-detection system. Sparse on details but it's the kind of open-ended prompt that can go a dozen different directions depending on what the interviewer actually wants.
  • Design a shape-detection system.

“Wide open prompt and I spent probably too long figuring out what scope they even wanted.”

View Post

Apple·Software Engineer·Onsite - Coding / Algorithms

May 2026
Apple SWE onsite, third round, one coding question. Not much to go on from what I remember but it was a standard LC-style problem.
  • Solve a LeetCode-style coding problem.

“It was a coding question, that's about all I can say.”

View Post

Apple·Data Scientist·Technical Phone Screen

May 2026
Quick Apple interview that came down to one statistics question. Nothing fancy, just pure probability theory on the spot.
  • What is the expectation of the variance?

“Blanked for a second because it sounds so clean and simple.”

View Post

Apple·Software Engineer·Onsite - System Design / Architecture

May 2026
Apple SWE interview with a system design and OOD focus. The main problem was designing a deck of cards with shuffle and draw operations, which sounds almost too simple until you actually have to argue about probability guarantees and complexity out loud.
  • Design a deck of playing cards with Card, Deck, and supporting classes (like Suit and Rank enums). Implement shuffle() to produce a uniformly random permutation and draw() to remove and return a card while preserving uniform-random order. Discuss the correctness of the probability argument and the complexity of each operation.

“I started with the class structure which was fine, Suit and Rank as enums, Card as a simple value object, Deck holding a list.”

View Post

Apple·Product Manager·Onsite - Product Sense / Strategy

May 2026
Product sense round at Apple for a PM role, one question about designing a maker-checker workflow for a finance platform. Pretty focused session, no fluff.
  • Design a maker-checker feature for a finance platform where every manual action requires two people: one to execute and one to approve.

“I went straight into the user flow and kind of forgot to frame the problem first.”

View Post