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

Onur Kleiss

Onur Kleiss

Freelance full-stack developer

Full-depth AI personas

Why this persona fits the audience

Juggles three client retainers and an open-source maintenance backlog across a free spreadsheet, GitHub Issues, and a local markdown checklist. Has never paid for task software and is used to stitching together simple tools by hand.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Freelance full-stack developer
  • Income: €85k freelance income
  • Education: MSc Computer Science
  • Company size: Sole proprietor
  • Years in role: 12
“The real challenge isn't building the software; it's building a system that lets you build the software without getting bogged down in the plumbing.”

Onur Kleiss, a 41-year-old freelance full-stack developer based in Berlin, has carved out a niche for himself by prioritizing pragmatism and self-reliance in his professional life. Holding an MSc in Computer Science, he transitioned to freelancing over a decade ago, seeking greater autonomy and the ability to work on projects that genuinely interested him. His income of €85k is generated by juggling three distinct client retainers, a demanding schedule that requires meticulous organization. This organizational challenge is compounded by his commitment to maintaining a popular open-source library he initiated, which adds a significant open-source maintenance backlog to his workload. Onur's approach to managing these diverse responsibilities is distinctly hands-on; he has never adopted paid task management software, instead relying on a self-constructed system. This system comprises a free spreadsheet for client billing and project overviews, GitHub Issues for tracking the open-source project's development, and a local Markdown checklist for his daily to-dos and personal notes. This reliance on simple, stitched-together tools reflects his deep-seated belief in efficiency and his aversion to unnecessary complexity. He recently made a conscious decision to invest time in refactoring his local Dockerized development environment, aiming to streamline build processes and reduce context-switching friction, a task he found more rewarding than some client work. This reflects his ongoing pursuit of order and optimization within his personal workflow, viewing his tools as extensions of his own capabilities rather than external dependencies. His income, while comfortable, is carefully managed, with a focus on investing in reliable technology and maintaining a stable living situation rather than pursuing conspicuous consumption. He values his independence highly, viewing his ability to manage his own workflow and technical stack as a core aspect of his professional identity and a testament to his resourcefulness.

Background & daily life

A day in their life

Onur's typical weekday begins around 7:30 AM with a strong coffee and a quick scan of Hacker News and his personal email. By 8:30 AM, he's usually diving into his first client's project, tackling urgent bug fixes or feature implementations. Lunch is a simple, pre-prepared meal eaten at his desk around 1 PM, often while reviewing pull requests for his open-source project. The afternoon might involve a video call with another client or focused coding on a third project. He dedicates an hour or two in the late afternoon to the open-source backlog, responding to issues and merging contributions. Evenings are for winding down, perhaps with some light reading on a new technology or tinkering with his home network setup, before preparing for the next day. He aims to finish work by 7 PM.

Lifestyle

Onur lives a focused, somewhat solitary life in a compact apartment in Prenzlauer Berg, Berlin. His routine is driven by client deadlines and personal projects. He prioritizes efficiency, often meal-prepping simple, healthy meals on Sundays to save time during the week. While not extravagant, he invests in quality hardware and reliable internet, seeing them as essential tools for his livelihood. Social life is limited to occasional meetups with a small circle of developer friends and online interactions within open-source communities. He finds satisfaction in optimizing his personal systems and maintaining a sense of control over his environment.

Work life

As a freelance full-stack developer, Onur's workdays are a constant balancing act. He manages three distinct client projects, each with its own codebase and communication channels, alongside the ongoing maintenance of a popular open-source library he initiated. His 'task management system' is a patchwork: a Google Sheet for client billing and high-level project tracking, GitHub Issues for the open-source project, and a local Markdown file for daily to-dos and notes. He thrives on the autonomy but feels the constant pressure of context switching and the invisible overhead of managing disparate information sources. He recently spent a weekend refactoring his local development environment setup to improve build times, a task he found more engaging than client work.

Relationships

Onur maintains a small, close-knit group of friends, mostly fellow developers he met during university or through online communities. They engage in technical discussions and occasional collaborative problem-solving. His family lives in a different part of Germany, and contact is primarily through weekly calls. He values their support but finds it difficult to explain the nuances of his freelance work. Online, he interacts with contributors to his open-source project, fostering a respectful but professional dynamic.

How they decide

Onur is highly analytical and research-driven when it comes to tools and processes. He prefers to understand the underlying mechanics and evaluate options based on efficiency, reliability, and long-term maintainability. He is not easily swayed by trends or marketing hype, preferring to rely on his own testing and the consensus of trusted technical communities. He will often prototype or experiment with a solution before committing to it, especially if it involves integrating new software into his workflow.

How they sound

Speaks with a measured, deliberate cadence, often pausing to formulate his thoughts precisely. His German is fluent and standard, with a slight academic inflection from his university days. He avoids jargon where simpler terms suffice but will use precise technical language when necessary. He tends to be understated, rarely expressing strong emotions, and prefers to focus on facts and logical reasoning. He might use phrases like 'Essentially,' 'The crux of the matter is,' or 'From a practical standpoint.'

Personality traits

  • methodical
  • resourceful
  • independent
  • detail-oriented
  • skeptical of complexity
  • patient
  • analytical
  • quietly determined

Goals

  • Achieve greater stability in his freelance income without sacrificing autonomy.
  • Contribute significantly to the long-term sustainability of his open-source project.
  • Build a more robust and automated personal infrastructure for his development workflow.
  • Maintain a healthy work-life balance that allows for deep work and personal learning.
  • Explore advanced TypeScript features and their practical application in large-scale projects.

Problems & frictions

  • The mental overhead of tracking tasks and progress across multiple, disconnected systems.
  • Occasional difficulty in estimating project timelines accurately due to unforeseen complexities.
  • The challenge of maintaining consistent communication and progress updates across diverse client expectations.
  • Finding dedicated blocks of uninterrupted time for deep work amidst client demands and open-source contributions.
  • The constant need to stay updated with rapidly evolving web technologies while managing existing commitments.

Values

  • pragmatism
  • self-reliance
  • order
  • efficiency
  • autonomy

Interests

  • open source
  • TypeScript
  • home networking
  • Docker
  • CI/CD pipelines

Media habits

  • Hacker News
  • Reddit (r/typescript, r/devops)
  • YouTube tech channels
  • Developer blogs
  • Podcasts on software architecture

Questions & answers

Onur Kleiss’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of TinyOrange (https://tinyorange.app) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make TinyOrange 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 use a combination of a spreadsheet for client billing and project overviews, GitHub Issues for my open-source work, and a local Markdown file for daily to-dos. TinyOrange's focus on simplicity and local storage is appealing, as I dislike cloud-based solutions that require accounts. The idea of separating 'sort it' from 'do it' with its two modes sounds interesting, and the timer feature might help with focus. However, the current free version saves only to the browser, and I'd need to export backups manually. The planned cloud sync is not yet available, which is a significant drawback for me. If cloud sync were robust and offered better cross-device capabilities, it might be compelling. But given the current state, I'd likely stick with my patchwork system.
    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.