Summary
✨ AI‑Generated
A Platform Engineer is sought to own the APIs and integrations connecting a modern software platform with customers' existing business systems. You will handle production-critical infrastructure, make architectural decisions in ambiguous situations, troubleshoot integrations, and take operational ownership when important systems require urgent attention.
Highlights
High-ownership engineering role with direct responsibility for critical APIs and integrations. The position offers substantial autonomy, exposure to complex systems, and the opportunity to solve ambiguous operational and technical problems with measurable business impact.
Description
Platform Engineer
The company is a Revenue Activation Platform: an agentic operating system for sales organizations.
Rather than passively recording call activity, the platform actively shapes downstream outcomes, converting observed selling behavior into targeted roleplay simulations, individualized coaching, and workflow interventions that measurably improve rep performance without introducing additional management overhead.
This role demands genuine operational ownership.
A candid illustration: if a late-night message reporting that a critical integration is down ahead of a 2,000-seat customer demo the next morning would feel like a burden rather than a call to action, this role is not the right fit.
You will own the APIs and integrations that connect the platform to every CRM, dialer, and communications tool in the customer's existing stack.
Work does not arrive as fully scoped tickets.
You will make judgment calls in ambiguous territory, such as determining how an OAuth flow should behave when a customer's identity provider exhibits undocumented behavior, and you will be expected to make those calls correctly, because you will be the domain expert in the room.
Production systems fail.
Rate limits will be reached ahead of major demos; webhooks will silently stop firing weeks after deployment.
When failures occur, the expectation is not to file a ticket and await triage.
You will diagnose the issue, communicate transparently with the affected customer, and ship the fix on an urgent timeline.
Role Overview
You will serve as the architect for two systems that must perform flawlessly in parallel: the company's public APIs and the integrations connecting the platform to the tools its customers already operate in.
On the API side, you will own design, versioning, and long-term maintainability end to end.
Every internal team and every external developer building against the platform will be building against architectural decisions you made.
On the integrations side, you will solve genuinely difficult distributed-systems problems: maintaining data consistency across systems that were never designed to interoperate, managing rate limits that activate at the least convenient moments, and sustaining synchronization guarantees through degraded behavior in customer CRMs.
You will work directly with the founding team to determine build priorities and evaluate which partnerships materially advance the business, through direct discussion rather than quarterly planning cycles.
Candidate Profile
Required qualifications:
Deep experience with API design patterns, versioning strategy, and architecting for long-term maintainability rather than the immediate releaseGenuine fluency in OAuth 2.0, OpenID Connect, and the broader discipline of securing data in transit between systems outside your controlSubstantial hands-on experience integrating against third-party SaaS APIs, including familiarity with the undocumented inconsistencies and nonstandard behaviors common across major platformsA demonstrated track record of end-to-end ownership in a fast-moving environment with minimal process guardrails
Preferred qualifications:
Prior startup experience, as an early employee or a founderExperience operating production systems on AWS with mature CI/CD practicesA shipped project of which you remain genuinely proud
