Lilly Stolz

Why this persona fits the audience

Leads a five-person mobile team at a Berlin startup shipping an iPad-heavy B2B app. Each developer works on a Mac; she maintains a shared cleanup checklist and a spreadsheet of device, simulator, and DerivedData reset steps for releases.

• Age: 41
• Location: Berlin, Germany
• Occupation: Engineering Manager, Mobile
• Income: €105k
• Education: MSc Computer Science
• Company size: Approximately 40 employees
• Years in role: 3

“Predictability in our release process isn't about rigidity; it's about freeing up our minds to focus on building great features, not fighting the build.”

Lilly Stolz, 41, is a seasoned mobile engineering manager at a fast-paced Berlin startup specializing in B2B iPad applications. Holding an MSc in Computer Science, she transitioned into management after several years as a senior iOS developer, drawn by the challenge of scaling teams and optimizing development workflows. Her current role places her at the helm of a five-person mobile team, where she meticulously oversees the development and release of their core product. Lilly's approach is deeply rooted in pragmatism and a drive for predictability. She understands the inherent chaos of startup environments and actively works to mitigate it through structured processes. A prime example is her dedication to refining the mobile release pipeline. Recognizing the pain points of inconsistent build environments and time-consuming manual cleanup, she has developed and maintains a comprehensive shared checklist and a detailed spreadsheet. This documentation guides her team through the necessary steps for resetting devices, simulators, and DerivedData caches, aiming to make each bi-weekly release as smooth and error-free as possible. She views this meticulous attention to detail not as bureaucracy, but as essential groundwork for developer efficiency and product stability. Lilly is financially conscious, earning a solid €105k income, which she manages responsibly, prioritizing long-term security and investing in experiences over excessive material possessions. Her work-life balance is crucial; while deeply committed to her team's success, she strictly adheres to her working hours, valuing her personal time for running, reading, and recharging. This discipline stems from a desire to avoid burnout and maintain a sustainable career trajectory. She is respected by her team for her technical acumen, her calm demeanor under pressure, and her genuine commitment to fostering a supportive and productive work environment. Her recent focus has been on further automating parts of the build and testing process, a project born from observing the recurring friction points her team faces during release cycles.

Background & daily life

A day in their life

Lilly's typical weekday begins around 7:30 AM with a quick check of overnight build statuses and urgent Slack messages. After her morning run and breakfast, she's fully engaged by 9:00 AM. The morning is usually packed with a stand-up meeting, one-on-one check-ins with her developers, and focused work on refining the release checklist or investigating a recurring build issue. Lunch is often a working lunch, perhaps reviewing a product spec or discussing a technical challenge with a colleague. The afternoon might involve sprint planning, code reviews, or collaborating with the backend team on API integrations. She aims to wrap up by 5:30 PM, ensuring all critical tasks are addressed and the team is set for the next day, often ending with a final review of the day's progress.

Lifestyle

Lilly's life outside work is structured but flexible. She wakes early for a run most mornings, often along the Spree or through Volkspark Friedrichshain, followed by a quick, healthy breakfast. Evenings are typically quiet, spent reading, catching up on industry news, or occasionally meeting friends for a relaxed dinner or a craft beer at a local Kneipe. She's financially responsible, saving diligently for future travel and potential property investment, but enjoys Berlin's cultural offerings. Her social circle is tight-knit, primarily composed of fellow tech professionals and a few long-term friends from university.

Work life

As the mobile engineering manager, Lilly's days are a blend of technical oversight, team management, and process refinement. She spends a significant portion of her time unblocking her five developers, reviewing pull requests, and planning upcoming sprints. A core part of her role involves ensuring smooth, predictable release cycles for their iPad-centric B2B application. This means meticulously managing the shared cleanup checklist and the detailed spreadsheet that guides developers through device, simulator, and DerivedData resets, especially critical before each bi-weekly deployment. She champions pragmatic solutions to technical debt and strives to foster a collaborative, low-friction environment.

Relationships

Lilly maintains strong professional relationships with her team, fostering an environment of mutual respect and open communication. She collaborates closely with the Head of Product and the CTO, often acting as a bridge between technical execution and product vision. Her personal life is anchored by a small group of close friends, many of whom are also in the tech industry, providing a valuable sounding board for both work and life challenges.

How they decide

Lilly approaches decisions with a blend of pragmatism and thoroughness. She values data and evidence, preferring to research options, consult with her team, and understand the potential impact before committing. While she can be decisive when necessary, she generally favors a measured, iterative approach, especially when it involves process changes or adopting new tools. She's not easily swayed by hype and prioritizes solutions that offer tangible benefits and fit within the team's existing workflow.

How they sound

Lilly speaks with a clear, measured cadence, her German accent subtly present. Her tone is generally calm and professional, avoiding overly casual slang but also not being stiff. She uses precise technical language when discussing engineering topics but can simplify complex ideas for non-technical stakeholders. She tends to avoid hyperbole and focuses on factual reporting and reasoned arguments. When discussing team matters, her voice carries a tone of supportive leadership.