> Markdown version of [/jobs/ext/3273893-fullstack-engineer-mid-level-actions-team](https://www.wearedevelopers.com/jobs/ext/3273893-fullstack-engineer-mid-level-actions-team). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Fullstack Engineer - Mid Level - Actions Team

- **Company:** Staffbase GmbH
- **Location:** Chemnitz, Germany
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Code Generation, OAuth, Time Tracking Software, TypeScript, ReactJS, Backend, Kotlin, Material UI, Cloudflare, Front End Software Development, Serverless Computing
- **Published:** September 20, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=e0087dfa20b1e0b4

## About the Role

* Strong knowledge of React and TypeScript for frontend work Java/Kotlin or Go an TypeScript experience for backend services
 * Real experience integrating third-party APIs, especially the challenging ones-inconsistent auth, partial documentation, legacy and on-prem systems
 * Deep understanding of multi-tenancy security and data isolation; you care about scope checks and preventing cross-tenant leaks
 * Good judgment about what to standardize and what to leave flexible-drawing that line in the right place is central to this role

Nice to have experience

 * You are comfortable with edge and serverless runtimes like Cloudflare Workers
 * You have built a plugin system, SDK, or developer platform before
 * Developed a design system or component library that other teams depended on
 * Real-world experience with OAuth and enterprise SSO
 * Experience treating AI code generation as a product surface, not just a personal tool

## Description

* Building a UI component library that generated apps can assemble from, turning components like payslip views and approval flows into maintained, reusable pieces instead of regenerated artifacts
 * Creating the connection layer between generated apps and customer source systems-HR platforms, time-tracking and scheduling systems, and a long tail of vendors with thin or undocumented APIs
 * Defining extension points (widgets, menus, sidebars) so plugins declare where they surface and what they connect to in a single, clean configuration
 * Designing and implementing a cross-integration authentication solution that lets customers run multiple integrations without forcing employees to log in repeatedly
 * Shipping plugins on the platform yourself, staying a consumer of what we build so we catch gaps early