Backend Engineer, Integrations & APIs
About stellar
Nonprofit (SDF) that develops and grows the open-source Stellar blockchain for low-cost cross-border payments, stablecoins, and tokenized real-world assets.
Bootstrapped · 100–200 people
Job description
The full responsibilities and requirements are on the employer’s site.
Open application page ↗Source and classification
Production engineering · Evidence for this classification:
research project. We are actively building a high-performance platform designed to handle real value. We operate as a fast-moving, highly technical team with no layers of management. You will work directly with the protocol architect and core systems engineers to take this completely greenfield project to production. If you thrive on the urgency of a new launch and want the agility of an early-stage startup with the stability of SDF, this is the place to be. About the Role: We need a Backend/Systems Engineer who owns the critical layer between our core infrastructure and the outside world. The public API, indexing, data pipelines, and everything that makes the system usable by developers and partners. Today, nobody owns this layer end-to-end. Pieces exist, but the JSON-RPC endpoint, transaction status tracking, analytics pipelines, and data services are a greenfield waiting for an
More from the job description
Interested in working on cutting-edge blockchain technology and creating equitable access to the global financial system? Since 2014, the mission-driven team at the Stellar Development Foundation (SDF) has helped fuel the tremendous growth of the Stellar blockchain network, an open-source platform that operates at high-scale today. Developers and companies around the world build on it, and the SDF team is expanding to support the rapidly growing and changing Stellar ecosystem. About the Project & Team: At the SDF, a small team of roughly 8 engineers is incubating a novel distributed systems prototype. Not a blockchain as you know it, something new. This is a rare opportunity for a zero-to-one build where much of the infrastructure and tooling does not exist yet. You will be building it. To be clear: this is not a maintenance role for our existing network, nor is it an academic research project. We are actively building a high-performance platform designed to handle real value. We operate as a fast-moving, highly technical team with no layers of management. You will work directly with the protocol architect and core systems engineers to take this completely greenfield project to production. If you thrive on the urgency of a new launch and want the agility of an early-stage startup with the stability of SDF, this is the place to be. About the Role: We need a Backend/Systems [... source excerpt omitted ...] ously from someone who has already been through a complex infrastructure launch (like a testnet or mainnet). You know what breaks, what gets skipped and regretted later, and what "production-grade" actually means for infrastructure that handles real value. What the First Few Months Look Like: Month 1: Understand the system architecture end-to-end. Get the full stack running locally. Own the JSON-RPC spec and start building. Month 2-3: Working RPC endpoint. Submit a transaction, query its status, check a balance. Indexer serving the block explorer. Transaction lifecycle fully instrumented. Beyond: Data pipelines, partner integrations, API hardening, load testing. Bake in the pro [... source excerpt omitted ...] external tools, SDKs, and wallets use to communicate with the core network (transaction submission, status queries, account state). Transaction Lifecycle: Own the full path from client to consensus and back. Status tracking, error reporting, and timeout handling. Indexer & Query Backend: Build the data backend that powers the block explorer, partner integrations, and historical state queries. Data & Observability: Build out analytics pipelines (e.g., BigQuery population) and implement robust metrics and event logging using tools like Prometheus, Clickhouse, and Sentry. Cross-Functional Impact: Work across service boundaries, getting comfortable reading code in components y
Employer postings · Data from · Sources