Senior Site Reliability Engineer for Fuse Team

Join the Fuse team — the team responsible for the item data management capabilities that connect Bloomreach Data Hub with Marketing, Search, Recommendations, and emerging Loomi agent use cases.

Fuse owns and evolves the systems behind Data Hub item collections: ingesting items data, transforming and validating it, managing data schemas and lifecycle, and distributing data reliably to downstream Bloomreach products. Item collections provide a unified source of data that can be used across all Bloomreach products.

Our current areas of focus include:

• Unified items data pipelines: processing records into structured items and keeping data synchronized with Marketing and Search destinations.
• Catalog APIs and lifecycle management: customer-facing and internal APIs, catalog creation and naming, schemas, destinations, migrations, and backward-compatible evolution.
• Scalable storage and indexing: operating and improving systems built on PostgreSQL, Bigtable, Elasticsearch, Solr.
• Reliable jobs execution: submission, queueing, execution, progress reporting, retries, cancellation, rate limiting, and operational tooling.
• Cross-product capabilities: catalog data triggers, multi-dimensional data support, custom item types, catalog data enrichment, recommendations, and semantic catalog profiles for agentic use cases.

As a Senior SRE, you will be the team’s reliability and operability leader. You will work alongside backend engineers, embedded QA, Product, and Engineering Management to make complex product-data systems observable, scalable, safe to release, and straightforward to operate.

Fuse embraces AI-assisted engineering. We expect engineers to use modern coding agents thoughtfully to accelerate investigation, development, testing, documentation, and operational work while retaining full ownership of correctness, security, and production outcomes.

Working from one of our Central European offices (Bratislava, Prague, or Brno), or remotely (Czechia, Slovakia) on a full-time basis, you’ll become a core part of the Engineering organization.

As a P3 Senior SRE at Bloomreach, you are an independent reliability professional who can turn ambiguous operational problems into measurable improvements and lead initiatives end-to-end with minimal day-to-day guidance.

Your challenge will be to make Fuse’s distributed data platform dependable across the complete data path:

customer or integration → Data Hub API → records and transformations → items → asynchronous jobs execution engine → storage and indexes → Marketing, Search, Recommendations, and Loomi consumers

• Own and improve the reliability posture of Fuse services, workers, APIs, queues, storage systems, and destination synchronization pipelines.
• Establish meaningful SLIs, SLOs, and error budgets for customer-facing APIs, asynchronous jobs, catalog data freshness, destination synchronization, and indexing.
• Build end-to-end observability across Data Hub item collections, from API request and job submission through processing, persistence, indexing, and downstream delivery.
• Ensure engineers can trace a workspace, item collection, catalog, or job across services without manually correlating disconnected logs and database records.
• Create and maintain actionable dashboards, alerts, and service health views using Grafana, Prometheus-compatible metrics, OpenTelemetry, PagerDuty, and GCP tooling.
• Detect missing, stalled, duplicated, or inconsistent processing before customers or downstream teams report it.
• Improve capacity planning and autoscaling using workload telemetry, queue depth, processing throughput, latency, memory usage, storage growth, and customer-level traffic patterns.
• Reduce noisy alerts and replace symptom-based monitoring with signals tied to customer impact.

• Improve the availability, scalability, and operability of catalog data across PostgreSQL/Cloud SQL, Bigtable, Elasticsearch, GCS, Kafka, and related storage systems.
• Support catalog placement, routing, index lifecycle, shard management, safe migration, and recovery across multiple Elasticsearch clusters.
• Develop safeguards for full replacements, delta updates, deletions, schema changes, destination changes, and catalog reindexing.
• Define and automate data-consistency checks between source records, transformed items, job state, Bigtable, Elasticsearch, and downstream destinations.
• Help establish practical platform limits and quotas for catalog size, API traffic, job concurrency, queue depth, payload size, and expensive operations.
• Partner with engineers on performance testing for large catalogs and high-throughput customer workloads.

• Own and evolve Kubernetes configuration and operational infrastructure for Fuse components.
• Improve deployment automation, progressive rollout, rollback, and validation across development and production environments.
• Make coordinated releases safer when changes span app/app, Fuse workers, Kubernetes configuration, and PostgreSQL migrations.
• Automate operational procedures that currently depend on manual commands, one-off scripts, or specialist knowledge.
• Maintain CI/CD pipelines with tests, linters, dependency management, security checks, image publication, and release verification.
• Create reusable tooling for local development, ephemeral environments, end-to-end testing, load testing, and production diagnosis.
• Ensure runbooks remain executable and are validated through exercises rather than existing only as documentation.

• Participate in and help improve the Fuse L3/on-call rotation.
• Lead incident investigation, mitigation, stakeholder communication, and follow-up for Fuse-owned systems.
• Use logs, metrics, traces, database state, queue state, and Kubernetes signals to diagnose failures across distributed workflows.
• Build safe operational tools for common support activities such as job tracing, queue inspection, rate-limit diagnosis, catalog health checks, and index recovery.
• Facilitate blameless incident reviews and ensure resulting actions address root causes rather than only immediate symptoms.
• Improve the handoff between customer support, L2, Fuse L3, Infrastructure, and dependent engineering teams.
• Reduce recurring support demand by turning incident knowledge into safeguards, automation, tests, dashboards, and clear documentation.

• Help Fuse meet Bloomreach security and compliance requirements, including ISO and SOC 2 controls.
• Enforce least-privilege access, workload identity, service-level authentication and authorization, secret rotation, encryption, and auditability.
• Protect customer isolation across workspaces, item collections, projects, accounts, databases, indexes, buckets, and asynchronous jobs.
• Ensure operational tooling and incident procedures respect production-access restrictions and PII-handling requirements.
• Partner with engineering teams to make security controls observable and testable rather than relying on undocumented assumptions.

• Participate early in the design of new Fuse capabilities so reliability, recovery, observability, limits, and operational ownership are defined before implementation.
• Review designs for failure modes, retry behavior, idempotency, backpressure, ordering, consistency, timeout handling, cancellation, and safe rollout.
• Clarify ownership boundaries and service contracts with teams including Campaigns, Data Pipeline, Integrations, Discovery, Recommendations, Infrastructure, Frontend, and QA.
• Help teams choose architectures that balance immediate delivery with long-term operability and cost.
• Coach engineers in production readiness, operational testing, debugging, and sustainable on-call practices.

Primary languages: Go, Python, SQL
APIs and application: REST APIs, Python application monolith, Go workers and services, Java Infrastructure: GCP, Kubernetes/GKE, internal Kubernetes deployment tooling
Databases and storage: PostgreSQL/Cloud SQL, Bigtable, Elasticsearch, GCS, MongoDB, Redis Messaging and coordination: Kafka, ETCD, asynchronous job queues
Observability: Grafana, Prometheus-compatible metrics, OpenTelemetry, GCP Logging and Monitoring, PagerDuty CI/CD and collaboration: GitLab, Jira, Confluence
Testing: Go and Python unit/integration tests, API and end-to-end automation, performance testing
AI-assisted engineering: Claude Code, Cursor, Copilot, Gemini CLI, or comparable tools

You do not need to have used every technology listed. You should, however, have operated distributed production systems and be comfortable learning unfamiliar components while diagnosing real incidents.

• You can show how your reliability work improved customer outcomes, engineering velocity, deployment confidence, or operational sustainability.
• You have introduced practices or tooling that changed how a team builds and operates production systems.
• You can define meaningful reliability measures and demonstrate improvement using data.

• You embrace the you build it, you run it principle and remain accountable from design through production operation.
• You can lead ambiguous reliability initiatives without requiring a fully prescribed solution.
• You take incidents from detection through mitigation, root-cause analysis, and prevention.
• You are cost-aware and use telemetry, capacity planning, and architecture—not guesswork—to manage cloud spend.

• You treat observability, limits, runbooks, rollback, idempotency, and recovery as part of the product design.
• You design for partial failure in distributed systems.
• You distinguish symptoms from root causes and prioritize systemic improvements over repeated manual intervention.
• You are comfortable working in systems where a single customer operation crosses multiple services, queues, databases, and team boundaries.

• You use metrics, logs, traces, profiling, and workload data to form and validate hypotheses.
• You can turn operational telemetry into actionable feedback for developers and Product.
• You are comfortable analyzing throughput, latency, saturation, error rates, queue behavior, database performance, and storage growth.

• Strong hands-on experience operating services on Kubernetes in a major cloud environment, ideally GCP.
• Strong experience with observability and incident diagnosis for distributed systems.
• Experience with Go or Python; practical ability in both is a strong advantage.
• Experience operating at least one relational database, preferably PostgreSQL or Cloud SQL.
• Experience with one or more large-scale data or indexing systems such as Bigtable, Elasticsearch/OpenSearch, Kafka, GCS, or comparable technologies.
• Experience designing or operating asynchronous job-processing systems, queues, workers, and retry mechanisms.
• Experience with CI/CD, Infrastructure as Code, deployment automation, and safe database migrations.
• Understanding of API reliability, rate limiting, backpressure, idempotency, and multi-tenant isolation.
• Comfort participating in an on-call rotation and responding to production incidents.
• Ability to work effectively in a distributed, remote-first team.
• Practical use of AI coding tools to accelerate investigation and implementation without outsourcing engineering judgment.

• Experience operating catalog, product-data, ingestion, transformation, or indexing platforms.
• Experience with large Elasticsearch/OpenSearch clusters, shard management, index lifecycle, routing, or reindexing.
• Experience with Bigtable or another distributed wide-column database.
• Experience designing consistency validation across multiple storage or indexing systems.
• Experience with customer-facing data APIs, high-volume bulk ingestion, or full and incremental synchronization.
• Familiarity with product catalogs used by search, recommendations, marketing, or personalization systems.
• Experience coordinating reliability improvements across several engineering teams.
• Experience working in an environment with ISO, SOC 2, data-isolation, retention, and audit requirements.

• Ownership and accountability — you stay with a problem until it is understood, resolved, and less likely to recur.
• Systematic thinking — you identify patterns and root causes instead of repeatedly treating symptoms.
• Pragmatism — you balance reliability, delivery speed, complexity, and cost.
• Clear communication — you explain technical risks and trade-offs to engineers, Product, Support, and other stakeholders.
• Collaborative leadership — you raise the team’s operational capability rather than becoming the only person who can operate the system.
• Customer awareness — you connect technical reliability to catalog freshness, data correctness, product availability, and customer trust.
• Continuous improvement — you are comfortable revisiting assumptions and improving systems incrementally.
• Remote-first effectiveness — you communicate asynchronously, document decisions, and make progress across time zones.

• Get to know the Fuse team, its engineers, embedded QA, Product partner, Engineering Manager, and key cross-team collaborators.
• Complete Bloomreach engineering onboarding and set up your development environments.
• Understand the primary Fuse domains: Data Hub item collections, Catalogs, job execution and reporting, APIs, storage, indexing, and destinations.
• Map the core request flows and data paths through Fuse owned and downstream products.
• Review existing dashboards, alerts, L3 procedures, release practices, recent incidents, and known operational risks.
• Shadow the L3/on-call rotation and learn the team’s production-access and escalation procedures.

• Begin contributing to the Fuse L3/on-call rotation with support from experienced team members.
• Resolve production or pre-production issues using logs, metrics, job state, database state, and distributed traces.
• Deliver your first meaningful reliability improvement.
• Define or improve SLIs and SLOs for at least one critical Fuse workflow.
• Contribute to the production-readiness review of an active Fuse project.

• Own the reliability posture of at least one major Fuse domain end-to-end.
• Drive measurable improvement in one or more of:
  • Availability or successful job completion.
  • Overall data freshness.
  • Mean time to detect and recover.
  • Alert signal-to-noise ratio.
  • Deployment and migration safety.
  • Processing throughput or infrastructure efficiency.
  • L3 support effort and recurring incident volume.
• Lead an incident review or reliability initiative involving multiple teams.
• Establish reusable operational patterns that Fuse engineers can apply to new services and features.
• Be a trusted partner in architecture discussions, ensuring new catalog capabilities are observable, scalable, recoverable, secure, and on-call friendly from day one.

#LI-KP1