About the role
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 You'll be the technical voice in the room when Socure sells our orchestration platform to banks, fintechs, marketplaces, and more, owning every technical conversation from first discovery through signed contract, and building the decisioning workflow that ships with the deal. What you’ll do You'll run point on 20+ active deals at any given time, partnered with an Account Executive. On a given week you are: Leading a discovery call with a Fortune 100 bank's fraud ops team, then translating what you heard into a solution design their architects will actually implement Negotiating integration architecture - REST vs. SDK, sync vs. async, endpoint-only vs. full orchestration with a technical buyer who has opinions and constraints (security reviews, model risk governance, carrier consent, latency SLAs) Co-authoring the mutual action plan with your AE, identifying the real blockers, and getting unstuck when a security review or legal redline threatens the close date Demoing our no-code decisioning platform to an audience that ranges from a VP of Fraud to a staff engineer and calibrating the story to both Escalating real customer
requirements into Product and Engineering, and pushing back on a prospect when what they're asking for isn't right for them What makes this role different from most SC jobs Most pre-sales SC roles stop at the solution design. This one doesn't. Almost all of the build happens in pre-sales. You're not just scoping the solution, you're configuring it inside the RiskOS Platform, our no-code decisioning platform. You'll orchestrate identity, fraud, and device signals across Socure's product suite into a live workflow: setting thresholds, wiring reason codes into branching logic, defining fallbacks and step-ups, and shipping a decisioning flow the customer can actually put into production. That means when a deal closes, the decision logic is already built. Your job then shifts to a clean handoff with the Post-Sales and Technical Project Management teams. Partnering tightly to get the customer live fast, cleanly, and without losing the context you built during the sales cycle. Our best deals close and integrate without a handoff gap, and that's because the Platform SC owns the technical narrative end-to-end and hands it off as a working system, not a slide deck. If you want a job where you design something on a whiteboard and then throw it over the wall, this is the wrong role. If you want to own the technical outcome from first call, through the build, through a successful go-live, keep reading. What we're optimizing for We hire for four things, roughly in this order: Grit and broad shoulders. Deals break. Timelines slip. A prospect's config blows up your sandbox plan the day before a demo. The best SCs on this team absorb chaos, keep momentum, and don't need to be rescued. Sales acumen. You understand that your job is to help your AE close revenue, not to be the smartest person in the room. You can read a deal, spot a stalled champion, objection handle, and know when to push vs. when to back off. Technical ability. You can read an API spec, sketch an integration flow on a whiteboard, reason about data pipelines and decisioning logic, and hold your own with engineering buyers. You don't need to have written production code recently, but you should be able to debug a Postman call, configure a no-code workflow, and have a point of view on system design. Fraud, risk, or identity experience.
