Full Stack Engineer

Why Ajax The problem Have you ever stood at engineering standup and struggled to recall what you did the previous day? Imagine that failure to precisely track your time results in either 1) your client firing you for overbilling or 2) working for free. Now imagine that you need to track your time in 1/10 hour (aka 6 minute) increments, and you needed to write a verbose description for every line item. That’s what 1.2 million attorneys confront every day. How we solve it Ajax sits on customers’ computers and generates time entries for them. We predict their client and write the narrative, so all they do is review and release the entries into their billing system. Metrics we’re proud of We want to work with people who care about our customers and understand the company’s success indicators. You won’t see these metrics reported in many JDs, but they’re how B2B startups are evaluated. We’ve fought hard to make them exceptional. 0% Customer Churn : we have never lost a firm ( 96% Pilot Conversion Rate : when we start pilots, we win them (>70% is considered good) 140% Net Dollar Retention: after firms convert with Ajax, they share it with more and more employees (>120% is considered good) Take it from our customers Working at Ajax We strive to be the most customer-obsessed startup in the world. We work in-person in NYC 1) so that we can learn customer feedback directly from one another and 2) because we work hard, so we may as well be friends with each other. Our founders, brothers Jack and Alex (yours truly), lead our Go-To-Market (GTM) and Engineering teams, respectively. Our goal is to keep our two teams as tightly coupled as possible for as long as possible: our teams sit next to each other, eat lunch together, and celebrate pilot wins together. Our GTM team contributes to backlog meetings and our engineers directly communicate with customers. How we work, in practice Before Ajax, I had never worked on an engineering team that answered customer support chats through Slack. We don’t ask our programmers to double as support much anymore, but that orientation remains. Because an example is worth a thousand words, here’s a real sprint we had in November: During a pilot with an important firm, the GTM team noticed that activation was low We pulled some data from Posthog and Metabase and came up with a hypothesis: these users were the fastest billers we’ve ever seen, and Ajax’s entries weren’t ready for them in time Siyou restructured our React FE to show a Domino’s pizza style “entry in progress” tracker, assuring nervous billers that their work was indeed captured Alex issued a native app update for our Flutter app that captured data more quickly when users task switch Roger optimized some gnarly python async code to bring our p99 entry latency from ~180s to ~120s. 🎉 We won the pilot! 🎉 Our Hiring Process: Intro call with Alex Project walk through over Zoom In Office - 3 hours, then dinner with the team Offer 🎉 What you get $180-230 base + meaningful equity Full dental, health, and a lot of fun I like working here because we win a lot, we’re solving previously-intractable technical challenges, and at least once a week a customer tells me that our product is saving their life. If that sounds fun to you, send me an email.

{
  "content_hash": "2f64a6924d4ab68786a32b5eeb0914b9eef5cb0b9fc087541524f7fb996764f4",
  "source_hash": "2feaa65feed9e8c66cbb8227e41a01eb4b1450cd0fa112548ae54e7ba9f80bce",
  "last_changed_at": "2026-05-29T05:43:14.651Z",
  "active_status": "active"
}

{
  "language": "en",
  "location": {
    "raw": "New York City",
    "city": "New York City",
    "region": "NY",
    "country": "United States",
    "is_remote": false,
    "confidence": 0.75
  },
  "salary_max": null,
  "salary_min": null,
  "inferred_at": "2026-06-06T20:22:15.746Z",
  "launch_scope": {
    "reason": "english_us_canada",
    "included": true,
    "language": "en",
    "location": {
      "raw": "New York City",
      "city": "New York City",
      "region": "NY",
      "country": "United States",
      "is_remote": false,
      "confidence": 0.75
    },
    "countries": [
      "United States"
    ]
  },
  "remote_policy": null,
  "salary_period": null,
  "workplace_type": "on_site",
  "salary_currency": null
}

{}

{
  "id": "d7b2cd49-f068-488b-9b0d-ad87c71adc4d",
  "team": "Product & Engineering",
  "title": "Full Stack Engineer",
  "jobUrl": "https://jobs.ashbyhq.com/Ajax/d7b2cd49-f068-488b-9b0d-ad87c71adc4d",
  "address": null,
  "applyUrl": "https://jobs.ashbyhq.com/Ajax/d7b2cd49-f068-488b-9b0d-ad87c71adc4d/application",
  "isListed": true,
  "isRemote": false,
  "location": "New York City",
  "updatedAt": null,
  "apiVersion": "ashby-non-user-graphql-v1",
  "department": "Product & Engineering",
  "publishedAt": null,
  "workplaceType": "OnSite",
  "employmentType": "FullTime",
  "secondaryLocations": []
}