Software Engineer Operations, Order Management Team - eMAG

We’re always looking for the ones truly passionate about their work. If you are amongst them, you can rest assured there is a place for you in eMAG. We’ve grown very fast and are determined to keep doing so. What brought us here is our desire for continuous evolution and practical results.

More than 6000 colleagues are part of eMAG Teams . We strongly believe in people's development and therefore every year we invest more and more energy and resources to remain an organization that is constantly learning. We want to ensure that you’ll have the most talented colleagues and the proper environment to grow and achieve great results, to become what you desire on a personal and professional level. Join us, grow faster !

Software Engineer (Operations, Order Management Team)

We own a set of business-critical applications that have been running in production for years - written in PHP, carrying real revenue, and not going anywhere overnight. At the same time, everything new we build goes out in Go: smaller services, clearer boundaries, better performance characteristics under load. You'll be trusted to make architectural calls on the new Go services, decide how and in what order the legacy estate gets modernized, and set the standard for how the team works with agentic tooling. You'll also be a reference point for the engineers around you - through review, through mentoring, and through the patterns you leave behind. What makes this role different is how the work gets done. We treat agentic coding tools as the default way we write software, not as an occasional autocomplete. Most code in this team is produced through agents; the engineering skill sits in framing the problem, constraining the agent, and verifying the result. If you enjoy moving fast without losing control of what ships, this is the seat.

What you’ll have to do:

• Design and build new services in Go - API design, data modelling, concurrency, observability, and the operational side of running them;
• Keep legacy PHP applications healthy and shippable - understand undocumented behaviour, add tests around risky areas, refactor incrementally, and pay down debt without breaking what works;
• Carve functionality out of the PHP estate and move it to Go safely - strangler-fig migrations, parity testing between old and new paths, controlled cutovers with a real rollback story;
• Own the technical direction for your area - sequence modernisation work by risk and value, make the trade-offs explicit, and document the decisions;
• Deliver the majority of your code through agentic coding tools (Claude Code, Cursor, Copilot and whatever comes next) - writing precise specs and task decompositions, building the context and guardrails agents need, and reviewing generated code with the same rigour as your own;