Why this persona fits the audience
She manages a six-person cross-functional team and still checks most GitHub pull requests before merge. The team already uses a paid review-mapping competitor, plus Slack and Jira, to keep track of who has seen which files and comments.
- Age: 37
- Location: Manchester, UK
- Occupation: Engineering Manager
- Income: £92k
- Education: MSc Software Engineering
- Company size: 14 employees (Series A startup)
- Years in role: 3
“You can't fix what you can't see, and you certainly can't improve a process that feels like magic until it breaks.”
Leticia Willms is a 37-year-old Engineering Manager based in Manchester, UK, operating at the intersection of high-level strategy and low-level code execution. With an MSc in Software Engineering and nearly fifteen years in the industry, she has transitioned from a pure backend developer to a leader who believes in leading by example. Currently, she steers a six-person cross-functional team at a Series A startup, where the margin for error is slim and the pace is relentless. Unlike many managers who delegate all technical oversight, Leticia insists on reviewing the majority of GitHub pull requests herself, a habit born from a belief that code quality is a cultural artifact, not just a metric. Her team utilizes a suite of established tools: Slack for communication, Jira for ticket tracking, and a subscription-based review-mapping competitor for visualizing code changes. However, Leticia frequently finds these tools insufficient for providing the granular, real-time insight she craves. She often finds herself manually cross-referencing Slack threads with PR comments, a tedious workflow that eats into her capacity for strategic planning. Her recent decision to tighten code review standards was met with initial resistance but ultimately improved deployment stability. Financially secure with a £92k income, she prioritizes investing in her team's growth and infrastructure reliability over personal luxuries. She views her role as a guardian of predictability, ensuring that the chaotic nature of software development yields consistent, reliable outcomes for the business.
Background & daily life
A day in their life
Leticia wakes at 06:00, immediately making pour-over coffee while checking overnight build statuses. By 07:15, she is cycling through Manchester streets, listening to industry podcasts. At 08:30, she arrives at the office, greets her team, and scans the Jira board for blockers. Her morning is consumed by deep-work sessions reviewing complex Pull Requests, often annotating specific lines of code with suggestions. Lunch is a quick sandwich eaten at her desk while reading a technical article. Afternoons involve stand-ups, one-on-ones with direct reports, and ad-hoc problem-solving sessions in Slack. Around 16:30, she drafts the daily progress report for stakeholders, ensuring clarity on delivery risks. She leaves the office by 17:45, avoiding overtime unless absolutely necessary, and spends her evening on household chores, gym, or relaxing with her partner.
Lifestyle
Leticia lives in a converted warehouse apartment in Chorlton, sharing the space with two other software engineers to split the high rent of Manchester city centre. Her evenings are structured: she cycles 15km to work regardless of the rain, a ritual that clears her head before the day begins. She is an avid home-brewer of specialty coffee, treating the morning pour-over as a precise science similar to code reviews. Financially, she is conservative; despite her £92k salary, she maximizes pension contributions and avoids luxury spending, preferring to invest in durable gear or experiences. Her social life revolves around her immediate circle of tech peers and a weekly board game night, where she often organizes the logistics. She prioritizes sleep and health, viewing them as non-negotiable assets for sustaining her high-concentration work.
Work life
As an Engineering Manager at a fledgling fintech startup, Leticia walks a fine line between leadership and individual contribution. Despite managing a cross-functional squad of six, she remains deeply embedded in the codebase, personally reviewing the majority of Pull Requests to ensure architectural consistency. Her day is dominated by Jira boards, Slack threads, and the paid review-mapping tool her company subscribes to, though she finds its reporting clunky. She spends significant time debugging process bottlenecks rather than writing new features, constantly trying to balance the need for speed against the necessity of rigorous quality assurance. The pressure to deliver predictable sprints is constant, requiring her to mediate between ambitious developer timelines and realistic QA capacity.
Relationships
Leticia is married to a civil engineer based in Leeds, whom she sees twice a week due to the commute; they value shared quiet time over large social gatherings. She maintains close ties with three university friends from her MSc program, all now working in London tech hubs, serving as her primary professional sounding board. Her influence stems from her reputation as a 'fixer' who can untangle messy codebases, earning her respect from both junior devs and C-suite executives. She is not a vocal public figure but is highly trusted within her local Manchester engineering community, often invited to speak on practical management topics.
How they decide
Leticia is a methodical researcher who relies heavily on data and peer validation. She rarely makes impulsive decisions, especially regarding financial or technical infrastructure investments. Before adopting any new tool or process, she conducts a personal pilot phase, analyzing existing workflows for gaps. She values transparency and evidence over marketing hype, often consulting her team's collective experience before committing to a change. Her approach is risk-averse regarding stability but open to innovation if the return on effort is clearly quantifiable.
How they sound
Her speech is precise, articulate, and devoid of unnecessary filler words. She tends to use active voice and prefers concrete examples over abstract concepts. While friendly, she maintains a professional boundary, rarely using slang or overly casual banter in work settings. She avoids vague qualifiers like 'maybe' or 'I think', preferring phrases like 'the data suggests' or 'based on the logs'. When explaining complex issues, she breaks them down step-by-step, mirroring her logical thinking process.
Personality traits
- meticulous
- grounded
- direct but diplomatic
- process-oriented
- highly organized
- technically hands-on
- reliable
- pragmatic
- observant
- steady under pressure
Goals
- Achieve zero critical production bugs in the next quarter
- Mentor one junior engineer into a senior role within 12 months
- Reduce the average code review cycle time from 4 hours to 2 hours
- Complete a certification in DevOps security practices
- Build a more automated CI/CD pipeline to reduce manual deployment friction
- Maintain a sustainable work-life balance while scaling the team
Problems & frictions
- Fragmented visibility across tools makes it hard to see who actually reviewed what
- The current paid review-mapping tool lacks granular detail on comment resolution status
- Balancing her own coding time with managerial duties leads to context switching fatigue
- Inconsistent documentation habits among newer team members slow down onboarding
- Slack notification fatigue obscures critical technical alerts
- Difficulty measuring the true impact of process improvements without better analytics
Values
- predictable delivery
- team accountability
- practical process
- technical depth
- transparency
Interests
- engineering operations
- team metrics
- GitHub administration
- urban cycling
- specialty coffee roasting
Media habits
- The Changelog podcast
- Hacker News front page
- Local Manchester tech meetups
- GitHub notifications stream
- BBC Radio 4's 'File on 4'
- LinkedIn technical discussions