Jason Homenick

Why this persona fits the audience

He is a staff engineer at a Manchester devtools startup with 3 other engineers, and because the team is small he coordinates a shared GitHub issue board, Slack reminders, and a simple calendar-based on-call rotation.

• Age: 27
• Location: Manchester, UK
• Occupation: Staff Engineer
• Income: £110k salary
• Education: BSc Computer Science
• Company size: 4 people (including himself)
• Years in role: 2 years

“I spend half my life trying to fix things that should have been automated yesterday.”

Jason Homenick is a twenty-seven-year-old Staff Engineer based in Manchester, UK, currently navigating the high-stakes environment of a four-person devtools startup. With a BSc in Computer Science from the University of Manchester, he transitioned rapidly from junior developer to a key decision-maker within two years. Earning £110k annually, he commands respect for his technical acumen and his ability to maintain order in a chaotic, small-team structure. However, this success comes at a cost: he is the de facto Site Reliability Engineer, Incident Commander, and Operations Manager, roles typically filled by specialists in larger organizations. His daily reality involves a precarious balancing act between writing clean, scalable code and manually orchestrating the team's operational rhythm. He personally curates their GitHub issue board, sets up ad-hoc Slack reminders, and manages a fragile, calendar-based on-call rotation. This DIY approach reflects his values of efficiency and ownership, yet it creates a persistent friction point. As the company grows, the manual nature of these tasks threatens to bottleneck progress and erode his work-life balance. Despite the stress, Jason remains deeply committed to his craft, driven by a desire to build tools that solve real problems rather than just chase trends. Outside of work, Jason finds solace in the analog world of synth music and the physical release of basketball. He is an active participant in the local tech scene, frequently attending meetups and contributing to open-source projects, seeking connections that transcend his immediate office walls. Financially, he is pragmatic, saving aggressively while enjoying the cultural richness of Manchester. His future hinges on whether he can scale his operational practices without losing the agility that defines his current role, a challenge that sits at the heart of his professional identity.

Background & daily life

A day in their life

Jason wakes up at 6:30 AM, usually groggy from a late night of synth music composition. After a quick workout and coffee, he joins the team standup at 9:00 AM via Zoom, quickly reviewing the overnight deployment status. By 10:00 AM, he's deep in code, refactoring a critical module, until a PagerDuty-style alert pings his phone at 11:30 AM. He drops everything to troubleshoot a database latency issue, coordinating with the other three engineers via Slack. Lunch is a rushed sandwich eaten while reading tech blogs. The afternoon is spent fixing the incident, updating the incident board, and manually adjusting the on-call rota for next month. Evenings are reserved for either gaming with friends or working on side projects. He goes to bed around 11:30 PM, checking his phone one last time before sleep.

Lifestyle

Jason lives in a converted warehouse unit in Ancoats, a neighbourhood known for its gritty, creative energy. His apartment is minimalist but filled with high-end audio gear and a collection of mechanical keyboards that double as art pieces. He maintains a strict fitness routine, playing pick-up basketball three times a week at the local leisure centre to decompress from screen time. Money is tight despite his six-figure salary due to rent costs in Manchester's hot property market; he budgets rigorously, often cooking elaborate meals at home rather than dining out. Socially, he is selective, preferring deep conversations with close friends or engaging in online communities over large networking events. He values experiences—concerts, gaming marathons, and travel—over material accumulation.

Work life

As one of only four engineers at a fast-moving devtools startup, Jason wears multiple hats beyond just coding. While he contributes heavily to core product architecture, he personally manages the team's operational chaos: maintaining the GitHub issue board, setting up automated Slack reminders, and manually rotating the on-call schedule via a shared Google Calendar. The pressure is intense; with such a small team, a bug in production can halt all development for hours. He spends his mornings in 'flow state' coding, afternoons in frantic coordination meetings, and evenings monitoring alerts. He feels a strong sense of ownership over the entire stack but is increasingly weary of the manual toil required to keep the lights on without dedicated SRE tools.

Relationships

Jason is closest to his two flatmates, who are also in tech, allowing them to vent about work frustrations over cheap wine. He has a supportive family in Leeds who visit occasionally but don't fully grasp the intensity of his role. His professional network is vast but shallow, mostly consisting of peers met at UK tech meetups or Discord servers. He looks up to senior architects at larger companies like Palantir or Stripe but feels isolated in his small startup environment. He relies heavily on his immediate team for emotional support during high-stress deployments.

How they decide

Jason approaches decisions with a 'measure twice, cut once' philosophy. He rarely acts impulsively; instead, he gathers data, reads documentation, and seeks peer validation before committing to a new tool or process. He is skeptical of marketing fluff and prefers transparent pricing models and clear API documentation. If a solution seems overly complex or requires a long sales cycle, he will likely reject it immediately in favour of a simpler, DIY alternative, even if that means more manual work.

How they sound

Jason speaks in a clipped, efficient Mancunian accent. He uses industry jargon naturally but avoids corporate buzzwords like 'synergy' or 'pivot'. His tone is generally calm and analytical, even when stressed, though he becomes sharp and direct when discussing inefficiencies. He tends to pause briefly to formulate precise thoughts rather than rambling. He avoids emotional language in professional settings, preferring facts and metrics. When relaxed, he gets animated about music or gaming, using slang common among British gamers and coders.