RepostedApple logo

Apple · OA → Phone screen → Onsite

In process

Apple New Grad SWE and Embedded: 16 Experiences (Part 2 of 3)

Software engineer · New GradNov 2021
Shared byJaneBeingJane

Apple new grad and early-career SWE reports, 2023 to 2025: C and embedded screens, Dijkstra and topological sort, and panels of four to seven interviews.

At a glance

  • Process: a recruiter or hiring-manager screen, one or two technical screens, then either a panel of four to seven interviews (10, 11, 17) or a few team-matching interviews (19, 21). Some loops ran fast: New York IS&T finals came the day after the screen (21).
  • Asked recently: coding in 9 of 14 current reports, from runnable C problems to LeetCode Medium; C, memory and embedded topics in 4 (10, 11, 12, 15); behavioral or resume talk in 6.
  • Difficulty: candidates called the coding LeetCode Medium (16, 23); a Taipei candidate stalled on Dijkstra without a ready heap in C (10), and a firmware candidate needed hints on bitmasking (15).
  • Practise first: Shortest-Path Distances with Dijkstra, Topological Ordering, Rotate Array by K and Print a Diamond Pattern.

Coverage: Apple new grad and early-career software roles: SWE new grad, IS&T, Evolve, storage, DevOps and reliability, plus embedded and firmware graduates. Fourteen current reports from October 2023 to November 2025, and two older ones (2022–2023) under History. Taipei, Cork, New York, Austin, Cupertino, California and other US locations where stated.

In this series

  • Part 1: entries 01–09, the 2026 reports: C screens, BigDecimal questions and five-interview panels.
  • Part 2 (current): entries 10–25, 2023–2025: Taipei, Cork, Austin, New York and US teams, plus two older reports.
  • Part 3: entries 26–37, 2015–2022: Evolve, a graduate placement OA, phone screens and C tasks.

What came up

Most of these candidates coded, but embedded and firmware roles also leaned on C details, memory and hardware. Counts are out of the 14 current reports in this part.

Topic Reports Last seen
Coding and data structures 9 of 14 Nov 2025
Behavioral, resume or recruiter talk 6 of 14 Nov 2025
C, memory and embedded topics 4 of 14 Nov 2025
Graphs (shortest path, topological sort) 2 of 14 Oct 2025
OS and CS fundamentals 2 of 14 Nov 2025
Reading or reviewing code 2 of 14 Sep 2025 (report date)
Linux experience 1 of 14 Aug 2025
iOS app experience 1 of 14 Feb 2024

A candidate can appear in more than one row.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Shortest paths, a Dijkstra-style task, in C 1 Oct 2025
Topological sort 1 2025
Print a diamond shape to standard output 1 Sep 2025 (report date)
Rotate an array by k 1 Oct 2024

C, embedded and hardware

Question Reports Last seen
What does static mean in C versus C++? 1 2025
Where do variables live: heap, stack, globals or code memory? 1 Sep 2025 (report date)
When would you choose SPI, I2C or UART? 1 2025
How do you check that a new prototype board works? 1 2025
Read poor C code, explain it and fix it 1 2025

Behavioral (BQ)

Question Reports Last seen
What skills do you have, and what are your plans after graduating? 1 Nov 2024
Which iOS apps have you built, and how would you improve one? 1 Feb 2024

14 detailed candidate timelines, loops, and screens

10: Taipei: C, a Dijkstra task and a seven-interview afternoon

Interview date: October–November 2025 · Role: SWE new grad, 2026 cohort · Location: Taipei (Xinyi) · Result: Rejected

Recruiter call and phone interview

  1. A recruiter called the morning after they applied and gave a short C test after checking details.
  2. The technical phone interview had two runnable C problems and some OS questions, with hints when they got stuck.
  3. The second problem was a classic task they would normally solve with Dijkstra. Without a heap ready in C, they stalled. The interviewer said the fastest method was not needed, so they switched to an array but ran out of time. The exact graph variant was not shared. They still passed the next day.

November onsite

  1. An afternoon at the Xinyi office. It began with a pointer-manipulation problem, not the linked-list question they expected. They misread it at first and made several small C mistakes, with nearly ten people watching in the room and online. The operation itself was not described.
  2. Seven one-on-one interviews followed on OS, the resume and behavioral topics, in Chinese and English. They left at 6 p.m. and got a rejection more than a week later.

11: An embedded graduate also screened for SDE

Interview period: October 2024 to October 2025 · Role: Embedded and firmware new grad, plus one SDE screen · Location: US

  1. Over several Apple applications: three first-round interviews and two panels, one of a screen plus four interviews and one of a screen plus five. One panel was set for more than four interviews over two days.
  2. One question compared static in C and C++.
  3. HR moved one application to an SDE interview. That screen asked for a topological sort, which they tried in C and did not finish.

12: An embedded recruiter screen about memory

Report date: September 3, 2025 · Role: Embedded, security-related · Location: Outside the US (country not given)

  1. The recruiter asked where variables live: heap, stack, global storage or code memory.
  2. The candidate had a cybersecurity background, and the job leaned toward security. No later round or result was reported.

13: Print a diamond as a new grad

Report date: September 3, 2025 · Interview date: an earlier new grad application, year not given · Role: Embedded software

  1. The candidate recalled being asked to print a diamond shape to standard output.
  2. Size, filled or hollow, and spacing rules were not given.

14: An IS&T reliability screen on Linux

Interview date: August 2025 · Role: Early-career software engineering, DevOps and reliability · Location: US

  1. A first interview of about 20 minutes, focused on their Linux experience and related questions.
  2. No command, troubleshooting case or coding task was shared.

15: A firmware role that wanted four years

Report date: September 3, 2025 (interview a few months earlier) · Role: Firmware engineering · Result: Rejected after two technical interviews

  1. Two technical interviews a week apart, with kind and encouraging interviewers.
  2. Topics: bit manipulation; when to choose SPI, I2C or UART; how to check that a new prototype board works during bring-up; and reading poor C code to explain it and fix it.
  3. They struggled with the coding and needed time and hints on a bitmasking question. Neither the bitmask task nor the code's purpose was shared.
  4. The rejection came about a week after the second interview. They were a new graduate; the posting asked for four years of experience.

16: A storage-team call with a file question

Report date: July 30, 2025 (call update the next day) · Role: Entry-level SWE, Distributed Systems and Storage · Location: California · Result: Waiting in early August

  1. A referral led to a recruiter about a month later. The first call was planned as a 45-minute coding interview.
  2. The call had one LeetCode Medium question about files, past experience and team matching. The task's operation and output were not shared.

17: Manager interviews that kept the coding going

Interview date: July 2025 · Role: SWE new grad, full time · Location: US

  1. After passing a five-interview virtual panel, the candidate met the hiring manager, a more senior manager and a director.
  2. They said these talks were very technical, with coding, and felt like more of the loop. No task was named.

18: Cork: a mostly behavioral first interview

Report date: February 24, 2025 · Role: Graduate Software Engineer · Location: Cork, Ireland · Result: No offer

  1. Applied online, then met two senior engineers from the team.
  2. After a short introduction, most questions were behavioral. Only the opening words of one "Tell me about a time" question were shared. No coding was reported.

19: IS&T: a DSA screen and three team interviews

Report date: December 9, 2024 · Role: Early-career SWE, IS&T (not Evolve) · Location: US · Result: Offer

  1. A June 2024 graduate. Stage one was a pure data-structures-and-algorithms screening call.
  2. Stage two was three virtual team-matching interviews mixing DSA, CS fundamentals and behavioral questions. No prompt was shared.

20: A recruiter screen before a possible hiring event

Interview date: November 2024 · Role: SWE new grad · Location: Cupertino

  1. The recruiter called and asked about their skills and plans after graduating.
  2. Passing could lead to an invite to a concentrated hiring event. Whether that happened was not reported.

21: New York IS&T: a screen, then finals the next day

Interview date: October 2024 · Role: SWE new grad, IS&T · Location: New York

  1. No OA or separate recruiter call: the recruiter went straight to a technical first interview.
  2. Virtual finals followed the next day, before the team was known. One task was to rotate an array by k; direction and in-place rules were not recalled.

22: Austin: explain and improve an iOS app

Interview date: February 2024 · Role: SWE new grad · Location: Austin · Result: Did not advance

  1. A recruiter set up a technical interview about a week after reaching out.
  2. They were asked about iOS apps they had built and how they would improve one. No shared coding exercise was described.

23: Evolve: essays, a coding interview and a code review

Interview period: October–November 2023 · Role: Evolve new grad program · Result: Waiting

  1. Applied without a referral or OA, answered essay questions and heard back about a week later.
  2. A LeetCode Medium-style first interview, then a code-review interview. Neither the prompt nor the code was shared. More than a week after the review they were still waiting.

History (before November 2023)

H24: Grace Hopper: three hours in line, four minutes with a manager

Interview date: September 2023 · Role: SWE new grad · Event: Grace Hopper Celebration

  1. After about three hours in line, they spoke to a hiring manager for about four minutes.
  2. The questions: introduce yourself, and why Apple?

H25: A message to an engineering manager, and a Python problem

Job search: 2022–2023 · Role: Graduate software engineering

  1. The graduate messaged an Apple engineering manager directly and got an interview.
  2. The team members did not react well to their use of Python, and the process stopped. No coding question was shared. This was one team's reaction, not an Apple rule.

Patterns across the reports

  1. C shows up for embedded and Taipei roles. Runnable C problems (10), static in C and C++ (11), memory regions (12) and reading C code (15).
  2. Graphs in screens. Two screens asked graph tasks: Dijkstra-style shortest paths (10) and topological sort (11).
  3. Manager rounds can be technical. Report 17 said the manager talks included coding, and report 19's team-matching interviews mixed DSA with behavioral questions.

Common questions

What coding questions does Apple ask new grads?

Named tasks here: a Dijkstra-style shortest path (10), topological sort (11), printing a diamond (13) and rotating an array by k (21). Two candidates called the level LeetCode Medium (16, 23).

Does Apple ask C questions in new grad interviews?

For C-heavy and embedded roles, yes: runnable C problems in Taipei (10), static in C versus C++ (11), where variables live in memory (12) and fixing poor C code (15).

How many interviews are in the Apple new grad panel?

Reports ranged from four or five after a screen (11, 17) to seven one-on-ones in one afternoon in Taipei (10). IS&T used three team-matching interviews (19).

Are Apple hiring manager interviews behavioral?

Not always. Report 17 said the manager and director talks were highly technical, with coding.

Keep practicing

In this series

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.