About the role
A workflow can look simple on screen and still fail when requests are retried or two people edit the same record. In this senior role, you will decide how the interface, API and data model should handle those cases and make the approach clear to other developers.
What you will do
- Turn incomplete business requirements into a workable architecture and staged delivery plan.
- Review technical decisions, diagnose problems across the application, and explain the effect of shortcuts on future maintenance.
- Define validation, permissions and failure handling before a workflow spans several services.
- Review database migrations and release steps so an application change can be tested and recovered.
What you should bring
- Ability to reason about API contracts, data integrity and deployment tradeoffs, then explain those decisions in code reviews.
Examples of work in this role
- An architecture note that explains data ownership, integration boundaries and the decisions behind them.
- A reviewed implementation with tests for failed requests, conflicting changes and access restrictions.
Working arrangements
- Keep progress, questions, and blockers visible through the agreed communication channels.
- Availability, working hours, equipment needs, and any location eligibility requirements will be discussed during recruitment.
- Employment terms, compensation, and any benefits will be discussed during recruitment.
What to include in your application
- Use the application form and include your CV, availability, and a short explanation of why this work interests you.
- Show a feature that crossed the browser, server and database. Explain one failure path you designed for and how your tests or operational evidence checked it.
- Share only work you have permission to disclose. A redacted sample or a clear explanation is fine when client work is confidential.