Senior Backend Engineer (Python/Django)

Miare runs the software behind delivery fleets. Tens of thousands of deliveries a day, thousands of couriers on the road at any moment — dispatched, tracked, priced, and settled in real time. When our matching logic is slow, someone's food gets cold.

We started this Django codebase in 2016. Ten years later it's over a thousand tables, a Postgres past a terabyte doing thousands of transactions a second, millions of API requests a day, and a Go service holding every active courier's live connection. Some of it is beautiful. Some of it needs someone with taste and patience. We're honest about which is which.

We run all of it ourselves — our own Kubernetes, our own Postgres on our own hardware. No managed cloud doing the hard parts for us, which means more to learn and nowhere to hide.

What you'll do

• Own services through their whole life — design, build, deploy, and keep them healthy in production.
• Work on the parts that are actually hard: high-throughput dispatch, spatial queries, real-time tracking, financial settlement, async pipelines.
• Chase down real production problems across Django, PostgreSQL, and Kubernetes.
• Make the system faster and more observable, and make us quicker at shipping.
• Shape architecture, review code, and push back when something's wrong.

What we're looking for

Our stack is Python/Django at the core, Go for real-time services, PostgreSQL/PostGIS, and Kubernetes. You don't need all of it.

• Around 5 years building backend systems that run in production, a solid share of it in Python/Django and DRF.
• Real PostgreSQL depth — schema design, query optimization, and knowing why a query is slow, not just that it is.
• Automated testing as a habit rather than a chore.
• You've picked up an unfamiliar stack on the job before, and can tell us about a time you did.
• Judgment about the tradeoff between doing it right and shipping it this week.
• If your depth is in Go or infrastructure rather than Django, and moving toward Django appeals to you — apply anyway and say so. We'll read it properly.

We'll teach you the rest.

Any of these you already have is a bonus. None is expected.

• Go — a large part of our real-time stack is Go, and you'll work in it.
• Kubernetes, CI/CD, infrastructure-as-code, observability. You'll deploy and operate what you build. If you've never touched a cluster, we'll teach you.
• Distributed systems and async processing (Celery, Kafka).
• PostGIS and spatial data.

Where this goes

We hire backend engineers, but we grow software engineers. Over time you'll be able to take a feature all the way across — frontend, mobile, or infrastructure — as far as you want to take it. If breadth appeals to you, there's room. If you'd rather go deep on backend, that works too.

This isn't for everyone

We're a backend team of six. There's no separate infrastructure team that hands you a deployed environment, no QA team that catches your bugs, and no ticket queue between you and the problem. You'll have production access on your first week and you'll be responsible for what you put there. If you want specialized roles and clear handoffs, you'll be happier somewhere else.