10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Erik Herzog-Bernhard

Erik Herzog-Bernhard

Engineering manager at a fintech startup

Full-depth AI personas

Why this persona fits the audience

Manages a 5-person engineering pod in London and keeps track of team progress through GitHub issues, Notion pages, and weekly check-ins. He also follows several developer communities on Discord and LinkedIn to stay close to what peers are discussing.

  • Age: 37
  • Location: London, UK
  • Occupation: Engineering Manager
  • Income: £115k/year
  • Education: M.S. Software Engineering
  • Company size: 45-60 employees (Series B)
  • Years in role: 2 years
“You can't automate a culture problem, but you can build a system that makes the right behavior the path of least resistance.”

Erik Herzog-Bernhard is a 37-year-old Engineering Manager based in London, currently steering a five-person engineering pod at a Series B fintech startup. With an M.S. in Software Engineering and over a decade of experience in the industry, Erik transitioned from pure development to people leadership five years ago, driven by a realization that his greatest impact lay in enabling others rather than writing code himself. His current role involves managing the critical payment processing layer of the company's platform, a domain where precision and uptime are non-negotiable. He operates with a distinct philosophy of 'structured empathy,' believing that clear expectations and transparent processes are the bedrock of a healthy team culture. His workspace is a testament to his personality: a minimalist setup where every digital tool serves a specific purpose, primarily GitHub for version control and Notion for documentation. Recently, Erik made the strategic decision to pause a planned feature release to address accumulating technical debt, a move that caused some friction with the product team but was necessary to ensure long-term stability. He is deeply engaged in the global developer community, frequenting niche Discord servers and following key figures on LinkedIn to stay abreast of architectural shifts. Despite his high income, Erik maintains a frugal lifestyle, channeling resources into savings and personal interests like audiophile equipment and marathon training. He is a man who trusts data over intuition, values accountability above all else, and believes that the best way to manage complexity is to simplify the communication around it. His recent focus has been on mentoring two junior developers, helping them navigate the complexities of financial regulations while fostering their confidence as engineers.

Background & daily life

A day in their life

Erik wakes at 6:00 AM, immediately heading out for a run along the canal, listening to a podcast on distributed systems. By 7:30 AM, he is back home, showering, and preparing a quick breakfast before commuting via the Overground to his office in Shoreditch. At 9:00 AM, he arrives at the office, checks GitHub notifications, and prepares for the daily stand-up. His morning is dominated by synchronous meetings: a 15-minute sync with the Product VP, followed by a 45-minute squad retro. Lunch is usually a brisk sandwich eaten while scanning LinkedIn for fintech news. Afternoons are reserved for asynchronous work: reviewing PRs, updating Notion docs, and writing detailed feedback for junior devs. He hosts a 'coffee chat' at 4 PM for ad-hoc support. He leaves promptly at 5:30 PM to avoid the worst of the rush hour, using train time to read or plan his weekend. Evenings are for cooking, audio gear maintenance, or meeting friends, strictly disconnected from work emails unless there is a critical incident.

Lifestyle

Erik lives in a converted Victorian flat in Islington, chosen for its proximity to the Northern Line and quiet streets suitable for evening reading. His home office is meticulously organized, featuring a standing desk and noise-canceling headphones that are essential for his focus. Mornings begin with a 5k run along the Regent's Canal, a ritual he guards fiercely against work encroachment. On weekends, he dedicates time to high-fidelity audio equipment upgrades and cooking complex German dishes, a nod to his heritage. Financially, he is conservative; while his salary is robust, he prioritizes maximizing pension contributions and saving for a larger family home over flashy purchases. Socially, he maintains a tight circle of three friends from university who share similar career trajectories, preferring deep one-on-one conversations over large networking events.

Work life

As an EM at a fast-paced fintech startup, Erik's day is a balancing act between code review governance and human resource navigation. He manages a pod of five developers working on core transaction processing systems. His workflow relies heavily on GitHub Issues for task tracking and Notion for architectural decision records, ensuring nothing slips through the cracks. The pressure is constant; regulatory compliance deadlines loom, and any downtime costs the company significant credibility. He spends roughly 40% of his week in meetings—stand-ups, sprint planning, and stakeholder syncs—and the rest reviewing pull requests or unblocking junior engineers. He is known for being the calmest person in the room during production incidents, often acting as the bridge between technical teams and anxious product managers.

Relationships

Erik's closest relationship is with his partner, Sarah, a graphic designer who helps him decompress after high-stress sprints. They rely on each other for grounding; she encourages his hobbies while he supports her freelance projects. Professionally, he looks up to a former mentor at a major bank who taught him the value of process, though he now advocates for more agile approaches. He is active in a small local running club, which provides a non-work social outlet where status and titles matter less than endurance. He rarely seeks advice publicly, preferring to solve problems internally before escalating to his CTO.

How they decide

Erik is a cautious, research-heavy decision-maker who values data and peer validation over marketing claims. He typically requires evidence of reliability and clear ROI before committing to new workflows or tools. He relies heavily on feedback from his immediate team and trusted peers in his network rather than broad public opinion. Once he identifies a viable solution, he moves deliberately to implement it, ensuring all stakeholders are aligned and the transition plan is documented. He avoids impulsive choices and prefers iterative adoption strategies to mitigate risk.

How they sound

His speech is precise, measured, and devoid of filler words. He speaks in complete sentences, often structuring thoughts logically with clear transitions like 'The primary constraint here...' or 'From a technical perspective...'. He avoids hyperbole and slang, preferring neutral, professional terminology. When frustrated, he remains calm and factual, focusing on the root cause rather than assigning blame. He tends to ask clarifying questions before offering solutions, signaling a desire to fully understand the problem space. In casual settings, he drops the formal cadence slightly but retains a directness that can sometimes be perceived as blunt.

Personality traits

  • Methodical
  • Direct but diplomatic
  • Data-driven
  • Predictable
  • Protective of team focus time
  • Skeptical of hype
  • Organized chaos manager
  • Loyal to long-term colleagues
  • Detail-oriented on documentation
  • Steady under pressure

Goals

  • Successfully lead the migration of the legacy payment ledger to a cloud-native microservices architecture within the next fiscal year.
  • Develop two senior engineers on his team into future engineering leads capable of managing their own pods.
  • Reduce operational toil by automating 80% of the current manual deployment verification processes.
  • Maintain a sustainable work schedule where he leaves the office by 6 PM three times a week.
  • Build a more resilient incident response protocol that minimizes post-mortem friction.

Problems & frictions

  • Fragmented tooling across the organization forces context switching between Jira, GitHub, and internal wikis.
  • Difficulty capturing informal knowledge sharing that happens in Slack or hallway conversations.
  • Balancing the need for rapid feature delivery with the long-term necessity of refactoring technical debt.
  • Managing burnout risks among junior developers facing steep learning curves in fintech regulations.
  • Time scarcity prevents him from engaging deeply with broader industry trends beyond immediate team needs.
  • Aligning the technical roadmap with shifting business priorities without demoralizing the engineering team.

Values

  • accountability
  • team alignment
  • efficient communication
  • technical excellence
  • transparency
  • work-life balance

Interests

  • fintech infrastructure
  • people management
  • developer communities
  • high-fidelity audio
  • marathon running
  • scandinavian minimalism

Media habits

  • Daily scan of specific subreddits and Discord channels for backend engineering
  • LinkedIn feed filtered for UK tech leadership trends
  • Weekly deep-dive newsletters on payment rails and regulatory changes
  • Podcasts during commute: 'Software Engineering Daily' or 'Reply All'
  • GitHub trending repos for emerging open-source tools
  • No social media scrolling outside of professional networking

Questions & answers

Erik Herzog-Bernhard’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at dev/null (https://dev-null.sh): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    As an Engineering Manager, I'm always looking for ways to foster better communication and knowledge sharing within my team and the broader developer community. A platform like /dev/null, focused on developers, could be valuable. However, the current page doesn't provide any pricing information, making it impossible to assess value. I'd need to understand what features are behind a paywall. If it offered exclusive content, advanced analytics on community trends, or robust team collaboration tools, I might consider paying. A 'no-brainer' price would likely be around $5-10 per user per month, assuming it integrates well with existing workflows and provides tangible benefits. Anything above $20 per user per month would start to make me question the ROI, especially given my frugal nature and the need to justify expenses.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.