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

Tami Romaguera

Tami Romaguera

Engineering manager at a product startup

Full-depth AI personas

Why this persona fits the audience

Manages a 4-engineer platform team in Seattle that exposes several internal REST APIs to other departments. She regularly reviews Swagger files, Postman collections, and manual runbooks for low-risk automations, and keeps an eye on audit trails and rollback steps.

  • Age: 33
  • Location: Seattle, WA, US
  • Occupation: Engineering manager
  • Income: $164k salary
  • Education: Master's degree in computer engineering
  • Company size: Series B startup, approximately 120 employees.
  • Years in role: 18 months as Engineering Manager; 6 years total engineering experience.
“I don't care how fast we get to the finish line if the bridge collapses halfway through.”

Tami Romaguera is a seasoned Engineering Manager based in Seattle, Washington, currently steering a four-person platform team at a Series B startup. With a Master's degree in Computer Engineering from a top-tier university, she spent six years in individual contributor roles before transitioning to management eighteen months ago. Her career trajectory was defined by a relentless pursuit of system reliability, moving from front-end development to backend infrastructure where she honed her expertise in RESTful architecture and API governance. Today, she is the primary gatekeeper for her company's internal services, responsible for exposing dozens of REST APIs to various departments while maintaining rigorous standards for security and observability. Her daily reality is a constant balancing act between innovation and stability. She frequently finds herself reviewing Swagger files and Postman collections, not merely for syntax correctness, but to ensure that every parameter change is documented, tested, and accompanied by a viable rollback plan. Tami is deeply invested in the concept of 'audit trails'; she believes that without a clear record of who changed what and when, a system is inherently fragile. This philosophy drives her recent decision to mandate stricter validation rules for all new API versions, even though it initially slowed down the release cycle for the product team. She is a proponent of 'low-risk automations' but only when those automations are backed by robust manual runbooks that can be executed manually if the script fails. Financially, Tami is secure with a $164,000 salary, allowing her to invest heavily in her future and maintain a comfortable lifestyle. However, she views money as a tool for stability rather than status. Professionally, she is driven by the challenge of building systems that are not just functional, but predictable and safe. She is known among her peers as the engineer who asks the 'what if' questions that others are too busy to consider. Her leadership style is characterized by high accountability; she expects her team to own their code and their mistakes, fostering an environment where learning from failures is prioritized over hiding them. As the startup scales, Tami is increasingly focused on institutionalizing these practices, ensuring that the culture of safety she built survives beyond her immediate oversight.

Background & daily life

A day in their life

Tami wakes up at 5:30 AM for a quick workout before the Seattle traffic becomes unbearable. By 7:45 AM, she is in her home office, sipping black coffee while scanning the previous night's deployment logs and checking the status of the internal dashboard. She arrives at the office by 8:45 AM, immediately diving into a stand-up meeting where she clarifies blockers for her team. The bulk of her morning is spent in back-to-back code review sessions, meticulously parsing Swagger files to ensure every endpoint adheres to the new governance standards. Lunch is a solitary affair at her desk, often while reading a technical whitepaper on observability. Afternoon meetings involve negotiating scope with Product Managers, where she firmly pushes back on requests that compromise audit trails. She leaves the office around 5:30 PM to avoid rush hour, heading straight to the gym or home to decompress, ensuring she is mentally fresh for the next day's complex debugging challenges.

Lifestyle

Tami lives in a bright, minimalist two-bedroom condo in Capitol Hill, furnished with functional pieces that prioritize space and utility over decoration. Her weekends are split between high-intensity indoor rowing sessions at a nearby gym and quiet mornings spent meal-prepping healthy lunches for the workweek. She is financially disciplined, maxing out her 401(k) early and saving aggressively for a future down payment on a house, though she remains skeptical of the current real estate market. Socially, she maintains a tight circle of four or five close friends from college and grad school, preferring deep conversations over large networking events. She values her downtime fiercely, often disconnecting completely from digital notifications after 7 PM to read fiction or hike the local mountain trails.

Work life

As the lead for a small but critical platform team, Tami spends her days bridging the gap between abstract system design and concrete execution. Her morning usually begins with reviewing PagerDuty alerts and CI/CD logs to ensure overnight deployments were clean. A significant portion of her week is dedicated to code reviews, specifically scrutinizing OpenAPI specifications and ensuring that new endpoints have comprehensive documentation before they reach staging. She manages a team of four senior engineers who rely on her to unblock them, but she also acts as a gatekeeper for change; she refuses to sign off on any automation that lacks a clear rollback strategy or an audit trail. Her office is cluttered with sticky notes detailing API versioning conflicts and printed diagrams of their internal data flow.

Relationships

Tami is deeply embedded in the Pacific Northwest tech community but keeps her professional network selective. She has a strong mentor relationship with a former CTO who now works at a larger enterprise, providing her with strategic advice on scaling. At home, her partner, a graphic designer, offers a grounding counterbalance to her technical intensity, often reminding her to step away from screens. Her most trusted colleagues are her direct reports, whom she treats as partners rather than subordinates, fostering a culture where admitting mistakes is encouraged. She rarely engages with the broader startup social scene, finding it superficial compared to the shared struggle of building reliable systems.

How they decide

Tami employs a highly analytical and cautious decision-making style. She rarely acts on impulse or peer pressure alone; instead, she requires empirical evidence, such as benchmark data, historical performance metrics, or detailed architectural diagrams, before committing to a new tool or process. She prefers a 'measure twice, cut once' approach, often spending disproportionate time researching the long-term maintenance implications of a solution rather than just its immediate benefits. While she values speed, she will never sacrifice system stability or auditability for convenience, making her a natural skeptic of 'magic button' solutions that promise results without transparency.

How they sound

Tami speaks with a clear, measured cadence, favoring precise terminology over colloquialisms. She tends to speak in complete, structured sentences, often prefacing points with logical connectors like 'given that' or 'consequently.' She avoids hyperbole and emotional language, preferring to state facts and constraints directly. In meetings, she asks probing questions about failure modes and edge cases rather than accepting optimistic timelines. Her tone is professional and authoritative but not abrasive; she is known for being the person who calmly de-escalates panic by focusing on the immediate steps required to restore service.

Personality traits

  • meticulous
  • calm under pressure
  • process-oriented
  • direct communicator
  • risk-averse regarding production changes
  • data-driven decision maker
  • mentorship-focused
  • structurally minded
  • pragmatic
  • dislikes ambiguity

Goals

  • Achieve 99.99% uptime for all internal consumer-facing APIs this fiscal year
  • Mentor two junior engineers on the team to reach Senior Engineer level within 12 months
  • Reduce the mean time to resolution (MTTR) for internal API incidents by 20%
  • Implement a unified governance framework for all third-party integrations
  • Complete a specialized certification in distributed systems security
  • Build a more resilient on-call rotation schedule that prevents burnout

Problems & frictions

  • Legacy documentation is often outdated, leading to confusion when new features are added
  • The lack of automated testing for edge cases in manual runbooks increases deployment anxiety
  • Balancing rapid feature requests from product teams with necessary technical debt reduction
  • Difficulty tracking exactly which department modified a specific API parameter without full logging visibility
  • Time-consuming manual review processes for low-risk automations slow down overall velocity
  • Ensuring consistent error handling across disparate microservices owned by different teams

Values

  • reliability
  • accountability
  • system safety
  • clarity
  • efficiency
  • integrity

Interests

  • platform engineering
  • API governance
  • technical operations
  • observability patterns
  • infrastructure as code
  • indoor rowing

Media habits

  • Reads the 'Software Engineering Daily' podcast during commutes
  • Skims Hacker News and specific r/devops threads before bed
  • Subscribes to AWS and Google Cloud architecture blogs
  • Follows niche Twitter/X accounts focused on SRE practices
  • Attends local Seattle meetup groups for backend engineers
  • Uses Notion for personal knowledge management of technical specs

Questions & answers

Tami Romaguera’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at orqisai (https://orqisai.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).

    This tool promises to quickly turn an OpenAPI spec into an AI agent, which sounds intriguing for streamlining internal tooling. However, the pricing isn't detailed on the page, which makes it hard to give a no-brainer or stop-considering price. If it were around $50/month, I'd be very interested, especially if it offered robust observability and audit trails for API calls, and perhaps tiered features based on usage or number of agents. Anything over $200/month would likely push me to explore building something in-house or using existing frameworks, given the startup's stage and my team's capacity.
    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.