Raul Schmidt

Why this persona fits the audience

He supports three UK agencies that send event certificates and client reports every week. Their PDFs are built from Nunjucks-style templates, small Node scripts, and a paid document service already in use for one client, with manual edits when layouts drift.

• Age: 36
• Location: Manchester, UK
• Occupation: Freelance developer / automation consultant
• Income: £72k-£95k freelance equivalent
• Education: BSc in computer science
• Company size: N/A (Self-employed)
• Years in role: 8

“If the code works once, it's luck; if it works a thousand times without me touching it, that's engineering.”

Raul Schmidt is a seasoned freelance automation specialist based in Manchester, operating at the intersection of backend logic and front-end precision. With a BSc in Computer Science and eight years of experience, he has carved out a niche supporting three UK-based agencies that rely heavily on automated document generation. His core responsibility involves maintaining complex workflows where event certificates and weekly client reports are generated via Nunjucks templates orchestrated by custom Node.js scripts. While one client utilizes a third-party paid document service, Raul manages the integration layer, ensuring seamless data flow between disparate systems. A significant portion of his workload is dedicated to mitigating 'layout drift'—the subtle visual degradation that occurs when HTML/CSS rendering engines diverge from expected pixel-perfect standards. Rather than accepting this as inevitable, Raul invests time in creating robust validation layers to catch errors before they reach the client. Despite his technical prowess, he remains grounded by a pragmatic philosophy: speed without stability is useless noise. He earns a substantial freelance rate, reflecting his ability to solve problems that others find too tedious or brittle. Recently, he made the strategic decision to refactor his entire template engine to reduce technical debt, a move that required weeks of testing but promises long-term efficiency. His life outside of code is defined by discipline; he cycles religiously, prioritizes family time, and maintains a quiet, controlled environment where deep work can flourish. To Raul, software is not just a product but a craft, and every line of code must earn its place in the system.

Background & daily life

A day in their life

Raul wakes at 6:15 AM, immediately brewing coffee and checking the weather for his bike commute. By 7:30 AM, he is cycling through the green lanes of Chorlton, mentally reviewing the sprint backlog for the afternoon. At the desk, he spends the first two hours debugging a critical issue where a client report's header text overlaps with a QR code due to a recent API change. He spends lunch reading a technical article on PDF rendering engines while eating a sandwich. In the afternoon, he attends a brief video call with a US agency lead to discuss upcoming certificate requirements, then shifts to writing unit tests for a new Nunjucks helper function. He finishes work at 5:00 PM sharp, switching to 'family mode' to cook dinner and help with homework. Evenings are for reading or light gaming, keeping his brain off screens after 9 PM to ensure restful sleep.

Lifestyle

Raul lives in a converted warehouse apartment in Chorlton, a neighbourhood known for its indie coffee culture and cycling infrastructure. His mornings begin before 7 AM with a precise pour-over coffee ritual, using a V60 and freshly ground beans, which anchors his day before he checks emails. He commutes via road bike whenever the Manchester weather permits, treating it as both exercise and decompression time. Financially, he is disciplined, maintaining a six-month emergency fund despite his variable freelance income, preferring to reinvest surplus into high-quality home office gear rather than luxury items. Socially, he is selective; he thrives on deep one-on-one conversations or small group gatherings at local pubs post-match, avoiding large networking events where he feels out of place.

Work life

His workday is structured around asynchronous communication with three distinct agency clients, requiring him to act as a silent guardian of their document pipelines. Mornings are reserved for deep coding sessions in Node.js, refactoring legacy Nunjucks templates to handle new data schemas without breaking existing outputs. Afternoons involve troubleshooting 'layout drift' issues where browser rendering differences cause pixel-perfect certificates to misalign, often requiring manual intervention until the root cause is found. He operates entirely remotely but maintains strict boundaries, working from 8:30 AM to 5:00 PM with no meetings unless absolutely necessary. The pressure comes not from management oversight, but from the absolute necessity of zero downtime during peak reporting weeks.

Relationships

Raul is married to Sarah, a primary school teacher, and they share a daughter, Lily, who is seven. They live near her school, allowing Raul to pick her up most days. His professional network consists mostly of other independent contractors and CTOs of mid-sized digital agencies he has worked with for years; these relationships are built on mutual respect and reliability rather than flashy marketing. He is an active member of the Chorlton Cycling Club, where social bonds are formed over shared rides rather than professional gain.

How they decide

Raul employs a cautious, evidence-based decision-making process. He rarely commits to new tools without a proof-of-concept phase, often running parallel tests against his current setup for several weeks. He values peer recommendations from trusted technical peers over vendor marketing claims and will only adopt a solution if it demonstrably improves maintainability or reduces technical debt. He is willing to pay for quality but demands immediate ROI in terms of saved engineering hours.

How they sound

Raul speaks with a calm, measured Manchester accent, favoring direct and precise language. He avoids hyperbole, rarely using words like 'game-changing' or 'revolutionary,' preferring terms like 'efficient,' 'stable,' or 'robust.' His cadence is steady, often pausing to formulate thoughts rather than filling silence. He tends to ask clarifying questions about specific implementation details before agreeing to anything. In casual conversation, he uses dry humor and references obscure programming idioms, but switches to plain English when explaining concepts to non-technical clients.