Implement RBAC in FastAPI with a JWT role dependency

WHAT THIS TESTS: This tests your understanding of FastAPI dependency injection and your ability to separate cross-cutting concerns like authentication and authorization from business logic. The interviewer wants to see that you know how to compose dependencies, handle security schemes, and return semantically correct HTTP status codes. They also care whether you treat roles as claims inside the JWT rather than querying a database on every request.

A GOOD ANSWER COVERS: Four things in order. First, a base dependency that extracts the bearer token from the Authorization header, decodes the JWT, and returns a user object or dictionary containing at least the role field. Second, a parameterized authorization dependency that depends on the first one, accepts a list of allowed roles, compares the user's role against that list, and raises an HTTPException with status code 403 when the role is missing. Third, wiring the dependency into the path operation using FastAPI Depends, keeping the route handler clean and focused on its core task. Fourth, explaining why 403 is returned for forbidden roles versus 401 for missing or invalid authentication, and noting that dependencies are cached per request so nested dependencies do not re-run.

COMMON WRONG ANSWERS: Parsing the Authorization header manually inside the route handler instead of using a reusable dependency. Hardcoding the string admin inside the route rather than parameterizing allowed roles. Returning 401 Unauthorized when the token is valid but the role is insufficient; that should be 403 Forbidden. Attempting to query a user database inside the route to fetch roles when the role is already encoded in the JWT. Writing the JWT verification logic inline for every protected route instead of composing shared dependencies.

LIKELY FOLLOW-UPS: How would you handle multiple roles or hierarchical permissions like editor versus admin? What happens if the JWT is expired or malformed, and where do you catch that? How would you test this dependency in isolation using FastAPI dependency overrides? Would you store roles in the JWT payload or only a user ID, and what are the trade-offs? How do you handle route-level versus router-level versus global dependency application?

ONE CONCRETE EXAMPLE: Imagine a route DELETE /users/{user_id}. You define async def get_current_user which decodes the JWT and returns a User object with a role attribute. Then you define require_admin which depends on get_current_user, checks if current_user.role is not admin, and raises HTTPException with status code 403 and detail Admin access required. Finally, the route is declared with dependencies set to Depends require_admin in the decorator or function signature. This keeps the delete logic free of authorization boilerplate.

Source: fastapi.tiangolo.com