Frontend engineer job description template

A frontend engineer

JD that is not generic.

One short, opinionated template. 280 words, not 1,800. Below: a side-by-side teardown of the typical job description and what to cut, the template ready to copy, and a one-click button to post it via Picked.

One-click post

Do not want to copy-paste? Skip the document and let us post a role with this template plus your specifics. ~30 seconds.

Use this template →

$0.99 per AI-vetted candidate. First 50 free.

The teardown

Side by side. Cut everything in red.

A typical JD · 1,847 words

scroll-killing

Frontend engineer (typical posting)

About us · cut

Founded in 2019, ACME Inc is a fast-growing, mission-driven, customer-obsessed scale-up empowering the modern hiring loop. We have been featured in TechCrunch, won several awards, and our culture has been recognised by Best Places to Work.

About the role · cut

You will be joining a passionate, collaborative team of self-starters in a dynamic, fast-paced environment. We are looking for a high-performing professional who is excited by ambiguity and ready to wear many hats.

Responsibilities · cut

- Collaborate with cross-functional partners to align stakeholders - Drive impact across the business - Champion excellence - Be a culture ambassador for the team - Wear many hats - Lots more bullets like this

Requirements · cut

- 5+ years of professional experience - Strong communication skills - Self-starter - Team player - Comfortable with ambiguity - Bachelor's degree or equivalent

Nice to haves · cut

- A laundry list of every tool anyone on the team has ever used - MBA / advanced degree - Previous experience at a high-growth startup

Benefits · cut most of this

- Competitive salary - Equity - Health, dental, vision - Unlimited PTO (which no-one takes) - Free snacks (in office) - Annual offsite - Pet-friendly office - Pinball machine

Picked template · 280 words

ships

Senior frontend engineer · London or remote

We are hiring our fourth frontend engineer. You will own the candidate-facing app end-to-end (currently: the onboarding and assessment flows, used by about 12,000 candidates a month). The team is five engineers and one product designer who pairs on most surfaces.

One paragraph, not six sections

Context. What the role owns. Team size. How you ship. Everything else is noise until the interview.

Skip the company overview

They found your JD. They can find your website. They will skim it. They will learn about you in the interview if they are still interested.

Bullets only where they earn their place

A list of "responsibilities" tells the candidate nothing they cannot guess.

Post the comp band

You will filter the wrong people anyway. Either pre-application or after offer. Pre is cheaper.

The template · plain text

Copy. Paste. Replace the bracketed bits.

Post with this · 30s

frontend-engineer.md

280 words · 3 min read

# [Senior/Mid/Junior] frontend engineer · [city] or remote

We are hiring our [Nth] frontend engineer. You will own [the X app, currently used by Y users a month]. The team is [N] engineers and [N] product designer(s) who pair on most surfaces. [Who else writes frontend code]. [How you ship].

## You will be good here if

- You have shipped a customer-facing interface past v1 and have layout-shift war stories you can tell over a coffee.
- You think about accessibility before the ticket is filed and reach for the keyboard before the mouse when testing.
- [The third trait you actually care about, with a sentence on the behaviour you want].

## What we use

[Framework, design system, build chain]. We will not retrain you on a stack, but we do not care if you came from [adjacent stack] as long as you have shipped to real users.

## What you will not get

A Friday production push. A waterfall sprint plan. A design partner who hands you a JPEG and disappears.

## Compensation

[Currency][low] to [high] base. [low] to [high] percent equity. We post the band because we mean it and we will not negotiate against ourselves.

## How we hire

30-second post, screen plus assessment via Picked, 20-minute interview via Picked, one on-site half-day with the team and a product designer. We aim to give a yes or no in 7 days.

## What is the rubric

Component thinking, accessibility instinct, performance attention, design literacy, curiosity. Not credentials.

That is the JD. Apply via [link], or just send a paragraph about the last interface you owned past launch and what broke first.

[Your name], [your title]

Tone rules

Eight phrases to delete
from every JD you ever write.

"Rockstar / ninja / wizard"

Nobody respectable applies to this. Replace with: nothing.

"Self-starter"

Means: we have no plan and no manager. Replace with: name the actual autonomy.

"Comfortable with ambiguity"

Same thing again. Replace with: tell them the specific ambiguity they will face.

"Fast-paced environment"

Means: chaotic. Replace with: name the cadence, sprints, ship-day, on-call.

"Champion"

A verb that means nothing. Replace with: the actual outcome.