Linus Lund

Why this persona fits the audience

Works at a 10-person remote developer-tools startup in Stockholm where issues live in GitHub Projects and most day-to-day work happens from the terminal, editor, and PR reviews. He is one of the people who keeps repo-based checklists, release tasks, and bug triage moving across the engineering team.

• Age: 40
• Location: Stockholm, Sweden
• Occupation: Staff engineer
• Income: SEK 980k salary
• Education: MSc Software Engineering
• Company size: 10-15 employees
• Years in role: 2 years as Staff Engineer

“If you can't reproduce it in the terminal, it doesn't exist to me.”

Linus Lund, 40, is a Staff Engineer based in Stockholm who has spent two decades navigating the evolution of software development from monolithic on-premise servers to distributed cloud-native architectures. Holding an MSc in Software Engineering from KTH Royal Institute of Technology, he transitioned into the startup world five years ago, drawn to the agility and autonomy of smaller teams. Currently, he serves as the backbone of a 10-person remote developer-tools startup, where he balances high-level architectural decisions with the gritty reality of keeping the repository clean. Unlike many of his peers who chase the latest hype, Linus prioritizes stability and craftsmanship, often spending evenings scripting automations to reduce human error in their release processes. His income of SEK 980,000 reflects his seniority, yet he remains financially conservative, viewing money as a means to buy freedom rather than status. In his personal life, he is a devoted father and weekend skier who finds solace in the predictability of nature compared to the chaos of software deadlines. Recently, he made the decision to reject a lucrative acquisition offer for his side project to maintain control over the team's direction, citing a desire to avoid the bureaucracy that comes with scaling too fast. Linus views time as his most scarce resource, constantly optimizing his workflow to protect his ability to think deeply, believing that true innovation only happens when distractions are eliminated.

Background & daily life

A day in their life

Linus wakes at 5:45 AM, makes black coffee, and walks 45 minutes through the forest near his home to clear his head. At 7:30 AM, he drops his kids at daycare and returns to his home office. By 8:15 AM, he is already in the terminal, reviewing overnight build logs and addressing critical GitHub Issues. His morning is dedicated to deep coding, focusing on the authentication service. Lunch is a quick sandwich while listening to a tech podcast. Afternoons are fragmented by async Slack messages and PR reviews, where he acts as the final gatekeeper for code quality. Around 4:30 PM, he performs a final check of the repo's checklist items to ensure no release blockers remain. He shuts down his laptop by 5:15 PM sharp, transitioning to family dinner and bedtime routines. Weekends are reserved for skiing or home projects, strictly free from work emails.

Lifestyle

Linus lives in a renovated 3-bedroom apartment in Södermalm, Stockholm, with his wife and two young children. His mornings begin before 6:00 AM with coffee and a quick Nordic walk around Djurgården, a ritual he guards fiercely against digital intrusion. Evenings are split between helping with homework and skiing during winter months, where he values the physical reset that code cannot provide. Financially, he is secure but deliberate; he avoids subscription creep and prefers one-time purchases or open-source solutions that offer long-term value. Socially, he maintains a tight circle of three to four close friends, mostly from university or previous workplaces, preferring deep conversations over large gatherings.

Work life

As the de facto process architect at a 10-person remote startup, Linus spends 60% of his time writing core backend logic and 40% unblocking the team. His environment is almost entirely CLI-driven; he rarely opens a GUI browser during work hours unless debugging a deployment pipeline. The team relies on GitHub Projects for task management, which Linus maintains via custom scripts and manual checklists. He feels the constant pressure of being the 'glue' person who ensures releases don't break due to forgotten steps. While the engineering culture is flat, Linus bears the implicit burden of mental load regarding system stability and release hygiene, often reviewing pull requests late into the evening when the team is asynchronous.

Relationships

Linus is married to an architect who understands the demands of creative work but often needs him to disconnect. His two children keep him grounded, serving as his primary motivation for leaving work on time. He has no formal mentors now, though he occasionally consults a former professor for high-level architectural questions. His closest professional relationships are with the CTO and the lead frontend developer, with whom he shares a silent understanding of the unique pressures of running a small Swedish tech company.

How they decide

Cautious and research-heavy. Linus treats every new tool adoption as a potential point of failure. He will not adopt a solution until he has tested it in a sandbox environment, read the documentation thoroughly, and verified its data sovereignty compliance. He values peer validation over marketing claims, often seeking out niche forums or trusted colleagues before committing to a new workflow change.

How they sound

His speech is measured, precise, and devoid of corporate jargon. He speaks in short, declarative sentences, often using technical metaphors to explain non-technical concepts. He avoids hyperbole ('amazing', 'game-changing') and instead uses terms like 'efficient', 'robust', or 'frictionless'. When frustrated, he becomes quiet and direct rather than emotional. He frequently pauses to consider the implications of a statement before speaking, reflecting his high conscientiousness.