Full-Time
Senior Software Engineer
Go/MongoDB
Updated on 9/10/2026
Percona
201-500 employees
Open-source database software support and services
No salary listed
Rome, Metropolitan City of Rome Capital, Italy + 1 more
More locations: Madrid, Spain
Remote
 Software Engineering (1) |
|---|
Get referred to Percona
See people who can refer or advise you
- Strong production experience with Go, including goroutines, channels, context cancellation, worker pools, and backpressure.
- Solid grounding in distributed systems and data consistency, including at-least-once versus exactly-once delivery, idempotency, ordering, and resumable stateful processes.
- Hands-on knowledge of MongoDB change streams, the oplog, resume tokens, replica sets, and sharding.
- Experience building and operating command-line tools and HTTP APIs, and instrumenting them with metrics and structured logs.
- Experience writing tests that identify real problems and working across a mixed toolchain.
- Experience with Git and pull-request workflows, code review, and written communication with external contributors.
- Develop the PCSM core replication engine, including initial collection cloning and continuous change capture over MongoDB change streams.
- Handle resume tokens, ordering, resumability after failures, network drops, primary elections, and restarts without losing or duplicating changes.
- Build sharded-cluster support that accounts for chunk migrations and balancer activity while keeping the target consistent.
- Implement namespace filtering and automatic index management, including edge cases involving DDL, TTL, and source-target index differences.
- Improve clone parallelization, backpressure, memory usage, connection usage, performance, and throughput for large clusters.
- Build and maintain the CLI and HTTP API used to drive and observe synchronization, along with metrics and structured logging.
- Work on consistent backup, restore, and point-in-time recovery across replica sets and sharded clusters.
- Integrate backup storage with S3-compatible object storage, Google Cloud Storage, Azure Blob Storage, and remote filesystems.
- Work with pbm-agent, the pbm CLI, and MongoDB control-collection state coordinating cluster processes.
- Contribute through pull requests, code review, JIRA, and community forums.
- Maintain release quality through testing, packaging, continuous integration, and security scanning.
- Prior work on database internals, change data capture pipelines, extract-transform-load processes, or data migration tooling.
- Familiarity with Prometheus-style metrics and observability.
- Experience with golangci-lint, vulnerability scanning such as Trivy, and Debian and RPM packaging.
- Background maintaining or contributing to an open-source project with an external community.
- Exposure to large-scale MongoDB sharded clusters, including balancer behavior and backup interaction.
Percona specializes in open-source database software and services, offering free distributions of MySQL, PostgreSQL, and MongoDB along with Percona Monitoring and Management (PMM). Their paid services include consulting, managed database services, and support to help businesses optimize performance and reliability. The product approach combines free, enhanced open-source databases with expert, enterprise-grade services to manage and scale data. Percona differentiates itself through deep open-source expertise, a strong focus on performance optimization, and a free monitoring tool, paired with comprehensive paid services. The company’s goal is to help organizations run fast, reliable, and scalable databases by providing both accessible free software and seasoned professional support.
Company Size
201-500
Company Stage
Grant
Total Funding
$1M
Headquarters
Pleasanton, California
Founded
2006
Get referred to Percona
See people who can refer or advise you
Simplify's Take
What believers are saying
- Percona Server for MongoDB added RHEL 10 and Debian 13 support on August 11, 2026.
- Chainguard partnership on March 25, 2026 sells hardened container images with enterprise support.
- Percona shipped OIDC for MongoDB and PMM 3.6.0, expanding security and observability.
What critics are saying
- Oracle cut MySQL staff roughly 50% in autumn 2025, weakening upstream momentum.
- Managed cloud databases from AWS, Oracle, and MongoDB compress Percona's support margins.
- OpenEverest's spin-out to Solanica fragments attention and risks Percona losing platform control.
What makes Percona unique
- Percona sells only open-source database software, support, consulting, and managed services.
- Percona supports MySQL, PostgreSQL, MongoDB, Redis, and Valkey across hybrid deployments.
- Percona Monitoring and Management gives free database observability without SaaS lock-in.
Help us improve and share your feedback! Did you find this helpful?
Benefits
Remote Work Options
Flexible Work Hours
Paid Vacation
Paid Holidays
Company Equity
Phone/Internet Stipend
Professional Development Budget
Conference Attendance Budget
Growth & Insights and Company News
6 month growth
↑ 0%1 year growth
↑ 0%2 year growth
↑ 2%Percona for MongoDB: RHEL 10, its derivatives, and Debian 13 - On both x86_64 and ARM. August 11, 2026 Percona is happy to announce that Percona Server for MongoDB (PSMDB) 8.0.28-12 extends platform support to RHEL 10 and its derivatives (Oracle Linux 10, Rocky Linux 10, AlmaLinux 10, and other RHEL-compatible distributions) for both x86_64 and ARM (aarch64) architectures. This release also adds support for Debian 13 "Trixie" on x86_64 and ARM64. Percona'll continue to support that for 8.0, 8.3, and newer releases. This is an important step for anyone planning infrastructure refreshes around the latest Linux releases, and it's especially notable for teams evaluating ARM to cut infrastructure spend without sacrificing performance. What's new in 8.0.28-12. Starting with this release, Percona Server for MongoDB packages are available for: * RHEL 10 and derivatives like Oracle Linux 10, Rocky Linux 10, AlmaLinux 10 on x86_64 and ARM (aarch64) * Debian 13 "Trixie" on x86_64 and ARM64 (aarch64) Additionally, starting this release, Percona has included Software Bills of Materials (SBOMs) and Vulnerability Exploitability Exchange (VEX) for every release. SBOMs improve software supply chain transparency by documenting the components and dependencies included in a build. They are generated automatically as part of the release pipeline in the industry-standard CycloneDX format. OpenVEX files are published on GitHub Pages and provide the exploitability status of known vulnerabilities. For comprehensive information, refer to its [documentation](.../sbom.md). Ahead of upstream on Debian 13. As of this writing (August 2026), upstream MongoDB Community/Enterprise Server does not yet officially package or support Debian 13. Trixie isn't in MongoDB's supported platforms list, and the documented community workaround is to install the Debian 12 "Bookworm" build on Trixie hosts, since a native Trixie server build hasn't landed yet. PSMDB closes that gap now, with native Debian 13 packages rather than a buggy Bookworm build running out-of-distro. Why ARM is worth a serious look for MongoDB workloads. Percona has heard multiple times from you directly, via its forum, or on Reddit about the Interest in ARM for database workloads. Over the last few years, adoption has moved well past the experimental phase to resilient production readiness. Its adoption telemetry data show nearly 3x as many ARM instances over the last 12 months! I can see a number of benefits and reasons why its community users and customers adopted ARM over AMD or Intel CPU architectures: * Lower infrastructure costs. Cloud ARM instances, such as AWS Graviton, are commonly cited as running 20-40% cheaper than comparable x86 instances at similar or better performance (sanj.dev, "ARM vs x86 Cloud: Which Architecture is Cheaper in 2025?"), and benchmarking write-ups report up to 60% lower energy consumption for compute-intensive workloads on Graviton compared to x86 equivalents (nOps, "Are you missing out on AWS Graviton Cost Savings?"). * Competitive, and often better, throughput. RDS PostgreSQL Graviton" benchmark analysis shows Graviton4 delivering up to 40% better performance for OLTP-style workloads versus the previous Graviton3 generation. Apache Doris Delivers 70% Better Value on AWS Graviton. I can see MongoDB database achieving a similar level of performance-to-cost gain. * Memory bandwidth is a real differentiator. Graviton3's memory bandwidth (cited at roughly 115-120 GB/s) is reported to significantly outpace typical Intel Xeon configurations (roughly 60-70 GB/s) and AMD EPYC (roughly 80-90 GB/s) in independent comparisons (byteiota, "ARM vs x86 Cloud: 2025 Performance & Cost Benchmark"), which matters for memory-hungry workloads like MongoDB's WiredTiger cache and in-memory working sets. (Note: The above figures come from third-party blogs and vendor case studies rather than peer-reviewed benchmarks. Treat them as directional evidence that ARM is worth evaluating, not a guarantee of results for your specific workload. For the official recommendation based on your workload, reach out to Percona) Netflix has publicly stated that it saves over $15 million annually after migrating video encoding workloads to Graviton, while also seeing faster processing times, and other large-scale AWS customers have reported double-digit percentage reductions in compute costs after moving meaningful portions of their backend fleets to ARM (byteiota; sanj.dev). What to watch out for. One RHEL 10 detail to keep in mind when planning a migration: Red Hat raised the CPU baseline for x86_64 to the x86-64-v3 microarchitecture level, meaning the processor needs to support instruction sets such as AVX2 (Red Hat, RHEL 10 architecture documentation; vInfrastructure Blog). On the ARM side, RHEL 10 targets the ARMv8.0-A baseline (Red Hat documentation). This applies equally to Oracle Linux 10, Rocky Linux 10, and AlmaLinux 10, since they build from the same upstream sources. I highly recommend checking your current infrastructure before planning the move, especially for older bare-metal fleets. In general, but especially on ARM, remember that performance is workload-dependent. Some code paths and workloads leaning on x64-specific instruction extensions may not see the same gains as throughput-oriented, multi-threaded workloads on ARM. Benchmarking your own query patterns and index-heavy operations before a full cutover is essential. General benchmarks are a good signal, not a guarantee. Percona can help you get there. Migrating a production MongoDB deployment to a different infrastructure is a project with real decision points. There are a number of questions to answer around: Hardware or instance selection, driver and tooling compatibility, benchmarking against your actual workload, and a rollback plan. The Percona Services team helps customers plan and execute exactly this kind of migration. Percona start from initial architecture assessment and proof-of-concept benchmarking and go through to production cutover and post-migration tuning. If you're weighing a move to ARM, or just want to get onto RHEL 10 or Debian 13 without surprises, reach out to Percona to talk through your environment. Far enough. Said no pioneer ever.
Percona welcomes new Director to enhance global partnerships. Percona has appointed Louis Hood as Director of Global Partnerships and Channels to lead its global partner programme. * Monday, 1st June 2026 Posted 3 hours ago in Cloud Infrastructure + Asset Management by Sophie Milburn Percona, a provider of open source database software, support, and services, has announced the appointment of Louis Hood as Director of Global Partnerships and Channels. Hood brings more than two decades of experience in developing partner ecosystems across cloud, data, and enterprise technology. At Percona, Hood will work on the company's global partner programme. His role includes engaging with partner networks in line with Percona's focus on open source database solutions and approaches intended to support cost management and reduce vendor lock-in. His responsibilities include maintaining existing partner relationships and developing new partnerships aimed at providing access to Percona's database expertise. He will also focus on making the company's solutions easier to implement, scale, and use in customer environments. Prior to joining Percona, Hood served as part of the FinOps Cloud team at Tangoe, where he worked on helping organisations manage cloud spending and align technology investments with business priorities. He has also held roles at SoftServe and CDW, focusing on strategic partnerships and emerging technology markets. The appointment reflects a leadership change within Percona as it continues its activities in the open source database sector and develops its partner and channel organisation.
Percona has appointed Louis Hood as Director of Global Partnerships and Channels. Hood brings over 20 years of experience building partner ecosystems across cloud, data and enterprise technology sectors. In his new role, Hood will lead Percona's global partner programme, focusing on relationships with cloud providers, global systems integrators, independent software vendors and value-added resellers. He will work to make Percona's open source database solutions more accessible and scalable for customers operating in hybrid and multi-cloud environments. Hood previously served as FinOps Cloud Lead at Tangoe and held strategic alliance roles at SoftServe and CDW. Percona provides open source database software, support and services for systems including MySQL, PostgreSQL, MongoDB, Valkey and Redis.
Two projects, one mission - hackorum and pginbox join forces. Last week, Zsolt and I jumped on a call with someone who had been building something remarkably similar to what Percona, Inc. had been working on, completely independently. That someone is Jack Bonatakis, the creator of pginbox.dev, and that call turned into one of the most energizing conversations Percona, Inc. has had since launching hackorum.dev. Two builders, one problem. When Percona, Inc. launched Hackorum back in January, the goal was simple but important: make the pg-hackers mailing list actually readable. The list is the heartbeat of PostgreSQL core development, patches are proposed, debated, iterated on, and committed entirely through it. But the interface? Decades-old email threads. Dense, fast-moving, and not exactly welcoming to newcomers or even experienced contributors trying to manage the volume. Percona, Inc. built Hackorum to change that, a forum-style, read-only web view with commitfest integration, contributor profiles, read tracking, shared team notes, and more. Something that respects the existing email-based workflow while dramatically lowering the barrier to follow along. Jack didn't know at the time was that hackorum.dev existed but he reached the exact same conclusion, independently, and had already started building his own answer: pginbox.dev. Who is Jack? Jack Bonatakis is a Principal Software Engineer focused on Data & Insights, based in Washington, D.C and currently working at Robin, a Boston-based startup. His professional background spans data engineering, cloud analytics, and building data-driven platforms, with stints at MITRE working on government-sector data solutions, as well as roles at Rhino Insurance and DAS42, a cloud analytics consultancy. He holds a Master's degree from the University of Colorado Boulder and has built a career on turning complex, noisy data into something people can actually use. Which makes it completely unsurprising that he looked at the pg-hackers mailing list, one of the most information-dense, high-volume technical discussions on the internet, and thought: this could be so much better. That instinct led him to build pginbox.dev: his own take on giving PostgreSQL's mailing list ecosystem a more modern, inbox-style interface. He built it almost immediately after Percona, Inc. published its first blog post about Hackorum. Percona, Inc. were first, but only just. And the fact that two completely separate teams arrived at the same idea, at nearly the same time, with similar approaches, says something important about how real and widely felt this problem is. Joining forces. When Percona, Inc. got on the call with Jack, there was no awkwardness about the overlap. Quite the opposite, Percona, Inc. spent most of the time excitedly comparing notes on what Percona, Inc.'d each built, what worked, what didn't, and where Percona, Inc. wanted to take things. The conversation made it obvious pretty quickly that running two separate tools for the same community didn't serve anyone well. So Percona, Inc. made the call together: pginbox.dev will be sunset, and Jack will be joining the Hackorum project going forward. One project, a stronger team, and a clearer path for the PostgreSQL community. This is exactly what open source is supposed to feel like. Not a race, not a territory dispute, people who cared enough to build something from scratch, discovering they'd be stronger together than apart, and choosing collaboration over competition without a second thought. Percona, Inc. is not building Hackorum for any single company or any individual's portfolio. Percona, Inc. is building something that should last, something genuinely useful to the PostgreSQL community for years to come. A more inclusive, more navigable hacker future, built together. Welcome to the team, Jack. Percona, Inc. is genuinely glad you built what you built. And Percona, Inc. is even more glad you're building the next chapter with Percona, Inc. working on hackorum.dev If you haven't tried Hackorum yet, visit hackorum.dev. And if you want to get involved, here's how: * | Join the conversation and hop into its Hackorum Discord channel to ask questions, share ideas, or just follow along as Percona, Inc. build. * | Explore the code, everything is open source and available on GitHub. * | Report a bug or request a feature, Percona, Inc. track everything in the its GitHub Issues. Kai wagner. Kai joined Percona in 2022 as an Engineering Manager responsible for the PostgreSQL development team. Before joining Percona, he worked as a team lead and as a software engineer at SUSE Linux. He is now focusing on the coordination of the PostgreSQL development at Percona as well as acting as an open source evangelist.
Percona, a provider of enterprise-grade open source database software, has partnered with Chainguard to deliver secure container images of open source databases with full enterprise support. The collaboration addresses a key challenge: organisations struggling to securely deploy containerised databases without building custom images themselves. Chainguard will create hardened, minimal container images with verifiable provenance, FIPS readiness and defined CVE service-level agreements, whilst Percona provides enterprise-grade support. The partnership covers Percona's entire database portfolio, including software for MySQL, PostgreSQL and MongoDB, plus community versions of PostgreSQL, MySQL, MariaDB, Valkey and Redis. The collaboration aims to help organisations meet stricter security requirements and compliance frameworks whilst reducing the time teams spend patching and adapting container images.