Senior Backend Engineer; Core Platform

About NEWWORK

NEWWORK is building the world’s first AI-native ERP platform: modular, FLOW-orchestrated, and people-centric. Our mission is to redefine ERP — from rigid, siloed systems of record to a dynamic System of Work that proactively assists, automates, and learns. With modules like HR+, MAP Org Chart, Expenses+, and Finance+, we deliver a unified, intelligent ERP ecosystem that runs enterprises in real time.

Role Summary

As a Backend Engineer (Core Platform), you’ll design, build, and operate the foundational services that power NEWWORK’s AI-native ERP. You will own core backend systems — our distributed, AI-driven backbone, the FLOW runtime, multi-tenant identity & access control, and the developer platform that enables rapid product delivery.

This position is for a Senior Platform Engineer
who will work remotely (within Germany or Romania) to craft and deliver on our enterprise SaaS core platform. You’ll collaborate closely with Product Engineers, AI Engineers, and Security to turn business and AI requirements into reliable, scalable platform capabilities. Strong backend skills are essential, along with experience in distributed systems, event-driven architectures, and modern permission systems.

At NEWWORK, we practice Vibe Engineering — fast, collaborative, and AI-augmented product creation. That means rapid prototyping with Cursor and other tools, coding together in “flow sessions,” and co-innovating directly with customers.

Core Responsibilities

• Platform & Backend Engineering: Design and implement core services for our FLOW runtime, orchestration, and service-to-service communication in a multi-tenant SaaS environment.
• Event-Driven Architecture: Evolve our streaming and messaging backbone (topics, contracts, schemas), ensuring resiliency, idempotency, back pressure handling, and observability (outbox, saga/CQRS, replay, dead-lettering).
• Identity, Access & Permissions: Build and operate fine-grained, organization-aware permission systems (RBAC/ABAC/ReBAC), policy evaluation, and enforcement across services and data layers; integrate with MAP Org Chart for contextual access.
• API & Data Contracts: Define versioned APIs (gRPC/REST), schema governance, and compatibility guarantees; champion contract testing and documentation.
• Reliability & Scale: Set SLOs/SLIs, capacity plans, and autoscaling; engineer for high availability, disaster recovery, and graceful degradation across regions.
• Security by Design: Own authentication/authorization flows (OIDC/OAuth2/SSO), secrets/key management, encryption in transit/at rest, audit logs, and compliance‑ready controls.
• Developer
  
  Experience:
  
  Level up CI/CD (trunk‑based, progressive delivery, canaries), ephemeral environments, internal SDKs/CLIs/templates, and paved roads that accelerate teams.
• Observability & Operations: Establish end‑to‑end tracing, metrics, and structured logs; lead incident response, post‑mortems, and continuous improvement.
• AI Enablement: Provide safe execution rails for agents (policy guardrails, rate limits, sandboxing, auditability) and streaming interfaces that keep AI in the loop, not in the way.
• Collaboration & Vibe: Work in short, AI‑assisted cycles; partner with lighthouse customers to validate platform capabilities in real‑world scenarios.

Your Profile

• Experienced Builder: You have a proven track record (approx. 5–8 years) of building software products, preferably SaaS applications.
• Backend Depth: Several years building large‑scale backend systems in a modern language (e.g., Java/Kotlin, Go, Rust, or Type Script), with strong fundamentals in concurrency, transactions, and performance.
• Distributed Systems: Hands‑on experience with event‑driven architectures and stream processing; comfortable with delivery semantics, exactly‑once/at‑least‑once trade‑offs, and patterns like saga, outbox, and CQRS.
• Permissions Expertise: Practical experience designing/operating authorization systems (RBAC/ABAC/ReBAC), policy engines, and graph‑based permissions; you think in terms of principle‑of‑least‑privilege and explainability.
• Cloud‑Native: Proficiency with containers and orchestration (e.g., Kubernetes), service meshes, and infrastructure…