Tokio Marine North America Services Software Engineer Interview Guide

The 60-second brief

A Software Engineer at Tokio Marine North America Services (TMNAS) plays a critical role in designing, building, and maintaining the technological infrastructure of a premier global insurance group. Operating as a shared services entity, TMNAS provides critical IT, underwriting, and operational support to various Tokio Marine group companies. In this role, you will work on complex, high-availability systems that handle large-scale financial transactions, policy administration, and automated risk assessment. Your work will directly impact how the business processes claims, configures complex insurance products, and exposes core services through modern APIs.

This guide is scoped to a Software Engineer candidate at Tokio Marine North America Services.

Focus areas

• Java
• Software Engineering (General Role Competencies)
• Software Development

The Tokio Marine North America Services interview process

Tokio Marine North America Services candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Call

Initial conversation to validate your background, technical skills, and salary expectations.

What to demonstrate

• Initial conversation to validate your background, technical skills, and salary expectations
• Depth in Java

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.

Hiring Manager Interview

Focus on your resume, past project experiences, and foundational technical knowledge, especially around APIs.

What to demonstrate

• Focus on your resume, past project experiences, and foundational technical knowledge, especially around APIs
• Depth in Java

How to prepare

• Prepare two projects you led end to end, each with the decision you owned and what it cost.
• Have three questions about the team's roadmap and how success is measured in the first six months.

Panel Interview

Comprehensive, multi-hour interview with key stakeholders assessing real-world deployment and architectural challenges.

What to demonstrate

• Comprehensive, multi-hour interview with key stakeholders assessing real-world deployment and architectural challenges
• Depth in Java

How to prepare

• Answer aloud and timed: How do you ensure the security and authentication of APIs in an enterprise environment?
• Answer aloud and timed: If an integration with a third-party rating engine fails mid-transaction, how do you design your system to recover gracefully without losing data?

Where candidates lose points

Understand the Shared Services Model

Remember that TMNAS supports multiple distinct insurance entities. Frame your answers to show that you understand how your software solutions can serve diverse internal clients with varying needs.

Master Scenario-Based Frameworks

When answering situational questions, use structured communication methods like the STAR method (Situation, Task, Action, Result). Focus heavily on the "Action" and "Result" to show how your technical decisions led to positive business outcomes.

Be prepared for varying levels of interviewer engagement

Maintain your energy and professionalism even if your interviewer seems quiet or reserved during the technical walk-through.

Questions & practice

What is the difference between synchronous and asynchronous communication, and when would you use each?

Medium · API and Software Development Foundations

Approach

1. Say what the runtime actually does before reasoning about the code.
2. Name what is shared across threads and what owns each piece of state.
3. Identify the window where an invariant is briefly untrue.
4. 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?

Walk me through your resume and highlight a project where you had to overcome a major technical roadblock.

Medium · Behavioral & Professional Experience

Approach

1. Say what the runtime actually does before reasoning about the code.
2. Name what is shared across threads and what owns each piece of state.
3. Identify the window where an invariant is briefly untrue.
4. 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?

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 why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

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

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

Hold a per-tenant active cap against concurrent creates

Hard · write skew · isolation levels · constraints

A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.

Approach

1. Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
2. Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
3. Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
4. State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.

Follow-up

• A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
• The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?

Explain the lifecycle of a typical REST API request from the client to the database and back.

Medium · API and Software Development Foundations

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 handle versioning and backward compatibility when updating an existing API?

Medium · API and Software Development Foundations

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 the security and authentication of APIs in an enterprise environment?

Medium · API and Software Development Foundations

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?

If an integration with a third-party rating engine fails mid-transaction, how do you design your system to rec

Medium · Scenario-Based & Systems Engineering

If an integration with a third-party rating engine fails mid-transaction, how do you design your system to recover gracefully without losing data?

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?

Walk us through a scenario where a production application experiences a sudden spike in latency. How do you is

Medium · Scenario-Based & Systems Engineering

Walk us through a scenario where a production application experiences a sudden spike in latency. How do you isolate and resolve the bottleneck?

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. 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 design a software configuration workflow that allows non-technical business analysts to update i

Medium · Scenario-Based & Systems Engineering

How would you design a software configuration workflow that allows non-technical business analysts to update insurance product rates safely?

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?

Describe a situation where you had to integrate a modern cloud service with a legacy on-premises database. Wha

Medium · Scenario-Based & Systems Engineering

Describe a situation where you had to integrate a modern cloud service with a legacy on-premises database. What architecture did you choose?

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?

One log partition stops advancing while the others drain

Easy · poison message · head-of-line blocking · consumer lag

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

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

Suggested practice checklist

Built from the rounds and topics Tokio Marine North America Services candidates report.

Day 1 — Map the Tokio Marine North America Services loop

• Write out the reported sequence: Recruiter Call, Hiring Manager Interview, Panel 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 3 reported rounds, with the weakest marked.

Day 2 — Work Java

• Spend the session on Java, which Tokio Marine North America Services candidates report being tested on.
• Write one worked example in Java and time yourself on it.

Deliverable: One timed worked example in Java.

Day 3 — Work Software Engineering (General Role Competencies)

• Spend the session on Software Engineering (General Role Competencies), which Tokio Marine North America Services candidates report being tested on.
• Write one worked example in Software Engineering (General Role Competencies) and time yourself on it.

Deliverable: One timed worked example in Software Engineering (General Role Competencies).

Day 4 — Work Software Development

• Spend the session on Software Development, which Tokio Marine North America Services candidates report being tested on.
• Write one worked example in Software Development and time yourself on it.

Deliverable: One timed worked example in Software Development.

Day 5 — Answer out loud: API and Software Development Foundations

• Answer aloud, timed: Explain the lifecycle of a typical REST API request from the client to the database and back.
• Answer aloud, timed: How do you handle versioning and backward compatibility when updating an existing API?

Deliverable: Spoken answers to 2 reported API and Software Development Foundations question(s), under time.

Day 6 — Answer out loud: Scenario-Based & Systems Engineering

• Answer aloud, timed: If an integration with a third-party rating engine fails mid-transaction, how do you design your system to recover gracefully without losing data?
• Answer aloud, timed: Walk us through a scenario where a production application experiences a sudden spike in latency. How do you isolate and resolve the bottleneck?

Deliverable: Spoken answers to 2 reported Scenario-Based & Systems Engineering question(s), under time.

Day 7 — Answer out loud: Behavioral & Professional Experience

• Answer aloud, timed: Walk me through your resume and highlight a project where you had to overcome a major technical roadblock.
• Answer aloud, timed: How do you handle working with a stakeholder or team member who has a different technical perspective than you?

Deliverable: Spoken answers to 2 reported Behavioral & Professional Experience question(s), under time.

Behavioural preparation

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

Describe your experience with database optimization and how you write efficient queries for high-volume transa

Medium · API and Software Development Foundations

Describe your experience with database optimization and how you write efficient queries for high-volume transactions.

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 working with a stakeholder or team member who has a different technical perspective than you

Medium · Behavioral & Professional Experience

How do you handle working with a stakeholder or team member who has a different technical perspective than you?

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 time when you had to quickly learn a new proprietary tool or configuration language to deliver a pr

Medium · Behavioral & Professional Experience

Describe a time when you had to quickly learn a new proprietary tool or configuration language to deliver a project.

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 maintain your focus and deliver high-quality work during periods of organizational change or ambigu

Medium · Behavioral & Professional Experience

How do you maintain your focus and deliver high-quality work during periods of organizational change or ambiguity?

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?