Member of Technical Staff, API
Pylon, Palo Alto
The team
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.
Here is what you'll do
- 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.
- 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.