As a Software Engineer at Izertis, you play a pivotal role in delivering digital transformation solutions, technological consultancy, and specialized engineering projects for a diverse global clientele. This position is vital for designing, building, and maintaining robust software systems, enterprise platforms, and specialized technical architectures. Your contributions directly impact business clients across sectors such as public administration, aeronautics, telecommunications, and energy, ensuring that end-users experience reliable, scalable, and innovative digital services. This role combines deep technical execution with strategic problem-solving, often requiring you to collaborate with cross-functional project teams, client stakeholders, and specialized domain experts. Whether you are developing applications on enterprise platforms like PeopleSoft, configuring marketing cloud solutions, or supporting critical aerospace and infrastructure engineering, you will operate at the intersection of technical excellence and business value. The work environment is dynamic and project-driven, offering exposure to complex multi-stakeholder environments and cutting-edge digital ecosystems. While you will enjoy significant autonomy in solving technical challenges, you must also navigate structured project pipelines and client-specific requirements.
Initial Screening
reportedConducted by a talent acquisition or HR professional to verify background, language skills, and core qualifications.
What to demonstrate
- Conducted by a talent acquisition or HR professional to verify background, language skills, and core qualifications
- Depth in Identity and Access Management (IAM)
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 Evaluations
reportedDiscussions with project managers and technical leads to assess technical competence and domain alignment.
What to demonstrate
- Discussions with project managers and technical leads to assess technical competence and domain alignment
- Depth in Identity and Access Management (IAM)
How to prepare
- Answer aloud and timed: What is your experience with specific administrative or enterprise platforms like PeopleSoft or cloud-based marketing tools?
- Answer aloud and timed: How do you ensure code quality, maintainability, and proper documentation in fast-paced project environments?
Approval Layers
reportedInvolves multiple layers of approval and validation, especially for roles tied to public administration or specialized contracts.
What to demonstrate
- Involves multiple layers of approval and validation, especially for roles tied to public administration or specialized contracts
- Depth in Identity and Access Management (IAM)
How to prepare
- Answer aloud and timed: Can you describe a technical challenge you resolved while integrating third-party systems or legacy infrastructure?
- Answer aloud and timed: Tell me about a time when project requirements changed mid-stream. How did you adapt your development strategy?
PracHub editorial advice for the preparation topics above.
Highlight consultancy alignment
Emphasize your ability to work with clients, manage expectations, and adapt to changing project scopes, as these traits are vital in a technology consultancy.
Be ready for administrative validation
Ensure your official documentation, academic titles, and employment history are organized and readily accessible, as certain recruitment tracks require formal credential checks early on.
Structure your behavioral answers
Use the STAR method (Situation, Task, Action, Result) when discussing past projects, focusing heavily on the tangible results and lessons learned.
Communicate your thought process
During technical evaluations, talk through your reasoning out loud so interviewers can follow your logic even if you do not immediately reach the final answer.
Show genuine curiosity
Ask insightful questions about the types of clients, project lifecycles, and team structures you will be working with during your tenure.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Find overlapping job attempts and peak concurrency from lease records
A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.
Approach
- Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
- For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
- For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
- Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.
Follow-up
- A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
- Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?
Archive a resource graph without breaking live references or recursing
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
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?
Can you walk me through your hands-on experience with enterprise software architectures and custom development
Can you walk me through your hands-on experience with enterprise software architectures and custom development?
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 ensure code quality, maintainability, and proper documentation in fast-paced project environments?
How do you ensure code quality, maintainability, and proper documentation in fast-paced project environments?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you describe a technical challenge you resolved while integrating third-party systems or legacy infrastruc
Can you describe a technical challenge you resolved while integrating third-party systems or legacy infrastructure?
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?
How do you validate that your technical solution meets both functional requirements and client expectations?
How do you validate that your technical solution meets both functional requirements and client expectations?
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 manage your time and prioritize tasks when juggling multiple engineering deliverables?
How do you manage your time and prioritize tasks when juggling multiple engineering deliverables?
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 steps do you take when you encounter a technology or tool you have never used before on a live project?
What steps do you take when you encounter a technology or tool you have never used before on a live project?
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 approach debugging and optimizing performance in complex, distributed systems?
How do you approach debugging and optimizing performance in complex, distributed systems?
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 Izertis candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Izertis loop
- Write out the reported sequence: Initial Screening, Technical Evaluations, Approval Layers.
- 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 Identity and Access Management (IAM)
- Spend the session on Identity and Access Management (IAM), which Izertis candidates report being tested on.
- Write one worked example in Identity and Access Management (IAM) and time yourself on it.
Deliverable: One timed worked example in Identity and Access Management (IAM).
03Work PeopleSoft
- Spend the session on PeopleSoft, which Izertis candidates report being tested on.
- Write one worked example in PeopleSoft and time yourself on it.
Deliverable: One timed worked example in PeopleSoft.
04Work Salesforce Marketing Cloud
- Spend the session on Salesforce Marketing Cloud, which Izertis candidates report being tested on.
- Write one worked example in Salesforce Marketing Cloud and time yourself on it.
Deliverable: One timed worked example in Salesforce Marketing Cloud.
05Answer out loud: Technical and Domain Alignment
- Answer aloud, timed: Can you walk me through your hands-on experience with enterprise software architectures and custom development?
- Answer aloud, timed: How do you approach debugging and optimizing performance in complex, distributed systems?
Deliverable: Spoken answers to 2 reported Technical and Domain Alignment question(s), under time.
06Answer out loud: Project Experience and Practical Execution
- Answer aloud, timed: Tell me about a time when project requirements changed mid-stream. How did you adapt your development strategy?
- Answer aloud, timed: How do you validate that your technical solution meets both functional requirements and client expectations?
Deliverable: Spoken answers to 2 reported Project Experience and Practical Execution question(s), under time.
07Answer out loud: Behavioral and Cultural Fit
- Answer aloud, timed: Why are you interested in joining Izertis and contributing to our consultancy and technology projects?
- Answer aloud, timed: How do you handle feedback and constructive criticism on your code or architectural designs?
Deliverable: Spoken answers to 2 reported Behavioral and Cultural Fit 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.
What is your experience with specific administrative or enterprise platforms like PeopleSoft or cloud-based ma
What is your experience with specific administrative or enterprise platforms like PeopleSoft or cloud-based marketing tools?
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 when project requirements changed mid-stream. How did you adapt your development strategy
Tell me about a time when project requirements changed mid-stream. How did you adapt your development strategy?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe your experience collaborating with non-technical stakeholders or project managers during system rollo
Describe your experience collaborating with non-technical stakeholders or project managers during system rollouts.
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 Izertis and contributing to our consultancy and technology projects?
Why are you interested in joining Izertis and contributing to our consultancy and technology projects?
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 feedback and constructive criticism on your code or architectural designs?
How do you handle feedback and constructive criticism on your code or architectural designs?
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 disagreed with a team member or project lead regarding a technical decision. How was
Tell me about a time you disagreed with a team member or project lead regarding a technical decision. How was it resolved?
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 manage high-pressure situations, such as tight project deadlines or critical system outages?
How do you manage high-pressure situations, such as tight project deadlines or critical system outages?
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 situation where you took ownership of a failing process or project component to steer it toward suc
Describe a situation where you took ownership of a failing process or project component to steer it toward success.
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
What is your experience with specific administrative or enterprise platforms like PeopleSoft or cloud-based marketing tools?
- 02
Tell me about a time when project requirements changed mid-stream. How did you adapt your development strategy?
- 03
Describe your experience collaborating with non-technical stakeholders or project managers during system rollouts.
- 04
Why are you interested in joining Izertis and contributing to our consultancy and technology projects?
How difficult is the interview process at Izertis, and how much time should I spend preparing?
The interview difficulty is generally considered moderate and accessible, provided you have solid foundational experience in your stack. Preparation typically takes one to two weeks, focusing primarily on reviewing your past project experience and brushing up on core technical concepts.
Izertis Software Engineer candidate reports ↗What differentiates successful candidates from others during the evaluation loop?
Successful candidates stand out by demonstrating clear communication, practical problem-solving methodologies, and a strong understanding of how their technical work drives business and client value. Being able to explain past project challenges clearly is a major advantage.
Izertis Software Engineer candidate reports ↗What is the culture like for engineers at Izertis?
The engineering culture is project-driven, collaborative, and professional, blending the agility of a consultancy with the structured requirements of enterprise and public sector clients. Engineers are expected to be self-motivated and adaptable.
Izertis Software Engineer candidate reports ↗What is the typical timeline from the initial recruiter screen to receiving an offer?
The timeline can vary based on project demands and client-side approvals, sometimes taking anywhere from a few weeks to over a month. This is particularly true for roles tied to public sector competitions where administrative steps dictate the pace.
Izertis Software Engineer candidate reports ↗Are there remote or hybrid work opportunities available for this role?
Work arrangements depend heavily on the specific client contract, project requirements, and office location. Many roles offer hybrid flexibility, while others may require alignment with specific client sites or local office hubs.
Izertis Software Engineer candidate reports ↗What topics does Izertis test in interviews?
Izertis interviews most often cover Stakeholder Communication, QA Engineering, Data Modeling (Power BI), Identity and Access Management (IAM), and Stakeholder Management. The exact emphasis depends on the specific role you apply for.
Izertis 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.
- 01Izertis 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.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai 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.
Lambda Software Engineer Interview Guide
Failure-handling practice for Lambda 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.
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.