Why Socure?

Socure is building the identity trust infrastructure for the digital economy — verifying 100% of good identities in real time and stopping fraud before it starts. The mission is big, the problems are complex, and the impact is felt by businesses, governments, and millions of people every day.

We hire people who want that level of responsibility. People who move fast, think critically, act like owners, and care deeply about solving customer problems with precision. If you want predictability or narrow scope, this won’t be your place. If you want to help build the future of identity with a team that holds a high bar for itself — keep reading.

ABOUT THE ROLE

Socure’s Partner Ecosystem brings third-party data and decisioning partners into RiskOS. Every partner we onboard has to be integrated cleanly, operated reliably, implemented correctly in customer environments, and understood well enough that our Solutions and Sales teams can put it to work. This role owns the technical side of all of it.

You will be the technical point of accountability for the RiskOS partner ecosystem. You will align with partners on an integration approach. Solutions teams come to you when an implementation doesn't behave. You will define scope, requirements, and priority for the Partner Integration engineering pod. Internal teams come to you to understand what a partner product actually does and when to use it.

This is not just a coordination or ticket-writing role. You will personally run partner API discovery, write the specs the pod builds from, sit in the middle of live troubleshooting, and own the documentation the rest of the company depends on. You will drive the partner engineering pod's roadmap and execution without managing the engineers directly — technical credibility, clarity, and relationships are how the work gets done here.

It is also a role that will grow. As our partner marketplace takes shape, you will be the technical driver behind it: defining what it takes for a partner product to be integrated and consumed at scale.

WHAT YOU'LL DO

Own partner integrations end to end

• Own the program for every new integration: discovery, technical scope, specs, sequencing, and launch readiness — and the pod's roadmap, priorities, and capacity tradeoffs that deliver it.

• Establish reusable integration patterns — authentication, data mapping, error handling, retries, fallbacks — so each new partner integration is faster than the last.

• Work with Product and Legal/GRC so contractual and compliance constraints shape the design up front rather than surface as rework.

Be the technical counterpart to our partners

• Serve as the primary technical contact for partner engineering and solutions teams, from API discovery through release and deprecation cycles.

• Evaluate partner APIs, data models, SLAs, and support posture to identify the optimal integration path — and push back where their proposed pattern creates fragility, latency, cost, or compliance risk.

• Define what "integration-ready" means for the marketplace — technical requirements, certification, acceptance criteria — and eventually hold that bar with partners who build into our platform themselves.

Make partner products succeed in customer environments

• Work with pre-sales Solutions to help them understand partner products: what they do, what they require, what they cost, and what they can't do.

• Work with post-sales Solutions and Implementation to ensure correct configuration across sandbox and production, and flag workflow designs that will produce poor decisioning outcomes.

• Build the enablement material that lets Solutions teams handle routine cases independently.

• Own triage and resolution for integration escalations, define monitoring requirements for integration health, and run a recurring audit cadence that produces remediation rather than a list of known issues.

Own documentation and product expertise — and scale it with AI

• Own the technical documentation library: integration specs, API references, configuration guides, and troubleshooting runbooks. Treat documentation drift as a defect.

• Use AI aggressively to draft specs and documentation — with the judgment to catch hallucinated behavior and verify against source API docs — and build repeatable AI patterns so throughput isn't bound by your calendar.

• Develop working expertise in every partner product and act as the internal explainer for Sales, Solutions, Product, and Support.

WHAT YOU BRING

• 5+ years in technical program management, technical product management, solutions architecture, solutions engineering, or integration engineering, including direct ownership of external-facing technical work.

• Demonstrated ability to drive engineering execution without direct authority. You have owned a team's roadmap and delivery as an individual contributor and made it work through influence and credibility.

• Deep, practical fluency with REST APIs, authentication patterns, webhooks, data mapping and normalization, and the failure modes of third-party dependencies. You can read an API doc set and immediately identify what will break in production.

• Strong debugging instincts across distributed systems. You are comfortable in logs, traces, and payloads, and can isolate whether a problem is ours, the partner's, or a configuration issue.

• Proven ability to work directly with external technical teams — holding a firm technical position, saying no well, and keeping the relationship intact.

• Genuine people skills. This role runs on relationships: with partners, with engineers you don't manage, with Solutions teams under customer pressure, and with leadership. Technical strength alone will not carry it.

• Exceptional written communication. The specs and documentation you produce are what other teams depend on; writing is a core competency here, not a nice-to-have.

• Hands-on experience using AI tools in your actual workflow, with the discipline to verify output rather than trust it. You should be able to describe patterns you've built that made recurring work faster for more people than just yourself.

• Comfort moving between a partner architecture discussion, a customer implementation escalation, and an internal enablement session in the same day.

PREFERRED QUALIFICATIONS

• Background in identity, fraud, risk, KYC/KYB, credit, or adjacent data-provider ecosystems.

• Experience integrating and operating many third-party data vendors at scale, including managing vendor API versioning and deprecation.

• Experience building or scaling a partner marketplace, app store, developer platform, or partner certification program.

• Familiarity with decisioning or workflow orchestration platforms and how data products are composed within them.

• Experience working alongside pre-sales and post-sales organizations in B2B enterprise SaaS.

• Exposure to the compliance and contractual dimensions of third-party data use: data rights, permissible purpose, retention, and audit requirements.

• Prior hands-on engineering background, even if you've since moved into solutions, program, or product work.

Socure is an equal opportunity employer that values diversity in all its forms within our company. We do not discriminate based on race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.
If you need an accommodation during any stage of the application or hiring process—including interview or onboarding support—please reach out to your Socure recruiting partner directly.

Follow Us!

YouTube | LinkedIn | X (Twitter) | Facebook