Posting record
Open 13+ days
- Contentpass.jobs.personio.com's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Contentpass.jobs.personio.com, so its true age is longer.
Last checked Nov 5, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
The Mission
At contentpass, we are on a mission to save independent journalism and the free web. We believe that privacy is a fundamental right and that quality content deserves to be paid for without selling user data. Our "Pur-Model" enables over 700 publishers to offer their readers a choice: consent to tracking or browse completely ad- and tracking-free for a small monthly fee.
Your Role: The Heart of the Product
At contentpass, we often say that "the OIDC is the product, and the rest is glue." Our OIDC service is the central nervous system of our entire operation. It doesn't just handle logins; it manages the state of every single user interaction, subscription, and access right across hundreds of websites.
We are looking for a Senior Backend Engineer who wants to take ownership of this core infrastructure. You wonât just be maintaining a library; you will be architecting the future of how users interact with the paid web. We have a massive roadmap ahead, and you will be the one building the bridge to the next generation of contentpass.
What youâll do
- Architect & Scale: Lead the development and scaling of our central OIDC provider.
- OIDC Federation: Implement and manage integrations with other OIDCs and Social Logins, allowing for a seamless "login once, browse everywhere" experience.
- Extend Subscription Logic: Design and implement complex subscription mapping and entitlement logic that goes far beyond simple "active/inactive" states.
- Single-Article Payments: Build the foundation for granular payment models.
- Security & Privacy by Design: Ensure that our identity service remains a fortress for user data, strictly adhering to GDPR and the highest security standards.
- Collaborate: Work closely with our SDK and Frontend teams to ensure the "glue" connects perfectly to your core service.
Your profile
- Deep OIDC/OAuth2 Expertise: You donât just use libraries; you understand the underlying protocols, flows (Authorization Code, PKCE, etc.), and security implications.
- Backend Mastery: You are a seasoned developer, ideally with strong experience in TypeScript/Node.js .
- Identity Experience: You have worked with Identity Providers (IdPs) like Ory Hydra, Keycloak, or Auth0, or have built custom identity solutions from scratch.
- Product Mindset: You understand that technical decisions impact the business. You enjoy thinking about how "Identity" can enable new features like micro-payments.
- Security First: You have a "security-by-default" mindset and experience with JWTs, encryption, and token management.
- Language: Fluency in English (German is a plus, but not required).
Why us?
- Impact: You are working on one of the most critical parts of our company.
- Flexibility: We are a remote-first company. Work from our beautiful office in Berlin or from your home office anywhere in Europe.
- Growth: A high degree of autonomy and the chance to shape the technical roadmap of our core product.
- Purpose: Join a team that values privacy, independence, and the future of digital publishing.
- Equipment: The hardware you need to do your best work (MacBook, etc.).
Something wrong with this posting?