Build and defend an FDE take-home
Practise a compact integration task with a runnable record-cleaning exercise, a reproducible submission and a short technical defense.
What you'll be able to do
- Turn a brief into a small set of observable acceptance criteria
- Run and extend a deterministic data-handling exercise
- Defend a working submission with evidence and stated limitations
Before this: data-integration-and-recovery
Treat a take-home as a small delivery engagement. Read the brief and confirm its required inputs, outputs and time budget. Write acceptance criteria that another person can check. Follow the interviewer's policy on AI tools, external libraries and assistance.
For this original practice brief, import support records, keep the newest revision per ID and expose invalid records for review. The full prototype could show the resulting tickets and a reviewed draft answer. First make the data path reliable.
Run the data-handling slice
The cell uses an integer revision supplied by the fictional source. Higher revisions replace lower ones. It quarantines records with missing identifiers, subjects or valid revisions. Production code would also define how a conflicting payload with the same ID and revision is handled.
const records = [
{ id: "A1", revision: 1, subject: "Warranty question" },
{ id: "A1", revision: 2, subject: "Updated warranty question" },
{ id: "B2", revision: 1, subject: null },
{ id: "C3", revision: 1, subject: "Replacement part" },
];
const latest = new Map();
const quarantined = [];
for (const record of records) {
const valid =
typeof record.id === "string" && record.id.trim() !== "" &&
typeof record.subject === "string" && record.subject.trim() !== "" &&
Number.isInteger(record.revision) && record.revision >= 0;
if (!valid) {
quarantined.push(record);
continue;
}
const previous = latest.get(record.id);
if (!previous || record.revision > previous.revision) {
latest.set(record.id, record);
}
}
console.log("kept: " + [...latest.keys()].join(","));
console.log("A1 revision: " + latest.get("A1").revision);
console.log("quarantined: " + quarantined.length);
Change the order of the A1 records and run again. The final revision should still be 2. Then add a negative revision, an empty subject and a conflicting revision-2 record. Explain which behavior the current contract defines and which decision needs clarification. The exercise assumes each input is an object. Extending the ingestion boundary to handle arbitrary JSON is a further test.
Deliver an artifact someone can run
Include setup instructions, sample input, a command for checks and a short list of known limits. Demonstrate a normal request and an error path. If you include a model, keep credentials out of the submission and show how a reviewer supplies their own approved configuration.
Each stage leaves evidence for the reviewer, including the setup and failure behavior.
Rehearse the defense
Spend the first minute demonstrating the task. Next, trace the data path and explain a tradeoff. Show one failed case and the check that catches it. Finish with the next production improvement and the reason it has priority. Use the interviewer's actual time allowance when preparing a submission.
Practise this stage with ChannelPulse
Use the coding workbench to practise explaining changes and checking edge cases. Follow with a behavioral answer about the decision you made under time pressure, then review the feedback. Open interview practice.
Reading and attribution
The submission and interview themes draw on bicced's round guide, licensed under CC BY 4.0, and Tech Mahato's interview guide. The brief, code, input records and expected output are original ChannelPulse exercises.