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

Marion Lehner

Marion Lehner

Technical writer and docs engineer

Full-depth AI personas

Why this persona fits the audience

He works on docs-as-code, sample repos, and internal tooling scripts in GitHub for a developer platform team. He keeps his commits visible on his personal site and occasionally assembles screenshots by hand for his own progress log.

  • Age: 31
  • Location: London, UK
  • Occupation: Technical writer
  • Income: £63k salary
  • Education: MA Technical Communication
  • Company size: Mid-sized tech company (approx. 500 employees)
  • Years in role: 5
“The real satisfaction comes from building something that works perfectly, even if it's just a script to automate a tedious task.”

Marion Lehner, 31, is a dedicated technical writer and docs engineer based in London, UK, earning a £63k salary. His academic foundation is a Master's degree in Technical Communication, which he has applied rigorously over five years in his current role at a mid-sized tech company. His professional life is deeply embedded in the 'docs-as-code' philosophy. He manages GitHub repositories for a developer platform team, ensuring that documentation lives alongside the code it describes. This involves not only writing clear, accurate prose but also developing and maintaining internal tooling scripts to streamline the documentation workflow and ensure consistency. He's a strong proponent of making his work visible, maintaining a personal website where his GitHub commits are publicly displayed, a testament to his ongoing contributions and a way to track his progress. When documenting complex features or processes, he sometimes takes the extra step of manually assembling screenshots, a meticulous process that allows him to control the narrative and ensure visual clarity, even if it's more time-consuming than automated solutions. This personal log serves as both a progress tracker and a demonstration of his commitment to quality. His income is comfortable, allowing for savings and modest discretionary spending, but he prioritizes financial stability over ostentatious displays of wealth. He views his work not just as a job, but as a craft where precision, organization, and helpfulness are paramount. His MA provided him with a strong theoretical grounding, but his daily work is where he truly hones his practical skills, constantly adapting to new tools and methodologies within the rapidly evolving tech landscape. He sees his role as a crucial bridge between complex technical systems and the developers who use them, a responsibility he takes very seriously.

Background & daily life

A day in their life

Marion's typical weekday begins around 7:00 AM with a cup of tea and a quick scan of tech news. He leaves for his commute to the London office by 7:45 AM, using the train time to listen to a history podcast, often about Roman Britain or the Tudors. His workday, starting at 9:00 AM, involves a mix of writing new documentation, updating existing guides, and scripting. He'll spend a couple of hours refining a set of sample code repositories, then move to writing a new API reference. Lunch is usually a packed meal eaten at his desk while reviewing pull requests for documentation changes. Afternoons might involve a sync meeting with an engineering team or troubleshooting a documentation build script, before he heads home around 5:30 PM. Evenings are for personal projects, reading, or quiet relaxation.

Lifestyle

Marion lives in a well-organized, if slightly cramped, one-bedroom flat in a Zone 3 London borough, favouring the quieter residential streets. His routine is fairly consistent: early mornings with a strong cup of Earl Grey, followed by a train commute where he catches up on history podcasts or reads tech articles. Evenings are often spent tinkering with personal projects or reading. He's not a big spender, preferring to save for future travel or potential home improvements, and his social life is modest, revolving around a few close friends he sees for occasional pub visits or board game nights. He values his quiet time and finds comfort in predictable patterns.

Work life

As a technical writer and docs engineer at a mid-sized tech company, Marion's days are consumed by crafting clear, concise documentation for a developer platform. His focus is heavily on docs-as-code, meaning he's deeply involved with GitHub repositories, writing in Markdown, and ensuring sample code is functional and well-explained. He spends a significant portion of his time developing internal tooling scripts to automate documentation processes and maintain consistency across projects. Collaboration with engineers is frequent but usually asynchronous via Slack or GitHub issues. The pressure is on to keep documentation up-to-date with rapid development cycles, a challenge he meets with his methodical approach.

Relationships

Marion maintains a close but geographically dispersed relationship with his parents, who live in the Cotswolds. His core social circle consists of three long-term friends from university, with whom he shares interests in board games and occasional pub outings. Within his company, he has a good working relationship with the engineering leads he supports, who respect his thoroughness, though he doesn't socialize extensively with colleagues outside of work.

How they decide

Marion is a highly research-oriented decision-maker. He prefers to gather as much information as possible, compare options systematically, and weigh pros and cons before committing. He values evidence and clear logic, often creating spreadsheets or detailed notes to track his findings. He is not easily swayed by trends or peer pressure, preferring to trust his own analysis and the consensus of well-regarded experts in a field.

How they sound

Marion speaks with a clear, measured cadence, typical of standard British English. He avoids slang and overly casual language in professional settings, preferring precise terminology. His tone is generally calm and even, rarely showing strong emotion. He tends to use complete sentences and articulate his thoughts logically, often pausing to ensure he's chosen the right word. He might occasionally use slightly more formal phrasing than expected, reflecting his focus on clarity and accuracy.

Personality traits

  • Meticulous
  • Systematic
  • Patient
  • Introverted
  • Detail-oriented
  • Reliable
  • Methodical
  • Quietly curious
  • Pragmatic

Goals

  • Contribute meaningfully to open-source documentation projects
  • Develop a personal portfolio that showcases his expertise in docs-as-code
  • Achieve a senior technical writer or lead documentation engineer position
  • Travel to Japan to explore its historical sites
  • Master a new scripting language for automation

Problems & frictions

  • Keeping documentation perfectly synchronized with rapidly evolving software releases
  • Balancing the need for detailed technical accuracy with user-friendliness
  • Finding time for personal projects amidst demanding work schedules
  • Navigating internal company politics to advocate for documentation best practices
  • The sheer volume of information that needs to be processed and organized

Values

  • clarity
  • helpfulness
  • organization
  • accuracy
  • efficiency

Interests

  • docs-as-code
  • Markdown
  • history podcasts
  • tea
  • open-source tooling
  • pixel art

Media habits

  • Listens to history podcasts during commutes
  • Reads tech blogs and documentation sites
  • Follows key figures in developer advocacy on Twitter
  • Subscribes to newsletters on technical writing and developer experience
  • Watches YouTube tutorials for new tools

Questions & answers

Marion Lehner’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Forkest (https://www.forkest.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Forkest better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I don't use anything beyond my own GitHub commits, which I sometimes manually log or assemble screenshots for personal progress tracking. Forkest's premise of visualizing commit activity as a garden is novel, and the free tier seems to offer basic functionality. However, I'm unclear on how the 'Forest widget' or 'Animals on your best days' in the Pro tier would practically benefit my work. My current method, while manual, gives me precise control. The automated nature of Forkest is appealing, but I'd need to see a more tangible benefit beyond aesthetics to justify a cost. For now, I’d stick to my current methods.
    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.