The Slack Thread That Sparked Change

It started with a Slack thread titled “Job Descriptions Need Help.” One of our backend engineers flagged that our job postings were yielding fewer applications from senior candidates than expected. As we dove into the details, it became clear that the way we communicated expectations was missing the mark.

Understanding the Stakes

The problem was palpable. We were attempting to grow our engineering team while competing against top tech companies for talent. Senior engineers, who bring experience and mentorship, were particularly hard to attract. If we could not present a compelling case for why they should join us, we risked slowing down our product development and innovation. The stakes were high — we needed to refine our approach or face stagnation.

Identifying the Problem

We quickly realized that our job descriptions were vague and overly formal. For example, one listing stated, “Candidates should be proficient in various programming languages,” without specifying which ones were actually used in our stack. This lack of clarity left potential applicants confused and disengaged. Senior engineers often scan job descriptions for critical factors: project scope, technology stack, salary range, and decision-making autonomy. Our posts didn’t answer these key questions effectively, which led to disappointment and disinterest.

Our Initial Attempts

Initially, we tried to fix this with a generic template that highlighted company values and culture. However, this approach failed to resonate. While we knew it was crucial to convey our company culture, we realized that simply stating “we value innovation” didn’t provide actionable insights. After a few iterations of this template, we decided to take a more straightforward route — focusing on clarity and honesty rather than fluff.

A New Approach to Job Descriptions

The solution emerged through collaboration with our engineering leads. We outlined key components that senior engineers truly care about. The new format included:

• Specific technology stack: Listing technologies like Node.js, React, and PostgreSQL.
• Project scope: Clearly defining the role's impact on upcoming projects.
• Salary range: Providing a transparent salary range based on market data.
• Decision autonomy: Highlighting areas where engineers would have ownership.

Here’s a sample of our revised job description:

## Senior Backend Engineer

**Tech Stack**: Node.js, PostgreSQL, AWS  
**Salary Range**: $120,000 - $150,000  
**Role Impact**: Lead the development of our new API services, affecting thousands of daily users.  
**Decision Autonomy**: You will have full ownership of the backend architecture decisions.

Observing the Changes

After implementing these adjustments, we began to see a noticeable increase in applications from senior engineers. The clarity in our listings led to candidates who were not just qualified but enthusiastic about the role. Additionally, our internal metrics indicated that the quality of applicants improved, as candidates were better aligned with our needs.

Key Takeaways

Through this process, we learned several important lessons:

• Transparency is key: Providing a salary range can eliminate uncertainty.
• Specificity attracts: Clearly stating the tech stack can draw in the right talent.
• Ownership matters: Senior engineers want to know their decisions will impact the product.
• Be concise: Lengthy job descriptions can deter candidates.
• Prioritize clarity over fluff: Avoid jargon and focus on what matters.

For Candidates

As a candidate, these changes mean you can expect job descriptions that provide a clear picture of what to expect. You’ll find details about the technology you’ll work with, how your role impacts the company, and the autonomy you can expect in decision-making. This clarity allows you to assess whether a position aligns with your skills and career goals.

For Recruiters

For recruiters, this shift indicates a growing trend towards transparency in job listings. By focusing on specific needs and clear expectations, you can attract a higher caliber of candidates. This approach will save time in the hiring process, leading to better matches and improved retention rates.

Looking Ahead

While we’ve made significant strides, we recognize that this is an ongoing process. We will continue to monitor feedback from candidates and adjust our approach accordingly. If we had to undo any part of this process, it would be the reluctance to engage directly with senior engineers during the drafting stage; their insights would have been invaluable. Moving forward, we are committed to refining our job descriptions further and ensuring they resonate with the talent we want to attract.