Harden a Python Automation Workflow - Paid Technical Test
Employer not named by the sourceRemote
Frontier is not the employer and does not collect applications.
About this role
Python, Software Architecture, Test Automation, API, DevOps · This is a paid, fixed-price technical assessment using a small isolated Python repository and synthetic data. The budget cap is USD 200 and the expected timebox is 4 hours. Do not work beyond the timebox; document any unfinished work instead.
The repository simulates an automation that prepares and may create business records. It contains deliberate reliability and security defects. Your task is to make the workflow fail closed while keeping the implementation understandable.
### Required changes
1. Make dry-run the default and prove that no write client can be called without an explicit live mode. 2. Bind live execution to a single-use approval artifact containing the exact canonical payload hash. 3. Prevent duplicate creation across normal retries and concurrent attempts. 4. Add a durable, append-only audit trail without logging secrets or sensitive raw data. 5. Return clear machine-readable outcomes for dry-run success, blocked execution, duplicate detection, and successful write/readback. 6. Add or improve automated tests for the happy path and adversarial cases.
### Deliverables
- A Git patch or repository branch with the implementation. - Automated tests and one command