Job Description

Security Remediation Engineer

Location: Remote (Occasional travel to their London office)

Contract: Inside IR35

Day rate: Up to £800 per day

Duration: 6 months

Start date: ASAP

Key words: Security, hands-on application, workflow, release and logging remediation

The Security Remediation Engineer will support the delivery of hands-on application, workflow, release and logging remediation within a security assessment remediation programme.

The successful contractors will work with AppSec / DevSecOps, QA automation, MLOps, Data / AI Governance, ServiceNow / Jira specialists and the Security Remediation Lead to implement application-level changes that close controls and generate usable evidence.

This is a remediation engineering role. Candidates should be comfortable working in existing codebases, improving delivery workflows, tightening operational controls and documenting implementation evidence.

Assignment Objectives

- Analyse assessment findings and translate assigned remediation items into concrete software changes.

- Implement changes to application workflows, state transitions, access checks, release flows and integration behaviours.

- Support Jira workflow and status changes where application or delivery process alignment is required.

- Create or update release and rollback playbooks with practical engineering input.

- Improve application logging for user activity, security-relevant events, errors and operational diagnostics.

- Integrate with Application Insights, Log Analytics or comparable monitoring and telemetry tooling.

- Support secrets management and secure configuration using Azure Key Vault, managed identities and controlled deployment settings.

- Work with AppSec / DevSecOps engineers to remediate vulnerabilities, dependency issues and secure coding findings.

- Work with QA automation to increase regression coverage and make remediation test evidence repeatable.

- Support PostgreSQL access governance, data handling, retention and auditability improvements where application changes are needed.

- Maintain traceability from Jira tickets to code changes, pull requests, tests, releases and evidence artefacts.

- Document changes clearly enough for control owners, retesters and BAU maintainers to understand the control outcome