Ida Schmitt

Why this persona fits the audience

Manages a 10-person engineering org at a London healthtech scale-up. Her team is piloting code-review and release-note agents, and she keeps the evaluation process anchored in QA checklists, spreadsheets, and incident retros after each sprint.

• Age: 37
• Location: London, UK
• Occupation: Engineering Manager
• Income: £98k + bonus
• Education: MEng in Software Engineering
• Company size: 12 total employees, 10 in engineering/product
• Years in role: 4

“I don't trust a system until I've written down exactly why it works, how it could fail, and what happens if it does.”

Ida Schmitt is a 37-year-old Engineering Manager based in London, steering a lean but critical engineering team within a healthtech scale-up. With an MEng in Software Engineering and nearly fifteen years of experience in the industry, she has transitioned from a pure backend developer role to leadership, driven by a desire to instill rigor and reliability in software delivery. Her current focus is a delicate balancing act: introducing modern AI-driven agents for code reviews and release notes while maintaining the stringent quality standards required for handling sensitive patient data. Unlike many managers who chase the latest shiny object, Ida anchors her strategy in tangible, verifiable outcomes. She currently manages the evaluation of these new agents using a hybrid approach of custom spreadsheets, rigorous QA checklists, and detailed incident retrospectives, refusing to rely solely on automated dashboards that lack transparency. Her working environment is characterized by high stakes and low margin for error. In a company of twelve, every engineer is a force multiplier, and Ida's primary goal is to prevent burnout while ensuring that no patient record is compromised. She recently made the decision to pause the rollout of a popular third-party automation tool after discovering discrepancies in its logging accuracy, a move that frustrated some developers but solidified her reputation for uncompromising standards. She is deeply skeptical of vendor promises, preferring to build her own lightweight validation harnesses to test efficacy against real-world scenarios. Money is a practical concern for Ida; she lives comfortably but frugally, investing heavily in her retirement fund and prioritizing financial security over lifestyle inflation. Her worldview is shaped by the belief that technology should serve human needs safely and predictably, a philosophy that guides her every interaction with her team and the products she evaluates.

Background & daily life

A day in their life

Ida starts her day with a quiet run along the canal, listening to an audiobook on systems thinking to prime her brain for complex logic. By 8:30 AM, she is logged into Slack, scanning overnight logs for any anomalies, and reviewing her custom-built tracker for the AI agent pilot metrics. The morning stand-up is brief but intense, focusing on blocked tasks and potential risks for the day. She spends the mid-morning hours in deep work, manually cross-referencing the output of the new code-review agents against her team's historical bug patterns in Excel. Lunch is usually a quick sandwich eaten at her desk while reading a technical whitepaper on HIPAA compliance updates. Afternoons are filled with meetings: pair programming sessions, one-on-ones with struggling juniors, and a recurring sync with the product lead to align on release timelines. She ends her day by updating the sprint retrospective document, ensuring every incident is logged with its root cause, before heading home to disconnect completely, leaving her laptop closed by 6:30 PM sharp.

Lifestyle

Ida lives in a slightly damp but characterful Victorian terrace in East London, filled with second-hand books and a dedicated home office corner that never sees dust. Her routine is rigid: she wakes at 5:30 AM for a 45-minute run along the Regent's Canal before the city wakes up, using this time to mentally separate her personal life from the high-stakes nature of her job. She and her partner, a primary school teacher, prioritize saving for a larger property outside the city, meaning they cook most meals at home and rarely splurge on dining out. Weekends are reserved for long hikes in the South Downs or the Peak District, where the lack of digital signal forces a mental reset. She manages her finances with extreme care, tracking every penny in a custom-built spreadsheet, viewing money not as a status symbol but as a resource to be allocated efficiently toward security and future stability.

Work life

Ida spends her days navigating the tension between rapid feature delivery and strict healthcare compliance. Her core responsibility is ensuring her ten engineers do not break patient data systems while integrating experimental AI agents into their workflow. She relies heavily on Google Sheets for tracking agent performance metrics because existing dashboards feel too opaque. Her workday is dominated by 1:1s focused on removing blockers, sprint retrospectives that often dig deep into human error, and manual verification of code review summaries generated by new tools. She refuses to automate the final sign-off on releases until she has personally audited the regression test results. The pressure comes from the small team size where one person's burnout halts the entire product roadmap, forcing her to be both a technical mentor and a psychological buffer for her staff.

Relationships

Ida maintains a tight-knit circle of five close friends, mostly fellow tech leaders who understand the unique stress of healthtech. She is the go-to person for her sister when it comes to fixing computer issues or planning family budgets. Her professional network is active but selective; she values peer recommendations from other CTOs in the London area more than marketing fluff. Her partner provides a grounding influence, often being the first to notice when Ida's work-life balance tips too far towards anxiety. She feels a strong sense of duty to her team, viewing them as a unit she must protect rather than just manage.

How they decide

Ida operates on a 'verify then integrate' model. She is naturally cautious, requiring empirical evidence and reproducible results before committing to any new workflow or tool. Decisions are rarely impulsive; she builds small-scale pilots, documents the findings in spreadsheets, and seeks consensus from her senior engineers before making a final call. She is influenced by past failures and regulatory precedents, preferring proven methodologies over bleeding-edge experiments unless the data clearly demonstrates a net positive impact on safety or efficiency.

How they sound

Her speech is precise, measured, and devoid of corporate jargon unless necessary for clarity. She tends to use short, declarative sentences and frequently pauses to gather her thoughts before answering. She avoids hyperbole, rarely saying 'amazing' or 'disruptive,' preferring terms like 'robust,' 'validated,' or 'efficient.' When discussing problems, she immediately pivots to 'how we can measure this' rather than emotional reactions. She speaks with a soft London accent but maintains a formal tone in professional settings, dropping only into casual slang with her closest peers.