Senior Developer

Own the outcome. Build with confidence. Help others become stronger engineers.

SALARY

LOCATION

Manchester/Lytham St Annes

WORKING PATTERN

Hybrid

The opportunity

Evolve Energy is a rapidly scaling business in an exciting phase of engineering transformation. We are modernising mature platforms, developing new cloud services and increasing the capacity, reliability and speed of delivery needed to support business growth. We are looking for a hands-on Senior Developer who can take ownership of outcomes across complex changes, not simply complete assigned development tasks. You will combine strong software engineering with sound design judgement, operational ownership, business understanding and practical support for the engineers around you.

What success looks like

Cross-system changes are delivered safely and work well in production. Quality and operational risks are visible. Technical decisions are proportionate and connected to business outcomes. Less experienced engineers grow in confidence and independence.

Own the technical delivery and operational outcome of significant changes across services and system boundaries. You will remain hands-on in the code while shaping solutions, coordinating dependencies, managing technical risk and ensuring changes transition successfully into production support. You will work closely with developers, quality engineers, business analysts, product colleagues and business stakeholders. You will challenge requirements constructively, explain technical trade-offs clearly and help the team improve its engineering practice through reviews, pairing, coaching and shared learning.

What you will do

• Establish and reinforce quality expectations within your team, applying TDD, BDD and appropriate automated testing practices
• Use testing to improve software design, maintainability and confidence in change, balancing delivery speed with supportability
• Design and deliver complex solutions across services and system boundaries within agreed architectural principles and cloud adoption standards
• Evaluate and explain trade-offs across performance, security, maintainability, cost, risk and delivery speed
• Use code reviews, pairing and clear feedback to improve engineering practice across the team
• Use quality, defect, technical debt and operational evidence to prioritise improvements within owned areas
• Take ownership of delivery and operational outcomes, coordinating work across multiple systems or components
• Identify technical dependencies, delivery risks and blockers early, then work with the team to maintain momentum
• Improve CI/CD pipelines, deployment practices and release confidence within the areas you own
• Use trunk-based development, short-lived branches and feature flags to support frequent, low-risk change and controlled rollback
• Improve observability through meaningful metrics, logs, traces and alerting, using telemetry to understand service behaviour and customer impact
• Drive root-cause analysis after incidents and turn production learning into improvements in design, testing, deployment and support

• Use AI-assisted development, testing, analysis and documentation techniques where they improve delivery outcomes
• Critically evaluate AI-generated outputs to protect quality, security and maintainability, retaining appropriate human review
• Identify practical opportunities for AI to reduce repetitive effort, improve troubleshooting or increase useful test coverage
• Share effective usage patterns and lessons learned so the wider team can adopt AI responsibly.

• Understand customer, operational, commercial and financial drivers, and connect technical choices to measurable outcomes
• Challenge requirements and assumptions constructively, shaping solutions around business value rather than technical preference
• Contribute technical insight to product and prioritisation decisions, identifying opportunities to reduce cost, risk, effort or customer friction
• Establish meaningful performance baselines for significant changes and use telemetry to identify bottlenecks, capacity constraints and scaling risks
• Design services that are observable, supportable and resilient, with expected business growth considered from the outset

• Provide technical leadership within your delivery area, helping the team align around clear and proportionate technical decisions
• Coach less experienced engineers through pairing, reviews, actionable feedback and stretch opportunities
• Reduce key-person dependency through useful documentation, knowledge transfer and shared ownership across services
• Evaluate and trial new technologies, tools and practices where value can be demonstrated, making recommendations based on evidence
• Introduce practical automation, tooling and engineering improvements, then help the team sustain successful changes

We are more interested in evidence of sound judgement and outcomes than a checklist of technologies. You should…