Senior Integration Engineer

OUR VISION

Equs is a company building privacy-first AI, identity, and trust infrastructure for the agentic era. The digital world was built around platforms, not people. AI is rewriting what software can do, and we have a narrow window to make sure that future puts the individual at the center rather than further behind. We start from one conviction: your digital identity should belong to you, travel with you, and give you real agency in how you show up online.

You set the rules, you hold the keys, and you benefit from your own data.

We are building toward that future across every layer it requires: the infrastructure that makes it possible, the standards that make it interoperable, and the experiences that bring it to life for the people who use it. We are early, and we are clear about what is built today and what is still ahead. The people who use what we build keep control of their own data, and we hold ourselves to that standard in everything we make.

We're taking the EQUS Developer Toolkit to organizations of all kinds, from banks and other regulated institutions to employers, education providers, public bodies and digital platforms, and every one of them needs someone technical on our side to get them live. This is our first dedicated integration hire and a hands-on, customer-facing role. You'll be the technical lead for each customer from the first architecture call to the first credential in production: designing the solution, connecting their identity and back-end systems, and guiding them through security review.

You'll bring what you learn back into the product and the docs, and help shape how integration works as the team grows. You may be required to work on other EQUS products over time. Your day-to-day includes, but is not limited to:

• Designing each customer's solution, turning use cases such as KYC status, employee or student IDs, qualifications, age checks, membership and AI-agent payment mandates into a Developer Toolkit design (issuance and presentation flows, wallet model and build method) that the customer's architects can sign off
• Running technical onboarding, provisioning sandbox and production tenants, issuing client credentials, setting up Issuers, Verifiers and credential schemas with the customer, and enabling and tracking on-request features such as the Web Wallet, AP2 agent flows and quota increases
• Connecting customer identity systems, guiding IAM teams through Bring Your Own IdP (OpenID Connect), Authorization Server registration and OAuth client-credentials setup in both directions
• Getting back-end integrations live, specifying and reviewing each customer's Attribute Provider endpoint and helping their engineers debug using request IDs, error codes and rate-limit headers
• Supporting front-end teams as they embed our UI within strict security policies and allowed-origin rules, apply their branding, and enable the browser Digital Credentials API where devices support it
• Leading EU Digital Identity Wallet readiness, from moving Verifiers to X.509 and securing registration certificates from national Registrars to configuring trusted roots
• Owning the technical side of security and procurement, answering due-diligence questionnaires and joining security reviews using our data-handling, encryption, DPA and TOMs documentation
• Supporting business development in technical sales conversations, helping prospective customers understand what an integration involves and helping us close our first deals
• Acting as the customer's voice to product, logging and prioritizing the gaps that block deals and working with our engineering team and partners on fixes
• Making every integration faster than the last, writing quick starts, help-center articles, sample code and a reusable customer integration pack with sector variants, including a flow decision tree, security answers and a go-live checklist

You combine deep technical skill with real empathy for customers, and you're as comfortable with a bank's IAM team as with a startup's two developers. You're fluent in OAuth 2.0 and OpenID Connect and can work out why a token is rejected, you can read an OpenAPI spec and write enough back-end code to build sample integrations, and you understand PKI well enough to untangle a certificate chain.

You write clearly, whether it's an integration design, a security answer or public documentation. You are comfortable with…