> Markdown version of [/jobs/ext/3786184-senior-software-engineer-energy-data-platform-remote-uk](https://www.wearedevelopers.com/jobs/ext/3786184-senior-software-engineer-energy-data-platform-remote-uk). 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).

---

# Senior Software Engineer - Energy Data Platform | Remote (UK)

- **Company:** La Fosse, Clay
- **Location:** United States (Remote available)
- **Experience:** Expert
- **Salary:** $90,000.0 - $100,000.0
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Amazon Web Services, Microsoft Azure, C Sharp (Programming Language), Cloud Computing, Continuous Integration, Data Infrastructure, Python (Programming Language), TypeScript, ReactJS, Backend, Databricks
- **Published:** October 16, 2026
- **Apply:** https://arc.dev/remote-jobs/j/redirect/ps06gwturu

## About the Role

* A strong software engineer first, backend-leaning, with real depth in a high-level language (Python preferred; Java, C# or TypeScript also considered)
 * Hands-on cloud experience, ideally AWS or Azure
 * Solid CI/CD experience
 * A track record of owning builds end to end, not just picking up tickets
 * Opinions on how good systems should be built, and the confidence to explain and defend them
 * Clear communication with technical and non-technical audiences

Nice to have

 * Databricks or data platform experience
 * React / TypeScript
 * Energy or utilities background
 * AI-assisted development workflows

## Description

* Core member of a small platform team, sharing architecture and design with the Engineering Lead
 * End-to-end ownership, from system design through to delivery
 * Build the platform's integrations, pipelines and shared tooling, mostly back end, on a Databricks-based platform
 * Design and improve CI/CD so quality, reliability and observability are built in from the start
 * Work directly with energy modellers and non-technical stakeholders to understand what they need