Engineering
Own the architecture, not just the ticket
At Staffbase, engineers make real architectural decisions on systems that millions of people rely on every day.
Real complexity, real ownership
Staffbase isn't built for one type of user. It has to work for a comms leader in a corporate office and for a machine operator who's never had a company email address — often within the same organization, on the same platform. That's a genuinely hard engineering problem: reliability at enterprise scale, security that holds up to strict compliance standards, and an experience that's simple enough for anyone to use, but still carefully crafted. Our engineers work across backend, frontend, full stack, data, AI, security, quality assurance, and technical leadership roles that help set direction across all of it. Different specialties, same standard: build it right, because real organizations run on it.
What you'll work on: Problems worth solving
Reaching people who don't have a company laptop
Millions of frontline workers — on factory floors, in warehouses, on delivery routes — need the same critical information as someone at a desk. That means QR-code logins instead of email, offline modes for spotty connections, and interfaces that work on a shared device with no IT support nearby.
Making AI trustworthy enough for the enterprise
Making one platform feel like one platform
Hear it from the team
No polished talking points — just engineers describing what they actually build.
I joined Staffbase as a working student in 2019, so I'm somewhat of a Staffbase dinosaur. Staffbase has invested in my growth ever since — through conferences, learning resources, and backing my Bachelor's thesis. My managers and colleagues have encouraged every team switch and every move into a new domain. And the relationships you build along the way? They stick around.
Sophia
Backend EngineerMy unit is Foundation, so infrastructure is our domain. What makes me proud to work here: opening a new cloud region with the Core team, finding new ways to use AI to improve automation in App and Release Management, and scaling quality with AI in the Quality team.
Luca
Director, Engineering - FoundationsOur tech stack
We invest heavily in tooling that makes engineers faster — including AI-assisted development, so more time goes into solving real problems and less into repetitive work.
Backend
Java, Kotlin, Go
Frontend
React, JavaScript, TypeScript
Data & infrastructure
MongoDB, Terraform, Docker
Testing
Selenium, Cypress
Where we work
Our engineering teams are based across Germany, with Chemnitz and Berlin as our main hubs. Chemnitz is where Staffbase started, a deliberate bet that world-class engineering doesn't require a big-city address. Hybrid and flexible work is the default here, not a perk. You won't be expected to prove your commitment by logging office hours you don't need. That doesn't mean working in isolation, though: regular hackathons bring engineering together to build and solve problems side by side, the kind of in-person energy worth showing up for.
Your questions, answered
Do I need to speak German to work in engineering at Staffbase?
Is engineering at Staffbase remote, hybrid, or office-based?
Does Staffbase sponsor visas or hire internationally for engineering roles?
How much autonomy do engineers actually have over technical decisions?
What technologies does Staffbase's engineering team use?