At a Glance
- Tasks: Join us as a Founding Backend Engineer to shape our platform and tackle real energy challenges.
- Company: SOLR AI is revolutionising renewable energy with cutting-edge AI technology.
- Benefits: Competitive salary, equity options, pension, and a dynamic work environment.
- Other info: Join a VC-backed startup with excellent growth potential and a collaborative culture.
- Why this job: Make a tangible impact on the energy transition while working at the forefront of AI.
- Qualifications: Strong backend skills, experience in production environments, and a passion for innovation.
The predicted salary is between 85000 - 95000 £ per year.
Energy is the binding constraint on AI and economic prosperity: nothing scales until it's cheap, abundant, and sustainable. Sustainable energy is non-negotiable during a worsening climate crisis, but the forces driving the energy transition are now also resilience, sovereignty, and national security. SOLR AI builds at that pressure point: Frontier intelligence for the energy transition.
The renewable energy industry still runs on spreadsheets, PDFs, and weeks of manual survey work. SOLR AI is the intelligence layer replacing it: computer vision and machine learning over aerial imagery, geospatial, property, grid, and weather data and more, turning a UK address into a bankable-grade renewable energy assessment in minutes rather than weeks. The UK is the first market, not the last.
About the company: Stanley Wilson, co-founder and CEO, started building the company before ChatGPT was released; Dr Anna Chabokdast, co-founder and CTO (ex-tractable), trained her first ML model ten years ago. We were building at the frontier of AI in energy before the hype. Since then, we have our own models trained and in production, national coverage across all 14 UK distribution network regions, commercial energy operators live on the platform, first enterprise contracts converting, and the next generation of our models headed for the UK's fastest AI supercomputer. VC-backed and supported by Google for Startups, Barclays Eagle Labs, and Sustainable Ventures.
How we operate:
- Frontier science, shipped. We apply the frontier of AI research to real energy problems, and we're judged by what reaches production.
- Engineers are the fabric. Engineers own problems end to end: define, build, talk to users, ship. There is no layer between your work and the outcome.
- Extreme ownership, high slope. We hire for agency, learning rate, and humility over pedigree. You own the outcome, including what you get wrong.
- Research-led product development, product-led growth. Every research bet is measured by customer value; the product moulds our go-to-market.
- Clarity and candour. We write things down, build in the open, and give direct feedback.
- Intensity, honesty. This is seriously hard work at the edge of what's known. It's not for everyone, and that's the point.
Requirements:
The role: You’ll work directly with Anna, our co-founder and CTO, as our first founding engineer. The near-term job is turning a platform that works into a platform we can put contracts and SLAs behind: reliable, observable, secure by default, and able to onboard paying enterprise clients without every integration being a fire drill. Most of the day-to-day is backend and data engineering, and the scope is founding-level: you’ll shape the architecture with Anna, own whole systems end to end, and touch whatever the platform needs.
Over time the role grows into deploying and operating the production ML that powers the pipeline alongside Anna, so we’ll want proof you’ve already taken a deep learning model into production. The hard problem underneath all of it: standing behind accuracy claims contractually, on top of messy, heterogeneous external data, at national scale. In your first 90 days you’d ship multi-tenant authentication, a hardened ingestion layer with the observability we can put an SLA behind, and the benchmarking harness for those accuracy claims. Real production milestones, not onboarding theatre.
AI tooling and ownership:
Daily, fluent use of AI coding and agent tools is non-negotiable in this role, and the work trial will assess how you work with them. But we’ve seen the common failure mode where the agent quietly becomes the owner of the codebase. We want the opposite: you use these tools to move fast, and you can explain, defend, and rebuild any part of the system without them. If you can’t say why a piece of code exists, it doesn’t ship.
What you’ll work on:
- Harden the core pipeline against failure: timeouts, retries, and graceful degradation across external data dependencies.
- Build out CI/CD, structured logging, and alerting so we know about failures before clients do.
- Design and ship multi-tenant API authentication for design partners and enterprise clients.
- Own data engineering across the pipeline: ingestion, schema design, and geospatial queries over property, building, and imagery data.
- Build the automated testing and ground-truth benchmarking that lets us stand behind our accuracy claims.
- Work directly with our design partners and enterprise clients during onboarding and integration, and turn what you hear into what we build next.
- Shape architecture decisions directly with Anna as we onboard clients and scale, building to the standard that enterprise security and data-protection reviews expect, by default rather than retrofit.
What we’re looking for:
- Strong backend fundamentals: you can evaluate different ways of building an API and choose the right one for the problem, rather than defaulting to a framework.
- You’ve shipped and operated a real product in production, not just built one: you’ve carried on-call, handled an incident, or owned uptime for something people depended on.
- Data engineering judgement: pipelines over external APIs and data feeds, and the sense to pick the right schema and database for the problem.
- You’ve taken a deep learning model from prototype to production deployment.
- Engineering discipline as habit, not policy: testing, code review, secrets management, sane error handling, cloud-native by default.
Nice to have: geospatial or GIS work; experience in compliance-conscious environments (GDPR-heavy, fintech, healthtech); DevOps exposure; enough frontend competence to extend a client-facing interface; early-stage startup background.
Who shouldn’t join: If you want a spec handed to you, a team to disappear into, this isn't it: the near-term job is reliability engineering with a contract riding on it. If the uncertainty in what the company looks like in a year drives fear rather than excitement, then this isn't a fit.
Stack: Python backend, Typescript, a Postgres-family database with geospatial support, cloud-native infrastructure on GCP, and a modern frontend framework for the client-facing interface. We’ll go deep on the architecture with you during the process.
Compensation and equity, plainly: £85-95K base plus 1.25-1.75% of the company as EMI options (six-year vest, one-year cliff). We assess hard and we pay for demonstrated competence: the process maps you to a level, and each level carries a fixed salary and equity number at the top of what we’d pay for it. You get our best offer first, so you never have to negotiate for it. Before you sign we’ll walk you through the real numbers: the strike price, the current valuation, what dilution across future rounds realistically does, and the EMI tax treatment that makes this the most efficient equity a UK employee can hold. Plus pension and other benefits.
Founding Backend Engineer in London employer: SOLR AI
At SOLR AI, we are not just building cutting-edge technology; we are pioneering the future of sustainable energy with a culture that values extreme ownership and direct impact. As a Founding Backend Engineer, you will work closely with our co-founder and CTO, shaping the architecture and driving real production milestones in a dynamic environment that prioritises learning and innovation. With competitive compensation, equity options, and a commitment to transparency, we offer a unique opportunity to contribute to meaningful change while growing alongside a passionate team dedicated to tackling the climate crisis.
StudySmarter Expert Advice🤫
We think this is how you could land Founding Backend Engineer in London
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at SOLR AI or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to SOLR AI.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like SOLR AI.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like SOLR AI that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Founding Backend Engineer in London
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at SOLR AI.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at SOLR AI and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at SOLR AI
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If SOLR AI uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.