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

Opalina Menon

Opalina Menon

Founding engineer at a two-person startup

Full-depth AI personas

Why this persona fits the audience

Builds and deploys the product from a MacBook Air in Bengaluru, uses Claude Code for boilerplate and refactors, and routinely approves tool calls while checking staging, GitHub pull requests and cloud deploy logs.

  • Age: 26
  • Location: Bengaluru, India
  • Occupation: Founding Engineer
  • Income: ₹36 lakh/year salary + small equity
  • Education: B.Tech in Computer Science
  • Company size: 2
  • Years in role: 2
“The most satisfying part is seeing something I built actually *work* and solve a real problem, even if it's just for a few users at first.”

Opalina Menon, 26, is a founding engineer at a nascent two-person startup based in Bengaluru, India. Her journey into technology began with a B.Tech in Computer Science, where she excelled, driven by an innate curiosity and a desire to build things. Upon graduating, she gravitated towards the fast-paced, high-impact environment of startups, seeing it as the most direct path to learning and ownership. She co-founded her current venture with a partner who complements her technical prowess with business acumen. Her daily reality is intensely hands-on; she operates from a MacBook Air, meticulously crafting and deploying the company's product. Tools like Claude Code are indispensable, handling boilerplate code and suggesting optimizations, allowing Opalina to focus on the intricate architectural decisions and novel problem-solving. Her work involves a constant, fluid interaction with her development environment: checking staging servers, scrutinizing GitHub pull requests, and poring over cloud deployment logs, often approving automated tool calls without missing a beat. This relentless focus on speed and iteration is fueled by her value system, which prioritizes rapid learning and a deep sense of ownership over the product's success. She earns a substantial salary of ₹36 lakh per year, augmented by a small but significant equity stake, reflecting the high stakes and potential rewards of her role. While she lives comfortably, her financial habits are pragmatic, balancing current needs with strategic saving for the startup's future and her own long-term goals. She views her current role not just as a job, but as a crucible for growth, constantly pushing her to expand her technical horizons and develop the resilience required to navigate the volatile startup landscape. Her decision to pour her energy into this venture stems from a belief in its potential and a personal drive to create something meaningful and lasting in the tech world.

Background & daily life

A day in their life

Opalina's weekday begins around 7:30 AM with a strong filter coffee and a quick scan of tech news and overnight alerts. By 8:30 AM, she's at her MacBook Air, diving into code. The morning is dedicated to feature development, leveraging Claude Code for repetitive tasks and focusing on core logic. Lunch is a quick, often home-prepared meal eaten at her desk while reviewing GitHub pull requests. The afternoon involves more coding, debugging, and collaborating with her co-founder on deployment strategies. She routinely approves tool calls, monitors staging environments, and checks cloud logs. Evenings are for winding down, perhaps a short walk, before a late dinner and some personal learning or a brief Netflix session, often falling asleep around midnight.

Lifestyle

Opalina shares a modern, functional apartment in Bengaluru with a roommate, a fellow engineer from a different startup. Her days are packed, so downtime is precious. She prioritizes a strong cup of filter coffee each morning to kickstart her day. Evenings are often spent catching up on tech news or experimenting with new code snippets. Weekends might involve exploring local markets for fresh produce for her small balcony garden or meeting up with a few close friends for dinner. She's mindful of her finances, balancing her comfortable salary with saving for future investments and the startup's runway.

Work life

As a founding engineer, Opalina's work life is a whirlwind of creation and deployment. Her primary workspace is her MacBook Air, a sleek machine that's seen countless hours of coding. She relies heavily on AI coding assistants like Claude Code for generating boilerplate and suggesting refactors, freeing her up for more complex problem-solving. Her days are a constant juggle of writing new features, debugging, and monitoring the live product. She's deeply involved in the entire development lifecycle, from initial concept to cloud deployment, often approving tool calls directly from her IDE or terminal while simultaneously reviewing pull requests and sifting through logs.

Relationships

Opalina's closest professional relationship is with her co-founder, a dynamic individual who handles sales and strategy. They have a strong, results-oriented partnership built on mutual respect and shared vision. Outside of work, she maintains a small but close circle of friends, mostly fellow tech professionals, with whom she discusses industry trends and shares challenges. Her family, back in her hometown, is supportive but doesn't fully grasp the intricacies of her startup life.

How they decide

Opalina is a highly analytical and research-driven decision-maker, especially concerning her work. She weighs options carefully, often prototyping or testing solutions before committing. For personal purchases, she leans towards efficiency and long-term value, influenced by peer recommendations within the tech community and reviews from trusted sources.

How they sound

Speaks with a clear, precise cadence, often using technical jargon naturally. Her tone is generally calm and focused, but can become animated when discussing innovative solutions or complex technical challenges. She avoids overly casual slang but isn't stiff; her language is efficient and direct. She tends to understate personal achievements, preferring to let the work speak for itself.

Personality traits

  • intensely curious
  • highly pragmatic
  • driven
  • detail-oriented
  • self-reliant
  • adaptable
  • analytical
  • efficient

Goals

  • Successfully launch and scale the startup's product.
  • Become a recognized expert in her specific niche of AI-assisted development.
  • Achieve financial independence through equity and future ventures.
  • Continuously learn and master new programming languages and frameworks.
  • Build a sustainable and impactful technology.

Problems & frictions

  • Balancing rapid development with maintaining code quality and stability.
  • The constant pressure to innovate and stay ahead of competitors.
  • Managing limited resources (time, budget) as a small startup.
  • The inherent uncertainty and risk associated with early-stage startups.
  • Finding moments for deep, uninterrupted focus amidst constant context switching.

Values

  • speed
  • learning
  • ownership
  • autonomy
  • impact

Interests

  • AI assistants
  • indie SaaS
  • filter coffee
  • exploring new tech stacks
  • urban gardening

Media habits

  • tech blogs (Hacker News, Dev.to)
  • developer podcasts
  • Twitter (following tech leaders)
  • YouTube (coding tutorials, tech reviews)

Questions & answers

Opalina Menon’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Runnock (https://runnock.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Runnock 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).

    Right now, I'm primarily using my IDE and terminal to monitor builds, PRs, and cloud logs. Claude Code handles boilerplate and some refactoring, and I approve tool calls directly there. Spreadsheets aren't really part of my workflow for this. Runnock's idea of using the notch for quick status updates and approving tool calls without context switching sounds interesting, especially for Claude Code. However, I'm not entirely clear on how it integrates with *all* the tools I use daily. The pricing is a one-time purchase, which is appealing, but the specific amounts for multiple devices are a bit unclear (e.g., 'undefined9'). I'd consider it, but my current system works, albeit with more manual checks.
    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.