Senior Full Stack Software Engineer

FRYTE is redefining how electric logistics connects with the energy grid.

From our base in Munich, we're building the intelligence layer that powers the transition from diesel to electric freight.

Our SaaS platform enables fleet operators, dispatchers, and charge point operators to plan, optimize, and monetize electric truck charging — aligning fleet efficiency with grid stability.

Our vision:
replace big oil with smart electrons.

Our mission:
get e-trucks on the road – faster, smarter, more efficiently.

This is a deep technical role for someone who wants to go deep, not climb an org chart.

You’ll be the technical anchor of our backend — the engineer who sets the quality bar, owns the hardest design decisions, and quietly makes the whole system more robust and scalable. The person the rest of the team brings their thorny problems to, and who's genuinely happy to dig in.

We're explicit about this:
this is an IC role with a Staff Engineer trajectory. No management obligation, ever. Your influence comes through architecture, code, and mentorship — not headcount. If your idea of growth is becoming the person whose judgement defines how a system is built, this is for you.

One note on the title, because it travels badly between companies: we don't measure seniority in years, or in features shipped inside one familiar framework. We measure it in scope of ownership — systems you were responsible for when they broke, designs you had to revisit once reality showed up, assumptions that scale quietly humbled. Most good engineers learn that lesson several times, usually the annoying way.

We'd rather hire someone who already has.

You’ll work directly with the founders (former TUM researchers with deep energy + logistics expertise) on the integration layer that makes electric freight actually work: multiple domains, real production traffic.

• Own the architecture and production-hardening of our backend as we scale from seed onward
• Design and version stable, multi-domain APIs (multiple integrations, real-time data streams)
• Build the observability backbone — logging, tracing, metrics — so we operate with confidence, not hope
• Raise the bar across the codebase: patterns, ADRs, reviews, and the unglamorous work that keeps things maintainable
• Mentor and unblock the team through code and conversation — lift everyone's ceiling
• Move fluidly into Dev Ops, SRE, or frontend when that's what the problem needs

Backend: Python, FastAPI, Postgres, PostGIS

Frontend: React, Type Script

Infra: AWS

• A track record of owning production backend systems in Python (FastAPI) on SQL/Postgres — not just building in them. Carrying something you designed through deployment, failure, and the redesign that followed. (That depth usually takes 5+ years to earn; the years themselves aren't the point.)
• Strong backend and system design instincts — you reason about boundaries, failure modes, and versioning before you write the first line
• Architectural depth, ideally in charging, fintech, scheduling, or similarly stateful, integration-heavy domains
• A habit of operating across boundaries — backend, infra, the occasional frontend fix, sometimes code you had no business touching — because the problem never cared what your job description said
• A teaching reflex: you have an answer to most things and you're happy to share it

Git Hub Actions, observability tooling (tracing/logging/metrics), SRE practices, and a track record of maintaining or contributing to OSS —
because you find it fun
.

Most of all: we hire for trajectory and attitude. We're looking for the humble, curious expert who's a mentor and coach by instinct — not because it's in the job description.

• Impact that matters – every system you harden helps…