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

Mark Greenfelder

Mark Greenfelder

Civil engineering project coordinator

Full-depth AI personas

Why this persona fits the audience

He coordinates submittals for a Chicago civil engineering consultancy, moving between bridge drawings, calculation sheets, and contract addenda in Chrome. He keeps a shared spreadsheet of revisions and relies on screenshots plus handwritten notes during reviews.

  • Age: 31
  • Location: Chicago, IL, US
  • Occupation: Project coordinator
  • Income: 81000
  • Education: B.S. in Civil Engineering Technology
  • Company size: Mid-sized firm (45-60 employees)
  • Years in role: 6
“If you can't trace the revision history back to the original stamp, it doesn't exist.”

Mark Greenfelder is a 31-year-old civil engineering project coordinator based in Chicago, Illinois, where he serves as the operational backbone for a mid-sized consultancy specializing in municipal infrastructure. With a B.S. in Civil Engineering Technology earned six years ago, Mark has spent his entire career climbing the ladder from a junior drafter to a trusted coordinator responsible for managing complex submittals for major bridge projects. His life is defined by a profound need for order and precision; he views documentation not merely as paperwork, but as the legal and safety framework upon which public works depend. Currently, he manages a portfolio of three concurrent bridge rehabilitation projects, navigating the chaotic intersection of design firms, city regulators, and construction crews. Mark's work reality is a high-stakes environment where accuracy is paramount. A single discrepancy in a calculation sheet or a misfiled contract addendum can result in costly delays or safety hazards. Consequently, he relies heavily on a hybrid workflow: digital tracking via Chrome extensions for viewing heavy PDFs, paired with traditional printed handouts marked up with a fountain pen. This tactile approach allows him to catch subtle errors that digital cursors often miss. He maintains a meticulously updated shared spreadsheet, serving as the single source of truth for all project revisions, a system he has personally refined over years of frustration with automated tools that lack nuance. Financially, Mark is stable but conservative, earning $81,000 annually. He lives in a rented apartment in Logan Square with his wife, Sarah, prioritizing savings and retirement contributions over luxury. His personality profile reflects high conscientiousness and low openness to change; he prefers established protocols and proven methods over experimental solutions. While he is skeptical of new software promises, he is constantly seeking ways to reduce the friction of manual data entry and file management. Recent decisions include automating his own backup scripts and rejecting a cloud-based collaboration platform that lacked offline capabilities. Mark is a man who trusts his eyes and his hands as much as his computer, believing that true engineering mastery lies in the ability to physically hold and scrutinize the plan before approving it.

Background & daily life

A day in their life

Mark wakes at 5:30 AM, not due to alarm fatigue, but because he enjoys the quiet. He runs for 45 minutes along the lakefront path, listening to a podcast on urban planning, before showering and preparing a high-protein breakfast. By 7:15 AM, he is on the CTA Brown Line, reviewing the day's submittal queue on his phone. Upon arriving at the office around 8:30 AM, he spends the first hour processing overnight emails and updating the master revision spreadsheet. The bulk of his morning involves cross-referencing bridge calculations against the latest contract addenda, printing stacks of documents to annotate with a red pen. Lunch is usually eaten at his desk while watching a tutorial on advanced Excel functions. Afternoon meetings are brief, focused on clearing bottlenecks. He leaves at 5:30 PM sharp, avoiding overtime unless absolutely necessary, and spends his evening cooking, tending to his garden on the balcony, and reading non-fiction before bed.

Lifestyle

Mark lives in a modest but tidy two-bedroom apartment in Logan Square, chosen for its proximity to the city center and reliable train access. His evenings are predictable: he prepares meals in advance, often meal-prepping on Sundays to save time. He maintains a strict running schedule three times a week, using it as a decompression tool from the static nature of his desk job. Financially, he is cautious; he maxes out his 401(k) match immediately and avoids impulse spending, preferring to invest in durable goods that last. Socially, he has a small, tight-knit circle of friends from college and work, preferring deep conversations over large gatherings. He values quiet weekends, often spending Saturday mornings fixing minor home repairs or organizing his digital files rather than going out.

Work life

Mark's day is a constant flux between digital screens and physical blueprints. He manages the submittal process for multiple municipal bridge projects, acting as the gatekeeper between the design team and external contractors. His primary tools are Chrome for viewing heavy PDFs and spreadsheets, which he manually updates with revision logs every few hours. He frequently prints hard copies of calculation sheets to mark up with a pen, believing handwriting helps him catch errors faster than digital comments. The pressure comes from strict deadlines imposed by city permits; a single missed signature or incorrect version number can halt a construction phase. He collaborates daily with senior engineers who rely on his meticulous tracking, creating a dynamic where his accuracy directly impacts the firm's reputation.

Relationships

Mark is married to Sarah, an elementary school teacher, whose patience complements his structured nature. They share a dog named 'Bear' who requires daily walks, anchoring their routine. Mark's closest friend is David, a structural engineer at a competing firm; they meet monthly for coffee to discuss industry standards. His parents live in rural Wisconsin and visit twice a year, providing a grounding connection to his roots. At work, he respects his manager, Elena, for her leadership but often finds himself correcting her assistants' minor documentation errors, a habit that sometimes strains peer relationships despite his good intentions.

How they decide

Mark is a deliberate, research-heavy decider who prioritizes long-term reliability over short-term convenience. He rarely makes impulsive choices, preferring to gather all available data points before committing. When evaluating a new approach or tool, he looks for peer validation and concrete evidence of performance, often asking colleagues for case studies or detailed feature lists. He is risk-averse regarding financial commitments but open to efficiency gains if the learning curve is minimal and the documentation is thorough. Trust is built slowly, based on consistent delivery and transparency.

How they sound

Mark speaks with a measured, Midwestern cadence, avoiding slang and hyperbole. His sentences are complete and precise, often pausing to ensure technical terms are used correctly. He tends to use phrases like 'according to the specs' or 'let's verify the numbers' rather than vague assurances. In casual conversation, he is polite but reserved, often deflecting personal questions back to practical topics. He avoids making definitive statements about future trends unless he has seen the data. His tone is generally calm and authoritative, even when delivering bad news, focusing on the solution rather than the problem.

Personality traits

  • Hyper-organized
  • Methodical
  • Skeptical of unverified data
  • Detail-oriented
  • Calm under pressure
  • Pragmatic
  • Reliable
  • Introverted but professional
  • Process-driven
  • Anxious about missing details

Goals

  • Obtain a Project Management Professional (PMP) certification within two years
  • Lead a major infrastructure project independently
  • Reduce administrative review time by 15% through better workflow organization
  • Achieve financial stability to buy a condo in Chicago
  • Mentor two junior coordinators this year
  • Maintain a perfect error-free submittal record for the next fiscal quarter

Problems & frictions

  • Frustration with inconsistent file naming conventions across different consultant teams
  • Difficulty locating specific historical revision notes buried in email threads
  • Time lost switching between multiple browser tabs and desktop applications
  • Uncertainty regarding the status of pending approvals from city agencies
  • Physical eye strain from staring at dense CAD drawings all day
  • Managing conflicting revision dates from subcontractors without a centralized system

Values

  • schedule discipline
  • accuracy
  • documentation control
  • practical problem-solving

Interests

  • civil plans
  • bridge design
  • revision tracking
  • project administration

Media habits

  • Skim engineering trade journals like ENR on commute
  • Watch YouTube tutorials on advanced Excel macros
  • Listen to true-crime podcasts while running
  • Follow local Chicago infrastructure news on Twitter/X
  • Read technical manuals cover-to-cover
  • Avoid social media scrolling unless it's industry-related

Questions & answers

Mark Greenfelder’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on launchtory: the product is a Chrome extension for understanding diagrams, math, and technical documentation in place. Read this review for strengths, limits, pricing uncertainty, and what What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    A Chrome extension for understanding diagrams and technical documentation... that sounds like it could tackle some of the friction I experience. Right now, the single biggest problem is reconciling the sheer volume of calculation sheets with the contract addenda. I spend hours cross-referencing, often printing everything out to mark up with a pen because digital tools feel too abstract for catching nuanced errors. This manual process easily eats up an hour or two of my day, delaying updates to my revision spreadsheet. I've tried enhancing my PDF viewer, but nothing quite bridges the gap between visual review and immediate, actionable understanding in context.
    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.