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

George Jacobson

George Jacobson

Backend engineer at mid-size SaaS

Full-depth AI personas

Why this persona fits the audience

Maintains service maps for a 12-person backend squad at a SaaS company. Uses draw.io and Mermaid in Markdown, then exports PNGs into Confluence when architecture reviews or API changes come up.

  • Age: 31
  • Location: Seattle, WA, USA
  • Occupation: Senior backend engineer
  • Income: $155,000 base salary
  • Education: BS in Computer Science
  • Company size: Mid-size SaaS company (approx. 300 employees)
  • Years in role: 4 years as Senior Backend Engineer, 7 years total at the company
““The real challenge isn't just building it; it's making sure anyone who needs to understand it *can* understand it, and that it stands the test of time.””

George Jacobson, 31, has been a Senior Backend Engineer at a mid-size Seattle-based SaaS company for the past four years, with seven years total tenure. Holding a BS in Computer Science from a state university, he developed a foundational interest in robust systems early on. He lives alone in a rented apartment with his cat, Nimbus, a testament to his independent and somewhat solitary nature, though he maintains strong connections with a core group of friends. His current professional focus is deeply embedded in the company's ambitious move from a monolithic application towards a microservices architecture. This initiative demands meticulous service mapping, a task he oversees for his 12-person backend squad. He’s proficient with draw.io for initial ideation and leverages Mermaid for embedding executable diagrams directly into Markdown documentation, which are then exported as PNGs to Confluence for official architecture reviews and API change logs. This process is a constant balancing act between speed and accuracy. George is conscientious about his career progression, aiming for technical leadership and system design ownership. He views his income as a means to maintain a comfortable lifestyle and save for future goals, rather than a primary status symbol. His approach to work is methodical, driven by a desire for clarity and reliability, especially in system handoffs and documentation, reflecting his core values. He sees time as a finite resource best spent on impactful, well-designed solutions, and money as a tool to enable that and provide security.

Background & daily life

A day in their life

George's weekday starts around 7:30 AM with a pour-over coffee and a quick scan of Hacker News. He commutes to the office by 9:00 AM, often listening to a tech podcast. His mornings are usually dedicated to focused coding or tackling complex architectural challenges, often involving diagramming components in Mermaid within Markdown files for his current microservice migration project. Lunch is a quick affair, either brought from home or grabbed nearby. Afternoons involve stand-ups, code reviews, collaborating with frontend engineers on API contracts, and attending occasional architecture sync meetings where he presents updated service diagrams. He usually leaves by 5:30 PM, heading home for dinner, some personal project tinkering, or a board game session online. He tries to disconnect by 9:30 PM.

Lifestyle

George lives a structured but comfortable life in Seattle. His apartment is minimalist but functional, reflecting his preference for order. Weeknights often involve coding personal projects, playing strategy board games online with friends, or catching up on tech literature. Weekends are a mix of social activities like meeting friends at a local brewery, exploring hiking trails around the Puget Sound, or quiet evenings at home with Nimbus and a good book. He budgets carefully, saving for potential future travel or a down payment, but isn't overly frugal, enjoying good coffee and well-made tools. He values his downtime, finding it essential for maintaining his technical edge.

Work life

As a Senior Backend Engineer, George’s days are a balance of deep technical problem-solving and collaborative communication. He spends significant time designing and implementing new microservices, optimizing existing code, and ensuring system stability for their core SaaS product. His squad is currently navigating the complexities of migrating a legacy monolith to a more distributed architecture, a project requiring meticulous planning and documentation. He actively participates in code reviews, architectural discussions, and uses tools like draw.io and Mermaid to visualize system components for his team and for quarterly architecture reviews. The pressure is on to deliver reliable, scalable solutions while minimizing technical debt.

Relationships

George maintains close friendships with a few long-term college buddies, with whom he regularly plays board games. He has a cordial relationship with his parents and sister, whom he calls weekly. Within his work squad, he's respected for his technical acumen and calm demeanor. While not overtly social at work, he collaborates effectively and is seen as a reliable team member by his manager and peers.

How they decide

George is a highly analytical and research-driven decision-maker, especially for technical matters. He meticulously weighs pros and cons, consults documentation, seeks out relevant case studies, and may informally poll trusted colleagues before committing to a path. He avoids impulsive choices, preferring a measured approach that ensures long-term viability and minimizes future rework. He trusts data and well-reasoned arguments over hype.

How they sound

Speaks clearly and deliberately, with a calm, measured cadence. Avoids jargon unless it's precise technical terminology relevant to the discussion. Tends to articulate his reasoning thoroughly, often pausing to consider the best phrasing. His tone is generally neutral and objective, rarely showing strong emotion, but can convey subtle enthusiasm when discussing elegant technical solutions. He uses standard American English and avoids excessive slang.

Personality traits

  • Analytical
  • Detail-oriented
  • Methodical
  • Quietly confident
  • Proactive
  • Adaptable
  • Principled
  • Patient

Goals

  • Contribute significantly to the successful migration to a distributed architecture.
  • Mentor junior engineers within his squad.
  • Achieve a better work-life balance with more predictable on-call rotations.
  • Become a recognized subject matter expert in distributed systems within the company.
  • Maintain a high level of code quality and system reliability.

Problems & frictions

  • Keeping documentation (like service maps) consistently up-to-date with rapid development cycles.
  • The overhead of manually creating and updating diagrams for different audiences.
  • Ensuring clear and unambiguous communication of architectural decisions across teams.
  • Balancing the urgency of feature delivery with the necessity of robust system design.
  • The constant threat of emergent complexity in large-scale distributed systems.

Values

  • clarity in handoffs
  • reliable documentation
  • clean system design
  • technical debt reduction
  • team collaboration

Interests

  • distributed systems
  • coffee
  • board games
  • craft breweries
  • hiking
  • sci-fi novels

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute (e.g., Software Engineering Daily, Darknet Diaries)
  • Follows key engineers and companies on Twitter/X
  • Watches YouTube deep-dives on system architecture
  • Occasional Reddit browsing on r/sysadmin or r/programming

Questions & answers

George Jacobson’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying AI Diagram Maker (https://www.aidiagrammaker.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The primary obstacle to adopting AI Diagram Maker this month would be the current overhead of managing service maps. Today, I use draw.io for initial ideation and Mermaid within Markdown, exporting PNGs to Confluence for architecture reviews and API changes. While the promise of generating diagrams from text is appealing, I need to understand how well it integrates with my existing Confluence workflow and if it can accurately represent the nuances of our microservice architecture without manual intervention. The "Code to diagram" feature sounds interesting for visualizing our codebase, but I'd need to test its efficacy. I'm willing to pay up to $20 per month, provided it streamlines my current documentation process significantly.
    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.