We are looking for a Senior Backend Engineer to build and operate services that power Forecasting and Replenishment (FNR) systems at CP Axtra (Makro). This role is for someone who can design clean APIs and business logic, and who is also comfortable owning parts of the operational stack when needed. You will work across backend services, data flows, integrations, and reliability practices to deliver systems that are stable, observable, and easy to evolve.

Key Responsibilities

• Design, build, and maintain backend services using Java and Spring Boot for FNR applications and workflows.
• Own end-to-end delivery of features: requirements clarification, technical design, implementation, testing, release, and operational support.
• Build robust APIs for data-heavy use cases including search, filtering, pagination, and bulk-like workflows where appropriate.
• Implement and maintain asynchronous processing using Kafka (event-driven flows, consumers, retries, idempotency, and reprocessing patterns).
• Design and optimize Postgres schemas, queries, and indexes for performance and correctness at scale.
• Use Redis for caching, distributed locks, and performance improvements where appropriate.
• Implement security and access control patterns suitable for internal enterprise systems (authentication integration, role-based access).
• Improve observability and reliability: structured logging, metrics, tracing, dashboards, alerts, and incident debugging.
• Collaborate with Frontend Engineers, Data Engineers, Data Scientists, and business stakeholders to deliver end-to-end workflows.
• Contribute to platform and infrastructure work when needed (CI/CD improvements, environment setup, service configuration, production readiness checks).
  
  

Requirements

• 5+ years strong experience building production backend systems with Java and Spring Boot.
• Strong SQL skills and experience designing and optimizing Postgres-backed applications.
• Hands-on experience with Kafka or similar messaging systems, including consumer design, error handling, and operational patterns.
• Experience using Redis in backend systems (caching strategies, TTLs, invalidation, and concurrency control).
• Good understanding of distributed system fundamentals: consistency trade-offs, retries, idempotency, backpressure, and failure modes.
• Strong engineering practices: code reviews, automated testing, documentation, and disciplined release management.
• Operational mindset: ability to debug issues in production using logs/metrics/traces and drive fixes through to resolution.
• Clear communication and ownership mindset, able to work with cross-functional stakeholders.

Nice to Have

• Experience with infrastructure and operations work: containers, Kubernetes, service deployment, or cloud environments (Azure/AWS/GCP).
• Experience with CI/CD pipelines and release automation (GitLab CI, Jenkins, GitHub Actions, or similar).
• Experience with observability tooling (OpenTelemetry, Prometheus/Grafana, ELK, Datadog, or similar).
• Familiarity with schema migration tooling and practices (Liquibase/Flyway).
• Experience building internal platforms or shared libraries for consistent integration patterns.
• Experience in retail, supply chain, forecasting, replenishment, or operations-heavy domains.

What Success Looks Like

• Core FNR services are reliable, observable, and easy to evolve as business rules change.
• APIs and data flows are consistent and predictable, with clear error handling and stable contracts for consumers.
• Kafka-based processes are safe to operate with retry, reprocessing, and idempotency patterns in place.
• Performance remains strong as data volumes grow through efficient Postgres design and caching strategies.
• The team ships frequently with low regressions, and production issues are detected and resolved quickly.

Tech Environment (Indicative)

• Java, Spring Boot
• PostgreSQL
• Kafka
• Redis
• Standard tooling for CI/CD, monitoring, logging, and tracing in an enterprise environment