Open roles

SOFTWARE · Engineering

Senior Software Engineer

Maximum

SeniorRemote · USListed 6d ago
Apply on careers page

This company lists roles on a single careers page without individual links. The button opens that page and highlights “Senior Software Engineer” where the browser supports it.

Backed by

Pear VC

HQ

🇺🇸 Miami, FL, United States

Open roles

3

How to stand out for Senior Software Engineer at Maximum

Auto Match agent

Let ORI find you the best jobs.

Set up your Auto Match agent once - your target role, level and where you want to work. It searches every day, scores each opening against your profile and resume, and delivers the ones worth applying to, with a prepared application a click away.

Searches every day Scored against your profile Applications prepared for you
Sign in & set up Auto Match agent

Resume & career call

Get your resume reviewed for this role - 30-minute 1:1 call

Line-by-line resume feedback for this application, how to position your Role Readiness, and a clear plan for what to do next - with a OneRoadmap career coach.

Experience Senior · 6+ yrs

About the role

from listing

Senior Staff Software Engineer Location:Remote (US or Canada) Maximum is building a core banking platform. Not a layer on top of a legacy core: the ledger, product, payments, card and compliance systems a bank actually runs on. You would be involved in many big design decisions from day one. It also means correctness sits with you. You would own a domain service outright: its schema, its API, its workflows, its tests.

When a change touches twelve other services, you follow it into all twelve. We use AI coding agents heavily, and directing them is part of the job. Responsibilities Own a domain service end to end: schema, gRPC API, workflows, event consumers, tests, and the docs that explain why you built it the way you did. Design tables and queries in our schema DSL. Write workflows that survive partial failure: replay-safe, idempotent, and resumable from the step that broke.

Test against real environments in containers. Mocking is a last resort, and we will ask why you needed it. Review pull requests from humans and from agents, with the same suspicion for both. Turn messy external inputs into a data model that holds: a vendor file spec, a regulation, a feature or integration. Qualifications Several years shipping backend services in a statically typed language. Go preferred; strong experience in Java, C#, Rust or TypeScript is also welcome.

Real SQL experience: transactions, isolation levels, query plans, indexing, and migrations that run against tables with data already in them. You have debugged a distributed system in anger. You know what idempotency, at-least-once delivery and out-of-order messages do to a design. A testing habit, and an argument for why you test against real dependencies rather than mocks. You can read an unfamiliar spec, ask the two questions that matter, and start building without waiting for perfect requirements.

You use AI coding agents seriously and know when to throw away what they give you. Banking, payments, ledger, card or ACH experience helps. We can teach the domain; we would rather hire for judgment. To apply, email your resume to [email protected] with the subject line “Senior Staff Software Engineer”. Staff Software Engineer Location:Remote (US or Canada) Maximum is building a core banking platform.

Not a layer on top of a legacy core: the ledger, product, payments, card and compliance systems a bank actually runs on. You would be involved in many big design decisions from day one. It also means correctness sits with you. You would own a domain service outright: its schema, its API, its workflows, its tests. When a change touches twelve other services, you follow it into all twelve. We use AI coding agents heavily, and directing them is part of the job.

Responsibilities Own a domain service end to end: schema, gRPC API, workflows, event consumers, tests, and the docs that explain why you built it the way you did. Design tables and queries in our schema DSL. Write workflows that survive partial failure: replay-safe, idempotent, and resumable from the step that broke. Test against real environments in containers. Mocking is a last resort, and we will ask why you needed it.

Review pull requests from humans and from agents, with the same suspicion for both. Turn messy external inputs into a data model that holds: a vendor file spec, a regulation, a feature or integration. Qualifications Several years shipping backend services in a statically typed language. Go preferred. Strong experience in Java, C#, Rust or TypeScript etc. is also welcome. Real SQL experience: transactions, isolation levels, query plans, indexing, and migrations that have to run against tables with data already in them.

You have debugged a distributed system in anger. You know what idempotency, at-least-once delivery and out-of-order messages do to a design. A testing habit, and an argument for why you test against real dependencies rather than mocks. You can read an unfamiliar spec, ask the two questions that matter, and start building without waiting for perfect requirements. You use AI coding agents seriously and know when to throw away what they give you.

Banking, payments, ledger, card or ACH experience helps. We can teach the domain. We would rather hire for judgment. To apply, email your resume to [email protected] with the subject line “Staff Software Engineer”. Senior Software Engineer Location:Remote (US or Canada) Maximum is building a core banking platform. Not a layer on top of a legacy core: the ledger, product, payments, card and compliance systems a bank actually runs on.

You would be involved in many big design decisions from day one. It also means correctness sits with you. You would own a domain service outright: its schema, its API, its workflows, its tests. When a change touches twelve other services, you follow it into all twelve. We use AI coding agents heavily, and directing them is part of the job. Responsibilities Own a domain service end to end: schema, gRPC API, workflows, event consumers, tests, and the docs that explain why you built it the way you did.

Design tables and queries in our schema DSL. Write workflows that survive partial failure: replay-safe, idempotent, and resumable from the step that broke. Test against real environments in containers. Mocking is a last resort, and we will ask why you needed it. Review pull requests from humans and from agents, with the same suspicion for both. Turn messy external inputs into a data model that holds: a vendor file spec, a regulation, a feature or integration.

Qualifications Several years shipping backend services in a statically typed language. Go preferred. Strong experience in Java, C#, Rust or TypeScript etc. is also welcome. Real SQL experience: transactions, isolation levels, query plans, indexing, and migrations that have to run against tables with data already in them. You have debugged a distributed system in anger. You know what idempotency, at-least-once delivery and out-of-order messages do to a design.

A testing habit, and an argument for why you test against real dependencies rather than mocks. You can read an unfamiliar spec, ask the two questions that matter, and start building without waiting for perfect requirements. You use AI coding agents seriously and know when to throw away what they give you. Banking, payments, ledger, card or ACH experience helps. We can teach the domain. We would rather hire for judgment.

To apply, email your resume to [email protected] with the subject line “Senior Software Engineer”. No roles match those filters. Email [email protected] anytime.

This company lists roles on one careers page without individual links, so Apply opens that page and highlights “Senior Software Engineer” where the browser supports it.