Technical interview tips that actually help on the day

Most technical interviews test two things: whether you can solve a problem, and whether the interviewer would enjoy solving problems with you. These 15 technical interview tips cover both, from a two-week plan to what to say when you are stuck.

1. Know what gets tested

These software engineer technical interview tips start with one fact: the interview is rarely one thing. Ask the recruiter which of these you will face, because the preparation differs:

  • Coding problems on a shared editor such as CoderPad or HackerRank: arrays, strings, hash maps, trees, graphs, recursion.
  • A walk-through of past work, where you explain a project you built and the decisions in it.
  • System design, for mid-level and senior roles: sketch a service and discuss trade-offs.
  • Domain questions about the stack in the job description, such as SQL, concurrency or a framework.
  • A behavioral round, which is a separate skill. See our guides to STAR method examples and answering interview questions.

Codecademy's guide to preparing for a technical interview makes a similar point about being ready to explain past projects and the reasoning behind your choices (Codecademy, checked November 2026).

2. How to prepare for a technical interview: a two-week plan

To prepare for a technical interview, find out which rounds you will face, review core data structures and big-O, learn a handful of problem patterns, rehearse a walk-through of one past project, and solve problems out loud in the editor you will use. About an hour a day for two weeks is enough for most people. This plan assumes that. Adjust it to your time.

DaysFocusWhat to do
1 to 3FundamentalsReview arrays, strings, hash maps and sets. Write each from scratch once. Revisit big-O for the common operations.
4 to 6PatternsTwo pointers, sliding window, binary search, stack and queue. Two problems per pattern, then explain the pattern aloud.
7 to 9Trees and graphsBFS, DFS, recursion, and when to add memoization.
10 to 11Your own workPick two past projects and rehearse a three-minute walk-through of each.
12 to 13Mock interviewsSolve a problem out loud with a friend or a timer, in the same editor you will be using.
14RestLight review, then stop.

Daily practice compounds. Codecademy notes that doing code challenges every day makes ones that once took hours much faster over time (Codecademy).

3. Learn patterns, not answers

If you memorize a solution, a changed constraint breaks it. If you know the pattern, you can adapt. After every problem you solve, write one line: "this was a sliding window problem because the answer was a contiguous range with a running condition." That sentence is what you will reuse. See LeetCode patterns for the common ones, and the system design interview guide for the design round.

4. Data structures and big-O: know them well enough to say it

You do not need proofs. You need to say, for your solution, "this is O(n log n) for the sort, and O(n) extra space for the map," and to name the trade-off. Know the costs for the data structures you use: hash map lookup, array index, sorting, heap push and pop.

5. Prepare a project you can walk through

Choose one project you know in depth. Write down the problem, the options you considered, why you picked one, what broke, and what you would change. Codecademy's advice is to have a prior project ready to walk through with your interviewer (Codecademy). If you use Hintly or a similar tool, this is exactly the kind of note worth loading.

6. Last minute technical interview tips: the night before

  • Check the link, the editor and your audio. Join a test call if the company offers one.
  • Close notifications. Have water, paper and a pen.
  • Do a light review of your pattern notes. Do not start a new topic.
  • Sleep. Codecademy also recommends being well rested in the days before the interview (source).

7. In the room: clarify, plan, code, test

Use the same four steps on every coding problem.

  1. Clarify. Restate the problem and ask about inputs: "Can the array be empty? Are values negative? Is it sorted? How large can it get?" Ask for one example and check your understanding on it.
  2. Plan. Say the simple approach first, then improve it: "The brute force is two loops, O(n squared). I think a hash map brings it to O(n)." Agree the plan before you type.
  3. Code. Write clean, readable code and narrate in short phrases. Use clear names.
  4. Test. Walk through your example by hand, then the edge cases: empty, one item, duplicates, the largest case.

More on narration and recovering from bugs is in live coding interview tips.

8. Think out loud, in short sentences

Silence is the biggest risk, because the interviewer cannot give credit for thinking they cannot hear. Say what you are considering, even if it is half-formed: "I am wondering whether sorting helps, but that would change the order, so let me check if order matters." Keep it to a sentence at a time so you can still think.

9. Start with the brute force

A correct slow answer beats a half-built clever one. Name the brute force, say its cost, then improve it. It gives the interviewer something to work with and gives you a fallback.

10. Test your own code before they do

Trace your code line by line on the example, tracking variable values aloud. Finding your own off-by-one error is a good sign to an interviewer, not a bad one.

11. Know what to say when you are stuck

Everyone gets stuck. What matters is how you behave. Codecademy advises not stopping at "I don't know": pause, reason through the problem out loud, and ask the interviewer how they would approach it (Codecademy). Some lines to keep ready:

  • "Let me try a smaller example to see the pattern."
  • "My brute force is O(n squared). What is making it slow? I am repeating this lookup."
  • "I am not sure about this part. Would it be reasonable to assume the input is sorted?"
  • "I have two options, a heap or sorting. Can I talk through the trade-off and pick one?"

If you are stuck for more than a few minutes, ask a specific question instead of waiting.

12. System design basics

If the role is mid-level or above, expect one design round. Use a structure so you do not ramble:

  1. Requirements: what must the system do, and what is out of scope?
  2. Rough scale: users, requests, data size. Estimates are fine; say they are estimates.
  3. The main components and how requests flow between them.
  4. The data model and storage choice, with a reason.
  5. Bottlenecks and failure modes: what breaks first, and what would you add?

The interviewer is listening for trade-offs ("a cache makes reads faster, but I now have to handle stale data"), so say them.

13. Treat the behavioral round as its own skill

Technical rounds usually include questions like "tell me about a time you disagreed with a teammate." Prepare four or five stories in the STAR format and reuse them across questions. Start with STAR method interview examples.

14. Ask good questions at the end

Ask about how the team reviews code, how they handle on-call, and what the first three months look like. It signals that you think like a colleague.

15. Write down what was asked afterward

Within an hour, note the questions, what went well and what you would change. Codecademy suggests making notes on the questions asked (source). It makes your next round better, and it feeds your notes if you use a live AI interview assistant.

How do I do well in a technical interview?

Do well by showing your reasoning, not just an answer. Clarify the problem, say a simple approach first, narrate in short sentences, test your code with an example and edge cases, and stay calm when you are stuck. Interviewers score how you think and how it feels to work with you as much as the final code.

Five technical interview tips to remember

  1. Ask clarifying questions before you code.
  2. Say the brute force and its cost, then improve it.
  3. Think out loud in short sentences.
  4. Test with an example and edge cases.
  5. Take hints and ask specific questions when stuck.

Technical interview tips for freshers and for experienced engineers

The core is the same for everyone. What changes is what the interviewer expects you to show. (“Freshers” is the term used in the UK and India for new graduates.)

Technical interview tips for freshers and new graduates

Expect fundamentals: arrays, strings, hash maps, recursion and big-O. Use coursework, internships and personal projects as your walk-through. Be honest about what you have not used, and show how you learn: “I have not used that, but here is how I would find out.” Practice the same few patterns until you can explain them without notes.

Technical interview tips for experienced engineers

Expect the same coding round plus more depth on past work and design. Prepare two projects with the trade-offs, failures and results, and practice one system design from requirements to bottlenecks. Do not skip coding practice because you code every day: solving a puzzle in 40 minutes while talking is a different skill. See the software engineer interview questions guide for typical questions.

Technical interview cheat sheet: a one-page checklist for the last hour

  • Do you know which language you will use, and the syntax for maps, sorting and string handling?
  • Can you say the complexity of your last three solutions out loud?
  • Do you have your three-minute project walk-through ready?
  • Do you have a sentence ready for when you are stuck?
  • Have you eaten, and is your setup tested?

Common mistakes to avoid

The biggest ones are jumping into code, going quiet, and skipping the test step. Sections 7 to 11 show how to avoid each.

Where an AI assistant fits

Some candidates use live tools, and some companies now allow them in coding rounds while others do not. Always check the rules you were given. If you use one where it is allowed, treat it as a helper, not a substitute for knowing the material. Hintly has a screen shortcut that reads the problem on your screen and suggests an approach, complexity and code; see the AI coding interview assistant page, and the AI interview assistant overview for the rest of the interview.

Questions

How long should I prepare for a technical interview?

Two to four weeks of steady practice suits most people who already work as engineers: 45 to 60 minutes on most days beats one long weekend. If you have a few days, focus on arrays, strings, hash maps, and talking through your reasoning, and skip rare topics.

What should I do if I get completely stuck?

Say what you know, then try a smaller version. State the brute-force approach, check it on a tiny example, and look for what makes it slow. If you are still stuck after a few minutes, ask a specific question such as 'Would sorting first help here?' Interviewers generally respond better to a clear question than to silence.

Should I memorize solutions to common problems?

Memorizing is a weak strategy because a small change in the question breaks it. Learn the patterns instead: two pointers, sliding window, hash map lookups, BFS and DFS, recursion with memoization. Then practice recognizing which one a new problem needs.

How do I prepare for the system design round?

Practice a repeatable structure: requirements, rough scale, the main components, the data model, then bottlenecks and trade-offs. Talk through the trade-offs out loud, because the reasoning is what is being assessed.

What does technical interview mean?

A technical interview is a round where an employer tests job skills directly: you solve coding problems, explain past projects, design a system or answer questions about your tools. It is separate from the behavioral round, which covers how you work with people.

Is it okay to use AI tools in a technical interview?

Only if the company allows it. Read the instructions, ask the recruiter if unclear, and follow their rules. Some interviews ban outside help and some now expect AI tools.

Your next call, handled.

Hintly is almost ready. Leave your email and we’ll tell you the day you can download it.

Mac and Windows · No spam