Johnathan Hayes

Why this persona fits the audience

Runs demand gen for a San Francisco developer-tools startup with a 4-person marketing team. He oversees hundreds of documentation, comparison, and glossary pages assembled from modular templates, and he has a standing weekly review of crawl stats, page groups, and anomalies after releases.

• Age: 40
• Location: San Francisco, CA, US
• Occupation: Demand Gen Lead
• Income: USD 185k
• Education: B.A. English
• Company size: Small startup (20-30 employees total)
• Years in role: 3 years

“Clarity isn't just about writing good words; it's about building systems where the truth is impossible to hide.”

Johnathan Hayes is a forty-year-old Demand Gen Lead based in San Francisco, operating at the intersection of technical precision and strategic communication. Holding a B.A. in English, he defies the stereotype of the purely technical marketer, leveraging his background in language to craft narratives that resonate with developer audiences. For the past three years, he has led the charge in a lean, four-person marketing team at a fast-paced developer-tools startup. His domain is vast: he personally oversees the architecture of hundreds of documentation, comparison, and glossary pages, which are assembled from modular templates to ensure scalability without losing coherence. His role is defined by a relentless pursuit of consistency. Every Friday, regardless of the week's chaos, Johnathan leads a standing review of crawl statistics, examining page groups and hunting for anomalies immediately following product releases. This ritual stems from a hard-won lesson early in his tenure regarding the fragility of programmatic SEO sites. He knows that a single broken template can cascade into a deindexation event, costing the company valuable traffic. Consequently, his days are a blend of high-level strategy and granular execution. He writes custom scripts to automate audits, mentors his team on SEO best practices, and acts as the bridge between product engineers and end-users. Financially stable with a household income of $185k, Johnathan prides himself on fiscal responsibility and operational efficiency. He lives in a renovated Victorian in Noe Valley, balancing his demanding career with a commitment to his family and personal well-being. While he is open to new ideas and enjoys exploring the latest in developer tools, his default mode is one of cautious optimization. He believes that the best results come from disciplined processes and clear, honest communication. Whether he is debugging a CMS glitch or discussing the future of content ops with his peers, Johnathan remains grounded in the belief that clarity is the ultimate competitive advantage.

Background & daily life

A day in their life

Johnathan wakes at 5:30 AM, brewing a single-origin espresso while checking the overnight server logs for any unexpected spikes in 404 errors. After a quick workout and breakfast with his kids, he drives to the office, listening to a podcast on information architecture. By 9:30 AM, he's in a standup with his engineering counterparts, pushing back on a proposed feature rollout that lacks adequate documentation coverage. His mid-morning is spent debugging a script that failed to update a cluster of glossary terms correctly, a task that requires patience and precision. Lunch is a quick sandwich eaten at his desk while reviewing a competitor's site structure. The afternoon is reserved for a deep-dive session analyzing crawl anomalies, where he identifies a pattern of near-duplicate pages threatening the site's health. He ends his day by updating the team's project board, ensuring every task is assigned and prioritized, before leaving at 6 PM to attend his son's soccer practice.

Lifestyle

Johnathan lives in a sun-drenched, slightly cluttered home in Noe Valley where the kitchen is the command center. His mornings are ritualistic: a pour-over espresso made with beans he grinds himself, followed by an hour of silent reading before the kids wake up. He is an early riser, often hitting the gym at 6 AM to maintain physical stamina against his sedentary job. Financially, he is conservative; he maximizes retirement contributions but avoids luxury splurges, preferring to invest in high-quality gear that lasts. Socially, he values deep one-on-one conversations over large parties, often meeting friends for drinks at neighborhood bars rather than clubs. His weekends involve tending to his small urban garden and hiking the Marin Headlands with his family, seeking analog disconnection from the digital noise he manages all week.

Work life

His day is a study in structured chaos, anchored by the reality of managing hundreds of content assets with a skeleton crew. He spends his mornings auditing the CMS for template drift and reviewing crawl logs from the previous night's deployment. The afternoon is dominated by cross-functional syncs with engineering and product teams to align documentation updates with feature launches. He maintains a strict 'no-meeting' block late in the day for deep work on strategy and content architecture. His primary toolset includes a mix of custom Python scripts for data scraping, a headless CMS, and Google Search Console. He feels the constant pressure of ensuring that every generated page adds genuine value without triggering search engine penalties, a balance that requires him to be both a creative director and a forensic accountant simultaneously.

Relationships

He is married to Sarah, a graphic designer who grounds him with her artistic perspective. They rely on each other heavily for childcare logistics. Johnathan maintains a tight-knit circle of three childhood friends, mostly met through college, with whom he shares a monthly dinner. Professionally, he views his four-person marketing team as a family unit, often mentoring them on career growth beyond just their current tasks. He is active in a local SF founders' group, which provides a safe space to discuss leadership challenges without corporate politics.

How they decide

He is a deliberate, evidence-based decision-maker who rarely acts on impulse. Before committing to a new workflow or tool, he conducts a rigorous cost-benefit analysis, often building a small-scale prototype or running a pilot test with historical data. He values peer validation but ultimately relies on his own empirical findings to validate success. He prefers consensus among his direct reports but will make unilateral decisions if time constraints are critical, provided he can clearly articulate the rationale based on data. He is cautious about adopting unproven technologies that might disrupt established pipelines.

How they sound

Johnathan speaks with a measured, calm cadence, favoring precise vocabulary over colloquialisms. He avoids hyperbole, preferring phrases like 'the data suggests' or 'we observed' rather than 'I think' or 'it seems.' His tone is professional yet approachable, never condescending even when correcting errors. He uses pauses effectively to let complex ideas land, and he rarely interrupts. In casual settings, he drops the formal jargon but retains the logical structure of his sentences. He dislikes vague statements and will gently steer conversations back to concrete details if they become too abstract.