I use a job description questionnaire to gather information about the job directly from the jobholder (or from the jobholder's manager). I also take inspiration from other similar job descriptions online to make sure that I'm not overlooking any important aspects of the job. I then draft the job description and have the draft reviewed and approved by the jobholder's manager prior to issuing it to the jobholder.
We take the time to craft everything internally, without having to rely on AI tools or outsourcing the process to a third-party that doesn't perfectly understand what we're looking for. It takes longer, but it's absolutely worth it, and it's only fair to provide that level of quality to prospective employees and candidates too.
I'll be the first to admit, I'm not an HR leader. I work on the IT and service desk side of things, mostly behind the scenes at recruiting companies. But let me tell you, even from that vantage point, you can't miss how much the process of building job descriptions has changed lately—mostly because of AI stepping onto the scene. A few years ago, writing up a job description was practically an art form. People spent hours poring over bullet points, trying to get every responsibility and requirement just right. Now, I see more and more teams leaning on AI tools to do the heavy lifting. It's not just about speed (though that's a bonus); it's about consistency, reducing bias, and making sure those descriptions don't turn into jargon soup that scares off great candidates. What I find fascinating is how these AI platforms can scan piles of data, spot trends, and spit out job ads that actually make sense to both recruiters and job seekers. I've watched HR teams take AI-generated drafts and tweak them with their own flair, which feels like the best of both worlds—tech doing the grunt work, humans making it real. If you want a deeper dive on how this works and why it matters, there's a great post here: AI Job Descriptions: Why They Matter & How AI Can Write Them Right. Bottom line? I think we're finally at a place where AI isn't replacing people—it's making their jobs a little less overwhelming. And if that means better job descriptions and happier hires, I'm all for it.
One of the better approaches is to run a "compare and contrast" of existing benchmarks to the internal JD's, but this is incomplete without involving the people in the roles at some point - often this starts at a higher level with middle managers QCing the benchmark data and your internal repos/structure/taxonomy/what have you. There's a deeper level of value where regular employees are engaging with the structure on a daily basis and testing it against hiring, promotion, performance management, etc. You get really good feedback and refinements from that.
As Executive Director of LifeSTEPS serving over 100,000 residents across 36,000 homes in California, I've learned comprehensive job analysis is crucial for our supportive housing services. When developing positions for our special populations programs, I first identify the unique challenges our residents face. For seniors aging in place, we needed staff with geriatric experience and housing knowledge to achieve our 98.3% housing retention rate. The key is involving frontline workers in description development. Before expanding our formerly homeless support program, I shadowed our best performing coordinators for three days, documenting their actual activities versus assumed responsibilities. This revealed critical soft skills like trauma-informed communication that weren't in our original descriptions. Review descriptions annually against outcome data. We finded our most successful service coordinators spent 40% more time on community partnerships than indicated in their job descriptions, leading us to restructure roles and improve training. This analysis-based approach strengthened our team's ability to serve vulnerable populations.
Through my experience, I have learned that this process is crucial in ensuring that the right talent is hired for the right roles within an organization. To begin with, it is important to understand that job analysis and descriptions are two separate but interconnected processes. Job analysis involves gathering information about a specific job through observation, interviews, and questionnaires. This information is then analyzed to determine the essential duties, responsibilities, qualifications, and skills required for the job. Once this data is collected and analyzed, it can be used to create a comprehensive job description. A job description is a written document that outlines the key aspects of a job, including its title, duties and responsibilities, qualifications, reporting structure and performance expectations.
At ICS Legal, we create comprehensive job analyses by blending strategic planning with input from department leads and data-driven role evaluation. First, we conduct stakeholder interviews and review past performance benchmarks to understand what success looks like in the role. We then map out key responsibilities, required skills, and decision-making scope, aligning them with business goals and compliance standards. For job descriptions, we prioritize clarity, inclusivity, and SEO optimization. Each listing includes: a purpose-driven role summary, clear responsibilities, growth opportunities, and the soft/hard skills truly required. We also avoid jargon and gender-coded language to widen applicant reach. Using tools like HRIS platforms and feedback loops from recent hires helps us keep descriptions dynamic and relevant. The goal is to attract candidates who align not just with tasks, but with our culture and vision.
Creating a comprehensive job analysis and description starts with truly understanding the role from different angles, not just what's written on paper, but what actually happens on the job. I usually begin to study the "friction points" in the workflow. These are the moments where tasks slow down, get passed around, or cause confusion. For example, if one person always ends up helping others figure out a system or fixing small issues, that reveals an unspoken duty or expectation. These insights often don't come up in interviews or job checklists, but they're important. I look at informal communication tools like team chats or message boards. These casual conversations often show who's mentoring others, who shares updates first, or who takes initiative when something unexpected happens. These soft responsibilities might not have a formal title, but they often make a big difference in team performance. Including them in the job analysis gives a fuller picture of what's expected from the person in that role. Additionally, I ask people from other teams what they need or expect from the role. For example, a marketing team might expect fast responses from the design team, even if that's not written in the job duties. By asking outside stakeholders, I uncover cross-functional responsibilities that are often missed but still crucial. Once I gather all of this, I break the job down into clear categories: core duties, required skills, tools used, and success measures. I include things like soft skills, team culture fit, and the role's impact on others. This way, the final job description doesn't just explain the tasks, it tells the full story of the role and sets the right expectations from day one. Overall, understanding the environment, the people, and the problems the role is meant to solve is what makes a job description truly comprehensive. That's where the real insight comes from.
As someone who's built a trauma-focused therapy practice from the ground up, I've learned that job descriptions need to capture both the visible skills and the unseen emotional labor involved. When we were hiring our first associate therapist, I realized traditional HR approaches missed the complexity of therapeutic work entirely. I spend time mapping the actual nervous system regulation required for different roles. For our EMDR intensive therapists, I document not just "provide trauma therapy" but specifics like "maintain self-regulation during 6-hour intensive sessions" and "recognize dissociative symptoms within first 10 minutes of client distress." These details come from tracking my own physiological responses during sessions over months. The breakthrough came when I started including "parts work" analysis in job descriptions - identifying which internal qualities need to be accessible (compassion, boundaries, curiosity) and which need to be managed (rescuer tendencies, perfectionism). This approach reduced our turnover by helping candidates self-select more accurately. I also build in collaboration requirements that reflect real therapeutic relationships. Instead of generic "work with clients," I specify "engage in mutual feedback with clients about session effectiveness" and "adjust treatment approach based on client's nervous system capacity each session." This captures the dynamic, responsive nature that makes therapy actually work.
After 40 years in PR and media relations, I've learned that the best job descriptions come from observing what actually makes someone successful in the role, not what you think they should do. When I was building my publicity team, I noticed my most effective publicists weren't the ones with perfect writing skills—they were the ones who could work a room at galas and remember personal details about editors' kids. So I rewrote our job descriptions to emphasize relationship-building and emotional intelligence over technical credentials. The biggest mistake I see is writing descriptions in isolation. Before hiring my current royal commentary team, I spent three months at actual events watching how successful commentators interact with both media and their subjects. I finded they needed crisis management instincts more than historical knowledge—when Princess Diana's stories broke, quick thinking mattered more than encyclopedic royal facts. Test your descriptions against your star performers. I compared my top columnist's daily activities to our job posting and found 60% of their actual work wasn't mentioned. They were spending hours cultivating sources at charity events, not just writing—so we added "social networking" as a core requirement.
During my years as a trauma therapist and EMDR consultant, I've learned that the most accurate job descriptions come from understanding emotional labor requirements, not just technical skills. When I developed training protocols for new EMDR therapists, I realized we were missing 60% of what actually makes someone effective in trauma work. I started tracking what my most successful colleagues did differently during their intensive sessions. The breakthrough came when I noticed our best therapists spent significant time on emotional regulation techniques between processing phases - something never mentioned in traditional therapy job descriptions. This led me to restructure how we define therapeutic roles. The game-changer was measuring client outcomes against therapist activities. I found that therapists who incorporated mindfulness and body scan techniques had 40% better client retention rates. This data completely changed how we write job requirements, focusing on somatic awareness skills rather than just clinical credentials. Now I always include "emotional stamina" metrics when consulting on therapeutic positions. For intensive EMDR work, I specify the ability to maintain therapeutic presence during 6-8 hour sessions, because that's the reality of what produces results for complex trauma cases.
At HireSites, I learned that the best job descriptions come from analyzing your top performers, not copying templates. I tracked conversion rates and found that descriptions written after interviewing our best recruiters had 40% higher application quality than generic postings. The key is mapping the actual workflow, not just listing skills. When I launched Focus Group Placement, I broke down what moderators actually do minute-by-minute during sessions - managing group dynamics, probing for deeper insights, keeping discussions on track. This granular breakdown helped us identify candidates who could handle the multitasking reality. I always include performance metrics in descriptions because they attract results-oriented people. For my survey platforms like LevelSurveys, I specify that community managers need to maintain 85% member engagement rates and process 200+ quality responses daily. Numbers eliminate guesswork and self-select serious candidates. The biggest mistake is writing descriptions in isolation. I involve current team members in the process because they know which "soft" requirements actually matter - like patience for dealing with difficult focus group participants or attention to detail for survey quality control.
Creating a comprehensive job analysis and description requires more than listing tasks — it's about designing a role with purpose, clarity, and alignment to business outcomes. As HR leaders, we begin by understanding why the role exists, not just what it does. This involves consulting not only with hiring managers but also high-performing employees in similar roles to get real, on-the-ground insights. We use structured methods like competency mapping, task inventories, and workflow analysis to identify the technical and behavioral competencies needed for success. This helps uncover not only what a person should do but also how they need to do it — which is key to cultural fit and team performance. To make descriptions useful across the employee lifecycle, we include performance indicators, learning paths, and possible career progression. This turns a job description into a strategic tool for recruitment, onboarding, and internal mobility — not just a hiring document. We also ensure inclusivity and clarity by removing biased language and jargon, using gender-neutral terms, and focusing on impact over credentials. Instead of listing generic requirements, we highlight what success looks like in the first 6-12 months. Finally, job descriptions are never "set and forget." We treat them as living documents — reviewed regularly based on team feedback, market shifts, and role evolution — to stay relevant and competitive in a changing workforce landscape.
After litigating over 1,000 employment cases, I've seen how poorly written job descriptions become legal landmines. The key is making them bulletproof from a discrimination standpoint while actually reflecting what the job requires. I always tell employers to focus on essential functions versus nice-to-haves. In one case I handled, an employer required a college degree for a warehouse position that involved lifting boxes - completely unnecessary and it opened them up to disparate impact claims. Break down what someone actually does 80% of their time, not theoretical duties. The biggest mistake I see is vague language around "cultural fit" or subjective requirements. These become breeding grounds for discrimination lawsuits. Instead, use concrete, measurable criteria tied directly to job performance. For a sales role, specify "ability to maintain client database" rather than "good people skills." From my 20+ years representing employees, neutral hiring criteria aren't just good practice - they're legal protection. Every requirement should pass the test: can you prove this specific skill/qualification is necessary for job success? If not, remove it before it costs you in court.
As CEO of ENX2 Legal Marketing for 15+ years, I've built comprehensive job descriptions by literally working alongside my team first. When I was developing our client success coordinator role, I spent weeks doing the actual work myself - handling client calls, managing campaigns, troubleshooting issues. You can't write what you don't understand. The breakthrough came when I stopped writing job descriptions and started documenting success patterns instead. I tracked our top performers for months and finded they were spending 60% of their time on relationship building versus the technical tasks we originally hired for. This completely changed how we structured roles. I involve my team in rewriting their own descriptions annually because they know their jobs better than I do. We sit around our conference table and I ask them to list what actually drives results versus what we think they should be doing. The disconnect is always eye-opening. During our recent expansion, we created descriptions based on client feedback rather than internal assumptions. Our clients told us they valued responsiveness over credentials, so we restructured requirements around communication speed and availability rather than years of experience. Revenue jumped 40% with these better-matched hires.
I've spent 25 years helping families steer complex succession issues, and I've learned that job analysis for family businesses requires a completely different approach than traditional HR methods. When wealthy families bring me in to handle estate planning, I often see multi-generational businesses falling apart because they never properly defined roles or succession paths. The biggest mistake I see is families assuming blood relation equals job qualification. I worked with a Phoenix-area family business worth $50M where the founder's son was "automatically" the heir apparent, but nobody had ever documented what skills the leadership role actually required. We had to reverse-engineer the job analysis by examining what made the founder successful: relationship management with key clients, strategic thinking during the 2008 recession, and the ability to make tough personnel decisions. My approach involves interviewing three groups separately: the current leader, key employees, and family members who aren't involved in daily operations. This reveals huge gaps between perception and reality. In one case, family members thought the CEO job was mostly "big picture strategy," while employees knew 60% of the role was actually crisis management and vendor negotiations. The most effective job descriptions I've seen include "failure scenarios" - specific examples of what happens when someone lacks each required skill. Instead of just listing "financial acumen," describe how poor cash flow management nearly killed the business in Year X, or how understanding tax implications saved $200K annually.
At LAXcar, we consider our job analysis to be core to performance and culture fit. We start by shadowing employees for maximum operations, to understand the full range of what they do, not just what can be found in pre-existing descriptions. This gives us a broader context beyond roles and responsibilities that exist on paper and allows us to write roles that reflect the manifest of the position. From there, we partner with team leads to create core competencies, performance standards, and necessary soft skills. Take our dispatcher job description, for instance, which includes not only driving efficiency, but emotional resilience and multitasking under pressure—characteristics we've been able to identify through past performance reviews. Each job description additionally undergoes a quarterly review to adjust for changing business needs. Write job descriptions about the work and what it will entail. Don't just state the tasks — articulate what success looks like in 6 months. This not only brings on stronger candidates, but it also aids in retention by having roles meet development goals from day one.
After 15+ years in recruiting, I see a good job description as equal parts of marketing and reality check. My rule: skip the fluff, show a real week. We always sit with the hiring manager to pin down clear examples — typical tasks, who they'll work with, what success looks like early on. This honesty up front weeds out mismatches before the first call. I've seen too many hires fall apart when surprises pop up mid-process. A clear, realistic job description draws in people who know exactly what they're signing up for — saving my team hours and building trust long before day one.
Job descriptions are very important to me, but I don't believe in creating them until I need to. I first complete a good job analysis of the role, by watching and asking questions. How does this person spend their time? What resources/tools do they need? How does the role contribute to the greater system? I ask my team directly how they feel they are challenged, and where they add value. I also write the objective/outcome of the role, along with key accountabilities and desired qualities. However, I leave some flexibility in each role, since most people change/develop in a role, in the first year or two. I pay close attention to the language of the description. Is it clear, direct, non-judgmental, and realistic? After all, it's a description of what's happening in the role, not corporate fluff. I also try to tell the story of the role and the business, in a way that someone reading it wants to work there and be a part of it, rather than just a place to work for a paycheck. I think this is how I have been able to attract and retain quality people.
We start by defining the "why" behind each role—what problem it solves and how it supports our mission. Then, we talk to the team: the hiring manager, coworkers, and anyone the role would collaborate with. That gives us clear insights into what's essential versus nice-to-have. We keep the description focused—listing top responsibilities, measurable goals, and the key skills that matter most in our fast-paced environment.