Krishna Dey Shipped · Core product systems
OAuth 2.0 Device Authorization Grant
Researched and implemented the OAuth 2.0 Device Authorization Grant (RFC 8628) as reusable authentication infrastructure, built for the Gmail integration but designed to back "Login with SpotDraft" from any constrained or limited-input client.
Software Engineer
Shipped.
Gmail frontend integration built by another engineer; this covers the backend device-authorization capability behind it.
Challenge
SpotDraft needed secure authentication for external clients where a conventional embedded web login was not a good fit, starting with the Gmail integration, without hard-coding a Gmail-specific auth path.
Approach
I researched RFC 8628 and proposed the Device Authorization Grant as the right model, then implemented the internal device-authorization endpoints and use cases: device and user code issuance, a separate-browser verification step, and client polling that handled authorization-pending, slow-down, denial, and expiry states before issuing tokens.
Outcome
The flow shipped as the backend behind SpotDraft's Gmail login experience (the Gmail frontend itself was built by another engineer) and as reusable authentication infrastructure other constrained clients could adopt without rebuilding the flow.
What it taught
Building the standard protocol instead of a Gmail-specific shortcut meant the same authentication path could be reused the next time a constrained client needed it, instead of becoming one-off integration debt.
More projects
All projectsClickWrap captures recorded acceptance of terms in-product — a checkbox, link, or agreement viewer on a website, app, or signup flow — without sending the agreement through a full negotiation and e-sign ceremony. We explored that product shape as a 2023 hackathon with Sanket Mishra and Punit Batra; another team later shipped it. The shipped product has surpassed SpotDraft's internal target of more than $1M in revenue impact.
An Amazon EFN chapter focused on internal fulfillment systems, requirements engineering, data pipelines, marketplace-launch automation, and high-scale inventory services where correctness and latency both mattered.
A 3-month Google Summer of Code 2019 contribution to Chapel, a parallel/distributed-computing language: built its UnitTest module from scratch into the standard library, including locale-aware test configuration for a language whose whole point is running across distributed compute nodes.