Tem-Energy Limited
Staff Full Stack Engineer (Sell Side Engine)
Tem is hiring a hands-on Staff Full Stack Engineer for a new Origination & New Products squad, rebuilding manual tendering, contracting, and pricing flows into scalable systems for renewable generators. The core stack is Python and AWS serverless (Lambda, API Gateway, DynamoDB, EventBridge), with React/TypeScript front-end work when needed.
- Compensation
- Not disclosed
- Location
- United Kingdom
- Work setup
- Not specified
- Seniority
- Staff
- Employment
- Not specified
- Experience
- Not specified
- Category
- Fullstack
- Posted
Skills
Must have
- Deep technical depth in backend and systems design, with a track record of owning architecture-level decisions on complex, integration-heavy systems
- Comfortable in core stack: Python, AWS serverless (Lambda, API Gateway, DynamoDB, EventBridge), and event-driven architectures
- Comfortable operating without a full spec: able to take a defined slice of an ambiguous problem and turn it into a shippable plan
- Experience delivering work where a critical dependency sits with a team you have no authority over
- Proven product delivery experience as a Full Stack or Backend Engineer in a startup or fast-paced product environment, with ownership of complex projects from start to finish
Nice to have
- React/TypeScript exposure
- Prior experience mentoring engineers or setting technical direction, even without a formal leadership title
- Experience in energy, fintech, or another regulated, high-stakes commercial domain
- Exposure to workflow orchestration, event-driven systems, or real-time pricing engines
- Experience originating new product lines from scratch rather than only scaling existing ones
Full description
Requirements
- Deep technical depth in backend and systems design, with a track record of owning architecture-level decisions on complex, integration-heavy systems
- Comfortable in our core stack: Python, AWS serverless (Lambda, API Gateway, DynamoDB, EventBridge), and event-driven architectures. React/TypeScript exposure is a plus but not the bar
- Comfort operating without a full spec: able to take a defined slice of an ambiguous problem and turn it into a shippable plan
- Experience delivering work where a critical dependency sits with a team you have no authority over
- Proven product delivery experience: experience as a Full Stack or Backend Engineer in a startup or fast-paced product environment, with ownership of complex projects from start to finish
- (Desirable) Prior experience mentoring engineers or setting technical direction, even without a formal leadership title. Not required. We’d rather have a brilliant engineer who has never led a squad than a mediocre one who has
- (Desirable) Experience in energy, fintech, or another regulated, high-stakes commercial domain
- (Desirable) Exposure to workflow orchestration, event-driven systems, or real-time pricing engines
- (Desirable) Experience originating new product lines from scratch rather than only scaling existing ones
What the job involves
- We're hiring a Staff Software Engineer to join Origination & New Products, a new three-person squad inside Sell Side Growth
- Sell Side Growth originates, contracts, and retains the renewable generators whose volume powers our platform - without generators, there's no product
- The engine is scaling fast, and much of the manual process underneath today's pipeline - tendering, contracting, onboarding - needs to be rebuilt to handle that growth rather than buckle under it
- This is a deep, hands-on IC role, not a squad-lead one - that's owned by the Staff/Senior Staff engineer leading the initiative
- You're free to go all-in on the hardest technical problems: integration with Rosso (our pricing and settlement engine), Control Room (our core tendering and pipeline platform), and the deal-gating risk tooling that lets us take on genuinely new categories of commercial risk safely
- We're not hiring for leadership polish here
- We're hiring a ridiculously good engineer
- Go deep on hard systems: Own architecture-level decisions on integration-heavy systems, reasoning clearly about boundaries, contracts, and failure modes
- Build for ambiguity: Take a piece of an undefined, commercially-driven problem and turn it into a shippable plan, within the direction your squad lead sets