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

Viktor Hellström

Viktor Hellström

Growth engineer at a subscription app

Full-depth AI personas

Why this persona fits the audience

He is on a six-person product growth team at a SaaS startup in Stockholm and builds the technical side of experiments for onboarding and pricing pages. The team ships tests with developers, but also expects non-engineers to propose and review experiment ideas.

  • Age: 33
  • Location: Stockholm, Sweden
  • Occupation: Growth Engineer
  • Income: SEK 760k annual salary
  • Education: MSc in Computer Engineering
  • Company size: Startup (approx. 50 employees)
  • Years in role: 2
“The elegance of a system isn't just in its performance, but in how clearly its logic unfolds.”

Viktor Hellström grew up in a quiet suburb of Gothenburg, Sweden, where his fascination with how things worked, particularly computers, began early. His parents, a teacher and an accountant, encouraged his academic pursuits, and he excelled in mathematics and science. This led him to pursue a Master of Science in Computer Engineering at KTH Royal Institute of Technology in Stockholm. During his studies, he developed a strong appreciation for well-structured code and efficient algorithms, often spending late nights contributing to small open-source projects or optimizing personal scripts. After graduating, he joined a mid-sized tech company as a backend developer, where he honed his skills in building scalable systems. However, he found himself increasingly drawn to the direct impact of product development and the challenge of optimizing user experiences through data. Two years ago, he transitioned to his current role as a Growth Engineer at a fast-growing SaaS startup in Stockholm. This role allows him to combine his engineering rigor with a focus on measurable outcomes. He's responsible for the technical implementation of A/B tests, primarily on the user onboarding and pricing pages, working with a small, agile product growth team. He meticulously crafts the JavaScript and backend integrations needed to run these experiments, always prioritizing data accuracy and system stability. He recently championed a refactoring of their experiment flagging system, which had become unwieldy, to improve deployment speed and reduce the risk of errors, a decision that significantly improved the team's velocity. Viktor lives a disciplined life, valuing efficiency and quality in both his professional and personal spheres. He sees his career not just as a job, but as a continuous process of learning and refinement, much like building a robust software architecture. He is conscious of his financial future, saving diligently, but also believes in investing in experiences, such as his passion for skiing in the Swedish mountains and exploring new coffee brewing techniques.

Background & daily life

A day in their life

Viktor's typical weekday starts around 7:30 AM with coffee and a quick scan of tech news. He arrives at the office by 9:00 AM, often grabbing another coffee. The morning is usually dedicated to focused coding: implementing a new variant for a pricing experiment, debugging a tracking issue, or refactoring a piece of experiment infrastructure. After a team stand-up around 11:00 AM, he might have a meeting with a product designer to discuss the technical feasibility of a new onboarding flow test. Lunch is often a quick affair, perhaps a packed meal or a visit to a nearby café. The afternoon involves more coding, code reviews for colleagues, and responding to Slack messages. He aims to leave the office by 5:30 PM, often spending the evening either working on a personal project, exercising, or relaxing at home.

Lifestyle

Viktor lives in a modern, well-organized apartment in Södermalm, Stockholm. His routine is structured: early mornings often involve a strong pour-over coffee and reviewing personal side projects or tech news before heading to the office. Weekends are a mix of social activities, like meeting friends for fika or a quiet dinner, and personal pursuits such as hitting the gym or planning his next ski trip. He's mindful of his finances, saving consistently for future travel and potential investments, but enjoys good quality experiences, especially around food and technology. He values efficiency in his personal life as much as in his work.

Work life

As a Growth Engineer at a rapidly scaling SaaS startup, Viktor's days are a blend of deep technical work and cross-functional collaboration. He's responsible for implementing and maintaining the technical infrastructure for A/B tests, focusing on user onboarding flows and pricing page experiments. This involves writing robust JavaScript, integrating with analytics platforms, and ensuring data integrity. He works closely with product managers and designers who propose experiment ideas, and with backend engineers to ensure smooth data flow. The pressure is on to ship tests quickly but without introducing bugs or compromising system stability, a constant balancing act.

Relationships

Viktor maintains a close-knit circle of friends, mostly met through university or previous jobs, with whom he shares interests in technology and outdoor activities. He has a good relationship with his parents, who live in a smaller town outside Stockholm, and calls them weekly. His immediate work team is small and collaborative, with a strong emphasis on mutual respect and shared goals, though he tends to keep his deeper technical thoughts to himself until he's fully formed them.

How they decide

Viktor is a research-heavy and analytical decision-maker. He meticulously gathers data, reads documentation, and often prototypes solutions or explores different technical approaches before committing. He values evidence and logical reasoning, and while he respects his colleagues' opinions, he ultimately relies on his own thorough investigation and technical judgment. He is not impulsive and prefers to understand the full implications of a decision before acting.

How they sound

Viktor speaks with a clear, measured cadence, typical of educated Swedes. His English is fluent but carries a subtle Swedish accent. He tends to be direct and precise in his language, avoiding excessive slang or overly casual phrasing, especially in professional contexts. He uses technical terms accurately and expects others to do the same. He's not one for small talk unless initiated, and even then, his responses are often concise and to the point. He avoids hyperbole and focuses on factual statements.

Personality traits

  • Analytical
  • Meticulous
  • Principled
  • Reserved
  • Pragmatic
  • Focused
  • Systematic
  • Detail-oriented
  • Problem-solver

Goals

  • Become a senior engineer or tech lead within the next five years.
  • Contribute significantly to a major open-source project.
  • Achieve financial independence to allow for more travel and personal projects.
  • Maintain a healthy work-life balance without sacrificing career progression.
  • Develop expertise in scalable system design.

Problems & frictions

  • Balancing the need for rapid experimentation with maintaining code quality and system stability.
  • Dealing with legacy code or technical debt that slows down experiment implementation.
  • Ensuring accurate and reliable data tracking across multiple platforms and user touchpoints.
  • Communicating complex technical constraints to non-technical team members effectively.
  • The constant pressure to deliver measurable growth results in a competitive market.

Values

  • engineering quality
  • speed with guardrails
  • clean systems
  • data-driven decisions
  • continuous learning

Interests

  • software architecture
  • skiing
  • coffee
  • open-source projects
  • backend optimization
  • Swedish fika culture

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute (e.g., Syntax.fm, Software Engineering Daily)
  • Follows key figures in software engineering and growth on Twitter/X
  • Watches YouTube tutorials for new programming languages or tools
  • Reads documentation extensively

Questions & answers

Viktor Hellström’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Nokose (https://www.nokose.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 pricing is not clearly stated on the page, which is a significant hurdle. The product blurb mentions a free tier for the first 100,000 visitors, but then refers to a USD per month subscription without details. To be a no-brainer, it would need to be very affordable for a startup, perhaps around $50-100/month for a basic plan that allows for a good number of experiments. Anything above $200/month would start to make me pause, especially without knowing the exact features included. What I would expect is robust A/B testing capabilities, clear reporting, and easy integration, especially given the emphasis on avoiding engineering bottlenecks.
    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.