Why this persona fits the audience
She is a founder in Seattle overseeing a small team that uses AI coding tools to maintain internal dashboards and a customer portal. Her team relies on a mix of spreadsheets, GitHub checks, and manual walkthroughs of the live site, and she is involved in deciding what gets reviewed before release. She is currently hands-on enough to see the repo-level details.
- Age: 44
- Location: Seattle, Washington, US
- Occupation: Founder and operations lead
- Income: $165,000 USD/year
- Education: MBA
- Company size: 8 employees
- Years in role: 6
“The real magic isn't just building something new; it's building it so reliably that it fades into the background, just working.”
Ida Jenkins, a 44-year-old founder and operations lead based in Seattle, Washington, has carved out a niche for her company by focusing on robust internal tools and customer-facing portals. Armed with an MBA and a keen operational mindset, she steers her team of eight employees, a mix of engineers and support staff, through the complexities of modern software development. Her journey into entrepreneurship wasn't a straight line; after several years in project management roles at larger tech firms, she identified a gap in how small to medium-sized businesses managed their internal digital infrastructure. She founded her current venture six years ago, driven by a desire to create more agile and efficient solutions. Ida is deeply involved in the technical aspects of her company, not just as a manager but as a hands-on contributor to strategic decisions. She understands the repo-level details, a testament to her commitment to operational excellence. Her team heavily utilizes AI coding tools, which Ida sees as powerful accelerators, but she remains acutely aware of the need for rigorous oversight. She personally reviews release candidates, balancing the speed afforded by AI with the imperative for stability and security. This involves a meticulous process that combines automated checks, GitHub reviews, and manual walkthroughs of the live site. Her decision-making is heavily influenced by data and team alignment, ensuring that priorities are clear and that everyone is working towards common objectives. Despite the demands of running a growing company, Ida prioritizes a sustainable work-life balance, recognizing that her own well-being is critical to the company's long-term success. She lives with her partner in a condo, sharing responsibilities for their dogs, and actively seeks opportunities for professional development and networking within the Seattle tech community.
Background & daily life
A day in their life
Ida's typical weekday begins around 6:30 AM with coffee and a review of urgent emails. By 8:00 AM, she's in the office, often starting with a brief stand-up with her engineering team to discuss ongoing tasks and any blockers. The morning is usually filled with meetings – one-on-one check-ins with team members, planning sessions for upcoming feature releases, and reviewing performance dashboards. She dedicates a block of time each afternoon to deep-diving into code repositories or analyzing user feedback. Before wrapping up around 6:00 PM, she prioritizes tasks for the next day and ensures her team has clear direction.
Lifestyle
Ida balances her demanding role with a commitment to personal well-being. She wakes early for a quick workout or a walk with her dogs before diving into work. Weekends are for catching up with her partner, exploring local hiking trails, or attending tech meetups. She's financially disciplined, prioritizing long-term business growth and personal savings over immediate luxuries, though she enjoys good coffee and occasional dinners out with her team.
Work life
Ida's days are a constant juggle of strategic planning and tactical oversight. She manages a lean team of four engineers and two support staff, all of whom leverage AI coding assistants for much of their development work. Her primary focus is ensuring the smooth operation of their internal dashboards and the customer-facing portal. She spends significant time reviewing code changes, analyzing performance metrics, and refining internal processes to maximize efficiency and minimize errors before any release.
Relationships
Ida's closest confidante is her partner, who offers a valuable outside perspective on business challenges. Within the company, she fosters strong, respectful relationships with her team, valuing their input and technical expertise. She also maintains a network of fellow founders in Seattle, with whom she exchanges operational insights and support.
How they decide
Ida is a data-informed, consensus-building decision-maker. She gathers relevant metrics, consults with her team, and weighs potential risks and benefits before committing to a course of action. While she trusts her intuition, she prefers to back it with evidence, especially when it involves significant operational changes or resource allocation.
How they sound
Ida speaks with a clear, measured cadence. Her tone is generally calm and professional, but can become more animated when discussing innovative solutions or team successes. She avoids overly technical jargon when speaking with non-engineers but is precise and direct when discussing code or operational details with her team. She uses phrases like 'let's look at the data,' 'what's the most efficient path here,' and 'how does this align with our priorities.'
Personality traits
- pragmatic
- detail-oriented
- proactive
- methodical
- collaborative
- resourceful
- calm under pressure
- forward-thinking
Goals
- Achieve consistent year-over-year revenue growth for her company.
- Build a robust and scalable internal infrastructure that supports future expansion.
- Foster a highly collaborative and productive team environment.
- Become a recognized leader in her niche within the Seattle tech scene.
- Maintain a healthy work-life integration that prevents burnout.
Problems & frictions
- Ensuring the reliability and security of AI-generated code for critical internal tools.
- Balancing the speed of development with the need for thorough quality assurance.
- Limited resources for dedicated QA personnel, leading to reliance on manual checks.
- Keeping up with the rapid evolution of AI coding tools and best practices.
- Communicating technical priorities effectively to non-technical stakeholders.
Values
- business stability
- team alignment
- clear priorities
- efficiency
- data-driven decisions
Interests
- internal tools
- startup operations
- process improvement
- AI in development
- lean methodologies
Media habits
- TechCrunch
- The Seattle Times
- HBR podcasts
- developer community forums
- industry newsletters