Backend engineer for booking and payments

Fresha; Greater London; On-site; GBP 90,000 - 130,000; Full time

Job summary

Fresha — ведущая платформа для индустрии красоты и благополучия, использующая ИИ для оптимизации операций. Ваша роль — владеть бэкэнд-функциями от идеи до релиза, выпускать изменения почти каждый день и работать над сервисами разных repos.

Ожидается опыт работы в проде не менее 5 лет, знание архитектур на основе событий и умение думать о надёжности и масштабируемости. В команде поддерживается культура внедрения новых практик и инструментов.

Qualifications

• 5+ лет опыта разработки и эксплуатации бэкенд-сервисов в продакшене.
• Умение проектировать устойчивые к сбоям системы и обрабатывать повторные запросы.
• Опыт работы с распределёнными системами и обработкой событий.
• Опыт работы с архитектурами, основанными на асинхронных событиях, Kafka или аналоги.

Responsibilities

• Разрабатывать фичи от дизайна до развертывания и последующего мониторинга.
• Не реже чем ежедневно выпускать изменения behind feature flag.
• Работать над несколькими сервисами и координировать релизы.
• Поддерживать качество и производительность системы, исправлять узкие места.

Skills

Backend разработка

Distributed systems

Kafka

Flag-based rollout

Производительность

Job description

Описание

Fresha is the leading AI-powered operating system for the global beauty and wellness industry, giving businesses everything they need to run smarter, grow faster and build stronger client relationships.

Задачи

Own features end to end: Design it, build it, test it, ship it, and look after it once it's live. Ship most days: Your change goes out behind a feature flag, usually the same day you write it. CI/CD handles the rollout. You watch the dashboards and roll back if it looks wrong. Work across services: Most features touch more than one repo. You'll plan and ship changes across several services at once. Work with the rest of the team: Product, Design, Frontend, Infrastructure and Mobile, from the first conversation through to release. Keep things healthy: Find the bottlenecks, fix the bugs, and keep an eye on performance and quality. Have a say in how we build: Our architecture and our engineering practices aren't fixed. We expect senior engineers to push on both.

Требования

• Experience: 5+ years building and running backend services in production.
• Correctness: You think about what happens when a request arrives twice, a downstream call times out halfway through, or two things update the same record at once. You design for it rather than finding out later.
• Distributed systems: You've built and run services at scale, and you know how they fail.
• Event-driven architecture: You've designed systems around asynchronous events, not just request and response. Kafka or equivalent.
• Comfortable close to production: You're at ease shipping behind flags and watching a change land. You know what to instrument before a rollout and what to watch afterwards.
• AI in your workflow: You use AI coding tools day to day and have a clear view of where they help and where they don't. You're happy building your own workflow rather than waiting for one, and you review what comes back before it ships.
• Languages: Strong in at least one backend language. We don't expect Ruby or Elixir on day one, but we do expect you to pick things up fast.
• Pragmatic: You care about the right tool for the job more than any particular stack, and you've worked in more than one style of language.
• Curious: You like getting deep into a domain, and you're willing to get into the weeds.
• Будет плюсом: Willing to broaden: Frontend or native mobile experience is a bonus rather than a requirement, but we do expect engineers to pick up what a piece of work needs.

Условия

Scale: Around 1 million bookings a day across 120 countries, and the payments that go with them, running on a platform we're breaking out of its monoliths while it serves traffic. Speed: We release daily, 500+ deploys a day, with not much standing between your branch and your users. Ownership: The tooling, data and permissions to run what you build, and a say in the technical direction of your area. Room to broaden: When you move into the frontend or mobile side, you get the time and support to learn it rather than being thrown at it.