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

Lorene Dibbert

Lorene Dibbert

Senior front-end engineer at an ecommerce brand

Full-depth AI personas

Why this persona fits the audience

Works on a 40k+ SKU retail site at a 6-person product team, checking new templates and checkout pages for HTML and accessibility regressions after every release. Uses axe in Chrome, browser devtools, and a shared issue sheet for triage.

  • Age: 34
  • Location: Seattle, US
  • Occupation: Senior front-end engineer
  • Income: $145k
  • Education: Bachelor's degree in computer science
  • Company size: Mid-sized ecommerce brand (approx. 500 employees)
  • Years in role: 5
““If it’s not accessible, it’s not truly finished. We owe it to every user to make the experience seamless, regardless of how they interact with the web.””

Lorene Dibbert, 34, has carved out a niche as a Senior Front-End Engineer in Seattle's competitive tech landscape, focusing on the intricate world of e-commerce. Her journey into software development began with a Bachelor's degree in Computer Science, fueled by an early fascination with how technology could bridge gaps and improve lives. She found her calling in front-end development, drawn to the direct impact on user experience and the tangible nature of crafting interfaces. For the past five years, she's been instrumental at a mid-sized retail brand boasting over 40,000 SKUs. Her role within a tight-knit 6-person product team means she’s deeply involved in the entire development lifecycle. A significant portion of her work involves rigorous post-release checks, specifically hunting for HTML and accessibility regressions on critical paths like new templates and checkout pages. Tools like `axe` in Chrome DevTools, along with browser developer tools and a shared issue tracker, are her daily arsenal. Lorene is driven by a deep-seated value for code quality and user access, believing that a functional website is useless if a segment of its audience cannot navigate it effectively. This principle guides her decisions, often leading her to advocate for more time spent on testing and refactoring, even when feature velocity is prioritized. Her income of $145k provides financial stability, allowing her to live comfortably while saving diligently for future goals, such as further professional development or perhaps a down payment on a home, though her current preference is renting. She approaches her career methodically, seeking steady growth and mastery over rapid, potentially unstable, advancement. She recently championed the adoption of a more standardized component library, arguing it would reduce duplication and improve consistency across the vast product site, a decision that required careful negotiation with the team lead but ultimately passed due to its clear benefits for both development efficiency and user experience consistency. Her current focus extends to exploring advanced frontend tooling that could potentially automate some of the more repetitive aspects of her regression testing, freeing her up for more complex problem-solving and architectural considerations.

Background & daily life

A day in their life

Lorene's typical weekday begins around 7:00 AM with coffee and catching up on tech news. After her morning walk or bike ride, she's logged in by 8:30 AM. The morning is often spent reviewing pull requests, attending a stand-up meeting with her product team, and then diving into development work, likely implementing a new UI component or fixing a bug. Lunch is a quick, healthy meal at her desk while listening to a podcast. The afternoon is frequently dedicated to testing: running `axe` checks, manually verifying new templates and checkout flows, and documenting any regressions found. She might have a brief sync with a designer or backend engineer to clarify requirements. Her workday usually wraps up around 5:30 PM, leaving her evenings free for personal pursuits.

Lifestyle

Lorene's routine in Seattle revolves around her demanding job and personal well-being. She lives a quiet life in a comfortable, though not extravagant, apartment. Mornings start with a meticulously brewed pour-over from a local indie roaster, followed by a brisk walk or bike ride to clear her head before settling into work. Weekends are a mix of focused personal projects, exploring hiking trails in the Cascades, and occasionally meeting friends for board games or live music. She’s financially responsible, prioritizing saving for future travel and a potential down payment, rather than impulse purchases. Her social circle is small but close-knit.

Work life

As a Senior Front-End Engineer at an ecommerce company with a massive product catalog, Lorene's days are often consumed by ensuring the site's stability and accessibility. She's part of a lean 6-person product team responsible for the entire user-facing experience. A significant portion of her time is dedicated to meticulously checking new templates and checkout pages for HTML and accessibility regressions after each release cycle. She relies heavily on `axe` within Chrome DevTools and a shared issue tracker for triaging. The pressure to deliver new features without breaking existing functionality, especially regarding user access for diverse audiences, is a constant undercurrent. Collaboration with backend engineers and product managers is frequent but usually focused and task-oriented.

Relationships

Lorene maintains strong but geographically dispersed friendships with former university colleagues. Her closest relationships are with her parents, whom she calls weekly, and a younger sister she texts daily. She values direct, honest communication and tends to trust the opinions of peers she respects in the tech community, particularly those focused on web standards and accessibility.

How they decide

Lorene is a cautious and research-driven decision-maker. She thoroughly investigates options, comparing features, reading documentation, and seeking out peer reviews or case studies when available. For work-related tools, she prioritizes solutions that demonstrably improve quality and efficiency without introducing significant complexity or risk. She's not easily swayed by trends and prefers pragmatic, proven approaches.

How they sound

Speaks clearly and deliberately, with a moderate pace. Avoids overly casual slang or jargon unless discussing technical specifics with peers. Her tone is generally measured and thoughtful, sometimes betraying a hint of fatigue when discussing project pressures, but always professional. She uses precise language, especially when explaining technical concepts.

Personality traits

  • methodical
  • detail-oriented
  • principled
  • patient
  • observant
  • steadfast
  • analytical
  • reserved

Goals

  • Become a technical lead or architect focusing on frontend performance and accessibility
  • Contribute to an open-source accessibility project
  • Achieve a better work-life balance, allowing for more dedicated learning time
  • Mentor junior engineers, sharing best practices for semantic HTML and ARIA
  • Complete a multi-day cycling tour

Problems & frictions

  • Balancing feature velocity with the need for rigorous accessibility testing
  • Dealing with legacy code that makes refactoring difficult
  • The sheer volume of changes across a large SKU site makes comprehensive manual checking tedious
  • Getting buy-in for larger architectural changes that improve long-term maintainability
  • The constant evolution of frontend tooling and best practices requires ongoing learning

Values

  • code quality
  • clarity
  • steady delivery
  • user access
  • thoroughness

Interests

  • component systems
  • cycling
  • indie coffee
  • frontend tooling
  • UX patterns
  • data visualization

Media habits

  • Reads Hacker News and Smashing Magazine daily
  • Listens to tech podcasts (e.g., ShopTalk, Syntax) during commutes/chores
  • Follows key frontend developers and accessibility advocates on Twitter/Mastodon
  • Occasionally browses Reddit for specific technical problems
  • Subscribes to a few curated newsletters on web development

Questions & answers

Lorene Dibbert’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Rocket Validator (https://rocketvalidator.com) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This month, what would stop me is likely the existing workload. We're constantly triaging regressions on our large retail site, and I'm already using axe in Chrome DevTools. While automated site-wide scanning sounds appealing, especially for our 40k+ SKUs, I'd need to see how it integrates with our current workflow and issue tracking. The AI integration is interesting, but my priority is robust, reliable regression detection. If it proved significantly more efficient than our current manual checks, I might consider paying around $75 per month, but that's a stretch given my personal budget.
    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.