Pylon

Pylon

Member of Technical Staff, API

Palo Alto · Staff+

Sponsorship not specifiedDetected 99 days ago
TypeScriptSQLPostgreSQLTemporalGraphQLAI Orchestration

About the role

  • About Pylon America's $13T mortgage market is one of the most important financial systems in the world.
  • But while every other financial instrument has been simplified to an API call, mortgages are still assembled by hand.
  • We're backed by Peter Thiel, Conversion Capital, QED, Citi, Fifth Wall, and the founders of Ramp, Blend, and Mercury.

Responsibilities

  • It underwrites the middle class and is the mechanism through which millions of families build wealth.
  • Publicly traded companies and the country's largest originators are already building on Pylon.
  • Join us in building America's mortgage rails.
  • Define what a mortgage is in code. Seriously. You'll work on semantic models that don't just represent mortgages as they exist today - they expand what a mortgage can be. This is product design at the API layer.
  • Design for nonlinearity. Mortgage flows aren't linear wizards. Our future API encodes choice, branching, and path-dependence natively. You'll work on guided experiences that model real-world complexity without exposing it as chaos.
  • Wants to own features from design to development to deployment to maintenance

Requirements

  • We're moving to a world where our API doesn't just respond to requests - it tells you what happened, why, and what you can do next.

Skills

  • GraphQL (this is the product)
  • NestJS
  • SQL (PostgreSQL)
  • Temporal.io http://Temporal.io (workflow orchestration)
  • Event-driven architecture
  • AI-driven development tooling and agentic infrastructure
  • Someone who:
  • Is deeply curious
  • Is willing to put the work in to solve the hardest of problems
  • Location: Palo Alto, CA Base Salary Range: $140,000/yr to $220,000/yr + Equity + Benefits

Compensation

  • $140,000/yr to $220,000/yr + Equity + Benefits

Company info

  • We're looking for Back End Engineers to join our API team.
  • We treat our GraphQL API as a product - because it is one.
  • Multiple customers build directly on top of it, and the quality of their experience is determined by how well we design, document, and maintain it.
  • Mortgage is a surprisingly rich domain to model.
  • It's path-dependent: the choices you make early in a loan constrain what's possible later.
  • It's nonlinear: different borrower situations branch into wildly different flows.
  • Most APIs in this space paper over that complexity.
  • We're building one that embraces it - encoding the real shape of mortgage into a surface that's impossible to misuse and delightful to build against.
  • Build toward an event-driven API. We're moving to a world where our API doesn't just respond to requests - it tells you what happened, why, and what you can do next. You'll help design and ship that future.
  • Make the complex feel simple. Our API should make the mortgage process impossible to get wrong. That means thoughtful abstractions, clear documentation, and an obsessive focus on developer experience.
  • Treat this as a product surface. You'll think about breaking changes, versioning, onboarding, and the full lifecycle of an API that real companies depend on.
  • We started from zero and created the first vertically integrated mortgage platform that turns origination into a single API.
Apply directly at Pylon →Create a free account for alerts like thisView Pylon immigration profile

This listing is sourced directly from Pylon's careers page and normalized into a canonical job model.