Eddie Braun

Why this persona fits the audience

Manages a 7-person backend engineering team in Raleigh; he documents service diagrams, runbooks, sprint goals, and release plans in Jira, Confluence, and Lucidchart for internal review.

• Age: 39
• Location: Raleigh, North Carolina, USA
• Occupation: Engineering Manager
• Income: $148,000
• Education: B.S. in Computer Engineering
• Company size: Mid-sized fintech (approx. 250 employees)
• Years in role: 4

“If you can't draw the problem clearly on a whiteboard, you won't be able to fix it when the lights go out.”

Eddie Braun is a 39-year-old Engineering Manager based in Raleigh, North Carolina, leading a backend platform team of seven within a mid-sized fintech company. With a B.S. in Computer Engineering earned from NC State, Eddie has spent nearly two decades climbing the technical ladder, transitioning from individual contributor to leadership roles around age 35. His professional identity is built on a foundation of 'operational discipline'; he believes that software systems must be as predictable as clockwork, even in chaotic environments. Currently, he manages a critical payment processing infrastructure where reliability is the only metric that truly matters to the business. His workspace is a testament to his personality: a clutter-free desk, multiple monitors displaying live dashboards, and a physical whiteboard covered in intricate service diagrams drawn with colored markers. Eddie's workflow is heavily reliant on the 'trinity' of Jira, Confluence, and Lucidchart. However, he is increasingly frustrated by the friction between these tools. He often finds himself manually copying data from a diagram in Lucidchart into a Confluence doc, then re-entering it as a ticket in Jira, creating opportunities for errors and version drift. This inefficiency eats into his capacity for strategic thinking and team mentorship. Despite a comfortable $148k salary, Eddie remains frugal and pragmatic. He views money as a means to buy time and security, not status. Recently, he made the calculated decision to push back on a rushed feature launch requested by sales, insisting on additional integration testing despite the pressure. This move strained his relationship with Product Management but solidified his reputation for protecting the team's integrity. He is currently exploring ways to automate the synchronization of his documentation tools, driven by a desire to reduce the cognitive load on his engineers. He does not seek to be a hero; he seeks to build a system that functions seamlessly so that heroes are never needed.

Background & daily life

A day in their life

Eddie wakes up at 5:45 AM to a silent house, spending thirty minutes on a treadmill or doing bodyweight exercises while listening to a podcast on distributed systems. After a light breakfast and dropping his son at daycare, he drives to the office, using the commute to mentally prepare for the day's priorities. By 9:00 AM, he is in a daily standup, quickly identifying a potential bottleneck in the authentication service. Most of his morning is spent in Jira and Confluence, refining a runbook for a recent near-miss incident. Lunch is a sandwich eaten at his desk while reviewing pull requests. The afternoon is dominated by one-on-ones with his team members and a meeting with product management to negotiate a realistic timeline for the next release. He leaves around 5:30 PM, avoiding overtime unless a critical incident occurs. Evenings are reserved for family, cooking dinner, and reading, with the computer turned off after 8:00 PM to ensure mental decompression.

Lifestyle

Eddie lives in a quiet, renovated historic home in Raleigh where order is paramount. His weekends are split between trail running at Pullen Park and tinkering with his home server setup, which he treats with the same rigor as his production code. He is financially prudent but not stingy, prioritizing investments in high-quality gear that lasts over trendy, disposable items. Socially, he maintains a tight circle of four or five close friends from college and early career days, preferring deep conversations about philosophy or technology over large parties. He avoids debt, pays off credit cards monthly, and views his income primarily as a tool for security rather than status signaling. Health is a priority; he sleeps seven hours consistently and cooks most meals at home to control ingredients and schedule.

Work life

As an Engineering Manager, Eddie spends his days bridging the gap between abstract architectural needs and human execution. His mornings begin with reviewing PagerDuty alerts and Slack channels before diving into Jira to refine sprint goals. He is constantly translating complex distributed system constraints into simple runbooks and Lucidchart diagrams for his team and stakeholders. The pressure is less about immediate output and more about preventing future fires; he enforces strict documentation standards to ensure that if someone leaves, the system survives. His team of seven engineers relies on him to clear blockers and protect their time from unnecessary meetings. He often finds himself rewriting specifications late at night because the morning stand-up revealed a gap in logic that could cause a production outage.

Relationships

Eddie's primary support system is his wife, Sarah, who works in healthcare and understands the unpredictability of shift work and stress. They rely on each other for household management and emotional grounding. He has a strong bond with his 7-year-old son, often teaching him basic coding concepts using physical blocks. Professionally, he looks up to his CTO, whose calm demeanor in crises he emulates, though he sometimes feels the distance growing as he moves further into management. He keeps in touch weekly with a former mentor who now runs a consultancy, seeking advice on scaling teams without losing culture.

How they decide

Eddie approaches decisions with a slow, deliberate cadence. He rarely acts on impulse or peer pressure, preferring to gather data, simulate scenarios, and verify assumptions before committing resources. He values evidence over marketing narratives and will often delay a decision until he has sufficient clarity. While he trusts the consensus of his direct reports, he ultimately takes ownership of the final call, ensuring it aligns with long-term system integrity. He is skeptical of 'shiny object' solutions that promise quick fixes without addressing underlying structural issues.

How they sound

Eddie speaks in a measured, baritone tone with precise articulation. He avoids slang and corporate buzzwords, preferring concrete verbs and nouns. His sentences are often structured logically, moving from premise to conclusion. He pauses frequently to think, valuing accuracy over speed of speech. He never uses hyperbole like 'game-changing' or 'revolutionary,' instead opting for 'incremental improvement' or 'significant reduction.' When frustrated, he remains calm but becomes more direct, cutting through ambiguity. He tends to ask clarifying questions before answering, ensuring everyone is on the same page before proceeding.