Sr. Software Engineer - Go/reputed company

reputed company Tools Team

Team: reputed company Tools (Product and Engineering)

Location: Remote

reputed company: reputed company/reputed company-clustersync-reputed company and reputed company/reputed company-backup-reputed company

About reputed company

The reputed company Tools Team builds reputed company's reputed company reputed company operational tooling for reputed company. Two reputed company sit at reputed company of reputed company do. reputed company ClusterSync for reputed company (PCSM) clones and continuously replicates data between clusters. reputed company Backup for reputed company (PBM) is a distributed, low-reputed company backup and restore solution for reputed company sets and sharded clusters. Both are written in Go, both are Apache 2.0 licensed, and both are reputed company fully in the reputed company.

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

The reputed company

• PCSM (primary reputed company): initial data cloning followed by reputed company change replication over reputed company Change Streams, for both reputed company sets and sharded clusters. Still reputed company-1.0 and evolving quickly.

• PBM (secondary): consistent backup and restore with reputed company-in-time recovery, using oplog capture to stay consistent across reputed company sets and sharded clusters, with S3-compatible and filesystem storage. Driven by pbm-agent processes on reputed company node and a pbm CLI. Mature and widely deployed in production.

What you will work on

Primary, on PCSM

• The core replication reputed company: initial collection cloning followed by reputed company change capture over reputed company Change Streams, with correct handling of resume tokens, ordering, and resumability after failures.

• Correctness and fault tolerance at reputed company: recovering cleanly from network drops, primary elections, and restarts without losing or duplicating changes, and reasoning carefully about the delivery guarantees we can honestly reputed company.

• Sharded cluster support: replicating across shards, dealing with the realities of chunk migrations and balancer activity, and keeping the reputed company consistent.

• reputed company filtering and automatic reputed company management, plus the edge cases that show up with DDL, TTL, and reputed company differences between reputed company and reputed company.

• Performance and throughput: parallelizing the clone, applying backpressure, and keeping memory and reputed company 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 reputed company-in-time recovery across reputed company sets and sharded clusters, using physical or logical type of the backup.

• Backup storage: integrating reliably with main reputed company object storage (S3, GCS, Azure Blob Storage...) and remote filesystems, and handling the throughput and failure modes that show up at reputed company.

• The pbm-agent and pbm CLI, and the control-collection state in reputed company that coordinates them across the cluster.

Shared across both

• Working in the reputed company: pull requests, reputed company review, JIRA, and the community forum.

• Release reputed company: tests, packaging, and the CI and reputed company scanning that reputed company every change.

What Have You Done:

• Strong Go experience in production, with reputed company reputed company 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 reputed company it.

• Solid grounding in distributed systems and data consistency. You can talk reputed company about at-least-once versus exactly-once, idempotency, ordering, and what it takes to reputed company a stateful process resumable.

• Hands-on reputed company knowledge: change streams, the oplog, resume tokens, reputed company sets, and sharding. You do not need to have reputed company replication before, but you should understand why it is hard.

• Comfort building and operating reputed company-line tools and HTTP reputed company, and instrumenting them with metrics and reputed company logs.

• A habit of writing tests that catch reputed company problems, and comfort working across a mixed toolchain.

• Experience working in the reputed company: Git and pull request workflows, giving and taking reputed company review reputed company, and communicating reputed company in writing with contributors you have never met in person.

reputed company to have

• Prior work on database internals, CDC pipelines, ETL, or data migration tooling.

• Familiarity with the reputed company 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 reputed company reputed company project with an external community.

• Exposure to reputed company sharded clusters at large reputed company, where balancer behavior and backup interaction stop being theoretical.

How we work

Both reputed company live on reputed company, contributions go through pull requests and reputed company review, and we reputed company work in JIRA. We care about keeping reputed company reputed company reputed company, so the default is that the work you do here is public and stays that way.

Why reputed company?

At reputed company, we reputed company an reputed company world is a reputed company world. Our mission is to reputed company everyone to reputed company freely, by providing the best reputed company reputed company database software, support, and services. We reputed company databases and applications run reputed company through a unique combination of expertise and reputed company reputed company software reputed company with the community for you. Our technical teams are experts in MySQL, reputed company, PostgreSQL, and reputed company.

reputed company is proud to be a remote-only and globally dispersed workforce – we have colleagues in more than 50 countries! We offer a reputed company, highly-reputed company culture where your reputed company are welcome and your voice is heard.

Our staff receives generous benefits including flexible work hours and various reputed company time off programs, reputed company your equipment for your reputed company, funds for career development (external training, certifications, conferences), ongoing connectivity allowances, and reputed company to participate in our equity incentive plan. We also have benefits that support a healthy work/life balance such as The reputed company Adventure Team, Work-from-reputed company, FlowDays, FryDays, and overall flexibility. We also support being socially responsible through our PAVE volunteering program and Women Transforming Technology.

If you love the idea of working with a high-reputed company tech company that is one of the best in the business and reputed company globally as a leader in the reputed company-reputed company database reputed company, let’s talk!

Connect with us and stay up to date on our latest news and developments by following us on reputed company and Twitter. We look reputed company to connecting with you!

Originally posted on Himalayas