Senior Backend Engineer (Access Management) at Cerby
—
Jul 6, 2026
—
Jul 21, 2026
What this job asks for AI summary
A senior backend engineering role at a cybersecurity SaaS company, focused on building and scaling systems that handle authentication, authorization, and identity management — including OIDC, SAML, SCIM, and IAM concepts like RBAC and ABAC. The work involves distributed cloud architecture, REST API development, and security-conscious engineering practices. The role suits an experienced engineer comfortable mentoring others and taking ownership across the full development lifecycle.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 3,400 people nationally plausibly meet what this posting asks for (software developers). range 1,400–5,100
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (13)
The job title is not stated in the posting; 'Unspecified' is used for advertised seniority. The scope and 5+ years of experience requirement, mentoring duties, and end-to-end ownership clearly support a Senior classification.
Authentication/authorization experience (OIDC, SAML, SCIM, JWT) is listed under the required qualifications block with 3+ years demanded at the capability level; that years figure is captured at the role level (the overall years minimum reflects the higher 5+ year overall gate).
Backend language requirement is Python or Go ('or equivalent') — Go is captured as an alternative to Python.
Cloud platform is required but no specific provider is named; AWS, Azure, and GCP are listed as alternatives reflecting the open-ended 'or equivalent' framing.
SQS is called out as an example of queuing/messaging platforms; it is the only named tool and is treated as the canonical representative of that hard gate.
S3 is listed as the named distributed data store; MySQL/PostgreSQL are named as interchangeable relational options; Redis/DynamoDB as interchangeable key-value options.
OpenTelemetry and Datadog appear explicitly as 'a plus' within the required section — treated as preferred.
Okta and EntraID appear under the 'Nice to have' section as IdP integration experience.
SOC 2, GDPR, and HIPAA appear under 'Nice to have'; HIPAA is omitted as a separate skill since it is grouped with SOC 2/GDPR under the same compliance-frameworks bullet.
Prior cybersecurity experience is noted as 'a plus' in the required section — not extracted as a discrete skill since it names no specific technology.
No compensation figures are provided in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): SaaS application development.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.