5 exercises — covering the Temporal programming model, activities vs workflows, signals and queries, workflow versioning, and error handling patterns.
Structure for Temporal Workflow Engineer answers
Workflows vs Activities: workflows are deterministic, durable, and cannot perform I/O; activities do the actual work
Signals vs Queries: signals change workflow state (async); queries read workflow state (sync, no side effects)
Versioning: use GetVersion() / workflow.GetVersion() to safely change workflow logic without breaking in-flight runs
Error handling: activities retry automatically; workflows survive crashes; use compensating activities for saga pattern
0 / 10 completed
1 / 10
The interviewer asks: "Explain the difference between a Workflow and an Activity in Temporal. What rules must each follow?" Which answer is most precise?
Option B is strongest. It precisely defines the determinism requirement for workflows (same history → same commands), names the specific prohibitions (no random, no system time, no direct I/O), explains why (replay divergence), contrasts with activities (no determinism requirement, do actual I/O, retry independently), and names the most common mistake (I/O inside workflow → silent correctness errors on replay). Option A incorrectly states "both can call external services" — workflows cannot. Option C uses execution duration as the criterion — wrong; duration is not what distinguishes workflows from activities. Option D focuses on language — polyglot support is a feature but not the defining characteristic.
2 / 10
The interviewer asks: "How do you handle a change to workflow logic when there are already in-flight workflow instances?" Which answer is most operationally safe?
Option C is strongest. It names the specific API (workflow.GetVersion() / change ID), explains the mechanism (existing runs see old marker → old path; new runs → new path), describes the cleanup process (maintain both paths until old runs complete), recommends descriptive change IDs, and includes a testing method (replay test against old histories). Option A terminates in-flight workflows — data loss and business process interruption. Option B deploys without versioning — causes replay divergence for in-flight workflows, which manifests as panics or silent correctness errors. Option D claims Temporal handles this automatically — incorrect; the developer must use the versioning API.
3 / 10
The interviewer asks: "What is the difference between a Signal and a Query in Temporal? When do you use each?" Which answer is most precise?
Option B is strongest. It defines each with its key properties (signal: async, write, durable, queued; query: sync, read, no side effects, no history recording), gives concrete use cases for each, and addresses the important limitation: queries cannot reach a completed workflow. Option A is too vague. Option C states the write/read distinction but misses durability, queuing, side effects, and the completed workflow limitation. Option D uses signals for everything — queries have significantly lower overhead (no history write) for read operations; using signals for read operations pollutes the workflow history.
4 / 10
The interviewer asks: "How do you implement the Saga pattern in Temporal for a multi-step transaction?" Which answer is most complete?
Option B is strongest. It describes the compensation stack pattern (register compensations as you go, execute in reverse on failure), distinguishes retriable from non-retriable failures, and — critically — handles compensation failures (failed compensation → inconsistent state → human operator). Option A only retries the failed step — no compensation for already-completed steps, leaving the system in an inconsistent state. Option C claims Temporal has built-in saga support — incorrect; Temporal provides the durable execution primitives but the developer implements the compensation pattern. Option D uses a database transaction — this does not work across multiple services or external APIs.
5 / 10
The interviewer asks: "How do you observe and debug a Temporal workflow in production?" Which answer shows the most operational maturity?
Option C is strongest. It names five observability layers (workflow history, metrics with specific metric names, structured activity logging with correlation fields, search attributes, alerting), includes the critical warning about not logging inside workflow code (replay issue), and specifies actionable alert conditions. Option A relies on worker logs and restarting — logs alone miss the workflow history context; restarting does not fix a corrupted workflow. Option B uses print statements — does not survive in production and causes replay issues. Option D relies on Temporal Cloud — valid for managed Temporal but does not describe the observability design.
6 / 10
Liam (Senior Temporal Engineer) sends you this Slack message: 'Hey, the OrderProcessingWorkflow is failing intermittently. Logs show errors related to a timeout with our payment gateway integration. We're seeing about 15% failure rate. Any ideas?' How should you respond initially?
The key here is gathering information before jumping to conclusions. Simply stating a potential issue without further investigation risks misdiagnosis and wasted effort. Asking for logs and instance ID allows you to understand the context of the failure and pinpoint the root cause – this demonstrates operational maturity and efficient troubleshooting. Options A & C are reactive without proper data; option D is a common but often ineffective immediate action.
7 / 10
You're reviewing a Pull Request for a new Temporal workflow designed to update customer addresses. The PR description reads: 'This workflow updates the customer's address based on a notification from our CRM system. It uses a Signal to trigger the update and a Query to retrieve the old address. It handles retries using exponential backoff.' However, you notice no explicit error handling is present for the Query step. What's your most appropriate comment?
A good code review focuses on robustness. While the PR description mentions error handling for the Signal (which is correct), neglecting to handle errors in the Query step – which retrieves data *before* the update – introduces a significant vulnerability. The CRM system could be unavailable, leading to a cascading failure. Adding explicit error handling demonstrates proactive risk mitigation.
8 / 10
During a standup meeting, your team lead asks: 'How's the progress on implementing Temporal's retry mechanism for the InventoryUpdateWorkflow?' You respond with: 'We're using Temporal's built-in retry configuration and setting the maximum retries to 3. We've also implemented exponential backoff.' What is the MOST important next step you should outline to ensure operational stability?
While all options have *some* merit, monitoring execution logs is fundamentally crucial for understanding *why* retries are failing. This data informs adjustments to the retry strategy (e.g., reducing backoff, increasing max retries) and reveals potential systemic issues within the workflow or its dependencies. Options A & B address reactive actions; option D is documentation, which follows action.
9 / 10
You're designing a Temporal workflow to process e-commerce orders. You need to use Saga pattern to handle the payment, inventory and shipping steps. Which of the following best describes how you should approach this within Temporal?
Temporal's Saga support is designed for this purpose. Utilizing Temporal's built-in Sagas allows you to define each step (payment, inventory, shipping) as a distinct saga, ensuring that if one fails, only that specific saga is rolled back, preserving the integrity of the overall transaction. Options A & C are overly complex; option D introduces manual state management which defeats Temporal's purpose.
10 / 10
Your team is deploying a new Temporal workflow to production. You need to observe and debug any issues that arise. Which of the following techniques would provide the MOST comprehensive view for operational monitoring?
While logs and alerts are important, they provide only reactive insights. Distributed tracing allows you to follow a single request as it flows through your microservices architecture, pinpointing exactly where latency or errors occur – this is crucial for understanding complex Temporal workflows and diagnosing performance bottlenecks or failures. Option A provides limited visibility; option D is a response *after* an issue.
What does "Temporal Workflow Engineer Interview Questions — Best-Answer Practice" cover?
Practice answering Temporal Workflow Engineer interview questions in professional English. 5 exercises on activities vs workflows, signals, versioning, error handling, and workflow observability.
How many questions are in this interview set?
This set has 10 exercises, each with a full explanation.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do these exercises include model answers?
Yes. Each interview question gives you several possible responses and asks you to pick the one that communicates most clearly and completely — the explanation then breaks down exactly why that answer works, including the specific vocabulary a strong candidate would use.
What if I choose an answer that isn't the strongest one?
You'll see which option was correct and read a full explanation of why it's stronger than the alternatives, plus the key vocabulary and phrasing worth reusing in a real interview.
Can I retry the questions?
Yes — use the "Try again" button on the results screen to reset and go through the set again.
Is this the same as a real technical or behavioural interview?
No — it's focused practice for the language side of interviewing: recognising which phrasing sounds precise and confident versus vague, and knowing the vocabulary interviewers expect for this role. It won't replace mock interviews, but it builds the vocabulary you'll need in one.
Where can I find interview prep for other roles?
Browse the full Interview exercises hub for 170+ modules covering behavioural, technical, and system design rounds across dozens of IT roles, or check the "Next up" link below to continue.
Do I need an account, and is my progress saved?
No account is needed. Progress is tracked only for your current visit — reloading or leaving the page resets the counter.
Who writes these interview questions?
Every question is written by the CoderSlingo team based on real technical interview patterns for this role, then reviewed for accuracy and clarity.