cswork / libraryOpen practice workspace

Interview guides · Fieldguide.Ai

Fieldguide.Ai Software Engineer Interview Guide

Fieldguide.Ai Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Fieldguide.Ai, you are at the forefront of redefining trust in global commerce. The company focuses on modernizing the complex, document-heavy workflows of cybersecurity, privacy, and financial audits. By building software that automates and streamlines these critical processes, you are directly empowering the practitioners who ensure business integrity. Your work will involve designing and delivering high-quality features that translate complex regulatory and audit requirements into elegant, user-focused digital experiences. Because Fieldguide.Ai operates in a highly technical and high-stakes domain, you will be expected to balance rapid iteration with the long-term maintainability and reliability of the platform.

This guide is scoped to a Software Engineer candidate at Fieldguide.Ai.

Focus areas

  • Software Engineering Fundamentals
  • TypeScript
  • React

The Fieldguide.Ai interview process

Fieldguide.Ai candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screen

Initial screening by a recruiter to assess candidate qualifications and fit.

What to demonstrate

  • Initial screening by a recruiter to assess candidate qualifications and fit
  • Depth in Software Engineering Fundamentals

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 Assessment

Live coding or problem-solving session to evaluate technical skills.

What to demonstrate

  • Live coding or problem-solving session to evaluate technical skills
  • Depth in Software Engineering Fundamentals

How to prepare

  • Answer aloud and timed: Explain the trade-offs between using a monolithic vs. microservices architecture for a platform like ours.
  • Answer aloud and timed: How would you debug a performance bottleneck in a React application?

Leadership Interaction

Interviews with leadership, including the CTO, to assess cultural fit and mindset.

What to demonstrate

  • Interviews with leadership
  • Including the CTO, to assess cultural fit and mindset

How to prepare

  • Answer aloud and timed: Describe a time you had to refactor legacy code to improve scalability.
  • Answer aloud and timed: How would you design a system for ingesting and processing large volumes of unstructured audit documents?

Where candidates lose points

Communicate your process

Even if you know the answer, explain your reasoning out loud. Interviewers at Fieldguide.Ai are looking for how you approach complex problems, not just the final code.

Prepare for the CTO interview

You may meet with leadership. Be ready to discuss your long-term career goals and how they align with the trajectory of the company.

Study the product

Understand the "why" behind Fieldguide.Ai. Researching audit and compliance challenges will give you a significant advantage when discussing feature design.

Clarify salary expectations early

As noted in recent experiences, be explicit about your compensation requirements during the initial recruiter screen to ensure both parties are aligned.

Questions & practice

Walk me through your thought process for optimizing a function that handles high volumes of document data.

Medium · Technical Craft and Coding

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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 do you approach testing for edge cases when building a new feature?

Medium · Technical Craft and Coding

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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?

Identify the heaviest tenants in a five-minute window under memory pressure

Medium · top-k · heavy hitters · streaming

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

  1. 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.
  2. 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.
  3. 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.
  4. 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?

Explain how you would structure a database schema for a multi-tenant audit platform.

Medium · System Design and Architecture

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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

  1. 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.
  2. 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.
  3. 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.
  4. 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 trade-offs between using a monolithic vs. microservices architecture for a platform like ours.

Medium · Technical Craft and Coding

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 design a system for ingesting and processing large volumes of unstructured audit documents?

Medium · System Design and Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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?

What considerations would you make when integrating a third-party API into our existing infrastructure?

Medium · System Design and Architecture

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. 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?

How do you ensure data consistency in a distributed system?

Medium · System Design and Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. 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 debug a performance bottleneck in a React application?

Medium · Technical Craft and Coding

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. 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 Fieldguide.Ai candidates report.

Day 1 — Map the Fieldguide.Ai loop

  • Write out the reported sequence: Recruiter Screen, Technical Assessment, Leadership Interaction.
  • 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.

Day 2 — Work Software Engineering Fundamentals

  • Spend the session on Software Engineering Fundamentals, which Fieldguide.Ai candidates report being tested on.
  • Write one worked example in Software Engineering Fundamentals and time yourself on it.

Deliverable: One timed worked example in Software Engineering Fundamentals.

Day 3 — Work TypeScript

  • Spend the session on TypeScript, which Fieldguide.Ai candidates report being tested on.
  • Write one worked example in TypeScript and time yourself on it.

Deliverable: One timed worked example in TypeScript.

Day 4 — Work React

  • Spend the session on React, which Fieldguide.Ai candidates report being tested on.
  • Write one worked example in React and time yourself on it.

Deliverable: One timed worked example in React.

Day 5 — Answer out loud: Technical Craft and Coding

  • Answer aloud, timed: Walk me through your thought process for optimizing a function that handles high volumes of document data.
  • Answer aloud, timed: How do you approach testing for edge cases when building a new feature?

Deliverable: Spoken answers to 2 reported Technical Craft and Coding question(s), under time.

Day 6 — Answer out loud: System Design and Architecture

  • Answer aloud, timed: How would you design a system for ingesting and processing large volumes of unstructured audit documents?
  • Answer aloud, timed: What considerations would you make when integrating a third-party API into our existing infrastructure?

Deliverable: Spoken answers to 2 reported System Design and Architecture question(s), under time.

Day 7 — Answer out loud: Behavioral and Cultural Alignment

  • Answer aloud, timed: Tell me about a time you had a disagreement with a product manager; how did you resolve it?
  • Answer aloud, timed: Describe a situation where you had to take ownership of a project that was failing.

Deliverable: Spoken answers to 2 reported Behavioral and Cultural Alignment question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time you had to refactor legacy code to improve scalability.

Medium · Technical Craft and Coding

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 a disagreement with a product manager; how did you resolve it?

Medium · Behavioral and Cultural Alignment

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 situation where you had to take ownership of a project that was failing.

Medium · Behavioral and Cultural Alignment

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 receiving critical feedback on your code or design choices?

Medium · Behavioral and Cultural Alignment

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 does it mean to you to build "lovable" software?

Medium · Behavioral and Cultural Alignment

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?