Software Engineer - Android

A career with Gravity Payments is an opportunity to be on a collaborative team where creative leadership, passion for progress, and responsibility are paramount. Our team members focus and commit to providing for our clients and our community because we care deeply for others.  

This is a role on the Payments Platform team, which is responsible for Android software and SDKs that run on payment terminals in environments in many industries across the US. The code you write reads cards, talks to card networks, and moves money. It is EMV-certified and PCI-scoped. There is no staging environment for a merchant whose terminal will not take a payment.

• You ship Kotlin on our PAX terminal applications and payment SDK, and your work holds up in a certified environment where a behavior change can invalidate a certification.
• You have opinions about architecture, API shape, and error handling, and you state them in design review. When the team goes the other way, you can explain the trade-off you accepted.
• You think in terms of what the code costs to support for the next five years, not what it costs to write this week. Terminals in the field cannot be hot-fixed the way a web app can.
• You design the failure paths instead of finding them in production. Process death mid-transaction, a network drop between authorization and signature, a certificate rotation that outruns the fleet: you raise these before they are incidents.
• You work productively when the answer is not yet known. Our largest epic lists nineteen open questions today, and you help close them rather than waiting for someone else to.
• You use AI-assisted and agentic tooling daily and have a view on where it earns its place and where it does not. You review what it produces the way you review a teammate's pull request.
• You raise the team's Android capability. You write down what you know, and the next engineer ramps faster because of it.

• →Build and maintain Android applications and libraries in Kotlin for PAX payment terminals, including the merchant-facing payment application and the partner-facing device SDK.
• →Work at the integration boundary: the PAX POSLink library, BroadPOS P2PE, EMV chip application selection, encrypted card payloads, key slots, and device registration.
• →Design for correctness under failure. Idempotency, retry safety, bounded timeouts, crash recovery, and durable correlation between a device transaction and the partner session it belongs to.
• →Participate substantively in engineering design documents and code review. Raise structural concerns, distinguish them from style, and defer where the call is not yours.
• →Own the quality of what you ship end to end: tests, instrumentation, release notes, and the support burden it creates.
• →Partner with the EMV certification effort. Understand which changes require a certification conversation before they are made.
• →Treat AI-assisted and agentic tooling as a core competency. Use it daily, and bring what you learn back to the team.

• 2+ years shipping production Android applications in Kotlin, including work you did not start yourself. Structured concurrency, dependency injection, and Compose or a credible reason you are on Views.
• You have shipped software where a defect has consequences: payments, banking, healthcare, identity, safety, industrial control, or comparable. Consumer utilities and portfolio applications do not clear this bar.
• Demonstrable opinions on architecture, module boundaries, public API design, and error handling, with specific examples of a decision you made and what it cost you.
• Comfort with ambiguity. You can describe a project where the requirements were genuinely unsettled, what you did to narrow them, and what you deliberately deferred.
• Evidence of long-horizon thinking: a deprecation you sequenced, a migration you finished, a dependency you refused, or a public interface you shaped knowing you could not take it back.
• Active daily practice with AI-assisted and agentic tools, and a view on how engineers should use them.
• Coachable. You take direct feedback, act on it, and come back with questions.

• Android development against payment terminal hardware: PAX, Clover, Sunmi, Verifone, Ingenico, Square, or comparable. Clover application development is a direct plus.
• EMV, card-present processing, tokenization, or PCI DSS scope experience.
• Published or distributed an Android library or SDK that third parties consumed: Maven artifact versioning, dependency isolation, backward compatibility, and deprecation policy.
• Network security work on Android: certificate pinning, mutual TLS, OkHttp interceptor chains, secure storage on device.
• Experience where a release could not be rolled back quickly, and you planned around that constraint

This job description is a snapshot of the role at this moment in time. As our organization evolves, so do our roles. Responsibilities may shift to meet changing business needs. We seek individuals who are adaptable, proactive, and open to growth as we continue to move forward together.

• Must have access to a wired internet connection and access to at least a 25 megabits per second (mbps) download and 20 mbps upload speed connection.