Mid-Level Backend Engineer

For most people, buying or selling a car is one of the biggest financial decisions they make. Karnameh has several business lines that help them through it, all running on a platform of multiple microservices. Our backend engineers build that platform and keep it running, working closely with the product and business teams who depend on it.

The engineers who do well here are curious, thoughtful, and self-driven. They look for the problems that matter most, whether that's a new service or an old bug, rather than waiting to be told what to do. They plan carefully, and they change the plan when new information shows it's wrong.

The kind of work you'll do

• Services and APIs. Designing, building and evolving services, the contracts between them and the data that flows through them.
• Third-party integrations. Payment and financial providers, messaging services and partners. You don't control the other side, so timeouts, retries, duplicate or missing callbacks and reconciliation are the real work.
• Automation and AI. Internal tools for our operations and finance teams, automating work that's still done by hand, and LLM-powered features and agents.
• Reliability. Monitoring, debugging in production, performance, and following an incident through to the change that stops it from happening again.
• Data. Data models, analytical queries, pipelines and data quality.
• Evolving what already runs. Refactoring, upgrades and paying down technical debt, which is a large share of the job.

What we look for

• Experience. Usually two years of backend development. You've built and maintained services in production, you can track down a problem from logs and metrics, and you take well-defined work from design to release as part of a team.
• Solid foundations. Clean, well-structured Python; REST APIs, ideally with Django and DRF; SQL and relational databases; Git, Linux, and enough English to read technical documentation easily.
• Understanding before building. You make sure you've understood the problem, and you ask the questions whose answers change the design.
• Correctness. You look for the case that breaks your work before your users find it, test what you change, measure before you optimise, and check that it really worked once it's live.
• AI with judgment. You use AI tools, coding agents included, every day, and you know where they go wrong. Whoever typed the code, you understand every line you merge.
• Teamwork and communication. You share what you know, give and take code review with care, and ask for help early when you're stuck. You explain your thinking clearly, in writing and in conversation, to engineers and non-engineers alike.
• Eager to learn. You learn fast, you welcome feedback, and you want to take on larger design work over time.

Nice to have

• Experience with high-scale systems and products used by many real customers.
• Hands-on experience with transactions, idempotency or concurrency problems.
• Event-driven systems, message brokers, asynchronous task processing and caching.
• Search engines, NoSQL or analytical databases, data pipelines, or machine learning in production.
• Docker and Kubernetes.
• Shipping something real with LLMs: prompt design, evaluation and improving output quality.

Before you apply

• Location. Tehran. We work mostly on-site, with the option of working remotely on some days, so this role is for people who live in or near Tehran and are happy to work from the office.
• Level. This is the mid-level role. If you've already led projects from an unclear need to production and made the main design decisions yourself, our Senior Backend Engineer role is the better fit. Go by what you've actually done, not by your current title.

If most of this sounds like you, apply. You don't need to know every tool on day one; you'll learn the rest alongside experienced engineers.