Platform Backend Engineer: Payments & Subscriptions

Speechify; United States; Remote; USD 120,000 - 180,000; Full time

Benefits offered by this job

Autonomy

Competitive compensation

Asynchronous work culture

Impactful work

Diversity & inclusion

Job summary

Speechify is seeking a backend engineer to design, build, and own the APIs powering payments, subscriptions, auth, consumption tracking, and the public TTS API. You will optimize existing services for speed, cost, and reliability, and automate repetitive work to enable broader team impact.

You will collaborate with product, mobile, and web teams to keep the backend architecture aligned with product direction and scale.

Qualifications

• Proven backend experience in TS/Node (required).
• Direct experience with GCP; working knowledge of AWS, Azure.
• Habit of giving away work you used to own, and something to show for the room it created.
• Daily setup with AI agents described in detail — what runs unattended, what you review.

Responsibilities

• Design, build, and own APIs behind payments, subscriptions, auth, consumption tracking, and the public TTS API.
• Make existing services faster, cheaper, and more reliable without breaking them.
• Provide pre-shipment correctness checks and maintain post-change monitoring.
• Automate repetitive parts of the role to focus on higher-value work.
• Turn solitary work into repeatable team processes.
• Design B2B and enterprise integrations for customers building on Speechify.
• Collaborate with product, mobile, and web to keep backend architecture ahead.

Skills

TS/Node

GCP

Docker

Kubernetes

CI/CD

Observability

Debugging

Tools

Docker

Kubernetes

Job description

Speechify is seeking a backend engineer to design, build, and own the APIs powering payments, subscriptions, auth, consumption tracking, and the public TTS API. You will optimize existing services for speed, cost, and reliability, and automate repetitive work to enable broader team impact.

You will collaborate with product, mobile, and web teams to keep the backend architecture aligned with product direction and scale.