Skip to main content
PProfileMatch

41 open Full Stack Developer jobs

Real, currently-open Full Stack Developer roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Full Stack Developer guide.

Hiring snapshot for Full Stack Developer

The most common locations right now are San Francisco Bay Area (5), San Francisco (HQ) (4), New York City (3). 13 of these 41 roles (32%) list a remote option. 22 were posted in the last two weeks. By team, the biggest groups are Engineering (36), Data & AI (4).

Computed from the 41 open listings shown below.

Guide: working as a Full Stack Developer

Full-stack developers own features end to end, from the database table and API route to the screen a user clicks. In smaller teams they may also set up deployment and monitoring. The value of the role is shipping a complete slice of functionality without hand-offs, so judgement about where logic belongs matters as much as depth in any one layer.

Core skills employers look for

  • A UI framework (React, Next.js)
  • A server runtime (Node, Java, Python)
  • SQL and an ORM
  • Sign-up, login and session flows
  • Deploying to a cloud host
  • Testing a feature across layers
  • TypeScript on client and server
  • Environment config and secrets

How to stand out when you apply

  • Ship one complete product rather than many tutorials: user sign-up, a real database, a few meaningful features, deployment, and a note on what you would change next.
  • Describe a feature you carried across every layer, naming the schema change, the endpoint, the UI and how you tested the full path, since that is the role in miniature.
  • Show judgement about constraints, such as sharing types between client and server or choosing server rendering for a page that must be indexed by search engines.
  • Keep the delivery story visible: a CI pipeline that runs tests, preview deployments for each change, and environment variables kept out of the repository.

What the interviews usually cover

Expect breadth: a coding problem, frontend questions on components and state, and backend questions on APIs, SQL joins and authentication. Many processes include a take-home or live task to build a small feature with both a UI and an endpoint. Interviewers also probe judgement, for example whether validation belongs on the client, the server or both, and why.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company