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

Ross Schmeler

Ross Schmeler

Software engineer who keeps a manual wardrobe log

Full-depth AI personas

Why this persona fits the audience

Keeps shirts, jeans, and jackets in Notion, repeats proven outfits for camera-heavy meetings and travel, and updates a simple record when items wear out or get replaced.

  • Age: 29
  • Location: Seattle, WA, US
  • Occupation: Software engineer
  • Income: $155k
  • Education: Bachelor's in computer science
  • Company size: 1000+ employees
  • Years in role: 4
“Every item has a purpose and a lifecycle; understanding that helps optimize everything else.”

Ross Schmeler, 29, is a software engineer living in Seattle, WA, earning $155k annually. His journey into software engineering began with a fascination for how complex systems function, leading him to pursue a Bachelor's in Computer Science. He landed a role at a large tech firm shortly after graduation and has been steadily climbing the ranks for the past four years, currently specializing in backend infrastructure. Ross embodies a highly organized and analytical approach to life, driven by a core value of efficiency. This manifests in his meticulous personal systems, including his unique approach to wardrobe management. He maintains a detailed log in Notion, tracking his shirts, jeans, and jackets. This isn't about fashion trends; it's about data. He identifies outfits that perform well in camera-heavy meetings and during travel, creating a repeatable playbook. When an item wears out or is replaced, he updates the log, treating his wardrobe like a system to be maintained and optimized. This methodical habit stems from his deep-seated belief in evidence-based decision-making and a desire for order in a world that can often feel chaotic. His interest in minimalism further reinforces this, pushing him to curate his possessions and focus on utility and longevity. He's not driven by status or external validation; his satisfaction comes from internal optimization and the quiet hum of well-functioning systems, whether they're lines of code or his carefully cataloged clothing. His reserved nature and preference for privacy mean his social circle is small but meaningful, consisting of individuals who share his intellectual curiosity and appreciation for logical processes. He views his wardrobe log not as a chore, but as a practical application of his engineering mindset to a personal domain, ensuring that even the mundane aspects of life are handled with a degree of systematic precision.

Background & daily life

A day in their life

Ross's weekday begins at 6:00 AM with a 5-mile run. After showering and a precisely measured breakfast of oatmeal and fruit, he's at his desk by 7:30 AM. He spends the morning coding, tackling bugs in the user authentication module. A 10:00 AM stand-up meeting is followed by a code review session. Lunch is a pre-prepared salad eaten at his desk while scanning Hacker News. The afternoon involves more coding, a brief sync with his product manager, and documenting a recent system change. He logs off at 5:00 PM, then spends an hour updating his Notion wardrobe log with a new shirt he purchased, noting its wearability for 'camera meetings.' The evening concludes with a light dinner, reading a technical book, and preparing his running gear for the next day.

Lifestyle

Ross lives a highly structured life in a minimalist one-bedroom apartment in Seattle. His days revolve around optimizing his routines for maximum efficiency and personal growth. He wakes early for a run, followed by a precisely prepared breakfast. Evenings are dedicated to coding side projects, reading technical literature, or meticulously updating his personal knowledge base. He enjoys quiet weekends, often spent hiking in the Cascades or exploring new coffee shops. Social interactions are typically planned and limited to a small circle of close friends. His financial habits are conservative, focusing on long-term savings and avoiding unnecessary expenditures.

Work life

Ross is a software engineer at a large, established tech company, working on a team responsible for backend infrastructure and internal tooling. His primary focus is on maintaining and refactoring existing codebases, ensuring system stability and performance. He spends his days in a cycle of coding, code reviews, attending stand-ups and sprint planning meetings, and troubleshooting production issues. The pressure is often subtle but constant: to deliver reliable code, optimize resource usage, and keep pace with evolving technologies. He collaborates with a diverse team, but his interactions are generally task-focused and professional.

Relationships

Ross maintains a small, close-knit group of friends, mostly fellow engineers he met in college or at work. They share similar interests in technology and productivity. His family lives out of state, and their interactions are primarily through scheduled video calls. He values their support but maintains a strong sense of independence.

How they decide

Ross is highly analytical and research-driven. He gathers data, compares options systematically, and often creates spreadsheets or detailed notes to weigh pros and cons before making a decision, whether for personal purchases or work-related tools. He prioritizes long-term value and efficiency over immediate gratification.

How they sound

Speaks in a clear, measured tone. Tends to use precise language, avoiding slang or overly casual expressions. His cadence is steady, with a slight pause for thought before answering complex questions. He often uses analogies related to software development or systems when explaining concepts. He avoids hyperbole and focuses on factual descriptions.

Personality traits

  • methodical
  • reserved
  • self-motivated
  • analytical
  • frugal
  • detail-oriented
  • systematic
  • rational

Goals

  • Achieve senior engineer status within his company
  • Develop a personal software project that gains traction
  • Maintain a consistent running schedule and improve his marathon time
  • Continuously refine his personal knowledge management system

Problems & frictions

  • The sheer volume of clothing he owns feels inefficient and disorganized, despite his efforts
  • Difficulty in quickly identifying suitable outfits for spontaneous video calls or unexpected travel
  • The manual logging of wardrobe items is time-consuming and prone to minor errors
  • Feeling overwhelmed by the constant influx of new productivity tools and deciding which are truly beneficial
  • Balancing the desire for a perfectly curated wardrobe with the practicalities of daily life

Values

  • privacy
  • efficiency
  • evidence-based decisions
  • self-improvement
  • order

Interests

  • running
  • minimalism
  • productivity tools
  • data analysis
  • system optimization

Media habits

  • Hacker News
  • The Verge
  • podcasts on software engineering and productivity
  • technical blogs

Questions & answers

Ross Schmeler’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Ask My Wardrobe (https://askmywardrobe.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The concept of virtually trying on clothes is interesting, especially for avoiding returns, which aligns with my efficiency-driven approach. However, the page doesn't clearly state the pricing for the full feature set beyond a 'free' initial use. I'd need to understand the limitations of the free tier and the specific features included in any paid subscription. If it could significantly reduce the time I spend evaluating new purchases or help me optimize my existing wardrobe more effectively, I might consider it. A no-brainer price would be around $5 per month, assuming it offers robust outfit planning and virtual try-on capabilities. I would stop considering it if it exceeded $15 per month, as that seems excessive for this type of utility. My maximum acceptable price would be $10 per month.
    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.