Data Platform Engineer
Paxos · Remote · mid
Paxos · Remote · mid
Applying to Paxos? Our only careers site is paxos.com/careers, and we only recruit via @paxos.com email. Details below. ___
Today’s financial infrastructure is archaic, expensive, inefficient and risky — supporting a system that leaves out more people than it lets in. So we’re rebuilding it.
We’re on a mission to open the world’s financial system to everyone by enabling the instant movement of any asset, any time, in a trustworthy way. For over a decade, we’ve built blockchain infrastructure that tokenizes, custodies, trades and settles assets for the world’s leading financial institutions, like PayPal, Venmo, Mastercard and Interactive Brokers.
The Data Engineering team at Paxos builds and maintains the data infrastructure that powers our engineering partners and analytics teams. Our mission is to provide scalable, reliable, and secure data access to support critical business needs, including product analytics, business intelligence, client and regulatory reporting, and operational efficiencies. By continuously enhancing our data platform, we drive innovation, optimize costs, and unlock new revenue opportunities. You'll be working closely with a small, high-impact team of engineers across US and India time zones.
As a Data Platform Engineer, you will own important parts of our data platform from design through production operation. Depending on the problem, your work may involve data ingestion and pipelines, streaming systems, data lakes and warehouses, time-series or relational databases, Kubernetes, cloud infrastructure, platform automation, security, or governance. We do not expect every candidate to arrive with experience in every part of this stack. We are looking for strong engineering fundamentals, deep experience in at least one relevant area, sound technical judgment, and a demonstrated ability to learn unfamiliar systems quickly.
This role is well suited to someone who enjoys turning ambiguous needs into reliable, maintainable systems; can work independently while collaborating closely with partners; and takes responsibility for the operational outcomes of what they build. For example, a strong engineer with Spark experience should not be excluded simply because Paxos does not currently use Spark—the relevant signal is how they designed, scaled, and operated data systems and how effectively they can transfer that knowledge to a new environment.
sourced from the original posting ↗ · always verify details there before applying
Paxos · Remote
Paxos · Remote