Senior Backend Engineer

Ориентир по рынку≈ 280 000 – 410 000 ₽наша приблизительная оценка по 31 вакансии этой роли и грейда, у работодателя вилка не указана

🏢 ОфисSeniorПолная занятость

≈ 280 000 – 410 000 ₽наша приблизительная оценка

Стоит ли откликаться

Стоит откликнуться, но спросите про деньги

Сумму в объявлении не указали. Сколько платят за похожую работу, видно в разборе. Вакансия живая, задачи расписаны.

3 из 4 в норме

Зарплата не указана: ваша цель, нижняя граница и фраза для первого созвона

Написать напрямуюВ тексте вакансии есть контакт: письмо уйдёт человеку, а не в систему подбора

Вакансия на английскомПереведёт заголовок и описание вакансии на русский

Наша компания

We're looking for someone to take real ownership of our backend architecture. Not another CRUD service, distributed systems, event-driven design, and AI running inside the backend itself rather than behind someone else's API.

Чем предстоит заниматься

Designing and owning scalable distributed systems end to end, and writing down the reasoning behind your decisions so the rest of the team can follow it, ADRs, diagrams, design reviews

Modelling messy business domains properly with DDD and turning them into services that stay clean a year later

Event-driven work is a big part of the job: Kafka or RabbitMQ, designing topics and queues, thinking through delivery guarantees and what happens when things fail

Actual implementation inside performance-critical code, model serving, inference pipelines, vector search, and the latency and cost tuning that comes with it

The rest is what you'd expect from a senior role: designing schemas that hold up as data grows, reviewing code, mentoring the people around you, and working closely with product, data and DevOps

Наши требования

Real architecture experience, microservices, modular monoliths, hexagonal/clean, and opinions about when each one is the wrong choice

A solid grasp of event-driven patterns: event sourcing, CQRS, sagas, idempotency, eventual consistency, message ordering

Production experience with Kafka or RabbitMQ is non-negotiable. Partitioning, consumer groups, retries, dead-letter queues, delivery semantics, you should have debugged these under load, not just read about them

Experience scaling systems horizontally (caching, load balancing, sharding, HA), hands-on AI implementation work (embedding pipelines, RAG, inference optimization, batching, GPU/CPU resource management), practical DDD, and strong database design, indexing, transactions and isolation levels, knowing when SQL beats NoSQL and when it doesn't

Strong proficiency in at least one strictly typed OOP language: Java, C#/.NET or C++. SOLID and design patterns should be part of how you work day to day, including knowing when a pattern is overkill