How to Write an Effective Job Description...

An effective job description tells a qualified candidate what the work is, what success looks like, and whether they should apply. It is short enough to read on a phone and complete enough to use for screening, leveling, and pay decisions.

This guide explains how that document works in 2026, who should use it, and how to write it for Web3 roles without slowing hiring or creating legal risk.

What is a job description

A job description is a factual record of a single role. It states the job title, where the work happens, what the person will own, what skills are required to do it, and what pay to expect. A job post is the shorter public version of that record that you publish on job boards.

Use the description to set expectations before anyone applies. Use the interview to test whether those expectations are met. Confusing the two leads to posts that are either marketing brochures or legal documents that repel applicants. The best posts read like clear instructions for the right person.

Who this guide is for

Founders and hiring managers at early-stage protocols, L2s, wallets, infra teams, and exchanges who need to write a post without a large HR team.
Recruiters and people operations running Greenhouse, Lever, Ashby, or Workday who manage multiple Web3 roles and need a consistent format.
Hiring managers for non-technical Web3 roles in community, product, growth, marketing, business development, design, and research who need to replace vague Web2 templates with proof-based requirements.

If you are hiring a smart contract or protocol engineer, you will need technical specifics that do not belong in a generic template. If you are hiring for community or growth, you need different proof. This guide covers both.

How it works: the mechanics

A job description has eight parts that do different work. Skip one and you shift the cost to interviews or to rejected applicants.

1. Title, location, and work model

Use a standard title that candidates search for. LinkedIn and Indeed both report that non-standard titles such as "Blockchain Guru" reduce search hits by more than 50 percent. Keep the title under 60 characters and add the stack when it helps: "Solidity Engineer - DeFi Vaults" is more findable than "Web3 Wizard."

State location, timezone overlap, and work model up front. In Web3 about 70 to 75 percent of listings on Web3.career and gm.careers are remote as of 2026. If the role requires on-site in one city or 4 hours overlap with EST, say so in the first 3 lines.

2. One-paragraph summary

One paragraph that answers: what team is this, what problem does the role solve in the next 6 to 12 months, and who does it report to. Write 2 to 3 sentences. Front-load the outcome.

Weak: "We are looking for a talented individual to join our team and help build decentralized finance products."

Strong: "You will own ERC-20 and ERC-4626 vault contracts for a lending protocol with about $80M in total value locked. You will ship audited code, write the Foundry test suite, and work with two senior engineers and an external auditor. The team works remotely with overlap 13:00 to 17:00 UTC."

The second version lets a reader decide in 10 seconds whether the role fits.

3. Responsibilities written as outcomes

List 5 to 7 responsibilities as outcomes, not tasks. Include ownership and success measures where you can.

Design and ship vault contracts and deployment scripts, with fork tests against mainnet state and invariant tests in Foundry.
Own access control and upgrade flow for two core contracts, documented in a risk memo for each release.
Review at least two pull requests per week and pair with the frontend team on gas estimation and transaction simulation in Tenderly.

LinkedIn's 2018 study of 4.5 million jobs in the US and UK found that short posts perform better. Posts with 150 words or less got 17.8 percent more applications than posts with 450 to 600 words. Textio's analysis of more than 1 billion posts in January 2024 found the best-performing posts were 300 to 660 words in total. That is about two-thirds to one and one-half pages single-spaced. If your draft is over 600 words, you have not narrowed the scope.

4. Requirements and preferred skills, split honestly

Split this into two lists.

Required - must have on day one: 3 to 5 items that are truly non-negotiable and job-related. For a Solidity role this is often:

Solidity 0.8.x, Foundry or Hardhat, and OpenZeppelin Contracts 5.x used without copy-paste
A record of verified contracts on Etherscan or another explorer, or merged pull requests to a reputable repo
Ability to explain checks-effects-interactions and to prevent reentrancy, access control failures, and input validation issues from the OWASP Smart Contract Top 10 (2025)

Preferred - useful to have: 2 to 3 items that help but can be learned in 90 days.

Do not list 15 must-haves. Research on application behavior shows women and candidates from underrepresented groups are less likely to apply unless they meet most listed items, so long lists narrow the pool. Also, requiring a degree when the work does not need it can screen out qualified candidates. U.S. guidance cited by DataPeople and EEOC notes this can affect Black, Hispanic, rural, and veteran applicants at higher rates. If a skill can be learned in the first months, mark it as preferred.

5. Working conditions and essential functions

Describe what the job requires in plain terms to support ADA clarity and to reduce later disputes. Include:

Type of work: for example, remote, on-call for deployments, light travel to audits or conferences
Physical or time demands when relevant: for example, incident response during a release window
Supervisory responsibility: hire, train, evaluate, assign work, or none

Avoid vague phrases like "physically demanding." State the specific need: "Lifting not required. Work is done at a computer."

6. Pay range and benefits

Pay range disclosure is now law in most major hiring markets.

As of July 2026, 16 US jurisdictions require a salary range in the job posting itself: California, Colorado, Connecticut, District of Columbia, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York State, New York City, Vermont, Washington, and several cities in Ohio. Thresholds differ: California 15 or more employees, Illinois 15 or more, New York 4 or more, New Jersey 10 or more, Massachusetts 25 or more, Minnesota 30 or more. Sources: PayTransparency.app validator updated July 5, 2026; Paycor 2026 state table updated January 26, 2026; Davron November 26, 2025 summary; Clockspot fact-check May 25, 2026. Remote posts are often covered if the employer is based in a covered state or if a worker in that state could perform the role.

Most of these laws also require a general description of benefits and other compensation. California Labor Code Section 432.3 as amended by SB 642, effective January 1, 2026, defines "pay scale" as the good faith estimate the employer expects to pay upon hire and requires that range in any posting for employers with 15 or more employees. Washington and Illinois have similar good faith standards and ban open-ended ranges. New Jersey rules cap the spread to 60 percent of the minimum, so a posting of $100,000 to $190,000 would exceed that limit.

The EU Pay Transparency Directive, Regulation 2024/1689, requires member states to transpose pay transparency rules by June 7, 2026, including pay information in the vacancy notice or before the first interview. British Columbia and Ontario have parallel posting rules in Canada, with Ontario's rule confirmed for January 1, 2026 and a $50,000 maximum spread in most cases.

Even when not required, including the range helps. MoshJD's 2026 synthesis of HR surveys cited Resume Genius data that 74 percent of workers feel more confident negotiating when ranges appear. Ongig and LinkedIn note similar effects on application quality. Put the range near the top: for example, "Base salary $130,000 to $165,000, plus token grant with 4-year vest and 12-month cliff. Range reflects level and location; stock or token terms in offer letter."

7. How to apply and what you will see from proof of work

Tell candidates what to send and how you will evaluate it. This improves the quality of applications and respects time.

Ask for GitHub, portfolio, or writing links, not just a PDF. For Solidity roles ask for verified contract addresses. For growth or community roles ask for writing samples, governance forum posts, or Dune dashboards. State that private repos should include a short video walkthrough.
State the steps and timing: "30 minute screen, 60 minute technical review, paid 2 to 4 hour take-home for finalists. We reply within 48 hours after each step."
Explain pay for take-homes that take more than 2 to 3 hours. Senior candidates expect it.

8. Compliance line

End with a plain equal opportunity statement and a link to where the full posting lives. Example: "We are an equal opportunity employer. We consider all qualified applicants without regard to race, color, religion, sex, national origin, disability, age, or genetic information." This reflects EEOC guidance under Title VII, the Age Discrimination in Employment Act, the Americans with Disabilities Act, and the Genetic Information Nondiscrimination Act as summarized on eeoc.gov and dol.gov. Avoid language that suggests a preference, such as "recent graduate," "digital native," "young energetic team," or "manpower," all of which Textio and other bias checkers flag as age or gender coded.

What changes for Web3 roles

Web3 posts need chain and risk details that a generic template omits. Be specific so candidates can self-select.

Name the stack and the risk. A Solidity post that says "Ethereum and EVM chains, Solidity 0.8.x, Foundry, Hardhat, OpenZeppelin" will get better matches than "blockchain experience." If the role is Rust on Solana, say Solana, Rust, and Anchor. If it is Move on Sui or Aptos, or Cairo on Starknet, say so, and note that the pool is smaller.

Show ownership, not just tech. State what the person will own: "Own two vault contracts from spec to audit, including invariant tests, deployment verification on Etherscan, and incident runbook." That wording maps to accountability for money-moving code.

Ask for proof that fits the track:

For developers: pinned repos with tests including fuzz and invariant tests, static analysis with Slither, fork tests, and audit or contest reports. Rework's 2026 Web3 developer template and Web3.career's Solidity template both list verified contracts and audit history as standard proof.
For non-technical roles: governance votes, forum comments, blog or Mirror posts, Twitter threads with sources, community support threads in Discord where the candidate helped others, or partner onboardings with outcomes. Hiring strategy work at Hashtag Web3 has found that Discord helpfulness and governance writing predict community and operations performance better than a polished resume.

Explain token and vesting terms in the post. Do not promise price. State the structure you use: "Token grant vesting over 4 years with 12-month cliff, linear monthly after cliff, minimal TGE. Terms enforced on chain where applicable and described in the offer letter. Candidates should seek independent tax advice." That phrasing follows the conventional baseline described by Streamflow and Tokenomics.com for core teams in 2026 and leaves valuation to the offer stage.

Pros and cons

Short, outcome-focused post, 300 to 450 words

Pros: Higher apply rate on LinkedIn, easier mobile reading, forces you to choose what matters. Matches Textio's 300 to 660 sweet spot and LinkedIn's 17.8 percent lift for concise posts.
Cons: Less room for company story. You must put culture and roadmap on your site and link to it, not in the post.

Detailed post, 600 plus words with full context

Pros: Fewer unqualified applications when requirements are strict, better for specialized search on Indeed where 700 to 2,000 words can get 30 percent more applications according to RecruiterFlow summaries cited by Knowledgelib. Useful for rare stacks.
Cons: Lower skim rate, higher drop-off on mobile, harder to keep current.

Task list versus outcome list

Task lists are easy to write but they attract doers of tasks, not owners of outcomes. Outcome lists are harder to draft but they give candidates a way to show how they would succeed.

Strict requirements versus split must-have and nice-to-have

Strict lists feel thorough but they filter out capable candidates who could learn the preferred items. Split lists increase applications from qualified people who have strong proof but non-traditional backgrounds, including pseudonymous builders whose GitHub matters more than a degree.

Most teams do best with a 350 to 500 word post that uses outcomes, split requirements, and a link to a longer technical spec for those who want it.

How to write it: practical steps

Gather inputs first. Get the hiring manager, one peer engineer, and one non-technical reviewer in one 45 minute meeting. Confirm title, level, reporting line, what success in 6 months looks like, and the pay band for that level and location.
Draft in the template order. Use the same order every time so reviews stay fast: title, summary, responsibilities, required, preferred, work conditions, compensation and benefits, how to apply, compliance line. This matches the 13-point template recommended by MoshJD and used by Greenhouse and Lever customers for auditability: title, summary, key responsibilities, required qualifications, preferred qualifications, skills and competencies, supervisory duties, work environment, physical requirements, FLSA classification, travel, compensation range, and version date.
Write requirements that can be tested. For each required item, note how you will test it: GitHub review, Etherscan verification, take-home with Slither and Foundry coverage, Dune query walk-through, writing sample. If you cannot test it, remove it.
Run a bias check before you publish. Use a tool such as Gender Decoder for a free check, or Textio, DataPeople, or Ongig for a scored review. Replace flagged phrases: "rockstar" to "expert," "aggressive goals" to "ambitious objectives," "dominant" to "confident." Textio case data reports that scores above 70 correlate with more applications from underrepresented groups. People Managing People and Index.dev reviews both note that neutral wording predicts better pool diversity. One field experiment cited in 2026 reporting found debiasing masculine language increased the share of women in the applicant pool without lowering total volume.
Add pay and location truthfully. Confirm the range is the good faith amount you expect to pay upon hire, not a wide placeholder. If you use a vendor to post, California law extends the duty to those third parties. Verify the range appears on your careers site and on each job board mirror.
Publish with links to proof. Link to your product docs, GitHub, and a short roadmap note. Candidates who have followed your governance forum or tested your contracts on testnet will use those links to tailor their application. That tailoring is your early signal of interest.
Measure and revise after two weeks. Track views, applies, qualified rate, time to first qualified applicant, and share of applicants from underrepresented groups if you collect that data lawfully. If you get fewer than 10 applications per week, the title is likely not searchable or pay is missing. If qualified rate is under 15 percent, requirements are too vague or too broad. Update the description every 6 to 12 months or when the work changes.

A short Web3 example you can adapt

Title: Solidity Engineer - Vaults, Remote, 4 hours EST overlap Location: Remote global, pay band disclosed in local equivalent Summary: You will own two ERC-4626 vault contracts for a lending protocol on Ethereum and Arbitrum. You will write Foundry tests with fuzz and invariant coverage, run fork tests, and ship with an external audit. Reporting to the CTO, with two engineers and a security reviewer. Responsibilities:

Ship vault contracts and deployment scripts with verified sources on Etherscan and a risk memo per release
Maintain coverage and add Slither to CI
Review teammate pull requests and document trade-offs Required:
Solidity 0.8.x, Foundry, OpenZeppelin Contracts, verified contracts or merged pull requests you can share
Ability to explain access control and reentrancy prevention using checks-effects-interactions
Written communication that shows threat model and test plan Preferred:
TypeScript with ethers.js, viem, or wagmi for dApp integration
Experience with audit reports or bug bounties Work model: Remote, incident response during release windows, no travel required Pay: Base $135,000 to $175,000 plus token grant with 4-year vest and 12-month cliff, general benefits listed in the offer letter. Range is the good faith estimate upon hire. How to apply: Share resume, GitHub, contract addresses, and one paragraph on a vault risk you would watch for and why. Steps: screen 30 minutes, technical 60 minutes, paid take-home 2 to 4 hours.

Common mistakes to avoid

Inflating requirements. Listing every tool you might use turns a mid-level role into an unfilled senior search. Move anything learnable to preferred.
Hiding pay. Omitting the range cuts applications and creates legal exposure in the 16 jurisdictions that now require it. It also lowers negotiation confidence for 74 percent of workers per the 2026 Resume Genius survey cited above.
Writing long blocks of text. Dense paragraphs hide the outcome the candidate cares about. Break into bullets and keep sentences short. Textio finds that shorter sentences and bullet ratios near one-third of the post improve completion.
Clever titles. "Crypto Ninja" may feel on brand but it is not searchable. Index.dev and Knowledgelib both flag discoverability losses above 50 percent.
Copying another team's post. A vault engineer and a protocol engineer are different risk profiles. Tailor the language and the proof you request.

Limitations and trade-offs

Salary survey numbers lag. BLS Occupational Employment and Wage Statistics for May 2024, published August 2025, shows $133,080 median for software developers, but it is base only and about a year behind. Glassdoor and Levels.fyi are faster but self-reported and skew to large tech. Use two sources and state the mix you compared.
Bias scores predict pool diversity, they do not prove a hire will be fair. You still need structured interviews and scorecards. The EEOC's May 18, 2023 technical assistance on adverse impact and the January 2025 SHRM note that federal anti-discrimination laws still apply whether the step used software or a human.
Pay bands force harder choices. A tight 60 percent spread under New Jersey rules means you must level the role before you post.

FAQ

How long should a job description be? Aim for 300 to 660 words for the public post. That range performed best in Textio's 1 billion post analysis from January 2024. Keep it under 600 words if you post mainly on LinkedIn or mobile, where 150 words or less lifted apply rates by 17.8 percent in LinkedIn's 4.5 million job study.

Do we have to include a salary range? In the 16 US jurisdictions listed above, yes if you meet the employee threshold and the role could be performed there or could be filled by a resident who saw the post remotely. In the EU you will need to disclose pay in the notice or before the first interview once the directive is transposed in each country by June 2026. In other states you should include it anyway for candidate trust and to avoid later disputes.

What should we put for pay when the grant includes tokens? List the base salary range as dollars. Describe the token grant in structure, not price: number of tokens is set in the offer letter, with vesting length, cliff, and release interval. State that tokens have market risk and that base alone should be livable. Do not project token value.

Should we require a degree? Only when the role needs it by law or by necessary licensing. Otherwise list skills and proof: verified contracts, audits, dashboards, or writing samples. This broadens the pool and avoids unnecessary filtering that affects protected groups, as documented in 2023 reporting on degree requirements.

How many requirements should we list? Three to five must-haves and two to three nice-to-haves. More than that suggests the scope is not defined. Each must-have should map to a screen you will actually run.

Can we use AI to draft the posting? Yes for a first draft, then edit for accuracy, brand, and inclusive language. SHRM's February 2025 survey of 2,040 HR professionals found 43 percent of organizations use AI in HR, and 65 percent of those use it for job description generation. Keep a human reviewer who can change the outcome before you publish, and log the model version if you operate in New York City under Local Law 144 or in the EU under Articles 9 to 15 of the AI Act.

What record should we keep? Job title, level, location and remote policy, pay band source and date, requirement list with job-related justification, compliance review date, bias check score and tool, pay range posted and where, applicant counts, and next review date. Keep version history so you can show what changed and when.

Sources and further reading: LinkedIn 7 Tips for Writing Job Posts That Attract Candidates, August 14, 2018 based on 4.5 million jobs; Textio How to write job descriptions in 2024, January 4, 2024 based on 1 billion plus posts; MoshJD Job Description Format in 2026, November 25, 2025; Clockspot Pay Transparency Laws by State, fact-checked May 25, 2026 and SB 642 amendment January 1, 2026; PayTransparency.app Every State That Requires Salary Ranges in Job Postings, July 5, 2026; Paycor Pay Transparency Laws by State, January 26, 2026; Davron Salary Transparency Laws in 2026, November 26, 2025; Jackson Lewis Navigating 2026 Pay Transparency Laws, July 8, 2026; EEOC Technical Assistance on Title VII adverse impact, May 18, 2023; U.S. Department of Labor and EEOC employer pages; DataPeople Job Description Compliance, February 26, 2025 and Skima AI compliance guide July 27, 2026; Textio bias research via Index.dev November 5, 2025 and People Managing People August 13, 2026; SHRM Talent Trends February 2025 and HireVue February 2025 hiring data via how-to-use-ai-in-hiring.

How to Write an Effective Job Description for Web3 Roles