Interview guides · Nav
Nav Software Engineer Interview Guide
Nav Software Engineer interview guide: reported rounds, questions and how candidates describe the process.
The 60-second brief
As a Software Engineer at Nav, you play a pivotal role in shaping the future of financial technology solutions that empower small businesses. Your work directly impacts the design, development, and delivery of innovative software products aimed at helping users navigate their financial options more effectively. You will collaborate closely with cross-functional teams to ensure that the software meets both user needs and business requirements, ultimately driving growth and enhancing customer experiences. This role is critical as it combines technical expertise with creative problem-solving to address complex challenges within the financial sector. You will engage in diverse projects that range from developing new features for existing products to architecting entirely new systems.
This guide is scoped to a Software Engineer candidate at Nav.
Focus areas
- Pair Programming
- Software Engineering Communication
- Culture Fit / Team Collaboration
The Nav interview process
Nav candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.
Phone Screening
Initial call to assess candidate's background and fit for the role.
What to demonstrate
- Initial call to assess candidate's background and fit for the role
- Depth in Pair Programming
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Assessments
Evaluation of technical skills through coding challenges or assessments.
What to demonstrate
- Evaluation of technical skills through coding challenges or assessments
- Depth in Pair Programming
How to prepare
- Answer aloud and timed: Can you discuss your experience with cloud services (e.g., AWS, Azure)?
- Answer aloud and timed: What methods do you use for version control in your projects?
Pair Programming Sessions
Collaborative coding sessions to evaluate problem-solving and teamwork skills.
What to demonstrate
- Collaborative coding sessions to evaluate problem-solving and teamwork skills
- Depth in Pair Programming
How to prepare
- Answer aloud and timed: Describe a challenging bug you encountered and how you resolved it.
- Answer aloud and timed: Describe your experience with pair programming and how you approach it.
Cultural Alignment Discussions
Conversations focused on assessing the candidate's fit with company culture.
What to demonstrate
- Conversations focused on assessing the candidate's fit with company culture
- Depth in Pair Programming
How to prepare
- Answer aloud and timed: How do you handle disagreements when coding with a partner?
- Answer aloud and timed: Give an example of how you've communicated complex technical information to a non-technical colleague.
Where candidates lose points
Prepare for Pair Programming
Since Nav values collaboration, practice pair programming with a friend or colleague to build comfort and fluency in this format.
Be Authentic
Show your true self during interviews. Authenticity resonates well with interviewers and reflects your cultural fit.
Engage with Interviewers
Ask questions about the team and company culture during your interviews to demonstrate your interest and engagement.
Questions & practice
Write a function to reverse a linked list.
Medium · Coding / Algorithms
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you implement a basic caching mechanism?
Medium · Coding / Algorithms
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Can you explain the time complexity of your solution for a given problem?
Medium · Coding / Algorithms
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Write a simple RESTful service in your preferred programming language.
Medium · Coding / Algorithms
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you optimize a slow-running SQL query?
Medium · Technical / Domain Questions
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Find version gaps and relay lag with window functions
Medium · window functions · event tables · frame semantics
outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.
Approach
- Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
- Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
- Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
- Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.
Follow-up
- Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
- Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?
Explain the differences between REST and GraphQL.
Medium · Technical / Domain Questions
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What methods do you use for version control in your projects?
Medium · Technical / Domain Questions
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a challenging bug you encountered and how you resolved it.
Medium · Technical / Domain Questions
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Give an example of how you've communicated complex technical information to a non-technical colleague.
Medium · Pair Programming / Collaboration
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What techniques do you use to ensure productive collaboration during coding sessions?
Medium · Pair Programming / Collaboration
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you approach designing a new feature for an existing product?
Medium · Problem-Solving / Case Studies
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What strategies do you employ to ensure your code is maintainable and scalable?
Medium · Problem-Solving / Case Studies
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
If you were tasked with improving the performance of a web application, what steps would you take?
Medium · Problem-Solving / Case Studies
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you walk us through your thought process for debugging a complex application issue?
Medium · Problem-Solving / Case Studies
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Suggested practice checklist
Built from the rounds and topics Nav candidates report.
Day 1 — Map the Nav loop
- Write out the reported sequence: Phone Screening, Technical Assessments, Pair Programming Sessions, Cultural Alignment Discussions.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
Day 2 — Work Pair Programming
- Spend the session on Pair Programming, which Nav candidates report being tested on.
- Write one worked example in Pair Programming and time yourself on it.
Deliverable: One timed worked example in Pair Programming.
Day 3 — Work Software Engineering Communication
- Spend the session on Software Engineering Communication, which Nav candidates report being tested on.
- Write one worked example in Software Engineering Communication and time yourself on it.
Deliverable: One timed worked example in Software Engineering Communication.
Day 4 — Work Culture Fit / Team Collaboration
- Spend the session on Culture Fit / Team Collaboration, which Nav candidates report being tested on.
- Write one worked example in Culture Fit / Team Collaboration and time yourself on it.
Deliverable: One timed worked example in Culture Fit / Team Collaboration.
Day 5 — Answer out loud: Technical / Domain Questions
- Answer aloud, timed: Explain the differences between REST and GraphQL.
- Answer aloud, timed: How would you optimize a slow-running SQL query?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
Day 6 — Answer out loud: Pair Programming / Collaboration
- Answer aloud, timed: Describe your experience with pair programming and how you approach it.
- Answer aloud, timed: How do you handle disagreements when coding with a partner?
Deliverable: Spoken answers to 2 reported Pair Programming / Collaboration question(s), under time.
Day 7 — Answer out loud: Behavioral / Culture Fit
- Answer aloud, timed: Tell me about a time you had to adapt to significant change in a project.
- Answer aloud, timed: How do you prioritize tasks when working under tight deadlines?
Deliverable: Spoken answers to 2 reported Behavioral / Culture Fit question(s), under time.
Behavioural preparation
Behavioural rounds judge the decision you made and what it cost.
Can you discuss your experience with cloud services (e.g., AWS, Azure)?
Medium · Technical / Domain Questions
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe your experience with pair programming and how you approach it.
Medium · Pair Programming / Collaboration
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle disagreements when coding with a partner?
Medium · Pair Programming / Collaboration
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about a time you had to adapt to significant change in a project.
Medium · Behavioral / Culture Fit
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize tasks when working under tight deadlines?
Medium · Behavioral / Culture Fit
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe an instance where you took the lead on a project. What was the outcome?
Medium · Behavioral / Culture Fit
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What values are most important to you in a workplace?
Medium · Behavioral / Culture Fit
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?