Solutions Engineer

## The Role

We're hiring a **Solutions Engineer** to be the technical hand on the shoulder for the security and IT teams evaluating and rolling out Cerby. You'll sit between our customers and our product, turning a messy real-world access problem (the dozens of apps their identity provider can't touch) into a working, automated setup. This is a customer-facing engineering role for someone who likes the moment a blind spot a customer has lived with for years finally closes.

## What You'll Do

- Partner with prospects during evaluations: inventory the disconnected apps, map the access and lifecycle problem, and stand up a working proof on their own environment, not a slide
- Own technical proofs of concept end to end, from first call to 'it's in production'
- Translate security constraints (compliance requirements, least-privilege rules, change-control, nervous stakeholders) into a rollout that actually holds up
- Be the voice of the field inside Cerby: feed recurring friction straight to product and engineering
- Write the occasional reference architecture or onboarding playbook that saves the next customer a week

## What We're Looking For

- Experience in a customer-facing technical role (solutions/sales engineering, technical consulting, or a security/IT engineering role you can tell stories about)
- Hands-on comfort with identity and access: SSO, SAML/OIDC, SCIM provisioning, MFA, and the tooling (IAM/IGA/PAM) customers already run
- You can read a customer's environment on a call and sketch the rollout before it ends
- A clear writer and communicator who makes hard security plumbing feel simple to a mixed technical and business room

## Strong Advantages

Nice-to-haves, not strict requirements.

- Hands-on time with disconnected or legacy apps that never supported standard identity protocols
- Experience with browser-extension-based automation or RPA-style approaches to apps without APIs
- Comfort with scripting (Python, JavaScript) for glue and demos

## Why This Role Is Special

Cerby does something the rest of the identity stack can't, so the conversations are refreshingly concrete: you're not convincing a customer the problem exists, they've lived it. Your job is to show how much simpler it gets. You set how Cerby earns technical trust in the field.

## Location

Remote in the US.

## Next Steps

Tell us about one access or identity rollout you owned and how you knew you'd solved it. One real example beats a polished resume here.