Full Stack Login Flow

Atlassian commonly features a "Full Stack Login Flow" problem in their interviews for full stack roles, testing frontend, backend, authentication, and network concepts. Despite extensive searches across Atlassian sites, forums, and interview repositories, no exact match for the full problem statement with those precise tags was found publicly available.[1][9]

Typical Problem Structure

This interview question generally asks candidates to design and implement a complete login system spanning frontend (e.g., React form with validation), backend (e.g., Node.js/Express API with JWT), authentication (secure hashing, sessions), and network flows (HTTP requests, CORS, error handling).[7][9]

Key requirements often include:

• User registration/login forms with input validation.
• Backend endpoints for POST /register, POST /login returning tokens.
• Secure token storage (HttpOnly cookies or localStorage with caveats).
• Network considerations like HTTPS, rate limiting, CSRF protection.

Common Examples

Input (JSON payloads): POST /register { "email": "user@example.com", "password": "P@ssw0rd123" } Output: { "message": "User created", "userId": 123 }.[4]

POST /login { "email": "user@example.com", "password": "P@ssw0rd123" } Output: { "token": "eyJhbGciOiJIUzI1NiIs...", "user": { "id": 123, "email": "user@example.com" } }.[3]

Constraints

• Passwords: 8-128 chars, alphanumeric + symbols; hashed with bcrypt (12+ rounds).
• Email: Valid format, unique, rate-limited (5 attempts/5min).
• Tokens: JWT expiry 1h, refresh tokens 7d; max payload size 1KB.
• Network: 200 OK on success, 400/401/429/500 with JSON errors; CORS for frontend origin only.[2][5]

Proprietary Atlassian problems like this are typically shared only during onsite interviews and not published, similar to other companies' internal coding challenges. For preparation, review OAuth flows and MERN/PERN stacks.[9]