Why this persona fits the audience
Co-founds a 4-person devtools startup in Manchester. Keeps customer context in a Notion workspace, exported Gmail threads, and a few Python scripts that pull data from files and Slack; he uses Claude Code to generate docs and checks those notes before each prompt.
- Age: 26
- Location: Manchester, UK
- Occupation: Founding engineer
- Income: £65k salary plus small equity
- Education: Self-taught programmer with some university study
- Company size: 4
- Years in role: 2
“The real magic isn't just writing code, it's building the systems that let the code, and the people writing it, work smarter.”
Julian Spinka, 26, is a founding engineer at a nascent developer tools startup in Manchester, UK. His journey into software development was largely self-directed, punctuated by a brief, incomplete stint at university where he found the formal curriculum too slow. He gravitated towards practical problem-solving, honing his skills through personal projects and online resources. This self-reliance is a core tenet of his approach, extending to how he manages the company's customer intelligence. Julian meticulously curates customer context, a process he's built himself using a combination of Notion for structured notes, exported Gmail threads for conversational history, and custom Python scripts that aggregate data from Slack and local files. He leverages AI coding assistants like Claude Code not just for generating code snippets but also for drafting documentation, which he then rigorously reviews against his own notes before integrating it. This dedication to technical rigor and efficiency shapes his daily work. He lives frugally, prioritizing investment in learning and tools over immediate material comforts, reflecting a pragmatic approach to both his career and personal life. The startup environment demands constant adaptation, pushing him to constantly refine his self-built systems. Recently, he's been focused on improving the reliability of his data aggregation scripts, particularly after a minor incident where outdated customer information led to a slightly misdirected sales outreach. This has reinforced his belief in the necessity of a unified, up-to-date context bank, even if it's currently a patchwork of his own creation.
Background & daily life
A day in their life
Julian's typical weekday starts around 8:30 AM after a quick breakfast. He'll check Hacker News and Slack for urgent updates before diving into coding. Mornings are usually dedicated to feature development or bug fixing, often involving deep concentration. Lunch is a quick affair, sometimes eaten at his desk. Afternoons are a mix: more coding, reviewing pull requests from his colleagues, and crucially, updating the customer context in Notion or running his Python scripts to pull fresh data. He might spend an hour experimenting with Claude Code for documentation generation or exploring new AI coding techniques. Evenings often extend past 7 PM, sometimes involving a late-night coding session or a virtual sync with a co-founder, before winding down with a YouTube tutorial or a quick game.
Lifestyle
Julian lives in a rented two-bedroom flat in Levenshulme, sharing with a fellow developer from a different startup. His routine is heavily work-focused, often involving late nights fueled by strong coffee and the occasional takeaway. Weekends are a mix of catching up on personal projects, trying out new tech, and occasional social outings with his flatmate and a small circle of developer friends. He's not overly concerned with material possessions, preferring to invest time and money into learning and tools that enhance his productivity. Health-wise, he tries to fit in a run a couple of times a week but often prioritizes coding sprints.
Work life
As a founding engineer at a nascent devtools startup, Julian's days are a whirlwind of coding, system design, and customer interaction. He's deeply involved in building the core product, often writing the 'workflow glue' that connects different services. His current focus is refining the data ingestion pipeline for customer context, wrestling with API inconsistencies and ensuring data integrity. He spends significant time in Notion, meticulously documenting customer feedback and technical decisions, and uses Python scripts to automate data aggregation from Slack and Gmail. The pressure is constant, balancing rapid development with the need to understand user pain points intimately.
Relationships
Julian's closest relationships are with his co-founders, with whom he shares intense work sessions and strategic discussions. His flatmate provides a casual social outlet and a sounding board for technical ideas. He maintains contact with a few university friends, mostly online, but his social circle is relatively small, prioritizing deep connections over broad ones. His parents, back in their hometown, are supportive but don't fully grasp the intricacies of his work.
How they decide
Julian is highly analytical and research-driven when it comes to technical decisions. He'll spend time evaluating different libraries, frameworks, or architectural patterns, often prototyping small solutions to test hypotheses. For operational or workflow improvements, he prioritizes efficiency and demonstrable time savings. He's less swayed by hype and more by practical utility and elegant solutions to complex problems. He trusts his own judgment but will consult his co-founders on significant strategic choices.
How they sound
Speaks with a clear, measured cadence, often using precise technical terminology. His tone is generally neutral and focused, avoiding excessive slang or overly casual language in professional contexts. He tends to be concise, getting straight to the point, but can elaborate extensively when explaining a technical concept. He avoids hyperbole and emotional language, preferring factual descriptions. You might hear him say things like 'The data pipeline's bottleneck is currently X,' or 'We need to ensure the context is consistently updated.'
Personality traits
- analytical
- methodical
- resourceful
- detail-oriented
- independent
- pragmatic
- curious
- driven
- reserved
- systematic
Goals
- Build a robust and scalable core product for the startup.
- Achieve product-market fit within the next 18 months.
- Become a more proficient AI prompt engineer for development tasks.
- Automate more of the company's internal operational workflows.
- Maintain a high level of technical autonomy and ownership.
Problems & frictions
- Fragmented customer information across multiple tools (Notion, Gmail, Slack).
- Time spent manually consolidating and re-contextualizing customer data.
- Ensuring consistency and accuracy in documentation as the team grows.
- Balancing deep technical work with essential customer-facing activities.
- The inherent uncertainty and resource constraints of an early-stage startup.
Values
- self-reliance
- efficiency
- technical rigor
- problem-solving
- continuous learning
Interests
- developer tools
- automation scripts
- AI coding
- system architecture
- data pipelines
Media habits
- Hacker News daily
- Ars Technica for tech news
- YouTube for coding tutorials (e.g., Fireship, Ben Awad)
- Podcasts: Syntax.fm, The Changelog
- Occasional Twitter scrolling for developer memes and updates