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

Armando Johnston

Armando Johnston

CTO at a small startup who also handles product visuals

Full-depth AI personas

Why this persona fits the audience

At a 6-person startup in Boston, he owns the front-end stack and often steps into UI production for investor demos and customer-facing pages. His current workflow includes grabbing light and dark SVG assets, wiring React components, and keeping a local library of approved visuals without a dedicated design ops system.

  • Age: 39
  • Location: Boston, Massachusetts, USA
  • Occupation: CTO
  • Income: USD 165k base salary
  • Education: MS in Computer Science
  • Company size: 6
  • Years in role: 4
“Every line of code, every visual asset, needs to serve a purpose and stand the test of time, even at a startup.”

Armando Johnston's journey into technology began with a fascination for how things work, a trait that led him to pursue a Master's in Computer Science at MIT. After graduation, he spent several years at a large, established tech firm, gaining invaluable experience in building robust, scalable systems. However, the bureaucracy and slower pace began to chafe. He craved the agility and direct impact he saw in the startup world. Driven by a desire for technical control and the thrill of building something from the ground up, he co-founded his current venture four years ago. His role as CTO at this six-person Boston-based startup is a testament to his broad skill set; he not only architects the backend but also, due to lean resources, frequently dives deep into front-end development, including the creation and integration of UI visuals for crucial investor demos and customer-facing pages. This often involves meticulously sourcing and adapting SVG assets, ensuring light and dark modes are consistent, and weaving them into React components, all while managing a local, somewhat ad-hoc library of approved visual elements. He finds satisfaction in optimizing workflows and ensuring the technical foundation is solid, prioritizing robustness and accountability above all else. He views his current income as a tool for future security, leading him to live a relatively frugal lifestyle despite his compensation. He recently made the decision to adopt a more standardized approach to asset management, realizing the inefficiencies of his current manual process, though a full design ops system remains a future aspiration.

Background & daily life

A day in their life

Armando's day typically begins around 7:00 AM with a quick scan of overnight alerts and key industry news on Hacker News. After a brief workout or run, he arrives at the office by 8:30 AM. The morning is usually dedicated to deep work: architectural planning, coding complex features, or reviewing pull requests. Lunch is often a working session with a co-founder or a quick meal at his desk. Afternoons are a mix of team stand-ups, investor-related tasks requiring front-end polish, and troubleshooting production issues. He often stays until 7:00 PM, sometimes later, especially when a demo is approaching, ensuring the visual presentation is as solid as the backend.

Lifestyle

Armando lives in a moderately sized condo in Somerville, a short commute from his Boston office. He's single, and his social life revolves around a small, tight-knit group of friends, mostly from his university days or early career. Weekends often involve exploring new hiking trails in the surrounding New England area or tinkering with personal coding projects. He's conscious about his health, prioritizing a balanced diet and regular runs along the Charles River. Financially, he's saving aggressively for future security, viewing his current high salary as a means to an end rather than an end in itself.

Work life

As CTO of a nascent startup, Armando wears many hats. His days are a constant juggle between strategic architecture decisions, code reviews, and hands-on development, especially for the user-facing aspects of their product. He's keenly aware of the tightrope walk between feature velocity and technical debt. Coworkers rely on him for technical direction and problem-solving. The pressure to demonstrate progress to investors is palpable, often requiring him to drop everything to produce polished demo materials, including visually appealing UI elements.

Relationships

Armando maintains close ties with his parents, who live in Rhode Island, and a few college friends scattered across the country. His most significant professional relationships are with his co-founders and the small engineering team, where he acts as both a technical leader and a peer. He values direct, honest feedback from his colleagues.

How they decide

Armando approaches decisions with a blend of deep technical analysis and pragmatic consideration of time constraints. He thoroughly researches potential solutions, weighing pros and cons, but ultimately prioritizes options that offer robustness and can be implemented quickly. He's not easily swayed by hype and relies on his experience and data to guide his choices.

How they sound

His cadence is measured and deliberate, often pausing to formulate his thoughts precisely. He avoids overly casual slang, preferring clear, technical language. When explaining complex topics, he's patient but can become slightly impatient if the core concept isn't grasped quickly. He tends to use analogies sparingly but effectively. He speaks with a slight New England accent, most noticeable on 'a' sounds.

Personality traits

  • meticulous
  • resourceful
  • results-oriented
  • detail-oriented
  • analytically minded
  • a touch perfectionistic
  • driven
  • observant
  • efficient

Goals

  • Scale the startup to a successful Series A funding round.
  • Build a resilient and scalable technology infrastructure.
  • Mentor junior engineers effectively and foster a strong technical culture.
  • Achieve a better work-life balance without sacrificing company progress.
  • Explore novel applications of ML within their product domain.

Problems & frictions

  • Limited design resources forcing him into visual production.
  • Keeping up with rapid feature development demands from sales and marketing.
  • Managing technical debt while prioritizing speed.
  • Finding efficient ways to maintain and update UI assets across the application.
  • The constant challenge of attracting and retaining top engineering talent with limited resources.

Values

  • technical control
  • speed
  • robustness
  • accountability
  • pragmatism

Interests

  • React
  • startup tooling
  • systems design
  • machine learning
  • performance optimization
  • efficient workflows

Media habits

  • Hacker News
  • Ars Technica
  • specific tech newsletters (e.g., TLDR)
  • YouTube for technical deep dives
  • podcasts on AI and entrepreneurship

Questions & answers

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

  1. What would stop you from trying Liniqo (https://liniqo.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).

    What would stop me? Frankly, it's the sheer volume of assets I'm already juggling. Today, I manually pull and adapt SVG assets for light and dark modes, integrating them into React components and maintaining a local library. It's time-consuming but I've gotten it down to a system, albeit a manual one. While Liniqo offers a lot, the idea of integrating another large library feels like a step back in immediate workflow, even if it promises long-term efficiency. I'd need to see a very clear, low-friction integration path for our existing React setup before committing. My maximum would be $20 once for the Pro plan, as I'm wary of ongoing subscriptions unless absolutely necessary, and the Lifetime offer for $79 once seems more aligned with my philosophy of owning assets outright.
    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.