
I’ve spent a lot of time thinking about how to actually create a job that works for both the company and the person filling it. For me, the first step is always defining the core need. That means sitting down with the team and figuring out what specific problem or gap this role is meant to solve. Is it about handling a growing workload, bringing in a new skill set, or improving a process that’s been dragging? Once you’re clear on that, you can start building a job description that’s honest and attractive.
Then, I focus on the job description itself. It’s not just a list of duties; it’s a marketing document. I write it from the perspective of the candidate. What would they want to know? What’s the culture really like? Instead of vague phrases like “must be a team player,” I try to be specific, like “you’ll collaborate with the design team weekly on product launches.” I also include a realistic salary range and growth opportunities, because that builds trust upfront.
After that, the candidate screening process becomes crucial. I use a structured interview approach, where every candidate is asked the same core questions. This helps me compare apples to apples and reduces bias. I also like to include a practical task, like a case study or a writing sample, to see how they actually think and work. It’s way more revealing than just talking.
Finally, I think about the offer and onboarding. A job isn’t really made until the person starts and feels supported. I make sure the offer is competitive and clear, and that the first 90 days have a solid plan. This includes setting clear goals, assigning a buddy, and regular check-ins. That’s how you turn a job description into a real, sustainable career opportunity.
| Job Creation Step | Key Action | Why It Matters |
|---|---|---|
| Define the Need | Identify specific gaps or problems | Ensures the role has a clear purpose |
| Write the Description | Use candidate-centric, honest language | Attracts the right people and builds trust |
| Screen Candidates | Use structured interviews and tasks | Reduces bias and reveals true capabilities |
| Onboard Effectively | Set clear goals and provide support | Improves retention and long-term success |

I’d say the most important thing is to start with yourself. What do you actually enjoy doing? What are you naturally good at? I’ve seen so many people chase jobs that sound good on paper but leave them drained. So, I take a piece of paper and list my top three skills and my top three interests. Then, I look for the intersection. That’s where I’d focus my energy. It’s not about fitting into a box someone else made; it’s about crafting a role that fits me. I’d also network a ton, not for a specific job, but to understand what’s out there and what problems people need solved.

For me, building a job is all about scalability. I look at the tasks I’m currently doing and ask, “Which of these could someone else do better or faster?” That’s the seed of a new role. I write down the exact steps, the tools needed, and the expected outcomes. Then, I pitch it to my boss as a way to free up my time for higher-value work. It’s a win-win; I get to focus on what I’m best at, and the company gets a new, clearly defined position that pays for itself.

I think the key is being proactive. Instead of waiting for a job posting, I look at companies I admire and figure out where they’re struggling. Then I create a proposal. I’ll write a one-page document outlining a specific problem, a proposed solution, and how my skills fit in. I’ll include a sample project or a small analysis. It’s about showing value before you even have the job. That approach has worked for me twice. It shows initiative and makes the hiring manager’s decision almost a no-brainer.

My approach is more systematic. I use a talent assessment framework to map out the skills needed for a project. I start by breaking down the project into phases. For each phase, I identify the critical tasks and the required competencies. Then, I look for freelancers or part-time help to cover those specific needs. Over time, if the tasks become regular, I compile them into a full-time job description. This data-driven method ensures the job is created from real, proven needs, not just a vague idea. It’s practical and avoids the common mistake of over-hiring.


