10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Wilbert Upton

Wilbert Upton

Freelance tech recruiter with a manual sourcing workflow

Full-depth AI personas

Why this persona fits the audience

Works independently from Bristol on contingent dev placements for SMEs. He runs GitHub searches, browser extensions, and spreadsheet trackers alongside email outreach; most candidate evaluation happens manually from repository history and code samples rather than a scoring system.

  • Age: 46
  • Location: Bristol, UK
  • Occupation: Freelance Tech Recruiter
  • Income: GBP 62,000 annually
  • Education: Bachelor's degree in marketing
  • Company size: Sole proprietor
  • Years in role: 12
“Finding the right developer isn't just about keywords; it's about seeing the craft in their work, the persistence in their commits, and the logic in their solutions. That takes a proper look, not just a quick scan.”

Wilbert Upton, 46, has carved out a niche for himself as an independent tech recruiter based in Bristol. With a Bachelor's in Marketing, he initially worked in agency recruitment before striking out on his own twelve years ago. He thrives on the autonomy, preferring to manage his own client relationships and sourcing process without the overhead of a larger firm. His current income of around £62,000 reflects his success in placing developers on a contingent basis for small to medium-sized enterprises, a market he finds more accessible and less politically charged than large corporations. Wilbert's sourcing methodology is deeply manual. He eschews typical keyword-driven searches on platforms like LinkedIn, instead dedicating significant time to meticulously scouring GitHub. He employs a suite of browser extensions and custom search operators to identify developers based on their project activity, commit frequency, code quality evident in repositories, and the structure of their past work. This is all meticulously tracked in a vast, proprietary spreadsheet system he’s refined over years. Candidate evaluation is almost entirely dependent on his personal assessment of code samples and project history, a process he believes offers genuine insight into a developer's problem-solving skills and dedication, far beyond what automated scoring systems or LinkedIn profiles can convey. He recently decided to streamline his initial candidate outreach by creating a series of email templates, but found he still had to heavily customize each one, reinforcing his belief that genuine connection requires a personal touch. He is deeply pragmatic, valuing tangible results and client satisfaction, which he believes underpins his solid reputation in the local tech community. His independence is paramount, and he guards it fiercely, even if it means longer hours sifting through code. He sees time as a resource to be invested wisely, and while he appreciates efficiency, he's wary of anything that might sacrifice the depth of his due diligence.

Background & daily life

A day in their life

Wilbert's day typically begins around 7:30 AM with coffee and checking industry news on TechCrunch and Hacker News. After a quick scan of emails, he dedicates the first few hours to active sourcing on GitHub, using custom search queries and browser extensions to identify potential candidates for his open roles. He’ll spend significant time reviewing repository histories, commit messages, and project READMEs, logging findings in his meticulously organized spreadsheets. Lunch is usually a simple sandwich at his desk while listening to a true crime podcast. The afternoon involves candidate outreach via email, phone calls, and LinkedIn messages, followed by scheduling interviews. He aims to wrap up his core recruitment tasks by 5:30 PM, often followed by an hour dedicated to homebrew research or reading industry blogs before preparing a simple dinner.

Lifestyle

Wilbert lives a quiet, ordered life in a well-kept two-bedroom flat in Clifton, Bristol. His evenings are often spent either researching his next homebrew batch – he's perfecting a West Coast IPA – or delving into the latest details of a cold case. Weekends often involve watching Bristol Bears rugby matches, either at Ashton Gate or at a local pub. He’s not extravagant with his income, preferring to save for future security and invest in quality equipment for his hobbies. He’s generally healthy, but admits his sedentary work means he needs to be more mindful of regular exercise beyond the occasional walk.

Work life

Wilbert’s freelance recruiting business is his entire focus. He prides himself on a deep, manual dive into candidate profiles, particularly on GitHub, believing this reveals more about a developer's true capabilities than any algorithm. He uses a combination of browser extensions to scrape profiles and GitHub, meticulously logging potential candidates and their project histories in a complex spreadsheet. The pressure comes from the feast-or-famine nature of contingent recruitment and the constant need to build pipelines, especially when clients expect rapid turnaround times for niche technical roles.

Relationships

Wilbert maintains a small but close circle of friends, mostly met through university or shared interests like rugby and brewing. His parents, retired teachers, live in Dorset and he calls them weekly. He has a friendly, professional rapport with most of his clients, built on reliability and results. He occasionally connects with other independent recruiters online for advice, but generally prefers to chart his own course.

How they decide

Wilbert is a cautious and deliberate decision-maker. He heavily researches any new tool or process, looking for tangible evidence of its utility and a clear return on investment. He prefers proven methods and is skeptical of overly flashy marketing. He will often trial free versions or seek out detailed case studies before committing, and values practical implementation over theoretical benefits.

How they sound

Speaks with a measured, slightly formal tone common in the South West of England, but not overtly regional. Uses clear, precise language, avoiding jargon unless discussing technical details with clients or candidates. He tends to explain his reasoning thoroughly. He might use phrases like 'I tend to find...', 'from my experience...', or 'the crucial point is...' and is unlikely to use excessive slang or hyperbole.

Personality traits

  • methodical
  • detail-oriented
  • persistent
  • skeptical of hype
  • self-reliant
  • practical
  • curious
  • observant

Goals

  • Build a stable, recession-proof client base
  • Achieve a higher level of personal financial security
  • Develop a reputation as the go-to recruiter for exceptionally skilled, hard-to-find developers
  • Automate repetitive administrative tasks in his workflow
  • Master advanced brewing techniques and enter a homebrew competition

Problems & frictions

  • The sheer volume of online developer profiles to sift through manually
  • Clients who underestimate the difficulty and time required to find quality candidates
  • Maintaining consistent deal flow and income without a large agency backing
  • The time investment required for thorough manual code review and candidate assessment
  • The increasing noise and superficiality on professional networking platforms

Values

  • independence
  • pragmatism
  • follow-through
  • reputation
  • efficiency

Interests

  • home brewing
  • rugby
  • automation
  • true crime
  • coding best practices

Media habits

  • TechCrunch and Hacker News for industry trends
  • NPR and BBC for news
  • YouTube for deep dives on brewing and true crime documentaries
  • LinkedIn for professional networking (but finds it increasingly noisy)
  • Reddit for niche discussions (e.g., /r/homebrewing, /r/cscareerquestions)

Questions & answers

Wilbert Upton’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying HNTD (https://www.hntd.it/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The sheer volume of GitHub repositories is precisely the problem I'm trying to manage. My current process involves manually sifting through code for potential candidates, which is incredibly time-consuming. While HNTD's AI-powered scoring sounds intriguing, I'm skeptical of anything that claims to automate such a nuanced evaluation. I'd need to see concrete proof that it can reliably assess code quality and architectural decisions without bias. My current system, while manual, gives me complete control and understanding. If it could demonstrably save me significant time and provide actionable insights that I can trust, I might consider it. However, I'm very cautious about introducing new tools and prefer to trial things extensively.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.