openripplingbvp
Software Engineer III, Data Product
Shippo
LocationUnited States
WorkplaceREMOTE
EmploymentPLACEHOLDER, Full-Time Employee
Posted2026-06-18T06:44:08.503000-07:00
Last observed2026-06-29 02:03:26.103083
Job idbvp-shippo:rippling:97f97516-d61a-45b3-8fc4-e322fc87a7ec
About Shippo At Shippo, our vision is bold and clear: we are the shipping layer of the internet. Our mission is to make every merchant successful through excellent shipping, delivering world-class logistics technology and infrastructure. We’re building the backbone of global e-commerce — connecting merchants to carriers worldwide through a single API and intuitive dashboard. As a remote-first and globally distributed team , we believe flexibility fuels trust, autonomy, and performance. Our diverse perspectives — across continents, cultures, and time zones — drive our innovation and enable us to build solutions used by businesses everywhere. We invest in modern, scalable technology so our teams can build, ship, and iterate with confidence. Your impact starts here: every person at Shippo plays a direct role in shaping the infrastructure that powers global commerce and makes shipping simpler for businesses around the world. How we will deliver success together: The Data Products team is building Shippo’s next generation of customer-facing data and intelligence products—turning shipping data into actionable insights, automated recommendations, and configurable rule-driven experiences that help merchants make smarter decisions at scale. We're hiring a Software Engineer III to join this team as a foundational member. You'll work primarily in Python on backend services (~70% of your time) and contribute to React surfaces where merchants and internal users configure and observe these decisions (~30%). You'll ship features end-to-end, own meaningful pieces of the rules engine over time, and grow into broader scope as the product matures. Shipping & handling responsibilities Build and own components of the rule evaluation engine — the decision logic at the heart of Data Products — including authoring rules, evaluating them at scale, and exposing results to downstream systems. Develop backend services in Python (FastAPI) that handle high-throughput, low-latency evaluation workloads. Work with event-driven infrastructure (Kafka or equivalent) to integrate the engine with upstream data sources and downstream consumers. Design and evolve data models that support auditability, versioning, and reproducibility of rule outcomes. Build React interfaces that let merchants and internal users configure rules, inspect evaluations, and trust the system. Contribute across the full spectrum of the Data Products team’s work—business rules automation, ML-based APIs, customer-facing analytics, and intelligent recommendation systems. Partner with Data Science, Analytics Engineering, and Product to translate analytical signals into productionized decisions. Instrument what you ship: write meaningful tests, add metrics and tracing, and use production data to validate that changes landed as intended. Participate in team oncall and incident response for the services you own. Contribute to API design, service decomposition, and cross-team technical reviews as you grow into broader ownership. Help onboard new team members and share knowledge through code reviews, design docs, and pairing. Use AI coding tools (Claude, Cursor) effectively in your daily workflow and contribute to evolving team norms around them. Your shipping requirements 6+ years of professional software engineering experience, with at least 2 years shipping production full-stack features. Strong Python backend skills; FastAPI (or comparable async Python framework) experience preferred. Hands-on experience with event-driven systems (Kafka or equivalent) in production. Solid PostgreSQL skills, including schema design, indexing, and query performance. Production-level React experience, including state management and integration with backend APIs. Comfortable shipping behind feature flags, instrumenting code for observability, and iterating based on production signal. Practiced at writing tests (unit and integration) and treating reliability as part of the work, not a follow-up task. Strong written c
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.