Software engineering interviews are not one test. They are three: coding ability, system design thinking, and how you behave under pressure with other humans. The candidates who land offers prepare for all three on different schedules.
The shape of a typical loop: a phone screen with one or two coding problems, then a four to six round onsite with two or three coding rounds, one or two system design rounds (mid-level and up), and one or two behavioral rounds.
Coding: arrays and strings
- Two Sum. Hash map for O(n).
- Longest Substring Without Repeating Characters. Sliding window with a set.
- Container With Most Water. Two pointers, move the shorter side.
- Valid Anagram. Frequency count or sort.
- Merge Intervals. Sort by start, merge greedily.
Coding: trees and graphs
- Validate Binary Search Tree. Pass min and max bounds in recursion.
- Lowest Common Ancestor. Recursive DFS, return on match.
- Number of Islands. DFS or BFS from each unvisited land cell.
- Clone Graph. Hash map of cloned nodes plus BFS or DFS.
- Course Schedule. Topological sort, detect cycles.
Coding: dynamic programming
- Climbing Stairs. Fibonacci. dp[i] = dp[i-1] + dp[i-2].
- Longest Increasing Subsequence. Binary search for O(n log n).
- Coin Change. Bottom-up DP, dp[i] = min(dp[i], dp[i-coin] + 1).
- Word Break. DP plus a dictionary set lookup.
- Edit Distance. 2D DP over insert, delete, replace.
Coding: linked lists
- Reverse Linked List. Track prev, curr, next.
- Merge Two Sorted Lists. Dummy head, compare and link.
- Linked List Cycle. Floyd's slow and fast pointer.
- Remove Nth From End. Two pointers n apart.
- LRU Cache. Hash map plus a doubly linked list.
System design: the framework
Every system design round wants the same five moves, in order. Clarify functional and non-functional requirements. Estimate scale (users, QPS, storage, bandwidth). Sketch a high-level design with components and data flow. Go deep on the components that matter. Then address the bottlenecks: scaling, reliability, and where things break under load.
System design: ten classic prompts
- URL shortener. Hash function, base62, DB choice, caching, analytics, expiration.
- Twitter or X. Fan-out on write vs read, timeline generation, celebrity accounts, sharding.
- Chat application. WebSockets, delivery guarantees, presence, push, encryption.
- Video streaming. Encoding pipeline, adaptive bitrate, CDN, recommendations, storage tiers.
- Rate limiter. Token bucket, sliding window, distributed coordination, Redis.
- Search engine. Inverted index, ranking, crawl strategy, query processing.
- E-commerce. Inventory, cart persistence, payments, flash sales, fulfillment.
- Ride sharing. Geospatial indexing, location updates, matching, surge, ETA.
- Notifications. Priority queues, delivery guarantees, templates, throttling.
- Distributed cache. Consistent hashing, replication, eviction, invalidation.
Behavioral: the STAR shape
Situation, Task, Action, Result. Spend the most time on Action. Quantify Result when you can.
Leadership and initiative
- A project you led, including the decisions you owned.
- A time you went beyond your role.
- A problem you spotted and fixed without being asked.
- Someone you mentored.
- Your most impactful project, with the business outcome.
Conflict and challenge
- A disagreement with a teammate and how it resolved.
- Critical feedback you received and acted on.
- A real failure, owned, with the lesson.
- A difficult person you worked alongside.
- A tough decision and the trade-offs.
Technical problem-solving
- A complex bug or system issue you debugged.
- Something you had to learn fast and ship.
- A process or system you improved with measurable results.
- How you balance multiple priorities.
- Shipping under a tight deadline without lowering quality.
Company-specific notes
Google. Coding efficiency matters. System design pushes on planet-scale. The behavioral bar tests intellectual humility and comfort with ambiguity.
Amazon. Behavioral is the Leadership Principles, end to end. Prep a STAR story per LP, and lean into customer obsession and ownership.
Meta. Speed and clean code in the coding rounds. System design at depth. Culture fit on impact and openness.
Apple. Team-specific. Expect detail orientation and questions about your past work and design decisions.
Fundamentals you will get asked
- Processes vs threads. Separate memory spaces vs shared memory inside a process.
- Deadlock. Circular wait. Prevent with ordering, timeouts, or a resource hierarchy.
- CAP theorem. Consistency, availability, partition tolerance. Pick two under partition.
- SQL vs NoSQL. Structured ACID vs flexible schema and horizontal scaling.
- REST vs GraphQL. Resource endpoints vs a single endpoint with client-shaped queries.
Where candidates lose points
- Coding before clarifying. Restate the problem and the constraints first.
- Silent coding. Narrate the trade-offs as you go.
- Skipping edge cases. Empty input, nulls, overflow, single element.
- Over-engineering. A working brute force first, then optimize.
- No questions. The interviewer reads engagement.
A study plan that works
Coding: daily medium problems on LeetCode for six to eight weeks, with timed practice in the last two. System design: read engineering blogs and walk through real architectures, not just frameworks. Behavioral: write out eight to ten STAR stories that cover the major themes and rehearse them aloud. Mock interviews under real conditions in the final stretch. Then research the company you are about to walk into.
Helpful resources
- Bureau of Labor Statistics - Occupational Outlook Handbook
- LinkedIn Learning - Professional development courses
- Handshake - Early career job platform