A practical guide for software engineers

Technical interview preparation

Confirm the format, solve unfamiliar problems aloud, explain system tradeoffs and prepare truthful examples from your work. Start with a baseline, then repeat the part that needs attention.

Start with the actual interview

Read the invitation and job description together. Ask your recruiting contact which rounds to expect, what each assesses, how long they last and which tools or languages are allowed. Confirm assistance rules, including AI use, before the assessment.

Write a short preparation brief: target role and level, confirmed rounds, unfamiliar subjects and practical constraints. If the format is unknown, record that question rather than filling the gap with an assumed company process.

Coding: agree on the expected result

Choose a small problem. Restate the inputs, output, equality rules and whether you may change the input. Work through a counterexample before choosing a data structure.

Practice example · coding

Find the ID whose repeated occurrence appears first in a left-to-right scan. Match strings exactly and return None when nothing repeats.

  • ["A", "B", "B", "A"] → "B"
  • [] → None
  • ["A", "a"] → None

The first original ID is A, but B repeats earlier. Explain how your scan remembers earlier IDs, then test that distinction.

Use the worked Python solution and tests to check your attempt. Explain the assumptions behind time and space costs. Next, choose a fresh prompt from the question bank and derive its solution independently.

System design: make one failure concrete

Define users, core actions and exclusions before drawing components. State assumptions about load and reliability, then explain which requirement each component serves.

Practice example · system design

Design an asynchronous report-export service. A user requests an export, checks its status and downloads the finished file.

Expected practice output: an API, durable job status, a queue, a worker and file storage, with a reason for each choice. Then answer: what happens if the worker writes the file but crashes before acknowledging the job?

Discuss the job identifier, retry behavior and how repeated processing avoids committing conflicting results. State what remains unresolved.

This is an illustrative exercise, not an employer question or a complete production design. The senior system-design practice guide adds a rubric for requirements, tradeoffs and failure handling.

Behavioral: prepare evidence you can defend

Choose real events involving decisions, disagreement, mistakes or uncertain requirements. Separate your contribution from the team's work. Use situation, task, action and result to organize the account.

Practice example · behavioral

Prompt: describe a technical decision you later changed.

Expected practice output: the original constraint, your responsibility, alternatives considered, evidence that changed your mind, your next action and the observed result.

Use facts from your own experience. If impact was not measured, say so. Prepare a follow-up about what you would do differently.

The software-engineer behavioral guide includes a story worksheet and follow-up checks. Keep confidential details out of your rehearsal.

Use a repeatable mock plan

  1. Baseline. Attempt one relevant task aloud without reading its answer. Note where clarification, implementation or explanation stalled.
  2. Review. Revisit the weakest step. Write a specific correction, such as adding an empty-input test or explaining a failed dependency.
  3. Transfer. Try an unfamiliar prompt or change one requirement. Check whether you can rebuild the reasoning rather than repeat a memorized solution.

Keep a short record: prompt, assumption missed, correction and next exercise. Compare AI practice, peer mocks and coaching to choose a feedback format that fits the skill you need to rehearse.

FAANG and other large tech interviews

Company labels do not define one interview process. Role, level and team matter; confirm your actual rounds and follow the invitation's instructions.

Microsoft's technical guidance emphasizes clarifying ambiguity, planning, testing and discussing complexity. Amazon's software-development preparation guide recommends confirming topics with your recruiting contact and applying fundamentals. These are each employer's published recommendations, not a universal interview format.

The examples here are editorial practice material. They are not leaked questions, predictions of company questions or a guarantee of an interview outcome.

Choose your next practice guide

Prepared with AI assistance. Official employer guidance checked November 20, 2026; the practice plan and examples are editorial guidance.