As a Software Engineer at North, you occupy a central role in redefining how businesses manage cloud infrastructure and finances. With businesses investing heavily in cloud technology and facing soaring costs, this role directly impacts our mission to deliver next-generation cloud spend management platforms. You will tackle complex problems involving scale, real-time data visibility, and automation, empowering global customers to grow efficiently without wasting time or money. Your day-to-day contributions involve designing and building robust systems, optimizing infrastructure, and collaborating closely with product and engineering leaders. Whether you are scaling our core platform or developing advanced capabilities like Agent North, your work influences critical business outcomes. You will drive projects from conception to production in a fast-paced environment that values technical excellence and autonomy. This role requires a blend of rigorous technical execution and creative problem-solving. You will work alongside top-tier talent and trusted global partners, making it an ideal position for engineers who thrive when given ownership over ambiguous, high-impact problem spaces. Expect a collaborative culture where your code directly shapes the future of cloud financial automation.
Recruiter Conversation
reportedInitial conversation focused on your background.
What to demonstrate
- Initial conversation focused on your background
- Depth in System Design
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 Screens
reportedEvaluate your coding fluency and domain expertise.
What to demonstrate
- Evaluate your coding fluency and domain expertise
- Depth in System Design
How to prepare
- Answer aloud and timed: Explain the difference between functional and procedural programming approaches.
- Answer aloud and timed: What actual languages and development environments have you used in past projects?
Onsite/Virtual Loop
reportedIncludes system design deep dives, technical problem-solving, and culture alignment discussions.
What to demonstrate
- Includes system design deep dives, technical problem-solving, and culture alignment discussions
- Depth in System Design
How to prepare
- Answer aloud and timed: How do you ensure robust error handling and maintainability in your codebases?
- Answer aloud and timed: Create a payment system design.
PracHub editorial advice for the preparation topics above.
Clarify ambiguous constraints early
When presented with an open-ended system design or coding prompt, always ask clarifying questions about scale, traffic patterns, and constraints before jumping into a solution.
Talk through your trade-offs
Interviewers want to see how you make technical decisions. Explicitly discuss why you chose one architectural pattern or data structure over another, highlighting pros and cons.
Structure your behavioral responses
Use the STAR method (Situation, Task, Action, Result) when answering behavioral questions to keep your stories concise, impact-focused, and easy to follow.
Emphasize code quality and testing
Highlight your familiarity with unit testing, code reviews, and maintainability. Demonstrating that you care about long-term code health is a major differentiator.
Show genuine curiosity about our mission
Take time to understand our platform and the specific problem spaces we tackle. Asking thoughtful questions about our technology stack and product roadmap signals strong engagement.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Merge partitioned event streams into one ordered feed with bounded lateness
The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.
Approach
- Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
- Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
- Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
- Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.
Follow-up
- The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
- The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?
Canonicalise a request body into a stable idempotency fingerprint
idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.
Approach
- Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
- Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
- Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
- Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.
Follow-up
- A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
- Where does the fingerprint get computed relative to request decompression and the body-size limit?
Identify the heaviest tenants in a five-minute window under memory pressure
The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.
Approach
- Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
- Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
- State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
- Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.
Follow-up
- The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
- Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?
How do you manage database queries and optimization using SQL joins and indexing?
How do you manage database queries and optimization using SQL joins and indexing?
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?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
What is the difference between interfaces and abstract classes?
What is the difference between interfaces and abstract classes?
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 do you design and implement object-oriented software applications in Java, C#, or C++?
How do you design and implement object-oriented software applications in Java, C#, or C++?
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?
Explain the difference between functional and procedural programming approaches.
Explain the difference between functional and procedural programming approaches.
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 actual languages and development environments have you used in past projects?
What actual languages and development environments have you used in past projects?
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 do you ensure robust error handling and maintainability in your codebases?
How do you ensure robust error handling and maintainability in your codebases?
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?
Create a payment system design.
Create a payment system design.
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?
Explain Model-View-Controller (MVC) architecture and how components interact.
Explain Model-View-Controller (MVC) architecture and how components interact.
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?
How would you approach designing a cloud-based service for high-throughput data processing?
How would you approach designing a cloud-based service for high-throughput data processing?
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?
Discuss strategies for managing state and persistence in distributed environments.
Discuss strategies for managing state and persistence in distributed environments.
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?
How do you balance trade-offs between consistency and availability in system design?
How do you balance trade-offs between consistency and availability in system design?
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?
Discuss React hooks and the inner workings of the virtual DOM.
Discuss React hooks and the inner workings of the virtual DOM.
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 are the different HTTP methods and their appropriate use cases in RESTful APIs?
What are the different HTTP methods and their appropriate use cases in RESTful APIs?
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 do you troubleshoot performance bottlenecks in web applications?
How do you troubleshoot performance bottlenecks in web applications?
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?
Built from the rounds and topics North candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the North loop
- Write out the reported sequence: Recruiter Conversation, Technical Screens, Onsite/Virtual Loop.
- 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 3 reported rounds, with the weakest marked.
02Work System Design
- Spend the session on System Design, which North candidates report being tested on.
- Write one worked example in System Design and time yourself on it.
Deliverable: One timed worked example in System Design.
03Work Payment Systems
- Spend the session on Payment Systems, which North candidates report being tested on.
- Write one worked example in Payment Systems and time yourself on it.
Deliverable: One timed worked example in Payment Systems.
04Work High Performance Computing (HPC)
- Spend the session on High Performance Computing (HPC), which North candidates report being tested on.
- Write one worked example in High Performance Computing (HPC) and time yourself on it.
Deliverable: One timed worked example in High Performance Computing (HPC).
05Answer out loud: Core Technical & Object-Oriented Concepts
- Answer aloud, timed: What is the difference between interfaces and abstract classes?
- Answer aloud, timed: How do you design and implement object-oriented software applications in Java, C#, or C++?
Deliverable: Spoken answers to 2 reported Core Technical & Object-Oriented Concepts question(s), under time.
06Answer out loud: System Design & Architecture
- Answer aloud, timed: Create a payment system design.
- Answer aloud, timed: Explain Model-View-Controller (MVC) architecture and how components interact.
Deliverable: Spoken answers to 2 reported System Design & Architecture question(s), under time.
07Answer out loud: Web Technologies & Frameworks
- Answer aloud, timed: Discuss React hooks and the inner workings of the virtual DOM.
- Answer aloud, timed: What are the different HTTP methods and their appropriate use cases in RESTful APIs?
Deliverable: Spoken answers to 2 reported Web Technologies & Frameworks question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Explain your experience with Git version control workflows and CI/CD pipelines.
Explain your experience with Git version control workflows and CI/CD pipelines.
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 a time you faced a technical challenge and how you overcame it.
Describe a time you faced a technical challenge and how you overcame it.
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 on technical direction with product managers or peers?
How do you handle disagreements on technical direction with product managers or peers?
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 mentor a junior engineer or share technical knowledge.
Tell me about a time you had to mentor a junior engineer or share technical knowledge.
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 managing multiple competing deadlines?
How do you prioritize tasks when managing multiple competing deadlines?
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?
Why are you interested in joining North?
Why are you interested in joining North?
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?
- 01
Explain your experience with Git version control workflows and CI/CD pipelines.
- 02
Describe a time you faced a technical challenge and how you overcame it.
- 03
How do you handle disagreements on technical direction with product managers or peers?
- 04
Tell me about a time you had to mentor a junior engineer or share technical knowledge.
How difficult are the technical interviews at North, and how much preparation time is recommended?
The interviews are moderately to highly rigorous, focusing heavily on practical system design, clean coding principles, and domain expertise. We recommend dedicating at least 2 to 4 weeks of targeted preparation, reviewing fundamental object-oriented design, system architecture patterns, and your past project experiences.
North Software Engineer candidate reports ↗What differentiates successful candidates from those who do not pass?
Successful candidates distinguish themselves by demonstrating structured problem-solving, proactively discussing trade-offs, and writing clean, maintainable code. Beyond technical skills, they communicate their thought process clearly and show genuine enthusiasm for building products that solve complex user problems.
North Software Engineer candidate reports ↗What is the working culture like for engineering teams at North?
Our engineering culture emphasizes autonomy, continuous learning, and close collaboration across small, high-impact teams. We value work-life balance, offer flexible hybrid arrangements, and encourage engineers to take ownership of their projects from 0 to 1 in an open, supportive atmosphere.
North Software Engineer candidate reports ↗What is the typical timeline from the initial recruiter screen to a final offer?
The entire interview loop typically spans 2 to 4 weeks from your initial recruiter conversation to the final decision. We strive to maintain an efficient and transparent process while ensuring you have adequate time to meet with key team members and leadership.
North Software Engineer candidate reports ↗Are the positions remote or hybrid?
Depending on the specific team and role requirements, positions may offer remote flexibility or hybrid setups based out of our core engineering hubs. Check individual job descriptions for exact location guidelines and workspace expectations.
North Software Engineer candidate reports ↗What topics does North test in interviews?
North interviews most often cover Stakeholder Management, Communication Skills, JavaScript, Object-Oriented Programming (OOP), and Quantitative Reasoning. The exact emphasis depends on the specific role you apply for.
North Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01North Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Royal Cyber Software Engineer Interview Guide
What Royal Cyber asks Software Engineer candidates, from reported rounds and questions.
Raytheon Technologies Corporate Headquarters Software Engineer Interview Guide
What Raytheon Technologies Corporate Headquarters asks Software Engineer candidates, from reported rounds and questions.
Rakuten Symphony Software Engineer Interview Guide
What Rakuten Symphony asks Software Engineer candidates, from reported rounds and questions.
NCR Atleos Software Engineer Interview Guide
What NCR Atleos asks Software Engineer candidates, from reported rounds and questions.