Jobs / United States / Spreedly

Spreedly

Senior Database Engineer

Remote (USA) · Remote · US only Posted today

View original listing ↗ Tailor my CV first Source: Jobicy

Listed on Jobicy: the application continues on their site, which links to the employer. Optional: we can tailor a CV and cover letter for this job from your real experience first (the first one is free).

Where you can work from

United States only

Based on the listing's location: Remote (USA).

The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.

Visa sponsorship, if you would relocate

Sponsorship verdict

No sponsorship evidence yet

No government record and no wording either way. Not a refusal: ask the recruiter.

  • No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
  • The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
  • No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
  • Confirmed live todayWhen a source last listed this job as open.
Details and sources
No salary bar for this route
H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.

US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).

A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.

Before you apply

Sponsorship unknown

No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.

These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →

About the role

About Us: Spreedly is the Intelligent Payments Platform for businesses that want to own their payments strategy. Founded in 2007 and headquartered in Durham, NC, we give merchants, platforms, and fintechs a single API to connect to 150+ payment gateways and 40+ payment methods across 100+ countries, along with the intelligence to decide where every transaction should go. We're vendor-agnostic by design. Our customers choose their providers, keep their payment data portable, and never have to rebuild their stack to adopt something new. Payments are getting more complex, not less. Every new market, payment method, fraud tool, and now every AI agent checking out on a shopper's behalf adds another integration and another decision. Spreedly turns that complexity into an advantage. Our PCI Level 1 vault keeps cards and network tokens portable across providers. Smart routing and retries recover revenue lost to avoidable declines. Fraud and 3DS tools plug in with a single API call. And our payments intelligence turns transaction data into decisions merchants can act on. As agentic commerce moves from experiment to real sales channel, we're building the infrastructure that lets merchants accept agent-initiated payments through the providers they already trust. For the people who work here, that means hard technical problems at real scale, billions of dollars in annual transactions, at a moment when the rules of commerce are being rewritten. If you want ownership and work that shows up directly in your customers' revenue, you'll fit right in. About the Role Spreedly is hiring a Senior Database Engineer to become the go-to database expert on our Reliability team. You'll improve the performance and reliability of our existing distributed database environment and help engineering teams make database changes safely. This is a senior individual contributor role with no direct reports, and "senior" here means more than years of experience: you'll be the person the rest of engineering looks to on anything at the database layer. The opportunity is to shape how we manage and improve our databases, not to lead a migration. We already run CockroachDB, with infrastructure operated through Cockroach Labs' managed service. That means your focus is the part that's ours to own: workload, schema, queries, settings, capacity, and the practices around change. Our Reliability team works across application engineering, infrastructure, and platform to improve monitoring, prevent incidents, and recover quickly when incidents happen. It isn't a textbook SRE team. It's a small, highly autonomous group focused on continuous improvement, with real room to see a problem, propose a fix, and carry it through within the team's priorities. Database availability and performance matter a great deal in a payments environment, and the improvements you make here show up directly in the reliability our customers depend on. Responsibilities: Responsibilities Improve database performance • Investigate our current database setup to find performance bottlenecks and reliability risks, using instrumentation, code review, and staging tests where appropriate. • Find and improve slow-running queries, identify missing or inefficient indexes, and evaluate database settings against what the application actually needs. • Diagnose distributed-database issues such as transaction contention and retries, hot ranges, and inefficient access patterns, and partner with application engineers to fix them at the source. • Establish performance baselines so meaningful changes in workload behavior are visible early. Be the database subject-matter expert • Help engineering teams understand the risks and trade-offs of significant changes before they reach production, including schema migra

View original listing ↗