Mid/Senior Java Developer, Brazil

We're assembling a small team to take over a set of backend services that power a direct-to-consumer commerce platform of a global beverage/consumer goods company. The platform is being separated from the B2B ecosystem it was born in. As part of that separation, a group of critical services (orders, pricing, payments, and promotions/combos) is being forked as-is into the new environment, and they need a team that owns them.

The mission for this phase is clear: keep the lights on. Absorb these services fast, keep them stable through the highest-demand period of the year, and leave them better documented and tested than we found them. The client's architecture team is designing the target architecture in parallel. That work is not in this team's scope today, but it is the natural next step.

This is not greenfield. You'll inherit real services with real history, learn them from the people who built them.

What You'll Be Doing

• Own a portfolio of forked backend services (mostly Java/Spring Boot): bug fixes, small changes, and day-to-day stability.

• Drive knowledge transfer with the original team through shadowing sessions. Ask the right questions, map dependencies, and turn tacit knowledge into something written.

• Build service context documentation in three layers (business rules, application behavior, operations) following the client's template. This feeds both the human team and the AI-assisted development model the client already runs in production.

• Support incidents in a production environment that runs 24/7 across global markets, including critical flows like orders and payments.

• Work within an Azure-based infrastructure (Azure DevOps, pipelines, and subscriptions), contributing to the duplication and adaptation of CI/CD pipelines for the new environment

• Participate in the team's shift toward better engineering practices: adopting GitFlow, strengthening test coverage, and gradually incorporating quality gates - without breaking what already works

• Help classify services by technical criticality and flag systemic risks early, such as hidden dependencies, shared databases/queues, and fragile integrations.

Requirements (Must Have):

• Hands-on use of AI-assisted development tools (coding agents, assistants) in real work, with judgment about when to trust and when to verify.

• Java (backend, production experience) - this is non-negotiable

• Spring Boot - the core framework across the service landscape

• REST API design and integration

• Azure DevOps - familiarity with pipelines, repos, and environments

• Non relational (CosmosDB for MongoDB) and relational databases (PostgreSQL)

• Testing - JUnit for unit tests; familiarity with E2E or integration testing

• Incident response mindset - ability to diagnose, triage, and resolve issues in complex distributed systems under pressure

• English - for reading documentation, participating in cross-team calls, and written communication

• Hands-on experience operating and debugging distributed microservices in production: logs, tracing, triage under pressure.

• Clear, proactive communication. You'll extract knowledge from a team that is moving on, so you must be able to drive conversations, write things down, and escalate early.

• Comfort working on inherited/legacy code with a "understand first, change carefully" mindset.

Nice to Have Skills:

• Experience with microservices at scale - especially the operational realities of running and debugging many services in production

• Azure cloud services beyond DevOps (Service Bus, Blob Storage, Functions, etc.)

• Familiarity with DDD (Domain-Driven Design) concepts and service boundary thinking

• Go - a secondary language used in some newer services

• Understanding of internationalization and global commerce (multi-currency, multi-region systems)

• Performance optimization experience in high-throughput environments

What Makes This Role Different:

You'll be joining at a moment that requires adaptability over idealism - the goal isn't to redesign what's working, it's to understand it deeply, keep it running, and incrementally move it toward a cleaner state. The team values engineers who can hold two things at once: operational discipline today and architectural vision for tomorrow.

If you've ever had to inherit complex legacy systems, win trust through reliability, and earn the space to improve things over time - this will feel familiar in the best way.

Seniority Levels:

We're open to Mid-Level and Senior profiles. Both levels are hands-on: everyone on this team writes code, fixes bugs, and takes on-call shifts. The difference is scope and autonomy.

• Mid-Level: Delivers fixes and changes independently on well-understood services, with guidance on the more complex ones. Strong Java/Spring Boot fundamentals and solid microservices concepts. Takes part in incident response alongside senior engineers. Learns a complex domain fast through shadowing and documentation, and writes down what they learn.

• Senior: Delivers the hardest changes and fixes, especially on critical flows such as orders, pricing and payments. Leads incident resolution end to end, from diagnosis to fix in production. Drives knowledge transfer sessions with the outgoing team and turns what comes out of them into documentation and service context. Spots systemic risks such as hidden dependencies, shared resources and fragile integrations. Sets the quality bar for the team through code reviews, tests and standards, mostly by example.

  #LI-THAI23