You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
ClickHouse

Sr. Software Engineer - RBAC & Authorization

  • Remote
  • 6+ years

Salary

$142,000 - 250,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The Access Control team sets up and enforces authorization across the company's cloud product. That covers the roles and permissions model, organization hierarchies, API key management, and the security boundaries that every product surface and customer tenant relies on.

The team recently shipped custom roles and fine-grained access and is now reworking the architecture to handle the largest enterprise customer structures.

Responsibilities

  • Design and build the next version of the authorization model, including multi-level organization hierarchies, workspace isolation, and resource-scoped roles.
  • Apply authorization checks consistently across all public and internal APIs.
  • Create tooling and migration pipelines that change live authorization models without downtime or disruption to customers.
  • Work with Product, Design, and Customer Identity teams to build permission management interfaces that feel smooth to use.

Requirements

  • At least 6 years of experience building security platforms, access control engines, or core backend services at scale.
  • Solid understanding of RBAC and ABAC policy models, fine-grained permission enforcement, multi-tenant isolation, API keys, and SAML/SSO.
  • Strong TypeScript and Node.js skills, with good schema design in PostgreSQL or other relational stores.
  • A record of running live customer data migrations and building systems where correctness is critical.
  • Experience from enterprise identity platforms, IAM security tools, zero-trust cloud infrastructure, or core authorization teams at large B2B SaaS companies would be a strong fit.

Conditions

The company is globally distributed and remote-friendly, with operations in more than 25 countries.

Time off is flexible in the US and more generous in other countries.

The company is growing quickly and is at start-up stage.

Benefits

  • The company contributes towards your healthcare costs.
  • Every new team member receives stock options in the company.
  • A home office setup allowance of USD$500 for remote employees.
  • Opportunities to meet colleagues in person at company-wide offsites.

Where you’d work

Fully remote

You can work from

  • United States

About the company

ClickHouse

  • Industry: SaaS

Also hiring in Dallas, United States, Austin, United States, Houston, United States and 14 more places

38 of their 47 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 21 checks run
  • 1 red flag

Still hiring?

14 checks

No red flags

How crowded?

7 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • TypeScript
  • Node.js
  • PostgreSQL
  • JavaScript
  • ClickHouse
Seniority
Senior
Type
Full-time
Equity
Equity offered
Industry
SaaS
Specialty
Backend
Show 7 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Senior
Experience
6+ years
Tech stack
  • TypeScript
  • Node.js
  • PostgreSQL
  • JavaScript
  • ClickHouse

Location

Work model
Remote
Region
United States
Remote from
  • United States

Compensation

Salary
$142,000 - 250,000 / year
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason