Full Stack, Frontend, or Backend? How I Think About Role Fit

I get asked some version of this in almost every first call with a hiring manager: am I a full stack developer, a frontend developer, or a backend developer? The honest answer is that it depends on what the team needs, not what I would prefer to call myself.

As a Frontend Developer, I am most useful on teams that need React and Next.js interfaces that are fast, accessible, and hold up as the product grows: App Router, server components, design systems, and the kind of performance work that shows up in Core Web Vitals rather than a feature list.

As a Backend Developer, the value is in Node.js APIs, database design across PostgreSQL and MongoDB, and the unglamorous infrastructure, queues, caching, async jobs, that keeps an API responsive under real load instead of just in a demo.

As a Full Stack Developer, I am the person who can take a feature from a database migration through an API to a deployed UI without handing it off three times, useful on smaller teams, or when a feature genuinely spans both halves of the stack and a handoff would just slow it down.

None of these are a personality, they are a lens on the same underlying skill set: Node.js, React, Next.js, and AWS, applied wherever the team's gap actually is. If you are hiring for any one of the three, that is the conversation worth having.