A SaaS demo can show the right dashboard while its API still returns another customer's records. When hiring an engineer, ask them to explain how access is enforced on the server and tested outside the interface.
This review is for founders choosing someone to build a product with organisations, invitations or customer data. It helps assess practical experience without pretending that a short interview replaces a security assessment.
What counts as permissions experience in SaaS engineering?
Authentication establishes who is making a request. Authorisation decides whether that identity may perform a specific action on a specific resource. The engineer should connect that decision to trusted membership and ownership records.
Ask which paths can reach the same data: the dashboard, exported files, background jobs, search, support tooling and AI actions. A check in one controller does not automatically protect every other path.
Use a cross-customer scenario during the review
Describe two organisations with separate documents and billing settings. An employee belongs to both but has different responsibilities in each. Then remove their membership from one organisation while an earlier background task is waiting.
| Scenario | Evidence to discuss | What it reveals |
|---|---|---|
| Change organisation in a request | Server verifies active membership | Trust boundary understanding |
| Download an old export | Download checks current permission | Coverage beyond screens |
| Process a queued AI task | Defined execution-time authority | Handling of delayed actions |
| Invite an outside user | Scoped role and acceptance process | Membership lifecycle design |
There may be several valid implementation choices. What matters is whether the engineer states the rule, applies it consistently and can demonstrate rejection of a forbidden action.
Ask for failure evidence rather than security adjectives
Request a redacted example of a permission regression test or an explanation of a defect they found and corrected. If confidentiality prevents sharing code, a recreated fixture is sufficient for discussion.
Useful tests include changing resource identifiers, replaying an old request and exercising a non-admin role. Ask how denied requests appear to support staff without exposing sensitive records in logs.
Database policies can add another enforcement layer, but they have their own execution contexts and limitations. Avoid treating a named database feature as proof that an application is secure. The PostgreSQL row security documentation is a useful primary reference when reviewing a design that relies on that mechanism.
Match the hiring decision to the product boundary
A pilot with one internal team has a different review burden from a customer-facing multi-tenant service. Record the intended data boundaries, external integrations and high-impact operations before estimating the work.
My full-stack product work shows application context. For your project, request evidence tied to the actual roles and resources users will manage.
Is hiding buttons enough to enforce permissions?
No. The server must reject unauthorised requests even when the interface is bypassed.
Should a founder conduct the security review alone?
Use this interview screen to identify evidence, then involve qualified review for the product's actual exposure.
What should a pilot include?
Include permitted and rejected actions for each important role in your technical review brief.