Good Job Descriptions [StartupCTO]

Last Updated: 05 Dec 2025

|

Author: 114.119.147.45

Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 114.119.140.239
Lock expires at: Dec 5, 2025 09:07 AM (193 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

= Good Job Descriptions =

{{indexmenu>.|#scto.png tsort notoc}}

= Writing a Good Job Description =

There are several keys to writing a good job description, at least for technical roles. 

- Lead in with what the engineer is going to get out of the role. Try to be specific. Working with the latest technology? Wonderful training or learning opportunities? 
- Briefly talk about your company, and again mention specifics. You serve XYZ important clients (social proof). Or you handle X million transactions per day. 

== Role ==

Next, you'll want to talk about the role. For this, talk about the objectives of the role -- what do you want the person to accomplish. For example, you don't want to say 'You will be writing PHP code all day', instead you want to say 'You will be rebuilding our XYZ micro-service to be more performant'.

== Requirements ==

This is what sort of skills the person should have. It's best to avoid specific requirements like a number of years of experience, but instead talk about what they've done in the past (e.g. shipped code to production)

== Company & Benefits ==

This is where you can pimp out the company a bit more, and also talk about the benefits. Make sure to emphasize the company is stable and/or growing, and is a great place to work.

Page locked

About Me

Recent Changes

Get In Touch

Follow