Why this persona fits the audience
His 4-person team in Warsaw is extending a Rails product into a new AI feature set, with auth and billing already in place but a fresh admin area and onboarding flow to build. They use an existing competitor starter for new experiments and keep most product decisions in Linear and Google Sheets.
- Age: 30
- Location: Warsaw, Poland
- Occupation: CTO at a bootstrapped SaaS
- Income: €90k
- Education: MSc Computer Science
- Company size: 4-person team
- Years in role: 3
“The most elegant solution is often the one that works reliably, scales gracefully, and doesn't require constant firefighting.”
Maksym Filipiak, a 30-year-old CTO, has carved out a niche for himself leading a small, bootstrapped SaaS company from Warsaw. Holding an MSc in Computer Science, his career trajectory has been defined by a deep dive into Ruby on Rails development, evolving from individual contributor to technical lead. His current role is a testament to his systematic approach and technical acumen, managing a lean team of four developers and a designer. They are in the critical phase of extending their existing Rails product with a new AI feature set, a complex undertaking that requires careful architectural planning and execution. With core functionalities like authentication and billing already robust, the immediate focus is on building a fresh admin area and an intuitive onboarding flow for the AI capabilities. Maksym is pragmatic about tooling, leveraging a competitor's starter kit for rapid experimentation while relying on Linear for project management and Google Sheets for strategic planning. This blend of established practices and forward-looking development reflects his core values: systematic execution, reliability, and the pursuit of technical leverage. He is driven by the challenge of building scalable software and the satisfaction of seeing his team's work translate into tangible product improvements. His income of €90k supports a comfortable but not extravagant lifestyle, prioritizing long-term stability and professional growth over immediate material gains. He views time as a critical resource, constantly seeking ways to optimize workflows and maximize development velocity without compromising the integrity of the codebase. His journey is one of continuous learning and adaptation in the fast-paced world of tech startups.
Background & daily life
A day in their life
Maksym's day typically begins around 8:00 AM with a quick scan of Hacker News and urgent emails. He then joins his team for a brief stand-up meeting via video call, discussing progress and blockers. The bulk of his morning is spent coding, tackling complex architectural challenges for the new AI features, and reviewing pull requests. After a light lunch, he might spend an hour researching new AI libraries or debugging a tricky integration issue. The afternoon often involves more coding, planning future sprints in Linear, and occasionally collaborating with Kasia on household matters. He usually wraps up his workday around 7:00 PM, often followed by a run or some personal learning.
Lifestyle
Maksym shares a modern apartment in Warsaw's Śródmieście district with his partner, Kasia, a graphic designer. They enjoy exploring local cafes and restaurants, and try to maintain a healthy work-life balance, though work often encroaches. Maksym prioritizes regular exercise, usually jogging in the nearby Lazienki Park, and allocates time for learning new skills, such as advanced AI model deployment techniques. He values experiences over material possessions and has a modest, reliable car. His social life revolves around close friends and online developer communities.
Work life
As CTO of a bootstrapped SaaS, Maksym oversees a team of three developers and a designer. They work remotely, with a flexible schedule that often sees Maksym putting in extra hours to ensure deadlines are met. His primary focus is the technical roadmap, balancing the integration of new AI capabilities with the maintenance of their core Rails application. He spends a significant portion of his day in Linear, managing tickets, reviewing pull requests, and architecting solutions. The pressure to deliver quickly while maintaining code quality is constant.
Relationships
Maksym's primary relationship is with his partner, Kasia, who provides emotional support and a grounding influence. He maintains a small circle of close friends, mostly fellow developers he met during university or through online communities. His team in Warsaw is a professional relationship built on mutual respect and shared goals, though direct mentorship is limited by their remote setup.
How they decide
Maksym is highly analytical and research-driven, preferring to gather data and evaluate options systematically. He relies on technical documentation, community discussions, and internal team consensus. While he values speed, he is not impulsive; decisions are weighed against long-term implications and potential risks. He is pragmatic, often opting for the most efficient and reliable solution that fits within their constraints.
How they sound
Speaks with a measured, calm cadence, often pausing to formulate precise technical explanations. His English is fluent but carries a subtle Polish accent. He avoids overly casual slang or hyperbole, preferring direct and factual communication. When discussing technical topics, he can become quite detailed. He tends to be reserved in expressing strong opinions unless directly asked for his technical assessment.
Personality traits
- methodical
- results-driven
- self-motivated
- reserved
- analytical
- forward-thinking
- practical
- detail-oriented
- resourceful
- calm under pressure
Goals
- Successfully launch the new AI feature set within the next quarter.
- Achieve profitability and sustainable growth for the SaaS product.
- Build a robust and scalable technical architecture that can support future expansion.
- Continuously improve his understanding and application of AI in software development.
- Maintain a healthy work-life balance without sacrificing product quality.
Problems & frictions
- Limited engineering resources for rapid feature development.
- Balancing the need for speed with maintaining high code quality and reliability.
- Integrating complex AI models seamlessly into an existing Rails application.
- Managing technical debt while pushing forward with new initiatives.
- Finding time for deep technical research amidst daily operational demands.
Values
- systematic execution
- reliability
- speed
- technical leverage
Interests
- Rails architecture
- startup ops
- AI features
- Linear
Media habits
- reading Hacker News
- listening to tech podcasts
- following industry leaders on Twitter
- scouring Stack Overflow for solutions