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

Jake Labadie

Jake Labadie

Front-end engineer at a SaaS startup

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person B2B SaaS team in Austin. He exports SVG icons from Figma, runs them through SVGOMG or a CLI optimizer before committing, and checks bundle impact as part of normal front-end work. The team shares the same asset pipeline across product and marketing pages.

  • Age: 31
  • Location: Austin, TX, US
  • Occupation: Front-end engineer
  • Income: US$118k base
  • Education: BS Computer Science
  • Company size: Small (6 people)
  • Years in role: 4
“The elegance is in the efficiency; if it works well and loads fast, that's the real win.”

Jake Labadie, 31, is a dedicated front-end engineer who found his niche at a bustling SaaS startup in Austin, Texas. A graduate with a BS in Computer Science, Jake developed an early appreciation for the tangible impact of well-crafted code. His career trajectory has been shaped by a strong preference for 'clean code' and a deep-seated belief in 'team reliability.' He thrives in environments where performance and efficiency are not just buzzwords but core metrics, a philosophy that permeates his daily work. His current role on a small, six-person B2B SaaS team has honed his expertise in optimizing the entire asset pipeline. This involves meticulously exporting SVG icons from Figma, running them through optimization tools like SVGOMG or command-line interfaces to reduce file sizes, and always checking the bundle impact before committing code. The team's shared asset pipeline for both product and marketing pages underscores Jake's commitment to consistency and maintainability. Outside of work, Jake is driven by a desire for financial security, actively saving towards a down payment on a condo, and he dedicates time to personal coding projects. His recent decision to invest more time in understanding advanced performance budgeting techniques stems from a belief that speed is a fundamental aspect of user experience and a competitive advantage. He views his work not just as writing code, but as engineering solutions that contribute directly to the company's success and user satisfaction, prioritizing privacy and robust functionality above all else. His approach to technology is pragmatic, always weighing the benefits against potential complexities and ensuring solutions are sustainable in the long run.

Background & daily life

A day in their life

Jake's typical weekday starts around 8:00 AM with coffee and scanning Hacker News. He's usually at his desk by 9:00 AM, diving into code reviews or tackling a feature ticket. The morning is often a mix of focused coding and stand-up meetings. Lunch is a quick affair, often eaten at his desk while catching up on Slack or an industry blog. Afternoons involve more development, pair programming sessions, or collaborating with the product manager on upcoming features. He's meticulous about committing code, ensuring his SVG assets are optimized and bundle impact is checked. He often wraps up by 6:00 PM, but might spend an extra hour if a critical bug arises or he's deep in a challenging problem. Evenings are for personal projects, dinner, and unwinding.

Lifestyle

Jake lives a fairly routine life in Austin, balancing his demanding job with personal interests. He and his roommate keep the apartment tidy and have a system for shared chores. His evenings often involve coding side projects, researching new web technologies, or occasionally meeting up with friends for board games or live music. He's mindful of his spending, prioritizing saving for a down payment on a condo, but enjoys good coffee and craft beer. Health-wise, he tries to hit the gym a few times a week and enjoys cycling around Lady Bird Lake on weekends.

Work life

As a front-end engineer at a lean SaaS startup, Jake is deeply involved in the entire asset pipeline. He's the one ensuring SVGs from Figma are optimized to the smallest possible file size without visual degradation, often running them through tools like SVGOMG or custom CLI scripts before they hit the codebase. This focus on bundle impact is a core part of his workflow, especially since the same pipeline serves both the product and marketing sites. He collaborates closely with a small, tight-knit team where trust and reliability are paramount. The pressure to deliver performant features quickly is constant, but Jake finds satisfaction in the efficiency and technical elegance of his solutions.

Relationships

Jake has a solid, if not extensive, social circle. His roommate, a graphic designer, is a good friend, and they often discuss work-related challenges from different perspectives. His closest friends are a mix of former college classmates and colleagues, with whom he shares a passion for technology and occasional outdoor activities. His parents, who live in a suburb, are supportive but don't fully grasp the nuances of his career.

How they decide

Jake is a research-heavy and pragmatic decision-maker. He'll thoroughly investigate options, compare specifications, read reviews, and often prototype or test solutions himself before committing. He values data and evidence over hype, and peer recommendations from trusted colleagues carry significant weight. He tends to be cautious, especially with new tools or processes that could impact team reliability or code quality.

How they sound

Jake speaks in a clear, measured tone. He's not overly verbose, preferring to get straight to the point. He uses precise technical language when discussing his work but can explain complex concepts in a more accessible way if needed. He tends to avoid jargon or buzzwords unless they're standard industry terms. His cadence is steady, reflecting his methodical nature. He might use phrases like 'That makes sense,' 'We need to be mindful of,' or 'The data suggests.'

Personality traits

  • Detail-oriented
  • Methodical
  • Proactive
  • Skeptical of over-hyped tech
  • Reliable
  • Independent
  • Pragmatic
  • Quietly competent

Goals

  • Contribute significantly to the growth and success of his current startup
  • Master advanced front-end performance optimization techniques
  • Build and launch a personal project that solves a niche problem
  • Achieve financial independence through investments and savings
  • Mentor junior developers in best practices for front-end development

Problems & frictions

  • Balancing the rapid feature development pace with the need for robust, performant code
  • Ensuring consistent asset quality and optimization across different team members' workflows
  • Managing technical debt in a fast-growing startup environment
  • The constant pressure to stay updated with the rapidly evolving front-end landscape
  • Finding time for deep, focused work amidst frequent meetings and urgent requests

Values

  • clean code
  • speed
  • team reliability
  • privacy
  • efficiency

Interests

  • React
  • design systems
  • open-source tools
  • performance budgeting
  • web performance optimization

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows engineering blogs on Medium and Substack
  • Checks Twitter for industry news and updates
  • Watches YouTube tutorials for new libraries/frameworks

Questions & answers

Jake Labadie’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of SimpleSVGs (https://www.simplesvgs.online/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make SimpleSVGs 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 export SVGs from Figma and run them through SVGOMG or a CLI optimizer before committing. It's part of our standard pipeline. If SimpleSVGs offered significantly more advanced options or better integration than what I'm already using, that would be a draw. However, it being browser-based and requiring manual uploads for batch processing (as I understand it) means it's likely worse for my team's workflow than our current automated CLI approach. The main thing keeping me on my current setup is the automation and integration into our Git workflow. I wouldn't pay for this service.
    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.