About the role
An inherited website may depend on custom code, extensions and hosting settings that are poorly documented. You will assess those dependencies, choose a build or maintenance approach and guide changes that keep important visitor journeys working.
What you will do
- Assess unfamiliar websites and define a safe build, migration, or maintenance approach.
- Review release readiness and resolve problems involving custom code, extensions, and hosting dependencies.
- Map the CMS, extensions, customisations and hosting dependencies before a migration or substantial update.
- Define release checks for forms, redirects, editable content and recovery, then review evidence before publishing.
What you should bring
- Ability to assess CMS architecture, browser behaviour and hosting dependencies, including the consequences of changing an unfamiliar site.
Examples of work in this role
- A site assessment that distinguishes urgent defects, maintenance risks and planned improvements.
- A release and recovery plan with checks for important pages and visitor actions.
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.
- Describe an inherited site you improved or migrated. Explain how you found a hidden dependency and checked the release.
- Share only work you have permission to disclose. A redacted sample or a clear explanation is fine when client work is confidential.