Senior Software Engineer (Java Microservices & Cloud-Native Platforms)

About the role We're hiring a senior, hands-on engineer who turns high-level concepts and architectural direction into production-grade software, with a high degree of autonomy. You will own microservices end to end: domain modeling, API design, implementation, and deployment and operation on Kubernetes. The ideal candidate thinks like an architect but codes like a craftsman. You are comfortable debating trade-offs at the whiteboard, and just as comfortable turning those decisions into clean, testable, Job Responsibilities Design and build microservices. Own services end to end with Java and Spring Boot: domain boundaries, API contracts (REST, gRPC, event-driven), data models and integration patterns. Turn architecture into implementation. Take high-level concepts and design decisions and turn them into concrete designs, working code and incremental delivery plans, with minimal hand-holding. Contribute to architecture. Evaluate alternatives, document decisions (ADRs), flag risks early, and push back constructively when a design won't hold up in production. Own the DevOps lifecycle. Containerize, deploy and operate services on Kubernetes. Build and maintain CI/CD pipelines, Helm charts or manifests, and infrastructure-as-code. Engineer for production. Design for scalability, resilience and observability: metrics, tracing, structured logging, health checks, graceful degradation and capacity planning. Raise the engineering bar. Lead by example through thorough code reviews, meaningful automated tests and pragmatic refactoring. Mentor mid-level engineers. Work across boundaries. Collaborate with product owners, architects, QA and other teams to clarify

, align on interfaces and deliver predictably. Job Requirements Nice to have: Experience with a major cloud provider (AWS, Azure or GCP) and managed Kubernetes (EKS, AKS, GKE). Observability tooling: Prometheus, Grafana, OpenTelemetry, ELK or Loki. Infrastructure-as-code (Terraform, Pulumi) and GitOps tools (Argo CD, Flux). Service mesh (Istio, Linkerd) and API gateways. What Lenovo Can Offer You Compensation & Rewards Performance-based salary reviews and annual bonuses Meal tickets, service anniversary awards, and referral bonuses Employee share purchase program Health & Well-being Fully covered private medical insurance Annual well-being allowance for sports, training, relaxation, and therapy, and on-site chair massage Life & accident insurance with extra medical coverage Employee Assistance Program Training & Development Technical Ladder & Sales Excellence programs Individual Career Development Plans with mentoring Bookster subscription for continuous learning Time Away 21–28 vacation days depending on tenure Sick days and extra paid leave for public holidays on weekends Additional paid leave for employees with children Messaging and event-driven systems (Kafka, RabbitMQ or similar) and patterns such as sagas, outbox, CQRS, circuit breakers and retries. Relational and NoSQL databases (e.g. PostgreSQL, MongoDB, Redis), including schema design and query optimization. Strong testing discipline: unit, integration (Testcontainers), contract and performance testing12+ years of professional software development, with deep Java expertise (Java 17+): concurrency, memory model, JVM tuning and performance profiling. Extensive hands-on experience with Spring Framework and Spring Boot: Spring Web/WebFlux, Spring Data, Spring Security, Spring Cloud, and DI and configuration internals. A proven record designing and delivering microservice architectures in production: service decomposition, API versioning, distributed data management, idempotency and failure handling. Solid Kubernetes experience: Deployments, Services, Ingress, ConfigMaps and Secrets, autoscaling, resource limits, rolling updates, and troubleshooting live workloads. Practical DevOps skills: Docker, CI/CD (GitLab CI, GitHub Actions, Jenkins or similar), Helm or Kustomize, and GitOps practices. Strong grounding in software design: SOLID, DDD, design patterns, clean or hexagonal architecture, and knowing when not to apply them.