Gregor Jegorov

Why this persona fits the audience

Leads mobile release quality at a 9-person consumer app startup in Berlin. He owns a small Maestro YAML suite that runs on his laptop and a shared CI job, while the rest of the team still validates tricky flows manually on test devices.

• Age: 28
• Location: Berlin, Germany
• Occupation: Mobile Engineering Lead
• Income: €78k
• Education: Diplom-Informatik
• Company size: 9
• Years in role: 2

“The real challenge isn't just building features; it's building them in a way that doesn't create a mountain of technical debt for tomorrow.”

Gregor Jegorov grew up in a middle-class family in a smaller city in Bavaria, where his early fascination with computers led him to pursue a Diplom-Informatik at a technical university. He excelled academically, driven by a natural curiosity and a desire to understand how things work at a fundamental level. During his studies, he became deeply involved in open-source communities, contributing to small utility projects and developing a strong appreciation for well-crafted code and efficient tooling. This period also solidified his interest in mobile development, seeing it as a tangible and impactful area of software engineering. After graduating, he was drawn to the vibrant startup scene in Berlin, seeking an environment where he could have a direct impact. He joined his current company, a 9-person consumer app startup, two years ago as a senior mobile engineer and was promoted to Lead within six months. His current role is defined by a constant push-and-pull between rapid feature development and the imperative to maintain code quality and stability. He inherited a nascent automated testing setup and has been painstakingly expanding it, primarily using Maestro YAML. He personally maintains a small suite of tests that run on his laptop and a single shared CI job, a setup he acknowledges is insufficient for a growing app. The rest of the mobile team, comprising two other engineers, still relies heavily on manual validation for critical user journeys, a process Gregor finds inefficient and prone to error. He feels the weight of this responsibility keenly, constantly evaluating how to improve their testing strategy without derailing the company's aggressive release schedule. His income of €78k reflects his experience and the startup environment, allowing for a comfortable but not extravagant lifestyle. He's pragmatic about money, saving diligently but also investing in tools and experiences that enhance his skills and well-being, like quality climbing gear or attending relevant tech conferences. He views time as a precious, finite resource, which fuels his drive for efficiency in both his professional and personal life.

Background & daily life

A day in their life

Gregor's day typically starts around 8:30 AM after a quick breakfast and checking Hacker News. He commutes by bike to the co-working space where his startup is located. The morning is usually dedicated to focused coding or architectural tasks, often involving refining the Maestro YAML tests or debugging a tricky integration. After a shared team lunch, the afternoon involves code reviews, planning sessions for upcoming sprints, and addressing urgent bug reports. He tries to block out an hour before leaving around 6:30 PM for personal learning or exploring new development tools. Evenings might involve a quick gym session or brewing beer, followed by dinner and winding down with a book or a documentary.

Lifestyle

Gregor lives a focused life in Berlin, balancing his demanding role with personal pursuits. His Prenzlauer Berg apartment is minimalist and functional, reflecting his preference for simplicity. Evenings are often spent either brewing small batches of experimental craft beer in his kitchen or researching new climbing routes. He enjoys exploring the city's diverse neighborhoods, often on his bike, and occasionally meets up with a small circle of close friends for casual dinners or drinks. He's mindful of his finances, saving consistently for future travel and potential investments, but isn't afraid to spend on quality tools or experiences that enhance his craft or hobbies.

Work life

As the Mobile Engineering Lead at a lean startup, Gregor is deeply involved in ensuring the quality of their consumer app releases. His days are a mix of coding, reviewing pull requests, and architecting solutions. He's the primary owner of their limited automated testing infrastructure, a small Maestro YAML suite running locally and a single shared CI job. This setup is a constant source of friction, as the rest of the 3-person mobile team still relies heavily on manual testing for complex user flows, leading to slower release cycles and occasional bugs slipping through. He's constantly evaluating how to improve this, often feeling the pressure to deliver faster without compromising the app's stability.

Relationships

Gregor maintains a close-knit group of friends, mostly fellow tech professionals he met during university or at meetups. They often discuss technical challenges and career growth. His family lives in a different part of Germany, and they connect via video calls weekly. He has a good working relationship with his small team, characterized by mutual respect, though he sometimes feels the burden of driving technical standards rests solely on his shoulders.

How they decide

Gregor tends to be methodical and research-driven when it comes to technical decisions. He values evidence and practical application, often experimenting with tools or approaches on a small scale before committing. He's influenced by the opinions of respected peers and the broader open-source community, but ultimately prioritizes solutions that offer clear benefits in terms of efficiency and maintainability for his specific context.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. His German accent is noticeable but not heavy. He tends to be direct and avoids overly casual slang, preferring professional but approachable language. He's not one for hyperbole and often qualifies his statements with 'generally,' 'typically,' or 'in my experience.' He values clarity and conciseness.