Software Engineer

{
  "content_hash": "93d9593602a7f39bfe883dc0ef456592d6350317e1aed1c274907b10ffed8ebc",
  "source_hash": "bfbbda268a1b9ec9c3d0cf7ce9ec30d2350315677f756f78c0099db96d6a3469",
  "last_changed_at": "2026-06-03T12:27:03.173Z",
  "active_status": "active"
}

{
  "language": "en",
  "location": {
    "raw": "Seattle, WA",
    "city": "Seattle",
    "region": "WA",
    "country": "United States",
    "is_remote": false,
    "confidence": 0.9
  },
  "salary_max": 170000,
  "salary_min": 130000,
  "inferred_at": "2026-06-06T20:01:43.739Z",
  "launch_scope": {
    "reason": "english_us_canada",
    "included": true,
    "language": "en",
    "location": {
      "raw": "Seattle, WA",
      "city": "Seattle",
      "region": "WA",
      "country": "United States",
      "is_remote": false,
      "confidence": 0.9
    },
    "countries": [
      "United States"
    ]
  },
  "remote_policy": null,
  "salary_period": "year",
  "workplace_type": "on_site",
  "salary_currency": "USD"
}

{}

{
  "lists": [
    {
      "text": "What You'll Do",
      "content": "\n<li>Write high-quality, production-ready TypeScript code for our backend services and APIs</li>\n<li>Design, build, and maintain scalable services within our TypeScript monorepo</li>\n<li>Model data, design schemas, and optimize queries in PostgreSQL</li>\n<li>Integrate with external systems including HRIS platforms, ticketing systems, and third-party APIs</li>\n<li>Build infrastructure for AI-powered features—prompt engineering, context management, and reliable AI system integration</li>\n<li>Build for production with attention to observability, monitoring, and testability from day one</li>\n<li>Participate in design discussions, code reviews, and technical decision-making</li>\n<li>Collaborate closely with product, design, and engineering peers to deliver solutions that drive real business value</li>\n"
    },
    {
      "text": "What We're Looking For",
      "content": "<div>\n\n<li>3+ years of professional software engineering experience, primarily in backend development</li>\n<li>Strong proficiency in TypeScript or willingness to ramp quickly if coming from similar languages (Java, C#, Python)</li>\n<li>Solid experience with relational databases—schema design, query writing, and performance basics</li>\n<li>Familiarity with API design patterns and building services that other systems depend on</li>\n<li>Ability to work effectively in ambiguity, prioritize well, and balance speed with maintainability</li>\n<li>Strong communication skills and genuine interest in understanding the problems you're solving</li>\n<li>Experience building AI-powered features or working with LLM APIs is a significant plus, though not required—this field is new enough that we're more interested in your curiosity and learning orientation than checking a box</li>\n\n</div>"
    },
    {
      "text": "Our Company Values",
      "content": "<p style=\"margin-top: 0pt; margin-bottom: 0pt;\"><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\">Our four values aren't aspirational. They translate into concrete operating tenets that shape how we make decisions every day.</span></p>\n<div>&nbsp;</div>\n\n<li><strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\">Beat Yesterday.</span></strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\"> We re-evaluate our own toolkit every quarter, because the workflows that made you effective three months ago may already be outdated. We act on 70% of the information rather than waiting for certainty. We timebox, execute, and iterate, getting work in front of real people quickly instead of polishing in isolation. And we own our output regardless of how we produced it. AI can get you 80% of the way there. Everything that goes out with your name on it is your responsibility to review, refine, and stand behind.</span></li>\n<li><strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\">Embrace Type 2 Fun.</span></strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\"> We take on hard problems and find meaning in the work, even when it's uncomfortable. We assume good intent and follow up directly rather than venting in side channels. We celebrate wins loudly and specifically, naming the actual behavior so the whole team learns what great looks like. We are on by default, because we owe it to each other and to our customers to be available beyond what a regular corporate job would demand. And we do unscalable things today that build scalable advantages tomorrow. Every white-glove dinner, every hand-built territory map, every late-night booth setup earns us the right to scale later.</span></li>\n<li><strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\">Stay Hungry, Stay Curious.</span></strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\"> We expect everyone to be the expert on AI in their function before anyone asks them to be. The landscape changes weekly. When you learn something, teach it. Learn enough about adjacent functions to ask good questions, including what your AEs are saying on calls, how brokers actually make money, and why a benefits committee pushes back on a deal. Ask the question you think is too basic, because in complex domains like benefits, the cost of a wrong assumption can be a lost account. And remember: curiosity without urgency is a hobby. Learning has to translate into action on a timeline that matches the opportunity.</span></li>\n<li><strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\">Act Like an Owner.</span></strong><span style=\"font-size: 11pt; font-family: 'Plus Jakarta Sans', sans-serif;\"> We say the uncomfortable thing early, raising missed commitments or quality gaps directly with the person within 48 hours. We surface problems when they're small, not the week they become a crisis. Customer-facing work gets priority, always. And we close the loop every time, because over-communication is a feature at our stage, not a bug.</span></li>\n"
    }
  ],
  "country": "US",
  "createdAt": 1780062033831,
  "updatedAt": null,
  "categories": {
    "team": "Engineering",
    "location": "Seattle, WA",
    "commitment": "Full-time",
    "allLocations": [
      "Seattle, WA"
    ]
  },
  "salaryRange": {
    "max": 170000,
    "min": 130000,
    "currency": "USD",
    "interval": "per-year-salary"
  },
  "workplaceType": "onsite"
}