Apple Software Engineer Onsite Coding Questions
150+ questions from real Apple Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Apple Onsite Coding round test?
The Apple onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Apple Software Engineer Onsite Coding Questions
Apple Two-Round Pure Coding Interview Experience: Prefix Sum and Tree Iterator
Given an integer array nums and an integer k, find all continuous subarrays whose sum is exactly equal to k.Solution ApproachUse prefix sum + hash map. Maintain the current prefix sum sum. If sum - k
What are the chances? Apple interview
So I just finished a final round (virtual onsite) with apple for swe role (it’s a niche one, not general swe). They were 5 rounds in the final round (excluding the initial 15 minutes with recruiter),
Apple additional coding interview after onsite
Hey guys, I have received positive feedback from recruiters after panel interview with Apple three weeks ago and we discussed salary expectations. I was told that the verbal offer will come in a week
Expedia Group | Onsite Interview | SDE2 | Bangalore, India | Puzzle | 2D Matrix | Binary Tree
I had Expedia Group Onsite Interview (conducted virtually) for SDE 2 role, Bangalore location. The interview lasted for 1.5 hrs. Below are the questions - 1. Puzzle -> There are 3 Jars....
Hyderate The Nodes
Hello, Recently I gave a coding interview test at a company. This was one of the problem I was unable to solve. Can anyone please guide me through the approach and...
Apple Onsite
Apple onsite interview question. Design a class which implements following functions: func insertOrReplace(_ item: Int, at index: Int) func getMinIndex(of element: Int) -> Int
#146 LRU Cache
LeetCode #146: LRU Cache. Difficulty: Medium. Topics: Hash Table, Linked List, Design, Doubly-Linked List. Asked at Apple in the last 6 months.
#362 Design Hit Counter
LeetCode #362: Design Hit Counter. Difficulty: Medium. Topics: Array, Binary Search, Design, Queue, Data Stream. Asked at Apple in the last 6 months.
#1 Two Sum
LeetCode #1: Two Sum. Difficulty: Easy. Topics: Array, Hash Table. Asked at Apple in the last 6 months.
#200 Number of Islands
LeetCode #200: Number of Islands. Difficulty: Medium. Topics: Array, Depth-First Search, Breadth-First Search, Union-Find, Matrix. Asked at Apple in the last 6 months.
#206 Reverse Linked List
LeetCode #206: Reverse Linked List. Difficulty: Easy. Topics: Linked List, Recursion. Asked at Apple in the last 6 months.
#210 Course Schedule II
LeetCode #210: Course Schedule II. Difficulty: Medium. Topics: Depth-First Search, Breadth-First Search, Graph Theory, Topological Sort. Asked at Apple in the last 6 months.
#53 Maximum Subarray
LeetCode #53: Maximum Subarray. Difficulty: Medium. Topics: Array, Divide and Conquer, Dynamic Programming. Asked at Apple in the last 6 months.
#56 Merge Intervals
LeetCode #56: Merge Intervals. Difficulty: Medium. Topics: Array, Sorting. Asked at Apple in the last 6 months.
#253 Meeting Rooms II
LeetCode #253: Meeting Rooms II. Difficulty: Medium. Topics: Array, Two Pointers, Greedy, Sorting, Heap (Priority Queue), Prefix Sum. Asked at Apple in the last 6 months.
#713 Subarray Product Less Than K
LeetCode #713: Subarray Product Less Than K. Difficulty: Medium. Topics: Array, Binary Search, Sliding Window, Prefix Sum. Asked at Apple in the last 6 months.
#981 Time Based Key-Value Store
LeetCode #981: Time Based Key-Value Store. Difficulty: Medium. Topics: Hash Table, String, Binary Search, Design. Asked at Apple in the last 6 months.
#1146 Snapshot Array
LeetCode #1146: Snapshot Array. Difficulty: Medium. Topics: Array, Hash Table, Binary Search, Design. Asked at Apple in the last 6 months.
#23 Merge k Sorted Lists
LeetCode #23: Merge k Sorted Lists. Difficulty: Hard. Topics: Linked List, Divide and Conquer, Heap (Priority Queue), Merge Sort. Asked at Apple in the last 6 months.
#49 Group Anagrams
LeetCode #49: Group Anagrams. Difficulty: Medium. Topics: Array, Hash Table, String, Sorting. Asked at Apple in the last 6 months.
What to Expect in the Apple Onsite Coding Round
The Apple Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 150+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Apple show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Apple typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Apple Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 150 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access