PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Software Engineering Fundamentals/Microsoft

Explain how browser authentication works with JWTs

Last updated: Mar 29, 2026

Quick Overview

This question evaluates understanding of browser-based authentication with JWTs, covering token storage trade-offs, how tokens are sent with requests, refresh token/session renewal patterns, common security risks (XSS, CSRF), and differences from traditional server-side sessions.

  • hard
  • Microsoft
  • Software Engineering Fundamentals
  • Software Engineer

Explain how browser authentication works with JWTs

Company: Microsoft

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: hard

Interview Round: Onsite

Explain, at a high level, how authentication typically works in a browser-based web app when using JWTs. Cover: - Where the token is stored (e.g., memory, `localStorage`, cookies) and trade-offs. - How the browser sends the token on subsequent requests. - Refresh tokens / session renewal patterns. - Common security risks (XSS, CSRF) and mitigations. - How this differs from traditional server-side sessions.

Quick Answer: This question evaluates understanding of browser-based authentication with JWTs, covering token storage trade-offs, how tokens are sent with requests, refresh token/session renewal patterns, common security risks (XSS, CSRF), and differences from traditional server-side sessions.

Related Interview Questions

  • Explain OOP design and API rollout - Microsoft (hard)
  • Explain a project deeply - Microsoft (medium)
  • Explain Python, Java, and Memory Management - Microsoft (medium)
  • Compute precision/recall from a flaky top-k API - Microsoft (medium)
  • Explain deadlock cases and how to prevent them - Microsoft (medium)
Microsoft logo
Microsoft
Feb 11, 2026, 12:00 AM
Software Engineer
Onsite
Software Engineering Fundamentals
4
0
Loading...

Explain, at a high level, how authentication typically works in a browser-based web app when using JWTs.

Cover:

  • Where the token is stored (e.g., memory, localStorage , cookies) and trade-offs.
  • How the browser sends the token on subsequent requests.
  • Refresh tokens / session renewal patterns.
  • Common security risks (XSS, CSRF) and mitigations.
  • How this differs from traditional server-side sessions.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More Software Engineering Fundamentals•More Microsoft•More Software Engineer•Microsoft Software Engineer•Microsoft Software Engineering Fundamentals•Software Engineer Software Engineering Fundamentals
PracHub

Master your tech interviews with 8,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.