Engineering and IT · Job description template
Full Stack Developer job description template
This role exists so that one person can own a feature across every layer, with no hand-off between frontend and backend. The full stack developer takes a feature from a rough idea to working software in front of customers, touching the database, the API and the screens. They are accountable for features that work as a whole, not just their part of them.
First-year outcomes
What should be visibly different a year from now. Results, not tasks.
- At least six customer-facing features are shipped end to end by this person, each used by real customers within a month of release.
- Features move from agreed scope to production in four weeks or less, tracked from ticket start to release date.
- Each feature ships with a short written spec, automated tests and a note in the changelog, so anyone on the team can support it.
- A new developer can run the whole product locally in one day using the setup guide this person keeps up to date.
The work
Recurring work
- Break a feature request into database, API and interface tasks and estimate them.
- Build each layer of a feature and connect them.
- Release features behind a flag where useful and check usage after launch.
- Fix bugs wherever they sit in the stack.
Projects
- Write and maintain the local setup guide and seed data.
- Add usage tracking to new features so the team can see if they are used.
- Remove an unused feature or old code path that slows the team down.
Decisions they own
- How to split a feature into small releases.
- Where a piece of logic belongs: database, server or browser.
- When a quick version is good enough to learn from customers.
People they work with
- The product owner, to shape the feature and agree what done means.
- The designer, to agree screens and edge cases.
- Support or customer success, to hear how released features are used.
Requirements
Essential on day one
- Has shipped working features that span a database, a server API and a web interface.
- Working skill in one backend language and one frontend framework, for example Node.js and React or Python and Vue.
- Can write SQL and design a simple data model.
- Uses Git and writes automated tests as part of normal work.
Helpful, but can be learned
- Your specific stack, if they know a similar one.
- Cloud hosting and deployment pipelines.
- Product analytics tools for checking feature usage.
How to assess it
One piece of evidence for each first-year outcome.
| Outcome | Evidence to look for |
|---|---|
| Six features shipped end to end and used | Ask them to walk through one feature they built alone from idea to release. Good answers cover the data model, API, screens and what happened after launch. |
| Scope to production in four weeks or less | Give a feature brief and ask them to split it into releases. Good candidates find a small first version that can ship in days and leave extras for later. |
| Spec, tests and changelog with every feature | Ask for an example spec or pull request description they wrote. Good work is short, names edge cases and links to tests. |
| New developer running locally in one day | Ask how they would make setup easier for the next hire. Good answers include one command to start, seed data and a written guide that is tested by someone new. |
Opening for the job ad
You will take features from a rough idea to working software that customers use, across the database, API and screens. In your first year, you will ship a steady run of complete features, each with tests and notes that let the rest of the team support it.
Turning this into an ad? See how to write a job ad that gets applicants.
Next: interview for these outcomes
Eight structured questions for this role, each tied to an outcome above.
Full Stack Developer interview questionsSimilar roles
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.