LLD Java Concurrency: Design Cancelled Task Tracker for ExecutorService
Interview Experience
Question You have an
ExecutorService that runs tasks. When you call shutdownNow(), it returns a list of tasks that were never started. But what about the tasks that were already running and
Full Details
Question You have an
ExecutorService that runs tasks. When you call shutdownNow(), it returns a list of tasks that were never started. But what about the tasks that were already running and got interrupted mid‑execution? Those are gone – no trace, no list. How can you reliably track which tasks were cancelled (interrupted) during an abrupt shutdown, so you can later re‑process them? ---
Key Concepts - shutdown() vs shutdownNow() shutdown(): graceful – no new tasks, but running tasks continue. shutdownNow(): abrupt – tries to interrupt running tasks and returns pending tasks. - Thread interruption Running tasks that respect interruption may throw InterruptedException or check Thread.interrupted(). shutdownNow() sets the interrupt flag on all worker threads. - Tracking in‑flight cancellations You need to know which tasks were interrupted after they started but before they completed. - Wrapper pattern Decorate an ExecutorService to add tracking logic without changing the underlying executor. ---
Solution 1. Create a wrapper class that holds a reference to a real ExecutorService and a thread‑safe set (e.g., ConcurrentHashMap.newKeySet()) for cancelled tasks. 2. Override execute(Runnable r) Submit a wrapper Runnable to the real executor. Inside that wrapper: Call r.run() inside a try block. In a finally block, check if the executor is shutting down (isShutdown()) and the current thread is interrupted (Thread.currentThread().isInterrupted()). If both are true, add the original task to the cancelled set.
public void execute(final Runnable runnable) { exec.execute(() -> { try { runnable.run(); } finally { if (isShutdown() && Thread.currentThread().isInterrupted()) tasksCancelledAtShutdown.add(runnable); } }); }
Topics
About General Tech Interview Reports
This question was reported by a candidate who interviewed at General Tech. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at General Tech are the higher-signal extractions to take from this report.
For broader preparation context, the General Tech interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in General Tech reports consistently are the ones worth investing in; one-off niche problems are not.
During Your General Tech Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in General Tech reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.