Back-end Developer

Marathon Talent•New York, NY
•Remote

About The Position

Nummo builds software for recruiting teams that run many searches at once. The backend is where coherence is enforced across various tools like applicant tracking systems, notes tools, calendars, and spreadsheets. This role owns the path for designing and shipping services that manage searches, attach candidates, and advance them through stages. You will work on the agent runtime that reads recruiter messages, plans writes, and delivers them, as well as the workflow engine that manages tasks and integrations with third-party systems. A normal week involves a mix of product development and operational care, including debugging production issues and improving system reliability. The system is a TypeScript monorepo with a Postgres database and Temporal for workflow orchestration. Key backend challenges include managing identity, ensuring correct ordering of operations, and handling partial failures gracefully. The ideal candidate has experience building and operating backend systems, is comfortable with relational data and transactions, and has shipped integrations against third-party APIs. You should be proficient in TypeScript and prefer clear, concise code over extensive comments. While experience in recruiting is not required, a focus on the recruiter's user experience is essential.

Requirements

  • Built and operated backend systems that other people depend on.
  • Comfortable with relational data, transactions, and the implications of unique indexes or soft deletes.
  • Shipped integrations against third-party APIs, including their rate limits, draft-versus-published states, and eventual consistency.
  • Ability to read a stack from an HTTP request through a workflow history and identify the running step.
  • Write TypeScript that other people can change.
  • Prefer a small function with a precise name over a comment that explains a muddy one.
  • Care about what the recruiter sees, treating stage slugs, guest lists, and task titles as product behavior.
  • Understand how to handle scenarios like a candidate existing as a person, a candidacy, and an external applicant, and keeping those records tied together.
  • Understand how to handle time-sensitive operations, like a milestone recorded today opening a task for tomorrow.
  • Understand how to handle concurrent writes to the same data, ensuring the newer write wins.
  • Understand how to differentiate between a missing approval card and a true failure.

Nice To Haves

  • Experience in recruiting.

Responsibilities

  • Design and ship services that open a search from an external job, attach candidates, and advance them through stages.
  • Work on the agent runtime that reads a recruiter’s message, plans the writes for that turn, and delivers them.
  • Work on the workflow engine that opens the next task when a milestone is recorded and leaves a task alone when the step is already satisfied.
  • Work on integrations that talk to applicant tracking systems, calendars, documents, and notes tools, including polling and webhook paths.
  • Read production evidence when something fails, fix the narrow cause, and add the check that would have caught it.
  • Delete old paths once new ones are implemented and adopted.
  • Ensure the backend systems are reliable, with fewer stuck runs, fewer duplicate tasks, and fewer incorrect invites.
  • Make the loop from job publication to offer signing shorter and harder to get wrong.

Benefits

  • Pull requests with clear descriptions of behavior, risk, and verification.
  • Production access for diagnosis is read-only.
  • No fixing live searches by writing around the product.
  • Opportunity to talk to people who use the product, including production recruiting firms.
  • Involvement in the full search lifecycle from job publication to offer signing.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service