How to build a team on purpose
Most hiring is reactive. A role opens, panic sets in, and whoever interviews well by Friday gets the offer. That is not a hiring strategy. That is triage. It fills a seat, and it usually costs you more than it saves, because the person you hired under pressure is rarely the person the role actually needed.
I built my team differently, and the numbers say something about whether it worked. Ninety percent of Digital Diva is women, across five years and 200-plus completed client projects, spanning Pakistan, the UK, and the Gulf. That ratio did not happen because more women happened to apply. It happened because I built the funnel to find them, on purpose, from the first job post to the final decision.
The cost of hiring in a panic
Panic hiring optimizes for one thing: speed. It does not optimize for fit, for skill, or for the six months after the hire when the gaps in that decision start showing up in missed deadlines and redone work. Every founder has a story about the hire who looked great in the interview and fell apart in the role. That is not bad luck. That is what happens when the hiring process is built to close a gap fast instead of to find the right person.
The fix is not hiring slower for its own sake. It is being deliberate about the parts of the process that actually determine the outcome, and moving fast everywhere else. That is the whole shift: slow at the top of the funnel, where the decisions that matter get made, and fast once the right person is actually in front of you.
Write the job post for the role, not the resume you expect
Most job posts describe a candidate before anyone has met one. They list a degree, a number of years, a stack of tools, because that is faster to write than actually thinking through what the role needs. I stopped doing that. I write job posts for the work itself, skill by skill, and I let the description surprise me when it comes back.
That single change is most of why my team looks the way it does. When you describe the work instead of a stereotype of the person who usually does it, you stop filtering out people before they ever apply. You are not lowering the bar. You are describing the actual bar, instead of a shortcut for it.
Source where the overlooked candidates actually are
Job boards are efficient, and that is exactly the problem. Everyone posts there, which means everyone competing for the obvious candidates is looking in the same three places. The best hire I have made in the last two years came from a portfolio post in a small community group, not from a job board at all. She was not looking for a job that day. She was sharing her work.
If you only source where the obvious candidates already know to show up, you will only ever hire the obvious candidates. Some of the strongest people I have brought onto this team were not actively job hunting. They were building, quietly, somewhere I happened to be paying attention.
Stop treating culture fit as a filter
Culture fit, used as a filter, mostly filters out anyone who does not already resemble the team you have. It rewards sameness and calls it chemistry. I hire for judgment and hunger first. Culture builds itself around people who have both, and it builds a stronger culture than one selected for comfort.
This is the part founders resist most, because it means giving up the comfort of hiring someone who reminds you of yourself. But a team that only hires people who remind the founder of the founder stops growing the moment the founder’s own blind spots do. Judgment and hunger are not comfortable to screen for. They are the only two traits that actually predict whether someone will be good at a job you have not fully defined yet, which is most jobs worth having.
The framework, in full
Write the job post for the work, not for a candidate you have already pictured. Source where the people who are actually doing the work already are, not just where the job seekers are. Hire for judgment and hunger, and let culture fit follow from that instead of gatekeeping ahead of it.
None of this is complicated. All of it is slower than posting a generic listing and taking the first strong interview. That is the trade you are making, and it is worth making, because a team built this way does not need to be managed around the gaps a fast hire creates. You spend the time once, at the start, instead of every week after.
What it actually builds
A 90% female team was never the goal by itself. It is what happened when I stopped hiring for convenience and started hiring for the actual work, sourced from the actual places talent is, filtered on the traits that actually matter. My team did not build 200-plus client projects across Pakistan, the UK, and the Gulf because I got lucky with headcount. They built it because the people in those seats were the right people for what those seats needed, and I put in the work up front to find them instead of hoping the next Friday interview would.
That is the whole framework. Slow at the top of the funnel, fast on the decision once the right person is in front of you. Build the team on purpose, and it stops needing to be rebuilt.
What this looks like in the first 90 days
Founders often ask how long it takes before a deliberate hiring process starts showing results, because deliberate sounds like slow. It isn’t, once the funnel is built. The first 90 days of hiring this way usually looks like fewer applicants and a higher hit rate, a smaller, more relevant pool instead of a flooded inbox of people who read the job title and not the job. That trade is the whole point. A hundred generic applicants and three good ones is worse than twenty specific applicants and three good ones, because the first version costs you weeks of screening for the same outcome.
The other thing that shows up early is fewer surprises six months in. A hire made against judgment and hunger, sourced from where the actual work happens, rarely turns into the kind of quiet underperformance that panic hires produce. You feel the difference in what you’re not doing, not managing around a bad fit, not re-posting the same role in Q3 that you filled in Q1.
Questions founders ask about hiring on purpose
What does “hiring on purpose” actually mean? It means the makeup of your team is a designed outcome, not a coincidence of who happened to apply. Every part of the funnel, the job post, where it’s shared, what gets screened for, is built to find a specific kind of person, instead of whoever shows up first.
How do you hire for judgment and hunger instead of a resume? Ask questions that don’t have a rehearsed answer. How did you handle a decision with incomplete information? What did you do when a client or manager was wrong? A resume shows what someone has done. These questions show how someone thinks, which is what actually predicts performance in a role that isn’t fully defined yet.
Is a 90% female team a diversity target or a byproduct? A byproduct. I never set a quota. I built a hiring process that described the work honestly and sourced from places the usual channels overlook, and that process consistently surfaced strong women candidates. The ratio is evidence the process works, not the goal of the process.