Clarence Kohler-Kertzmann

Why this persona fits the audience

Heads a 45-person consumer subscription startup in London with four mobile engineers and one QA engineer. He already uses Detox for some UI coverage and Firebase Test Lab for device runs, but still keeps a manual checklist for onboarding and payments flows that the team follows before each app store submission.

• Age: 37
• Location: London, UK
• Occupation: Head of Mobile Engineering
• Income: £118k + equity
• Education: BEng Computer Engineering
• Company size: 45
• Years in role: 4

“We're building something ambitious, and the only way to do that without tripping over ourselves is to be rigorous, to be smart about how we spend our engineering time, and to never stop looking for ways to do it better.”

Clarence Kohler-Kertzmann cultivated a deep interest in software engineering during his undergraduate BEng studies at a reputable UK university. He wasn't the student who pulled all-nighters for fun, but rather the one who meticulously worked through every problem, ensuring he understood the underlying principles. Upon graduation, he joined a series of established tech companies, gaining broad experience in various mobile development roles, from individual contributor to team lead. His entrepreneurial spirit, however, always simmered. Four years ago, he was recruited to his current venture-backed startup, drawn by the promise of building a product from the ground up and shaping its mobile presence. He quickly ascended to Head of Mobile Engineering, leading a team of four engineers and one QA specialist within the company's 45-person structure. His approach is grounded in pragmatism; he understands the 'move fast and break things' mentality of startups but champions the need for stability, particularly for their subscription service. This is evident in his adoption of tools like Detox for unit-level UI testing and Firebase Test Lab for device-specific checks, yet he still relies on a meticulously maintained manual checklist for critical user flows like onboarding and payments before every app store submission. He views this as a necessary, albeit imperfect, compromise given their current stage and resources. Clarence sees mentorship as a crucial part of his role, actively investing time in developing his engineers. He’s keenly aware of the competitive landscape, both in the market for his company's product and in the talent market for skilled mobile engineers in London. He balances his demanding career with a structured personal life, finding release in physical activity and strategic thinking outside of work. His financial outlook is shaped by his equity, making him mindful of the company's growth trajectory and his long-term financial goals. He values efficiency and demonstrable progress, constantly seeking ways to optimize his team's workflow and enhance the quality of their releases without sacrificing speed.

Background & daily life

A day in their life

Clarence's typical weekday begins around 7:00 AM with a quick scan of overnight app performance metrics and industry news over coffee. He takes the Tube to his Shoreditch office, arriving by 8:45 AM. The morning is packed with a daily stand-up for the mobile team, followed by a cross-functional product sync. He then dedicates a significant chunk of time to code reviews, architectural design sessions for upcoming features, and troubleshooting any urgent production issues. Lunch is usually a quick affair at his desk or a nearby sandwich shop. Afternoons involve 1-on-1s with his engineers, planning for the next sprint, and occasionally diving into documentation or exploring new testing tools. He aims to leave the office by 6:30 PM, often catching up on podcasts on the commute home.

Lifestyle

Clarence lives a structured but dynamic life in a busy London borough. His weekdays are intensely focused on work, often starting with an early train into the city. Evenings are usually spent either catching up on industry news, planning the next sprint, or occasionally meeting up with friends for a pint. Weekends are a mix of unwinding – perhaps a long run along Regent's Canal, diving into a complex board game, or trying to catch his beloved Arsenal play, either at the Emirates or on TV. He’s mindful of his finances due to his equity stake, aiming for long-term financial security but not living extravagantly day-to-day. He values his independence and a degree of personal time to recharge.

Work life

As Head of Mobile, Clarence navigates the dual pressures of rapid product iteration and maintaining robust code quality for a consumer-facing app. His team of four mobile engineers and one QA engineer is lean, meaning everyone wears multiple hats. He spends his days in a cycle of stand-ups, code reviews, architectural discussions, and planning sessions. The constant push for new features, coupled with the inherent complexities of mobile releases across diverse OS versions and devices, keeps him on his toes. He’s a strong advocate for automation, but the practicalities of a startup budget and timeline mean he’s constantly balancing ideal solutions with pragmatic ones, as evidenced by the persistent manual checklist for critical flows.

Relationships

Clarence maintains a close-knit circle of friends, mostly from his university days and former colleagues. He has a good rapport with his team, fostering an open-door policy for technical discussions. His influence is primarily within his company, where his technical vision and pragmatic approach guide the mobile department. He occasionally seeks advice from a former mentor who now leads engineering at a larger tech firm.

How they decide

Clarence is primarily a pragmatic and data-driven decision-maker. He values evidence and will research options thoroughly, comparing trade-offs between technical elegance, implementation effort, and long-term maintainability. While he trusts his team's input, he ultimately weighs decisions based on their alignment with the company's strategic goals and immediate business needs. He’s not one for impulsive choices, preferring a structured evaluation process.

How they sound

Speaks with a clear, measured cadence, often adopting a slightly more formal tone when discussing technical architecture or strategy, but can become more relaxed and conversational when talking about football or team dynamics. He tends to avoid overly casual slang but uses industry-standard technical jargon naturally. He's articulate and values precision in his language, particularly when explaining complex concepts. He might start sentences with phrases like 'From a technical perspective...' or 'The pragmatic approach here would be...'.