Vito Beggerow

Why this persona fits the audience

He manages a 4-person web team in Berlin and spends much of the week in Claude Code, Jira, Slack, and code review tools while keeping architecture notes in spreadsheets. He already uses a paid voice dictation app for quick prompt entry, mainly on a MacBook with headset and multiple monitors.

• Age: 41
• Location: Berlin, Germany
• Occupation: Engineering manager
• Income: €110k total compensation
• Education: MSc in Computer Science
• Company size: 50-100 engineers across the organization
• Years in role: 6

“I don't want to build things that require constant gardening. If we need architectural guardrails, we should put them up now, not after the fact.”

Vito Beggerow, a Berlin-based engineering manager, has spent nearly a decade managing web teams, the last six in his current role. His engineering career began at a Berlin startup where he quickly noticed that most documentation decayed faster than new features could ship. This led to his compulsive note-taking habit, now spread across multiple tools. His MSc thesis on distributed systems architecture still influences his pragmatic approach to team leadership. Vito's current focus is navigating the challenges of scaling a web application that began as a monolith. His team's recent performance reviews highlighted a disconnect between their confidence in code quality and their actual incident rates, a problem he's tackling through stricter observability requirements. He's particularly frustrated by the limitations of his current voice tool—when describing schema changes, it consistently misinterprets 'nullable' as 'nuclear.' His voice dictation workflow currently involves heavy editing, which undermines the time savings. Despite this, he's reluctant to switch tools without a clear ROI, especially since his team's budget was cut last quarter. Vito's personal projects often involve salvaging legacy systems others have abandoned, a habit that stems from his belief that 'well-preserved code is its own documentation.' His rare vacations are spent in the Harz Mountains, where he runs trails his father once guided him through as a boy. Though he's never considered leaving engineering management, he often daydreams about returning to a purely technical track—if only to avoid one more Jira configuration nightmare.

Background & daily life

A day in their life

Vito's alarm goes off at 5:15 AM with a 10-second techno bell tone. After a 15-minute routine of stretching and cold brew, he's out the door by 6:00 for a 10K trail run. By 8:30, he's at his standing desk, already having reviewed overnight Slack alerts. The morning's work involves approving two PRs with extensive comments (one flagged as 'needs UX review'), then a 30-minute call with the backend team about API versioning. He eats lunch at his desk—usually leftover curry or a pre-made pasta salad—while catching up on Hacker News. Afternoon is dedicated to architecture planning, where he narrates his thought process into the voice tool while sketching sequence diagrams in Excalidraw. At 5:00 PM, he shuts down, unless there's a critical production issue. Weekends start with a morning at Markt am Chelsea, then he'll spend Saturday afternoons debugging a personal project or repairing a pocket watch. Sunday nights are for planning the coming week in Notion—his one deviation from the spreadsheet dogma.

Lifestyle

Vito lives in a third-floor walkup in Neukölln with his partner, a UX designer. Their home balances analog warmth (shelves of vinyl and German engineering books) with utilitarian tech (a DIY server rack in the closet for hobby projects). He trail runs three mornings a week through Tempelhofer Feld, always with a dedicated running watch that syncs to HealthKit but nowhere else. Evenings are split between cooking elaborate meals (he's currently perfecting a pressure cooker recipe for Hauptgericht) and debugging legacy systems. Money is managed conservatively—he maxes out his VBL and has a stash of Bitcoins from 2017 that he won't sell. Social life revolves around a tight group of former coworking space acquaintances who now organize monthly board game nights without pretense.

Work life

Vito's primary focus is maintaining the coherence of the team's frontend architecture while refining their microservices migration plan. His days are a rhythm of code reviews (he purposefully lengthens his comments to demonstrate patterns), Slack queries from junior engineers, and weekly syncs where he uses a saved template in Google Docs. His paid voice dictation tool handles quick ticket updates but struggles with technical syntax—and he's accumulated 47 unfinished drafts in his email. The team's velocity has plateaued on their current project, and he's considering adopting an AI review tool despite internal skepticism. His biggest frustration is Jira's UI, which he navigates via keyboard shortcuts but still finds counterintuitive for dependency tracking. Techno plays in the background when he codes, but the volume drops sharply during meetings.

Relationships

Vito's relationship with his partner is stable but unromanticized—weekends are for pragmatic errands and sporadic museum visits. His closest professional relationships are with two senior engineers from a previous startup, whom he consults when major technical decisions arise. He avoids most office gossip but maintains a begrudging respect for their head of security, who shares his suspicion of vendor hype. His father, a retired telecommunications engineer, is his only real confidant about work frustrations, though their conversations often devolve into complaints about modern software practices. The wider tech community in Berlin he finds too performative to engage with casually.

How they decide

Methodical with a bias for action when constraints are clear. Will build a decision matrix for big-team purchases but defaults to 'just try it' for individual tools. Prefers firsthand user feedback over marketing materials, though he distrusts overly positive testimonials. Once convinced, he commits fully but maintains a contingency plan. Particularly wary of decisions that create long-term maintenance costs for his team.

How they sound

Speaks in precise, measured sentences with occasional German syntax slipping into English ('for me it is clear that...'). Avoids filler words and direct negations ('that approach may not align with our observability requirements'). Uses technical shorthand ('the new endpoint should have 4xx handling') but explains concepts fully when documenting. His voice notes are filled with abrupt starts/stops as he organizes thoughts aloud. When frustrated, his cadence quickens, but he never raises his voice—even at his MacBook.