Full-Stack Engineer — Backend & Cloud Infrastructure

We're looking for a full-stack engineer to take over ownership of the platform behind Envira's products — the APIs, the web applications, the cloud environment they run on, and the internal tooling that keeps it all manageable. You'll be the person on the team who knows how it works.

This is a broad job. It spans backend, frontend, databases and operations. Nobody arrives knowing all of it, and we don't expect you to.

What you'll own

Two products are live. Envira Flood quantifies flood risk at address level, and Envira Agro covers agricultural risk. Both are web applications built in Python and React on a geospatial database, running in the cloud.

Concretely, you will:

• Ship features end to end — API, database, frontend, release, production

• Own our cloud environment: deployments, secrets, cost, and "why is prod down"

• Maintain our internal engineering tooling, including a desktop application with a Rust core

• Support the data team — a few analysts work in Python notebooks on satellite imagery, and part of your job is turning their analysis into jobs that run reliably on their own

You'll work alongside a frontend developer who leads our web applications and a data engineer who owns the data pipeline and database. On the backend and platform side, you'll be the owner.

We'd rather be honest about what that means: you'll have real autonomy from early on, and you'll sometimes be the one debugging production. If that sounds like the best part of the job rather than the worst, we should talk.

About Envira

Envira turns Earth observation data and AI analytics into finance-ready intelligence about climate and environmental risk. Traditional datasets look backwards. Our customers need to look forward — how exposed is this address to flooding, how will this season affect this field, what does this portfolio look like under climate stress.

Insurers, banks, agribusinesses and public agencies use our products to answer those questions. We won the EU Big Data from Space Award 2025, are a finalist for the EARSC European Start-Up Award 2026, and are backed by NextGenerationEU and Danish innovation funding.

We're a small team in Denmark. That's the reason this role has the scope it does.

How we build

AI-assisted development is the basis of all engineering work here, not an optional extra. A large share of our codebase was written in collaboration with AI coding tools, and we expect the same from you from day one. This is a hard requirement, and it's the main reason a small team can run a platform this size.

We're not asking whether you've tried an AI assistant. We're asking whether you can work at a high level with these tools — direct them precisely, read and review what comes back, throw away the parts that are wrong, and stay fully accountable for what you ship.

It also raises the bar on judgment rather than lowering it. AI makes it trivially easy to generate too much code. The engineers who do well here are the ones who use it to build the smallest thing that solves the problem, then keep it simple.

What we expect you to bring

This is a role for someone early in their career — a recent graduate, or one to three years in. We're not looking for a decade of experience, and we're not looking for a specialist. We're looking for breadth and judgment.

• Solid Python, and comfort with JavaScript/TypeScript and React

• Working SQL — you can read a query and reason about why it's slow

• You've built and run something in Docker

• Git as a daily tool, including branches and pull requests

• An understanding of how the web actually works — DNS, HTTPS, status codes, what a reverse proxy does

• Basic Linux: log into a machine, read the logs, work out why a process isn't running

• You've seen a CI pipeline run and have some idea what it should do

• Written English good enough to document your work

• You've deployed and operated something yourself — a cloud provider, a rented VPS, a home server. Which platform doesn't matter. Having been responsible for something that had to keep running does.

What we're not looking for

• A frontend developer who'd rather not touch infrastructure — half of this job is invisible in a UI demo

• An operations specialist who won't write product code — features still have to ship

• Anyone who reaches for microservices, message queues or Kubernetes to build a five-user internal page

How we hire

Three steps, and we move quickly:

1. A short screening call — a phone conversation or brief interview to assess if there is a potential fit.

2. A practical test, capped at two hours. Use AI tools — we expect you to. We grade whether it runs, whether you understood what you produced, and whether you knew what to leave out.

3. A second round - a deeper conversation where we also bring in the people you'd work with day to day.

When you apply, tell us about something you've built and run yourself — deployed and operated, not just written. That's worth more to us than a cover letter.