Blablacar

Site Reliability Engineer

Paris, FranceFull timePosted 12 days ago
Apply on Blablacar →

Sign into see who you know at Blablacar.

About BlaBlaCar

BlaBlaCar is the world’s leading community-based travel app enabling 27 million members a year to carpool or travel by bus in 21 countries. Our team of 800 employees counts over 50 nationalities and is spread across our 5 global offices, 30% working fully remotely.

Your Mission
By joining our Foundations department, you will be working alongside talented individuals grouped in small agile teams that each have strong ownership on their piece of these goals. Foundations is composed of seven teams which “provide consistent, easy to use, infrastructures, services, and expertise to support BlaBlaCar’s growth and evolution”. 
The Site Reliability Engineering team (SRE) is responsible to provide best in class Observability, Alerting and Incident management tools and processes to service teams. As an enabling team, we help BlaBlacar engineers to efficiently improve their service reliability. Empowering developers and bringing them our reliability expertise are at the core of our daily work. 
Technical stack:
Core Infrastructure: Kubernetes, Google Cloud Platform
GitOps/Delivery: GitHub, Terraform, Flux, Helm, Jenkins
Observability/Incident Management: Datadog, Opentelemetry, Grafana IRM,
In house Synthetic Tests platform: Playwright, Qualcium, SauceLabs
Languages: Go / Python for Tooling, Typescripts/JS for the testing platform
Your responsibilities 
Support software engineers by creating, maintaining, and improving observability and alerting tools and frameworks. You embrace the use of AI, leveraging agentic to eliminate toil and streamline your daily tasks
Own the Service Level Objectives (SLOs) framework, assist in the design and maintenance of indicators (SLI) and objectives to ensure service reliability.
Owning the incident management process by defining best practices, standards, and ensuring continuous improvement through post-mortems and chaos engineering. While developers handle incidents within their scope, you could step in as Incident Comma...