Loading open roles
Loading open roles
Loading role
Recroots · posted 4 months ago
End-to-end technical implementations for enterprise customers: discovery, integration architecture, configuration, testing, go-live, and handoff to customer success
Integration engineering across customer identity ecosystems: Okta, Azure AD/Entra, AWS IAM, Google Workspace, SailPoint, ServiceNow, and other IdPs and IGA platforms
Deployment playbooks and configuration templates that make every subsequent implementation faster and more predictable
Migration plans for customers displacing legacy IGA platforms—mapping existing policies, roles, and workflows to Oleria’s architecture
Technical documentation: architecture diagrams, integration specs, runbooks, and troubleshooting guides that customer IT teams can operate from
Product feedback grounded in deployment reality—not feature requests, but patterns and evidence from customer environments that shape the roadmap
POC and proof-of-value environments that demonstrate Oleria’s capabilities against customer-specific identity challenges during the sales cycle
4–7 years in implementation engineering, solutions engineering, DevOps, or technical consulting for enterprise B2B SaaS—ideally in cybersecurity, identity, or cloud infrastructure
Hands-on experience with identity platforms: Okta, Azure AD/Entra ID, AWS IAM, Google Workspace, or similar. You understand authentication protocols (SAML, SCIM, OAuth/OIDC) and how enterprise identity ecosystems connect
Strong engineering skills: Python, PowerShell, or similar scripting languages. Experience with APIs, webhooks, and building integration code that runs in production
Experience building implementation automation: deployment scripts, configuration templates, testing frameworks, environment provisioning tools
You’ve worked in cross-timezone teams and know how to maintain momentum asynchronously—clear handoff documentation, proactive status updates, no surprises
You use AI tools daily to accelerate engineering work: generating code, analyzing configurations, drafting technical documentation, debugging integration issues
Strong documentation skills. The playbooks and runbooks you write are clear enough that another engineer can pick them up and execute without a phone call
You care about quality and repeatability. You don’t just get the deployment working—you make it work in a way that can be replicated at the next customer