Software Engineer - Go/MongoDB (Remote)

Percona

Länderbedingungen prüfenVeröffentlicht am 28. Juli 2026Aktiv bestätigt am 15. Nov. 2026
Vollzeit

Job-Briefing

Aus der Anzeige gelesen und mit unserem Stellenindex abgeglichen

Bewerbbar aus
Nicht angegeben
Im Zweifel nachfragen
Arbeitsmodell
Vollständig remote
Ganzen Anzeigentext geprüft
Gehalt
Nicht angegeben
Level
Mid-Level

Die Rolle in 30 Sekunden

Aus dem Englischen

Als Software Engineer im MongoDB Tools Team entwickelst du vor allem Percona ClusterSync für MongoDB weiter und arbeitest auch an Percona Backup for MongoDB. Die Rolle richtet sich an erfahrene Go-Entwicklerinnen und -Entwickler mit Kenntnissen in MongoDB und verteilten Systemen.

Deine Aufgaben

  • Den Replikationsprozess für MongoDB-Cluster entwickeln und verbessern
  • Fehlerbehandlung und Datenkonsistenz bei Ausfällen und Neustarts sicherstellen
  • Unterstützung für Sharding, Filter und Indexverwaltung umsetzen
  • CLI, HTTP-APIs, Metriken und Logging entwickeln und pflegen
  • An Backup, Wiederherstellung und Point-in-Time-Recovery mitarbeiten
  • Go
  • MongoDB
  • Git
  • JIRA
  • Prometheus
  • golangci-lint
  • Trivy
  • S3
  • GCS
  • Azure Blob Storage

Das wird erwartet

Fachlich gefordert

  • Fundierte Go-Erfahrung in produktiven Umgebungen
  • Praxiswissen zu MongoDB Change Streams, Oplog, Resume Tokens, Replica Sets und Sharding
  • Gute Kenntnisse verteilter Systeme und Datenkonsistenz
  • Erfahrung mit Kommandozeilenwerkzeugen, HTTP-APIs, Metriken und strukturierten Logs
  • Tests schreiben sowie mit Git und Pull-Request-Workflows arbeiten können

Haltung

  • Klar und schriftlich mit externen Beitragenden kommunizieren
  • Code-Reviews konstruktiv geben und annehmen

Gut zu wissen

Bei uns seit
4. November 2026
Arbeitgeber
4 weitere offene Stellen bei Percona in unserem Index. Alle sind vollständig remote. Remote-Jobs bei Percona ansehen

Bevor du dich bewirbst

Diese Begriffe stehen wörtlich in der Anzeige. Wenn du sie beherrschst, gehören sie auch in deinen Lebenslauf.

  • concurrency
  • distributed systems
  • data consistency
  • change streams
  • resume tokens
  • replica sets
  • sharding
Passt die Stelle zu dir? Frag den KI-Berater

Automatisch erstellt von nomado24 aus der Anzeige und unserem Index. Keine Angabe des Arbeitgebers. Maßgeblich ist die Originalanzeige.

Stellenbeschreibung

MongoDB Tools Team

Team: MongoDB Tools (Product and Engineering)

Location: Remote

Projects: percona/percona-clustersync-mongodb https://github.com/percona/percona-clustersync-mongodb and percona/percona-backup-mongodb https://github.com/percona/percona-backup-mongodb

ABOUT THE TEAM

The MongoDB Tools Team builds Percona's open source operational tooling for MongoDB. Two projects sit at the center of what we do. Percona ClusterSync for MongoDB (PCSM) clones and continuously replicates data between clusters. Percona Backup for MongoDB (PBM) is a distributed, low-impact backup and restore solution for replica sets and sharded clusters. Both are written in Go, both are Apache 2.0 licensed, and both are built fully in the open.

This role sits primarily on PCSM, which is younger and moving fast, so you will have real influence over how it takes shape. You will also work across into PBM. The two tools share many hard problems: cluster topology, the oplog and change streams, consistency across shards, and performance in very large production clusters. Backup and restore experience is a real advantage here, not just a box to tick.

THE PROJECTS

  • PCSM (primary focus): initial data cloning followed by continuous change replication over MongoDB Change Streams, for both replica sets and sharded clusters. Still pre-1.0 and evolving quickly.
  • PBM (secondary): consistent backup and restore with point-in-time recovery, using oplog capture to stay consistent across replica sets and sharded clusters, with S3-compatible and filesystem storage. Driven by pbm-agent processes on each node and a pbm CLI. Mature and widely deployed in production.

WHAT YOU WILL DO

PRIMARY, ON PCSM

  • The core replication engine: initial collection cloning followed by continuous change capture over MongoDB Change Streams, with correct handling of resume tokens, ordering, and resumability after failures.
  • Correctness and fault tolerance at scale: recovering cleanly from network drops, primary elections, and restarts without losing or duplicating changes, and reasoning carefully about the delivery guarantees we can honestly promise.
  • Sharded cluster support: replicating across shards, dealing with the realities of chunk migrations and balancer activity, and keeping the target consistent.
  • Namespace filtering and automatic index management, plus the edge cases that show up with DDL, TTL, and index differences between source and target.
  • Performance and throughput: parallelizing the clone, applying backpressure, and keeping memory and connection use sane against large clusters with great change volume.
  • The CLI and HTTP API that drive and observe a sync, and the metrics and logging that let an operator trust what is happening.

ALSO ACROSS PBM

  • Consistent backup, restore, and point-in-time recovery across replica sets and sharded clusters, using physical or logical type of the backup.
  • Backup storage: integrating reliably with main cloud object storage (S3, GCS, Azure Blob Storage...) and remote filesystems, and handling the throughput and failure modes that show up at scale.
  • The pbm-agent and pbm CLI, and the control-collection state in MongoDB that coordinates them across the cluster.

SHARED ACROSS BOTH

  • Working in the open: pull requests, code review, JIRA, and the community forum.
  • Release quality: tests, packaging, and the CI and security scanning that gate every change.

WHAT HAVE YOU DONE

  • Strong Go experience in production, with real fluency in concurrency: goroutines, channels, context cancellation, worker pools, and backpressure. You have debugged a race condition that only showed up under load, and you know how you found it.
  • Solid grounding in distributed systems and data consistency. You can talk clearly about at-least-once versus exactly-once, idempotency, ordering, and what it takes to make a stateful process resumable.
  • Hands-on MongoDB knowledge: change streams, the oplog, resume tokens, replica sets, and sharding. You do not need to have built replication before, but you should understand why it is hard.
  • Comfort building and operating command-line tools and HTTP APIs, and instrumenting them with metrics and structured logs.
  • A habit of writing tests that catch real problems, and comfort working across a mixed toolchain.
  • Experience working in the open: Git and pull request workflows, giving and taking code review well, and communicating clearly in writing with contributors you have never met in person.

WHAT WILL MAKE YOU STAND OUT

  • Prior work on database internals, CDC pipelines, ETL, or data migration tooling.
  • Familiarity with the Prometheus style of metrics and observability.
  • Experience with golangci-lint, vulnerability scanning (for example Trivy), and deb and rpm packaging.
  • Background maintaining or contributing to an open source project with an external community.
  • Exposure to MongoDB sharded clusters at large …
ashbyENGINEERING

Diese Stelle wird von einer externen Quelle bereitgestellt. Die Bewerbung erfolgt auf der Website der Quelle.

Neue Remote-Jobs wie „Software Engineer“ per E-Mail

Kostenlos und nur, wenn etwas Passendes erscheint.

Anmeldung per E-Mail bestätigen, jederzeit abbestellbar. Datenschutzerklärung.

Alle Remote Developer Jobs

Passende Job-Kategorien

Nicht der richtige Job?

Treffer zu deinem Profil: zwei siehst du kostenlos, mit Nomado24 Pro bis zu 24. Pro ansehen