Hashtag Web3 Logo
Stripe logo

Android Engineer, Terminal OS Platform

Stripe
San Francisco, SeattlePosted 216 days ago
Apply

Stripe is hiring a Android Engineer, Terminal OS Platform in 8512 Terminal - Eng — San Francisco, Seattle. The overview below is synthesized from the employer posting on stripe.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.

Who we are

About Stripe

Company context from the listing:

Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities.

About the team

Company context from the listing:

Stripe Terminal helps our users extend their online presence to the physical world. The Terminal team's mission is to make it as easy for businesses to accept in-person payments as the Stripe API has done for online payments.

Android engineers on the Terminal team will build and enhance the Device Platform including the applications and services that run on the physical Terminal devices. This also includes building the frameworks for other engineers, both internal and external to Stripe, to develop on our custom platform with ease.

What you'll do

Day-to-day scope for the Android Engineer, Terminal OS Platform as described in the posting:

Responsibilities

Day-to-day scope for the Android Engineer, Terminal OS Platform as described in the posting:

  • Design, build, and maintain Android apps and SDKs in Kotlin
  • Develop Android payment applications for a variety of devices and form factors
  • Work with engineers, product managers, designers, and stakeholders across the company to bring new features and products to Stripe's mobile users
  • Collaborate with Android developers who work on the Stripe mobile apps and Stripe Terminal to set best practices for Android development across the company
  • Work with user research and product design to understand users and address their needs

Who you are

Experience and skills the team lists as required:

The listing frames the Android Engineer, Terminal OS Platform at Stripe as a hands-on product role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement.

Minimum requirements

Experience and skills the team lists as required:

  • Have a strong technical background, with 2–6 years of experience in Android development.
  • Listen well and internalize the best ideas from all over the organization.
  • Prefer simple solutions and designs over complex ones, and have a good intuition for what is lasting and scalable.
  • Thrive in a collaborative environment involving different stakeholders and subject matter experts.
  • Put yourself in the shoes of your users and be a steward of crafting great developer and consumer experiences.

Preferred qualifications

Experience and skills the team lists as required:

  • Custom hardware experience on the Android platform
  • Payments expertise or knowledge
  • Backend infrastructure or services experience
  • Based in the PST time zone

Build a standout application

For the Android Engineer, Terminal OS Platform at Stripe, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.

Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.

In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.