Skip to content
Kombo

Senior Pre-Sales Engineer (NYC)

New York OfficeOnsite · United States
Senior · FullTime · Commercial
POSTED 14 SEPTVERIFIED 7H AGO
Apply Ask
Role
56 days opentrue age
Posted 14 Sept
Payats field
$180k–220kposted
▲ +3% vs market median $195k
$170k$223k
Market p25–p75
$170k–$223k
New York · n=269 · 365d to 6 Nov
CompanyKombo →
18open roles
Opened · 30d
+0
Closed · 30d
−0
3d of snapshots · 30d window
Market
17,060open · Senior Software engineering
Opened · 7d
+9135% of open
All software engineering
75,151open
All tracked boards · live 10 Nov · n=17,060

Location: New York City (On-Site, 5 days)

About Kombo

Kombo is the unified API for ATS, HRIS, LMS and payroll systems. Instead of spending months building integrations one by one, companies integrate once with Kombo and connect to 200+ platforms instantly.

Since Y Combinator (S22), we've grown to 8-figures in revenue, 80+ team members, and raised $30M+ from YC, Volition Capital, and Acadian Ventures. We're tripling the team and revenue this year. And we move upmarket, with larger, more complex deals and sophisticated buying committees.

The Role

We're hiring our US-based Pre-Sales Engineer to own the technical relationship with customers, from first sales call through successful implementation. The role is roughly 70% pre-sales / 30% post-sales, but the split is about time, not identity: We need someone who instinctively runs discovery and shapes deals, not someone who's comfortable in a technical conversation and happens to also do pre-sales.

You'll work closely with our Sales team, and our CRO to close deals and with Product/Engineering to turn customer insights into product improvements.

This is a builder role. You'll help grow our US GTM function and create the playbooks, while carrying deals yourself.

What You'll Do

Own the technical sales cycle

Run technical discovery that uncovers the business objective behind a request, not just the request itself, including in domains we haven't fully mapped yet, where you'll need to hold credibility without pretending to have answers you don't

Create technical proposals covering architecture, security, and implementation approach

Partner with AEs on complex, multi-stakeholder deals with engineering and executive stakeholders

Drive implementations to go-live for complex projects

Own the technical relationship from POC through signed contract through production deployment

Create the supporting technical assets as you go: demo environments, Postman collections, integration guides, troubleshooting documentation

Help Build the US Pre-Sales Function

Document repeatable playbooks for discovery, scoping, and implementation

Feed customer insight back to Product/Engineering in a way that shapes the roadmap without overpromising on it

What We're Looking For

3+ years in a technical customer-facing role at a B2B SaaS company, with genuine pre-sales ownership (discovery, champion-building, deal shaping) - not just implementation with some pre-sales overlap

Track record working complex deals with technical and non-technical stakeholders - consistent deal value of $100k-150k+

Strong communication skills: you can whiteboard architecture with engineers and translate value to executives

Hands-on with APIs - you can read documentation, ideally write sample code, and debug integration issues

Comfort with ambiguity and building things from scratch

What Success Looks Like in the First 6 Months

You've built and closed with at least one genuine technical champion in an enterprise account, not just a friendly technical contact

You've built real credibility with AEs and prospects in a domain (e.g. HRIS, ATS) you likely didn't know deeply on day one

You've built at least one reusable playbook, template, or asset (e.g. discovery framework, POC scoping doc, demo narrative) that other people on the team now use without you

You can point to your influence on ARR, deal velocity, or conversion

You're a trusted second read for AEs on deal strategy, and go far beyond just a technical resource they loop in when asked

How We Work

Ownership end-to-end. A customer isn't "handed off" when the contract is signed - you own the relationship from first technical call through successful go-live and beyond. Problems that surface in implementation are your problems to solve, not someone else's.

Written thinking. We use long-form documents to make decisions and share context. You'll write implementation plans, technical briefs, and customer-facing documentation that help the whole team move faster. If you prefer talking through everything in meetings, this isn't the right fit.

Source · KomboFirst seen 2 NovOriginal ↗