Developer Support Engineer

Berlin, On-site
· Full-time

€70,000-€90,000 + equity

Full-time

Kombo (YC S22) is building a unified API that saves engineering teams hundreds of hours by integrating dozens of HRIS, ATS, and Payroll systems into one API.

We're looking for a Technical Support Engineer to provide exceptional technical assistance to our rapidly growing customer base, debug complex integration issues, and help shape the foundation of our support function. You’ll be the technical bridge between our customers and our product / engineering teams.

Kombo is building the unified API for HR, payroll, and recruiting systems. Instead of companies spending months integrating with dozens of different systems, they can integrate once with Kombo and instantly connect to over 160 platforms. We abstract away the complexity of handling different data schemas, authentication methods, and API quirks.

Since going through Y Combinator in 2022, we’ve:

• Raised $30M+ of funding from Y Combinator, Acadian Ventures, 468 and other investors

• Grew from 0→ $12M+ ARR and hundreds of customers (growth-wise among the ~top-5% of VC-backed startups)

• Scaled to process data for the equivalent of 10% of Germany's workforce

• Grew to a team of 65+ team members (pictures!) in 2x offices

Kombo is an international company by default. We operate across two main hubs (NYC and Berlin) and work with a globally distributed team representing 20+ nationalities
.

At Kombo we care A LOT about excellent support for our customers to a degree that is unusual. We do so because fundamentally we view excellent support as a competitive advantage.

How this looks like in practice is that

• we win G2 badges for best support in our category

• we get customer love for our support weekly and even frequently hear that our support is the best that our customers ever experienced (across all products they have used)

• "Support quality" is one of the top 3 reasons companies choose Kombo

As we scale our presence in the US market, our current setup (support team rotating to the NYC office) is reaching its limits. To maintain our standard, we’re extending our existing team into the US and Germany.

In this role, you’ll act as a support engineer, not a support agent — solving most issues directly and collaborating with our engineering team on more complex ones.

• Troubleshooting & Debugging: Investigate API integrations, data-sync issues, authentication flows (OAuth, API keys), and provider-specific edge cases.

• Customer Guidance: Assist customer engineers via Slack, email & occasional video calls — clear, concise, and technical.

• Internal
  
  Collaboration:
  
  Work closely with Product & Engineering to elevate bugs, relay feedback, and shape fix priorities.

• Knowledge Building: Create and maintain internal / external docs and guides based on recurring topics.

• Process Improvement: Set up better tooling, automation, and reporting to scale our support capabilities.

• Debugging why new hires aren’t syncing correctly from a customer’s ATS (via Kombo) and fixing a mapping edge case.

• Helping a customer engineer resolve an OAuth 2.0 connection flow issue.

• Spotting a commonly misunderstood API parameter and collaborating with Engineering to improve docs or design.

• Building dashboards or alerts to proactively monitor integration health.

• Implement smaller new features across the codebase based on your findings

Tech you’ll work with: APIs (REST + SOAP + OAuth), Node.js, Type Script, SQL, GCP (logs & monitoring), and various HRIS / ATS / Payroll systems + Kombo’s own troubleshooting tools.

You’re a technically adept problem-solver with strong communication skills and a builder’s mindset.

You might be a great fit if you:

• Have a solid technical background (Software Engineer, Support Engineer, Solutions Engineer, etc.) and enjoy debugging APIs & integrations

  • You can navigate large, unfamiliar codebases. You're comfortable digging into code you didn't write and don't yet fully understand, tracing data flows and logic across a large production codebase to find the root cause.

  • You can write production code. You've shipped code to production…