Senior Backend Developer

Founded in 2000, Akakçe is Turkey’s leading price comparison platform, helping over 40 million users find the best deals every month. Our commitment to cutting-edge technology, data-driven insights, and continuous innovation makes us a key player in the e-commerce ecosystem.

About the Role

At Akakçe, we operate web and mobile platforms used by millions of users. Behind them sit backend systems that handle product and price data, merchant integrations, and search and listing traffic at scale — and that have to stay correct and available while doing it.

We are looking for Senior Backend Engineers who can design, build, improve, and operate those systems. Experience with our stack is useful, but engineering judgment, debugging ability, and depth of problem solving matter far more to us than which technologies appear on your CV.

What You Will Do

• Understand product and business problems, then design practical technical solutions.
• Build and improve backend services, APIs, data flows, and integrations.
• Work on systems that must stay reliable under high and uneven traffic.
• Improve the performance, scalability, maintainability, and observability of systems already in production.
• Investigate production issues, identify root causes, and implement fixes that hold.
• Collaborate with product, frontend, mobile, data, and infrastructure teams.
• Contribute to technical design discussions and code reviews.
• Reduce unnecessary complexity in existing systems.
• Own features and systems well beyond their first release.

What We Look For

We hire for engineering ability, not for a list of technologies. We would like to talk to you if:

• You can explain a system you designed, and what you gave up by designing it that way.
• You have diagnosed a production incident from evidence — logs, metrics, traces — rather than by guessing.
• You can explain why a query became slow and what you actually did about it, beyond adding an index.
• You have improved a system that was already running, step by step, without rewriting it.
• You can describe what happens when the same message is delivered twice, and how you designed for it.
• You can point to complexity you removed, and say what it was costing to keep.
• You write code another engineer can read, change, and test six months from now.
• You explain your reasoning clearly, and you change your mind when the evidence says you should.

Current Technologies We Use

Our backend runs on .NET, with relational databases and message queues. Depth in a comparable stack counts for as much as an exact match:

• .NET / .NET Core, or another mature backend platform (JVM, Go, Node.js, Python)
• Relational databases and SQL
• Message queues and asynchronous processing
• Git and CI/CD pipelines.

Nice to Have

• Experience with high-traffic consumer platforms.
• Experience with distributed systems, caching, background jobs, and performance work.
• Experience improving legacy systems without resorting to a rewrite.
• Work — professional, personal, or open source — that you can walk us through and explain in depth.

How We Interview

Our process is built around fundamentals and problem solving rather than framework trivia. Expect a practical coding exercise and a technical conversation about design decisions, trade-offs, failure modes, and how you debug real problems. We will ask you to explain your reasoning, and we will follow up on your answers.

"Your personal data gathered in your application to this job advertisement will be processed in automated systems to manage job application procedures by Akakçe Bilgi Teknolojileri Sanayi ve Ticaret A. Ş. ("Akakçe") according to the Law No. 6698 on the Protection of Personal Data ("KVKK") and related regulations."