Staff Backend Engineer

## About the Role Build the backend services that make Federis a reliable system of record for governance, policy, audit, workflow, connectors, tenants, deployments, and enterprise control-plane operations. ## Key Responsibilities - Design and implement APIs, domain services, database schemas, background jobs, event flows, and integration contracts for the core control plane. - Own critical services for tenants, workspaces, policy decisions, audit trails, evidence capture, connector lifecycle, and deployment metadata. - Build adapter-based integrations that keep external systems replaceable and separately deployable. - Ensure ACID behavior where needed, strong authorization checks, idempotent operations, observable workflows, and clear failure handling. - Write unit, integration, contract, and migration tests that support enterprise release confidence. - Mentor engineers through design review, code review, production debugging, and operational excellence practices. ## Required Experience - 7+ years building production backend systems in languages such as Go, Java, Kotlin, TypeScript, Python, or Rust. - Strong understanding of relational databases, transactions, API design, async jobs, distributed tracing, authorization, and schema evolution. - Experience with enterprise SaaS or infrastructure products where reliability, auditability, and security are core product qualities. - Ability to own ambiguous platform problems from design through operation and documentation. - Habit of writing maintainable code, clear tests, migration plans, and operational dashboards. ## Useful Differentiators - Experience with PostgreSQL, Kafka-compatible patterns, OpenTelemetry, OPA, Kubernetes operators, or workflow orchestration. - Prior work on governance, security, compliance, identity, data platforms, MLOps, or developer platforms. - Experience building SDKs, connector frameworks, or plugin systems. ## First 90 Days - Own at least one core control-plane domain from design review through production-grade implementation. - Establish backend coding patterns for APIs, authorization checks, audit events, migrations, and contract tests. - Reduce architectural uncertainty in a critical customer-facing workflow or integration path. ## Success Scorecard - Services are testable, observable, secure by default, and documented enough for other teams to extend. - Customer-facing workflows meet expected latency, reliability, and auditability targets. - Adapters and provider contracts remain clean instead of leaking vendor-specific assumptions into the core. - Production incidents and defects trend down as ownership matures. ## About the Company Federis is a system of record for governance, policy, audit, workflow, connectors, tenants, deployments, and enterprise control-plane operations.