Why this persona fits the audience
Leads engineering at a 9-person B2B SaaS and still joins customer-issue triage himself. He moves between Slack, Jira, cloud logs, and occasional replay clips when support tickets need more context.
- Age: 34
- Location: San Francisco, California, US
- Occupation: CTO at a seed-stage SaaS startup
- Income: USD 210k base + equity
- Education: B.S. Computer Science
- Company size: 9
- Years in role: 2.5
“It's not about building the fanciest thing; it's about building the most reliable thing that solves the problem, and doing it efficiently.”
Rolando Waters' journey into the heart of B2B SaaS infrastructure began not in a boardroom, but hunched over a keyboard in his university's computer lab. Armed with a B.S. in Computer Science from UC Berkeley, he cut his teeth at a few well-funded tech giants, learning the intricacies of large-scale systems. However, the siren song of building something from the ground up proved too strong. Two and a half years ago, he joined the founding team of his current venture, a seed-stage SaaS company focused on developer tooling, as their CTO. His role is multifaceted, encompassing everything from setting the technical vision and architectural roadmap to hands-on coding and infrastructure management. He still personally engages in customer-issue triage, meticulously sifting through Slack channels, Jira tickets, cloud logs, and session replays to pinpoint the root cause of user problems. This deep involvement stems from a core belief in technical clarity and reliable delivery, especially crucial for a lean, nine-person team where every contribution counts. Rolando's current focus is on optimizing their cloud spend without sacrificing performance and fortifying their core platform against potential scaling bottlenecks. He recently championed a shift towards a more robust observability stack, arguing that the upfront investment would dramatically reduce debugging time and prevent costly outages down the line. He views his equity stake not just as compensation, but as a direct alignment with the company's long-term success, driving his meticulous approach to every technical decision. His income, while substantial, is carefully managed, with a significant portion reinvested into his startup and personal development. He's acutely aware of time as a finite resource, constantly seeking ways to maximize team efficiency and automate repetitive tasks. His personal life reflects this pragmatism; his San Francisco apartment is functional and uncluttered, prioritizing his high-end coffee setup over extensive decor. He sees his work as an extension of his problem-solving nature, a continuous challenge to build robust, elegant solutions in a demanding environment.
Background & daily life
A day in their life
Rolando's day typically begins at 7:30 AM with a strong espresso and a quick scan of Hacker News and overnight alerts. By 8:30 AM, he's in Slack, responding to urgent messages and reviewing critical Jira tickets. His morning is usually packed with back-to-back virtual stand-ups, architectural design sessions for upcoming features, and code reviews. Around noon, he might join a customer support triage call if a complex issue arises, diving into logs and replay clips to diagnose. The afternoon involves more engineering team syncs, long-term planning, and often a deep dive into cloud cost optimization reports. He aims to wrap up by 7:00 PM, but late-night incident responses are not uncommon. He’ll often spend an hour or two after dinner on personal projects or reading industry whitepapers.
Lifestyle
Rolando lives in a modest but functional apartment in San Francisco's Inner Sunset, a deliberate choice to keep his burn rate low. His evenings often involve tweaking his La Marzocco espresso machine, perfecting his pour-over technique, or diving into technical deep-dives. Weekends might include a hike in Golden Gate Park or a quick trip to Marin Headlands. He prioritizes experiences and learning over material possessions, viewing his income as a means to fund his startup and secure future stability. Social life is often centered around tech meetups or small gatherings with fellow founders and engineers.
Work life
As CTO of a seed-stage B2B SaaS, Rolando's days are a relentless cycle of code reviews, architectural discussions, and hands-on debugging. He juggles strategic planning for future features with the immediate need to keep the current platform stable and performant for their growing user base. Collaboration is constant, primarily through Slack and Jira, but he insists on maintaining a deep understanding of customer pain points by joining support triage. The pressure to deliver reliable infrastructure on a shoestring budget is immense, requiring constant vigilance over cloud costs and team output. He sees his role as the bedrock upon which the product's success is built.
Relationships
Rolando maintains a close-knit relationship with his co-founders, particularly the CEO, with whom he shares a vision and a high degree of trust. His engineering team of seven looks to him for technical direction and mentorship. His parents, a retired teacher and an accountant, are supportive but don't fully grasp the startup grind. His closest friends are a mix of former university classmates and other founders he's met through the Bay Area tech scene.
How they decide
Rolando is a highly analytical and research-driven decision-maker. He gathers data meticulously, weighing pros and cons against his team's current needs and long-term technical vision. He's not easily swayed by hype or trends, preferring to evaluate solutions based on their practical impact and scalability. While he values team input, especially from his senior engineers, the ultimate decision often rests on his technical judgment and alignment with the company's strategic goals.
How they sound
Rolando speaks with a deliberate, measured cadence. His language is precise and technically accurate, often using industry jargon naturally but avoiding overly casual slang. He's not one for hyperbole or effusive praise. When explaining complex technical concepts, he'll often pause to ensure understanding. He tends to be direct and gets straight to the point, valuing clarity and efficiency in communication above all else. He avoids vague statements and always tries to back up his points with logic or data.
Personality traits
- meticulous
- driven
- detail-oriented
- problem-solver
- resourceful
- analytical
- patient
- calm under pressure
- deliberate
Goals
- Achieve product-market fit for his company's SaaS offering.
- Build a scalable and resilient engineering team.
- Become a recognized thought leader in his niche of B2B SaaS infrastructure.
- Secure Series A funding within the next 18 months.
- Maintain a healthy work-life balance, despite startup demands.
Problems & frictions
- Balancing rapid feature development with critical stability requirements.
- Limited budget for tooling and infrastructure upgrades.
- Hiring and retaining top engineering talent in a competitive market.
- The constant threat of production incidents impacting customer trust.
- Onboarding new engineers quickly to maintain team velocity.
Values
- reliable delivery
- technical clarity
- small-team efficiency
- pragmatic innovation
- founder's grit
Interests
- observability
- startup operations
- home coffee
- backend architecture
- cloud infrastructure optimization
Media habits
- TechCrunch daily digest
- Hacker News threads
- specific engineering subreddits
- re:Invent and KubeCon talks on YouTube
- podcasts on startup challenges (e.g., Acquired, How I Built This)