Miguel Leberer

Why this persona fits the audience

Part of a 12-person fintech startup in Berlin. He maintains a few long-running account-verification and ledger reconciliation jobs and currently runs one of them on a paid Temporal Cloud setup while the rest are handled by scheduled scripts and database flags.

• Age: 29
• Location: Berlin, Germany
• Occupation: Full-stack engineer
• Income: €92k
• Education: MSc in Software Engineering
• Company size: 12
• Years in role: 4

“The real challenge isn't just building features, it's building them in a way that doesn't create a ticking time bomb for tomorrow.”

Miguel Leberer, 29, is a full-stack engineer at a dynamic 12-person fintech startup based in Berlin. Holding an MSc in Software Engineering, he possesses a deep-seated drive for system correctness and auditability, values that stem from his early fascination with how complex systems function and fail. His career trajectory has been marked by a consistent focus on robust engineering practices, even within the fast-paced startup environment. He lives in a shared apartment in Prenzlauer Berg, a choice that reflects his pragmatic approach to finances and his preference for a communal living experience over solitary isolation. His income of €92k allows for comfortable living and a degree of financial security, which he supplements with diligent saving. Miguel's current professional focus is on maintaining critical account-verification and ledger reconciliation jobs. To address the inherent complexities and the need for reliable execution, he recently spearheaded the adoption of Temporal Cloud for one of these key processes. This decision was driven by a desire for better visibility, built-in retry mechanisms, and a more auditable workflow, moving away from the inherent fragility of his previous approach. However, the remaining critical jobs still operate on a less sophisticated stack of scheduled scripts and database flags, a compromise he finds increasingly concerning and a constant source of low-level anxiety. This duality in his operational landscape highlights the ongoing tension between rapid development and the imperative for rock-solid infrastructure in fintech. He is deeply interested in distributed systems and developer tooling, constantly seeking ways to improve the reliability and maintainability of his team's codebase. His personality, characterized by high conscientiousness and moderate openness, means he approaches problems methodically, meticulously analyzing solutions before committing. He is not prone to impulsive decisions, preferring to build a solid understanding before acting. This deliberate approach extends to his personal life, where he values routine and predictability, finding comfort in well-structured systems, both digital and analog.

Background & daily life

A day in their life

Miguel's weekday typically begins around 7:00 AM. After a quick breakfast and checking global tech news on Hacker News, he cycles to the startup's office. The morning is usually dedicated to focused coding on a new feature or tackling a particularly tricky bug. He has a stand-up meeting with his team around 10:00 AM, where they discuss progress and blockers. Lunch is often a packed meal or a quick bite from a nearby Imbiss. The afternoon might involve code reviews, architectural discussions, or diving into the operational aspects of their systems, including monitoring the Temporal Cloud job and investigating any anomalies in the script-based ones. He usually leaves around 6:00 PM, heading home to cook dinner and unwind, perhaps by reading a tech blog or listening to a podcast.

Lifestyle

Miguel lives in a shared apartment in Prenzlauer Berg, a vibrant district in Berlin, with two friends from university. He values his independence and enjoys the city's cultural offerings, often visiting galleries or attending small concerts. His routine is fairly structured, with early mornings dedicated to coding before the office buzz. He cooks most of his meals, prioritizing healthy ingredients, and occasionally splurges on craft beer at local pubs. While not a big spender, he's comfortable financially and saves a portion of his income, viewing it as a buffer for future stability rather than immediate gratification. Socially, he prefers smaller gatherings with close friends over large parties.

Work life

As a full-stack engineer at a lean fintech startup, Miguel's days are a blend of feature development and critical infrastructure maintenance. He's responsible for ensuring the reliability of core processes like account verification and ledger reconciliation. Currently, one of these crucial, long-running jobs is managed via Temporal Cloud, a decision made to improve its stability and auditability. The remaining jobs, however, still rely on a patchwork of scheduled scripts and database flags, a situation he finds increasingly precarious. He collaborates closely with a small team, often pair-programming or discussing architectural choices. The pressure to ship features while maintaining rock-solid stability is constant.

Relationships

Miguel maintains close ties with his two roommates, who are also friends from his MSc program. He has a small circle of trusted friends from university and work, with whom he shares his passion for technology and occasionally explores Berlin. His parents, who live in a smaller town in Bavaria, are supportive but don't fully grasp the intricacies of his work. He values their opinion but makes his own career decisions.

How they decide

Miguel is a methodical and research-driven decision-maker. He thoroughly investigates options, weighing pros and cons, and often seeks out technical documentation and case studies. He's not easily swayed by hype and prefers solutions with a proven track record or strong theoretical underpinnings. While he values peer input, especially from trusted colleagues, the final decision rests on his own analysis of technical merit and long-term viability.

How they sound

Speaks with a clear, measured cadence, often pausing to formulate his thoughts precisely. His German is standard, with a slight academic inflection from his university days. He avoids overly casual slang or jargon when discussing technical matters, preferring clarity and accuracy. When explaining complex systems, he tends to use analogies to make them more accessible. He’s not one for hyperbole and is generally reserved in his expressions of strong emotion.