At Norm Ai, a Software Engineer plays a pivotal role in building the industry's first platform for AI-driven regulatory compliance. The engineering team is responsible for developing sophisticated AI agents that can understand, interpret, and track complex regulatory frameworks. By translating dense legal and regulatory requirements into executable, high-performance software systems, you will directly impact how enterprise organizations navigate compliance at scale. This role sits at the intersection of advanced artificial intelligence, distributed systems, and product engineering. You will be building the core infrastructure that orchestrates large language models (LLMs), manages high-throughput data pipelines, and delivers intuitive, reliable user experiences. The engineering challenges here are highly complex, requiring a deep understanding of system architecture, data integrity, and deterministic execution within probabilistic AI systems. As a Software Engineer, your work will directly influence the speed, accuracy, and trust that enterprise clients place in Norm Ai. You will collaborate closely with AI researchers, product managers, and legal experts to design systems that are not just technologically advanced, but also robust enough to handle high-stakes regulatory environments. It is a highly collaborative, fast-paced startup environment where your technical contributions will have an immediate, visible impact on the product roadmap.
Initial Screen
reportedA conversation with a recruiter or hiring manager to discuss your background, interest in Norm Ai, and alignment with the role.
What to demonstrate
- A conversation with a recruiter or hiring manager to discuss your background, interest in Norm Ai, and alignment with the role
- 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 Screen
reportedA technical video call focusing on your prior experience and a small system design exercise to assess your architectural thinking.
What to demonstrate
- A technical video call focusing on your prior experience and a small system design exercise to assess your architectural thinking
- Depth in System Design
How to prepare
- Answer aloud and timed: How would you architect a backend data pipeline to ingest, parse, and index massive volumes of regulatory legal text?
- Answer aloud and timed: Explain how you would handle state management and consistency across a distributed network of AI agents.
Take-Home Assessment
reportedA practical coding project designed to evaluate your real-world development skills, code quality, and testing practices.
What to demonstrate
- A practical coding project designed to evaluate your real-world development skills, code quality, and testing practices
- Depth in System Design
How to prepare
- Answer aloud and timed: Design a rate-limiting middleware for an API gateway serving enterprise clients.
- Answer aloud and timed: Walk me through the most architecturally challenging system you have designed and deployed to production.
Virtual or Onsite Interview
reportedA multi-part interview loop that includes in-depth system design sessions, a review of your take-home assessment, and behavioral interviews with cross-functional team members.
What to demonstrate
- A multi-part interview loop that includes in-depth system design sessions, a review of your take-home assessment, and behavioral interviews with cross-functional team members
- Depth in System Design
How to prepare
- Answer aloud and timed: Describe a time when you had to optimize a slow database query or bottlenecked system. What was your methodology?
- Answer aloud and timed: How do you approach testing and ensuring reliability in systems that integrate with third-party APIs or external LLM services?
PracHub editorial advice for the preparation topics above.
Master System Design Fundamentals
Do not just focus on coding algorithms. Ensure you can confidently discuss database choices, caching, queueing systems, and API design. System design is a critical filter in the early stages of their process.
Over-Communicate During Technical Rounds
Whether you are walking through your resume or solving a system design problem, explain your thought process clearly. Interviewers want to see how you structure your thoughts and handle feedback.
Pay Attention to Take-Home Details
Treat the take-home assessment like production code. Write clear unit tests, include a structured README explaining your design decisions, and ensure your code is clean and easy to read.
Ask Thoughtful Questions
Use the time at the end of your interviews to ask insightful questions about the company's technical challenges, product roadmap, and engineering culture. This demonstrates your genuine interest and engagement.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement an efficient algorithm to find the shortest path in a weighted graph, and explain its time and space
Implement an efficient algorithm to find the shortest path in a weighted graph, and explain its time and space complexity.
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 write a multi-threaded program to process a batch of files concurrently while handling potential
How would you write a multi-threaded program to process a batch of files concurrently while handling potential race conditions?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Write a function to parse and validate complex nested JSON schemas representing regulatory rules.
Write a function to parse and validate complex nested JSON schemas representing regulatory rules.
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?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
Explain why the owner filter ignores the listing index
The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.
Approach
- Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
- For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
- Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
- Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.
Follow-up
- 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
- A dashboard runs this for 40 owners in one page load. What changes about the design?
How would you design a scalable web crawler that respects rate limits and processes millions of documents dail
How would you design a scalable web crawler that respects rate limits and processes millions of documents daily?
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?
Design a real-time notification system that handles millions of active users with minimal latency.
Design a real-time notification system that handles millions of active users with minimal latency.
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 architect a backend data pipeline to ingest, parse, and index massive volumes of regulatory lega
How would you architect a backend data pipeline to ingest, parse, and index massive volumes of regulatory legal text?
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 how you would handle state management and consistency across a distributed network of AI agents.
Explain how you would handle state management and consistency across a distributed network of AI agents.
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?
Design a rate-limiting middleware for an API gateway serving enterprise clients.
Design a rate-limiting middleware for an API gateway serving enterprise clients.
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?
Walk me through the most architecturally challenging system you have designed and deployed to production.
Walk me through the most architecturally challenging system you have designed and deployed to production.
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 approach testing and ensuring reliability in systems that integrate with third-party APIs or extern
How do you approach testing and ensuring reliability in systems that integrate with third-party APIs or external LLM services?
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?
One log partition stops advancing while the others drain
Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.
Approach
- Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
- Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
- Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
- Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.
Follow-up
- The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
- How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?
Built from the rounds and topics Norm Ai candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Norm Ai loop
- Write out the reported sequence: Initial Screen, Technical Screen, Take-Home Assessment, Virtual or Onsite Interview.
- 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.
02Work System Design
- Spend the session on System Design, which Norm Ai 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 Technical Interviewing (Coding/Problem Solving)
- Spend the session on Technical Interviewing (Coding/Problem Solving), which Norm Ai candidates report being tested on.
- Write one worked example in Technical Interviewing (Coding/Problem Solving) and time yourself on it.
Deliverable: One timed worked example in Technical Interviewing (Coding/Problem Solving).
04Work Take-Home Assessment
- Spend the session on Take-Home Assessment, which Norm Ai candidates report being tested on.
- Write one worked example in Take-Home Assessment and time yourself on it.
Deliverable: One timed worked example in Take-Home Assessment.
05Answer out loud: System Design & Architecture
- Answer aloud, timed: How would you design a scalable web crawler that respects rate limits and processes millions of documents daily?
- Answer aloud, timed: Design a real-time notification system that handles millions of active users with minimal latency.
Deliverable: Spoken answers to 2 reported System Design & Architecture question(s), under time.
06Answer out loud: Technical Experience & Prior Projects
- Answer aloud, timed: Walk me through the most architecturally challenging system you have designed and deployed to production.
- Answer aloud, timed: Describe a time when you had to optimize a slow database query or bottlenecked system. What was your methodology?
Deliverable: Spoken answers to 2 reported Technical Experience & Prior Projects question(s), under time.
07Answer out loud: Practical Coding & Problem-Solving
- Answer aloud, timed: Implement an efficient algorithm to find the shortest path in a weighted graph, and explain its time and space complexity.
- Answer aloud, timed: How would you write a multi-threaded program to process a batch of files concurrently while handling potential race conditions?
Deliverable: Spoken answers to 2 reported Practical Coding & Problem-Solving 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.
Describe a time when you had to optimize a slow database query or bottlenecked system. What was your methodolo
Describe a time when you had to optimize a slow database query or bottlenecked system. What was your methodology?
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 technical trade-off you had to make under tight deadlines. What did you prioritize and why?
Tell me about a technical trade-off you had to make under tight deadlines. What did you prioritize and why?
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?
Unblock an engineer without taking the keyboard
A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.
Approach
- Ask before diagnosing, and ask for things answerable from data they already have: the attempt count on the job rows that produced duplicates, the handler's observed duration against its lease expiry, and whether the duplicate rows share a natural key that a unique constraint could have caught.
- Teach the shape rather than the answer. A lease cannot distinguish a dead worker from a slow one, so a handler that outruns its lease is running twice by design, and deploys deliver the other half by killing handlers mid-run on every rollout. Both of their candidate theories produce identical duplicate rows, which is why the evidence has to come from timings rather than from argument.
- Hand over a checklist they execute: a natural key on every write the handler performs so the second copy collides rather than appends, the record of intent written before any external effect, a lease heartbeat while running, and the metric that shows it working.
- Keep ownership with them deliberately. Pair on the first write, then step back; if you finish it yourself you have closed one ticket and left the same person stuck on the next redelivery.
Follow-up
- How would you distinguish a genuine double-delivery from a lease expiry using only the data already stored?
- Their handler calls an external endpoint before recording that it did. What do you tell them to change first?
- 01
Describe a time when you had to optimize a slow database query or bottlenecked system. What was your methodology?
- 02
Tell me about a technical trade-off you had to make under tight deadlines. What did you prioritize and why?
- 03
A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.
What is the interview difficulty level at Norm Ai?
Candidates generally describe the interview process as average to challenging. The technical expectations are high, particularly around system design and the take-home assessment, but the interviewers are professional and collaborative throughout the process.
Norm Ai Software Engineer candidate reports ↗Where is the office located, and what is the work model?
Norm Ai is headquartered in New York, NY. The company operates with a hybrid or in-office model, and candidates visiting the office for onsite interviews have noted a highly professional environment, a great office space, and a collaborative team dynamic.
Norm Ai Software Engineer candidate reports ↗How quickly does the hiring team move?
The interview process typically moves very quickly. Norm Ai values efficiency, often scheduling successive rounds in rapid succession. However, because they maintain a competitive pipeline, candidates are encouraged to prepare thoroughly for early technical rounds to avoid being dropped without feedback.
Norm Ai Software Engineer candidate reports ↗What should I focus on for the system design round?
Focus on practicality and scalability. You should be prepared to discuss real-world constraints, trade-offs between different architectural approaches, and how to handle data consistency and reliability in distributed systems.
Norm Ai Software Engineer candidate reports ↗How hard are Norm Ai Software Engineer interviews, based on candidate reports?
With only a small sample, expect the experience to vary, but plan for a real system design focus rather than only light coding.
Norm Ai Software Engineer candidate reports ↗How many rounds does Norm Ai have for Software Engineer interviews, and what happens in each?
The Norm Ai Software Engineer loop includes four stages: an Initial Screen, a Technical Screen, a Take-Home Assessment, and a Virtual or Onsite Interview. The Technical Screen is a video call that covers your experience plus a small system design exercise. The Virtual or Onsite Interview is multi-part, including in-depth system design, a review of your take-home assessment, and behavioral interviews with cross-functional team members.
Norm Ai Software Engineer candidate reports ↗What topics are tested in Norm Ai Software Engineer interviews?
System Design is heavily tested, along with technical interviewing for coding and problem solving. Candidates should also expect Take-Home Assessment work, plus system considerations like scalability, API or service design, and distributed systems concepts. Technical communication and behavioral evaluation are included during the multi-part interview loop.
Norm Ai Software Engineer candidate reports ↗Does Norm Ai test system design and scalability for Software Engineers, or is it mostly coding?
System design shows up across multiple stages, including a small system design exercise in the Technical Screen and in-depth system design during the Virtual or Onsite Interview. The role also emphasizes scalability considerations, API or service design, and distributed systems concepts, so coding alone is not enough to cover the evaluation.
Norm Ai Software Engineer candidate reports ↗What does the Norm Ai Software Engineer take-home assessment focus on?
The take-home assessment is described as a practical coding project that evaluates real-world development skills, code quality, and testing practices. It is also explicitly reviewed during the Virtual or Onsite Interview, so you should prepare to explain your design decisions and testing approach.
Norm Ai Software Engineer candidate reports ↗What pay can I expect for a Norm Ai Software Engineer, and does it vary by level and location?
If you are comparing offers, rely on the level and location shown in each job posting, since pay can vary even when the role title is the same.
Norm Ai 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.
- 01Norm Ai 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.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p