Creating Your Tech Job Description, Part II: Questions to Consider

In the first part of our 'Creating your Tech Job Description' series, we discussed why having a great job description is important and how to start with internal alignment.

Next, we're going to cover important questions you should consider as you craft your job description:

Remote now or remote always?

This should be up top as it's a deal breaker for most candidates. People want to know whether they would be expected to go into the office now or in the future. It's not enough to say "remote" as people will still have questions.

What does this company do and why does that work matter?

The most important part here is “why does that matter”. Grandiose statements are unlikely to sit well here (see: Silicon Valley on HBO and any slogan they have there) but your company does exist for a reason! Share that reason here.

Example: Mpirik is addressing the undertreatment of heart diseases by collecting and analyzing data and using novel algorithms to automate patient identification for care. Our work makes sure people get the right care at the right time.

What does a day-in-the-life look like for this role?

Note: This isn't a list of bullet points. This is your opportunity to tell the story of what this person will be doing day to day.

Be very thoughtful of your language. For example, when you say that you want someone who is "entrepreneurial," you probably mean "thoughtful problem solver." But a candidate might perceive that as, "work long hours alone with little direction."

Balance your desire to highlight culture/benefits and technical needs.

What kinds of problems will this person solve?

Real examples! Avoid the catch all here! The requirements gathering, full-stack coding, DevOps expert is...unlikely. Instead this might be "improve our CI/CD pipelines" or "build new features on our existing mortgage product used by 2M users globally."

What is the team size and structure?

How big is the team? Are we all generalists? Will this person be a specialist in certain area? Will they be on one team or multiple teams?

Who will this person work with daily and how?

If people on your team have an impressive GitHub or notable blog, this could be a great chance to show people who they'll be able to work alongside. Top performers want to work with other smart people!

Environment: Tech Stack, Methodology, Dev Tools?

Are there any specific engineering practices that a candidate should know about? Scrum? Kanban? When listing your tech stack, make sure to include versions you're using!

Example: We love TDD. If you don't love TDD, you may not love it here.

Example: GitHub, Jira

Download 'Your Tech Job' Guide

10 views0 comments


735 N Water St. Suite 501

Milwaukee, WI 53202

Tel: 414.885.4519

© 2020 by Newance LLC. 

  • Facebook
  • Twitter
  • LinkedIn