Backend Software Engineer

About Get Whys

AI has made it much faster for go-to-market teams to create content, campaigns, and sales materials. But speed only helps if the work reflects what buyers actually think.

Get Whys helps teams check their work against insights from real B2B buyers. Those insights come from our proprietary buyer intelligence database, built from research interviews, and every one can be traced back to its original source.

We’re VC-backed and growing quickly—our ARR grew 10x in 2025. Our customers include Docusign, Intel, Commvault, Verizon, and Twilio. We’re a team of nearly 20 and are hiring across the company.

We’re a hybrid company, with hubs in Portland, New York City, Boise, and Bozeman. Our strong preference is to have someone in one of those hubs. We like working together, we take the work seriously, and we also expect people to have lives outside of it. We have artists, chefs, cyclists, dancers, and ultramarathoners on our team, and we’d love for you to bring yourself to it.

Location:

Hybrid — NYC, Portland, Boise, or Bozeman

Get Whys is looking for a Backend Software Engineer to help build the systems that power our product and connect Get Whys with the tools our customers already use.

You’ll work across backend services, APIs, integrations, and data pipelines, building systems that ingest, transform, synchronize, and serve data across our application and external platforms. That might mean building an integration with a platform like Salesforce, designing an API that powers a new product feature, or creating a pipeline that turns unstructured customer data into something our AI systems can reason over.

You’ll also help build the infrastructure behind our LLM-powered workflows and evolve our backend architecture as our product, customers, and data volume grow.

This role is ideal for someone who enjoys working across systems, making messy data useful, and designing reliable software in a fast-moving startup environment.

• Design, build and maintain backend services that power Get Whys’ core product.
• Build integrations with external platforms through APIs, webhooks and other integration patterns.
• Design systems for ingesting, transforming, normalizing, and synchronizing data between Get Whys and third-party systems.
• Own APIs, data models, and services that support customer-facing product features and internal tooling.
• Work with both structured and unstructured data, including pipelines that support search, analytics, and AI-powered workflows.
• Design reliable background jobs and asynchronous workflows for processing and moving data.
• Improve the reliability, performance, observability, and scalability of our production systems.
• Work closely with product and engineering to turn ambiguous product problems into pragmatic technical solutions.
• Help evolve our backend architecture as usage, integrations, and data volume grow.

• 4+ years of experience as a backend, platform, or infrastructure-focused software engineer.
• Strong proficiency with typescript and experience using it to build production backend systems.
• Strong experience designing, building, and maintaining backend services in production.
• Comfortable designing APIs, working with databases, and making thoughtful data-modeling decisions.
• Experience integrating with third-party platforms or APIs and working with concepts like webhooks, rate limits, retries, and asynchronous processing.
• Experience moving data between systems, including transforming, mapping, normalizing, or synchronizing data from different sources.
• Comfortable debugging distributed workflows and thinking about failure modes, idempotency, observability, and reliability.
• Ability to make pragmatic technical tradeoffs and work effectively in an early-stage environment.

• Healthcare, Dental, and Vision insurance (90% of your deductible, 75% of your dependents’)
• 401(k) with 3% company match
• Unlimited PTO
• 12 weeks paid parental leave
• 18 company holidays, with unlimited PTO
  • Our suggested minimum is at least 10 business days of PTO per year.
• We’re a historically remote company; NYC, Boise, Bozeman, and Portland are our first hubs, where we’ll have a hybrid office environment
  • We’ll always be remote friendly (e.g., no “X days in office”).
• Regular team- and company-wide in person gatherings.