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

Armando Herman

Armando Herman

Frontend developer using SVGs in product docs

Full-depth AI personas

Why this persona fits the audience

Adds icons, diagrams and lightweight vector illustrations to product pages, docs and onboarding flows for a startup; works from a shared Figma library plus copied SVGs from free icon sets.

  • Age: 31
  • Location: Seattle, WA, US
  • Occupation: Frontend developer
  • Income: $135k salary
  • Education: Bachelor's degree in computer science
  • Company size: Startup (50-75 employees)
  • Years in role: 7
“Consistency in the small details is what builds trust in the big picture.”

Armando Herman has been navigating the world of frontend development for nearly a decade, honing his craft since graduating with a computer science degree from a state university. His early career was marked by a broader scope, but he found a particular niche and satisfaction in the meticulous integration of visual elements, especially SVGs, into user interfaces and documentation. This led him to his current role at a fast-paced startup in Seattle, where he's responsible for ensuring the product's visual presentation is not only aesthetically pleasing but also technically sound and performant. He thrives on the challenge of bridging the gap between design and code, meticulously optimizing SVGs from Figma or external libraries to fit seamlessly into product pages, onboarding flows, and developer documentation. His apartment in Seattle serves as his sanctuary, a reflection of his organized nature, where he invests a significant portion of his $135k salary with future homeownership in mind. He values technical neatness above almost all else, finding deep satisfaction in clean code and well-optimized assets. This focus on quality and maintainability sometimes puts him at odds with the startup's relentless drive for speed, a constant negotiation he navigates with pragmatic patience. Recently, he's been championing the adoption of a more robust SVG optimization workflow within his team, pushing back against the quick-and-dirty copy-pasting of icons that can lead to bloat and inconsistencies down the line. He sees documentation not as an afterthought, but as a core part of the product experience, and dedicates significant effort to making it as clear and visually engaging as possible, often relying on SVGs to convey complex ideas succinctly.

Background & daily life

A day in their life

Armando's typical weekday starts around 7:00 AM with coffee and a quick scan of tech news before his 9:00 AM stand-up meeting. The bulk of his morning is spent coding new features or refactoring existing components, paying close attention to the integration of visual assets like SVGs into the product pages and documentation. After lunch, he might dedicate an hour to optimizing SVG files or collaborating with a designer on upcoming assets. The afternoon often involves code reviews, responding to Slack messages, and working on tickets related to UI polish or performance improvements. He usually wraps up his workday around 5:30 PM, often feeling a sense of accomplishment from having tackled complex problems.

Lifestyle

Armando lives a structured life in his Seattle apartment, prioritizing routine and quiet efficiency. His evenings are often spent refining personal coding projects or exploring new libraries. He enjoys hiking in the nearby mountains on weekends to decompress and reconnect with nature, a counterpoint to his screen-intensive work. Financially, he's saving diligently for a down payment on a condo, investing a portion of his salary. Socially, he's selective, preferring deeper connections with a small circle of close friends over large gatherings, often meeting up for board games or quiet dinners.

Work life

As a frontend developer at a rapidly growing startup, Armando is immersed in the practicalities of building user interfaces. His primary focus is on ensuring the product's documentation, onboarding flows, and public-facing pages are clear, performant, and visually consistent. This involves a significant amount of work with SVGs – integrating icons from a shared Figma library, optimizing them for web, and occasionally pulling from free icon sets to fill gaps. He feels the pressure to deliver polished features quickly while maintaining code quality and documentation accuracy, balancing his desire for technical neatness with the startup's need for speed.

Relationships

Armando maintains strong, albeit infrequent, contact with his parents back in California. His closest relationships are with a few long-term friends from university, with whom he shares a passion for technology and strategy board games. Within his company, he respects the design team's vision but often finds himself nudging them towards more technically feasible assets. His direct manager, the Head of Engineering, values his meticulousness and problem-solving skills.

How they decide

Armando approaches decisions with a methodical, research-driven mindset. He thoroughly evaluates options, weighing pros and cons based on technical merit, long-term implications, and available data. He's not impulsive and prefers to understand the 'why' behind a choice before committing, often consulting documentation or established best practices.

How they sound

Speaks clearly and deliberately, with a moderate pace. Avoids excessive jargon unless discussing technical specifics. Tends to use precise language and avoids hyperbole. His tone is generally calm and measured, often prefaced with 'Well,' or 'So, basically,'. Rarely uses slang, but might use mild technical abbreviations when comfortable.

Personality traits

  • meticulous
  • organized
  • detail-oriented
  • analytical
  • reserved
  • pragmatic
  • solution-focused
  • independent
  • diligent
  • patient

Goals

  • Achieve Senior Frontend Engineer title within two years
  • Contribute meaningfully to a widely-used open-source project
  • Own a property in the Seattle area
  • Master advanced SVG animation techniques
  • Mentor junior developers on best practices

Problems & frictions

  • Inconsistent SVG quality and sizing across different free icon sets
  • Time spent manually optimizing SVGs for optimal file size and performance
  • Ensuring design handoff from Figma to code is seamless and error-free
  • Balancing rapid feature development with thorough documentation updates
  • Navigating the constant churn of new frontend frameworks and tools
  • Finding clear, concise visual assets that align with the brand's evolving style

Values

  • technical neatness
  • maintainability
  • speed
  • clarity in communication
  • efficiency

Interests

  • SVG optimization
  • design handoff
  • product documentation
  • performance optimization
  • modern CSS techniques
  • open-source contributions

Media habits

  • Daily checks on Hacker News and Reddit (r/frontend, r/webdev)
  • Follows key figures in frontend development on Twitter
  • Listens to tech podcasts during commute (e.g., Syntax, ShopTalk)
  • Reads technical blogs and documentation extensively
  • Watches YouTube tutorials for specific coding challenges

Questions & answers

Armando Herman’s public research answers, newest questions first. Up to 10 per page.

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

    Well, my main concern right now is the inconsistency I encounter with free icon sets. I spend a lot of time manually optimizing SVGs to ensure they're performant and fit our brand, which is a bottleneck. Today, I'm essentially doing that work on a case-by-case basis, pulling from various sources. If VectorElements could guarantee a high level of quality and consistency, especially in their SVG icons, and perhaps automate some of that optimization, it would be valuable. My current approach means I'm not paying for assets, so I wouldn't pay more than $5 per month, and that's if the quality and workflow integration were significantly better than what I can cobble together myself.
    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.