> Markdown version of [/jobs/ext/3662747-software-engineer](https://www.wearedevelopers.com/jobs/ext/3662747-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer

- **Company:** Ukceh
- **Location:** Lancaster, UK
- **Salary:** £40,574.0 - £43,056.0
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Automation of Tests, Microsoft Azure, Cloud Computing, Code Review, Continuous Integration, Data Stores, Software Debugging, Integrated Development Environments, Python (Programming Language), NoSQL, Standard Sql, Software Engineering, Cloud Platform System, Git, Software Version Control, Docker
- **Published:** October 10, 2026
- **Apply:** https://ceh.wd3.myworkdayjobs.com/CEH_Careers/job/Lancaster/Software-Engineer_JR1599

## About the Role

* Has a good degree in an appropriate subject, or significant experience of working in a Software Engineering environment.

 * Solid, practical experience writing production software in at least one general-purpose language (Python is desirable, as it matches our current stack, but we welcome strong candidates from other languages).

 * Good software engineering practices: version control and branching (Git), automated testing, code review, debugging systems you did not write, and working with SQL and/or NoSQL data stores.

 * Working knowledge of cloud and containers: comfortable deploying to at least one cloud platform (Azure, AWS or GCP) and working with Docker or similar, with an understanding of CI/CD.

 * Clear communication and collaboration: able to work with non-specialists, write documentation and take and give feedback

 * An appetite to learn. Our stack and the wider landscape both move; we need people who stay curious.

## Description

Please keep each response to 150 words or fewer, using clear examples that highlight your own contribution and relevant experience.

Q1. Tell us about a piece of software you've built or maintained that other people depended on.

Q2. Describe a time you worked with someone who wasn't a software engineer to work out what they needed, or to explain a technical trade-off to them.

Q3. Tell us about a time you had to get up to speed quickly with an unfamiliar codebase, tool or technology.

What happens next?
Our panel will review your application, and we are committed to providing an outcome to all applicants.