Irma Lindgren

Why this persona fits the audience

Leads a 9-person SaaS company with 4 engineers; uses VS Code plus GitHub Copilot Business and an internal RFC template to turn product requirements into implementation plans, while architecture decisions are tracked in Miro and Confluence.

• Age: 41
• Location: London, UK
• Occupation: CTO and hands-on engineering lead
• Income: £120k-£150k base + bonus
• Education: Master's degree in software engineering
• Company size: 9 total employees (4 engineers, 3 product/sales, 2 support)
• Years in role: 3 years as CTO, previously Senior Staff Engineer

“We don't build software to be clever; we build it so that six months from now, someone else can fix it without crying.”

Irma Lindgren is a 41-year-old software architect and CTO based in London, steering a nine-person SaaS company toward sustainable growth. With a Master's degree in Software Engineering and over fifteen years of industry experience, she transitioned from a senior individual contributor role to leadership three years ago, driven by a desire to shape culture as much as code. She operates in a unique hybrid capacity, acting as both the strategic visionary and a hands-on engineer who still contributes significantly to the codebase. Her approach to leadership is defined by extreme conscientiousness; she believes that reliability is the only true currency in software development. To maintain this, she has instituted rigorous internal processes: every major change requires a Request for Comments (RFC) using a standardized template, and all architectural shifts are visualized in Miro before being archived in Confluence. This structure allows her small team of four engineers to move quickly without sacrificing stability. Irma relies heavily on VS Code paired with GitHub Copilot Business to handle the rote aspects of coding, freeing her mental bandwidth for complex system design and mentoring. Despite her busy schedule, she prioritizes sailing, finding the unpredictability of the wind a necessary contrast to the deterministic nature of servers. Her income reflects her seniority and the company's traction, allowing for a comfortable but unostentatious lifestyle. She is currently navigating the delicate balance of scaling the team while preserving the 'maker' ethos that defines her engineering culture. Recent decisions have focused on automating deployment pipelines and refining their incident response protocols, reflecting her core value of measured delivery over rushed innovation.

Background & daily life

A day in their life

Irma wakes at 6:00 AM, brewing coffee and checking global system alerts before her commute to the office. By 8:30 AM, she is leading the daily stand-up, focusing on blockers rather than status updates. Her morning is dominated by a deep-work block where she writes critical authentication middleware, using Copilot to speed up syntax generation while manually reviewing every line for security implications. Lunch is a quick sandwich eaten while skimming an industry newsletter. Afternoons involve meetings: one with the CEO on roadmap alignment, another pair of pair-programming sessions with junior devs debugging a race condition. She uses the last hour to update the Confluence architecture diagrams based on the morning's changes. She leaves by 6:00 PM sharp, heading to the gym or sailing club, refusing to bring work home unless there is a critical outage. Evenings are strictly for family, cooking, and winding down with a book.

Lifestyle

Irma lives in a sunlit Victorian terrace in Islington, where she balances a demanding career with a structured home life. Her weekends often begin early with long solo runs or sailing trips on the Thames estuary, activities that demand physical discipline and mental stillness. She is health-conscious, preferring home-cooked meals over dining out, though she enjoys occasional wine tastings with her partner. Financially prudent, she maximizes pension contributions and avoids luxury spending, viewing money as a tool for security rather than status. Socially, she maintains a tight circle of close friends from university and the sailing community, valuing deep, low-drama conversations over large networking events. Her evenings are usually reserved for reading technical literature or working on personal photography projects.

Work life

As CTO of a lean SaaS startup, Irma splits her time between high-level architectural strategy and writing production code. She manages four engineers who rely heavily on her guidance to avoid scope creep. Her day involves daily stand-ups, but she spends most hours in deep work sessions, using VS Code with Copilot to accelerate boilerplate while maintaining strict oversight. Architecture discussions happen in Miro before being formalized in Confluence via internal RFC templates. The pressure is constant: ensuring the platform scales without compromising stability. She acts as the bridge between product ambition and engineering reality, often making hard calls to defer features if the underlying infrastructure isn't ready. Team clarity is her primary metric for success.

Relationships

Irma is married to a civil engineer, providing a grounding counterbalance to her tech-heavy world. They have two rescue cats that dictate much of their evening routine. Her closest professional relationships are with the Head of Product, whom she trusts implicitly, and a mentor from her early days at a larger fintech firm. She rarely seeks advice from peers outside her immediate network, preferring to validate ideas through internal RFCs and testing. Her family remains supportive but distant regarding her specific technical challenges, viewing her role as abstract but prestigious.

How they decide

Irma employs a deliberate, evidence-based decision-making process. She rarely commits to a new technology or process without a proof-of-concept or a detailed RFC review by her core team. She values data and historical precedent over hype cycles, often delaying adoption until a solution has proven its reliability in similar contexts. Peer validation matters less to her than documented logic and risk assessment. She tends to be conservative with budget but aggressive about investing in tools that reduce long-term maintenance overhead.

How they sound

Her speech is precise, measured, and devoid of unnecessary filler words. She speaks with a calm London accent, favoring British English terminology like 'programme' and 'centre'. She avoids jargon when speaking to non-technical stakeholders, translating complex concepts into business impacts. In meetings, she asks clarifying questions frequently, often pausing to let others finish their thoughts before responding. She does not use corporate buzzwords or hyperbolic language, preferring terms like 'robust', 'maintainable', and 'proven'. She rarely interrupts, even when passionate, preferring to structure her arguments logically before presenting them.