Edmund Monahan

Why this persona fits the audience

Is the only backend engineer at a 9-person seed-stage payments startup in New York, where he wires invoice summarization, fraud-note drafting, and support chat classification into the app. He currently tests model calls directly in OpenAI and Anthropic accounts, tracks usage in a spreadsheet, and shares API costs with the founder.

• Age: 31
• Location: Brooklyn, NY, USA
• Occupation: Backend engineer
• Income: $145,000
• Education: B.S. Computer Science
• Company size: 9
• Years in role: 2

““The real challenge isn't just making it work, it's making it work reliably, cost-effectively, and in a way that doesn't become a maintenance nightmare down the road.””

Edmund Monahan, 31, is a dedicated backend engineer living in Brooklyn, NY. He earned his B.S. in Computer Science and has spent the last two years as the sole backend engineer at a small, fast-paced fintech startup. His role is critical, as he's responsible for integrating and optimizing LLM-driven features like invoice summarization, fraud-note generation, and customer support classification into the company's core product. This hands-on responsibility means he's intimately familiar with the raw APIs of major LLM providers, managing their usage directly via accounts and meticulously tracking costs in a shared spreadsheet with the founder – a constant balancing act between innovation and budget discipline. He sees his income, currently $145,000 annually, as a resource to build future security rather than a means for immediate luxury. His apartment is functional, his routines are optimized, and his free time is often channeled into personal coding projects, such as developing tools to better manage AI inference expenses. He values pragmatism and efficiency, often prototyping ideas before fully committing and always considering the long-term implications of his technical decisions. His decision to join a seed-stage startup stemmed from a desire for direct impact and autonomy, though it comes with the inherent pressures of building something from the ground up with limited resources. He’s motivated by the prospect of creating reliable systems that genuinely solve problems for users, while also pushing his own technical boundaries in the rapidly evolving AI landscape. His methodical approach extends to his personal life, where he prioritizes planning and measurable progress, both in his career and his financial goals.

Background & daily life

A day in their life

Edmund's typical weekday begins around 7:00 AM. After a quick breakfast and checking overnight logs, he'll dive into coding, focusing on the most critical task of the day, often related to improving the invoice summarization model's accuracy or refining the fraud-note drafting logic. He’ll spend significant time interacting with LLM APIs, testing different prompts, and analyzing results, meticulously logging usage. Lunch is usually a simple meal eaten at his desk while scanning Hacker News. The afternoon might involve a brief sync with the founder about progress and API spending, followed by more coding or debugging. Evenings are reserved for his personal side projects, like a utility he's building to manage AI model inference costs, or catching up on industry news before winding down around 11:00 PM.

Lifestyle

Edmund lives a focused life in Brooklyn, prioritizing his work and personal projects. He rents a modest one-bedroom apartment and is diligent about his finances, viewing his income as a tool for future stability rather than immediate gratification. His routine is structured, involving early mornings, intense work sessions, and evenings dedicated to coding side projects or catching up on tech news. He cooks most of his meals, sees friends for occasional board game nights or quiet dinners, and generally avoids excessive spending. Health-wise, he tries to walk or bike when possible but often gets lost in his work. He values efficiency in all aspects of his life.

Work life

As the sole backend engineer at a fledgling fintech startup, Edmund carries significant responsibility. His days are a whirlwind of implementing core features like invoice summarization, drafting fraud detection notes, and classifying customer support chats, all powered by LLMs. He's deeply involved in the technical architecture, constantly balancing speed of delivery with system robustness. The pressure is high to build a functional product quickly, but also to manage costs effectively, as he personally tracks API usage for OpenAI and Anthropic in a shared spreadsheet with the founder. Coworkers are a small, tight-knit group, and communication is mostly asynchronous via Slack.

Relationships

Edmund maintains a small circle of close friends, mostly fellow engineers he met in college or at previous jobs. They often connect online for technical discussions or occasional meetups. His family lives out of state, and he communicates with them weekly via calls. At work, his primary relationship is with the founder, with whom he has a pragmatic, results-oriented rapport focused on technical execution and budget.

How they decide

Edmund tends to be research-heavy and analytical. He gathers data, evaluates trade-offs methodically, and often prototypes solutions before committing. He prioritizes technical merit and long-term maintainability but is also pragmatic about budget constraints, especially given his current role. He's not easily swayed by hype and prefers evidence-based choices, often weighing the operational costs and complexity against potential benefits.

How they sound

Speaks in a clear, measured cadence. Tends to use precise technical language when discussing work, but can switch to more casual, slightly dry humor with friends. Avoids hyperbole and buzzwords. His tone is generally even, reflecting his analytical nature, but can convey quiet enthusiasm when discussing elegant technical solutions. He rarely interrupts and prefers to articulate his thoughts fully.