Staff Backend Engineer (Unit Intercity)

Technical owner of the entire unit's backend: holds the end-to-end picture of services, gates teams' key decisions, personally tackles the hardest problems, and proactively raises the bar. 2026 focus: product consolidation and the AI-First / Spec-First shift.

Own the unit's backend as a whole - coherence, reliability, and evolution of all services, not just your team's.
Validate and approve teams' technical decisions (ADRs/RFCs, API contracts); act as the final backend gate.
Proactively propose platform-level solutions where teams see only a local fix; turn recurring incidents into systemic fixes.
Audit the backend (tech debt, performance, reliability, security) and drive the improvement plan to production.
Write production code in the most critical areas
Take the hardest bugs and incidents; see post-mortem action items through to implementation.
Mentor seniors and tech leads, set standards, and drive Spec-First and CLAUDE.md/AGENTS.md quality.

Designing distributed high-load systems - microservices, event-driven (Kafka), API design; strong systems thinking and coupling/cohesion judgment; ADRs and trade-off analysis.
Expert in at least one production language Go; databases (SQL/NoSQL), data modeling, caching (Redis), concurrency under load.
Observability (Prometheus/Grafana), SRE practices, fault tolerance, deployment strategies (canary, feature flags).
OWASP, authn/authz; antifraud as a backend problem - rate limiting, attestation, request signing, mTLS, geo-spoofing protection.
Latency, local regulation, data privacy (GDPR/LGPD).
Hands-on AI-assisted development (Claude Code) and a Spec-First mindset.