Why this persona fits the audience
She leads a 5-person Berlin SaaS team that is rebuilding an internal ops portal and customer workspace in Next.js. The team already has Supabase in production, but auth, billing, roles, and admin flows are still being assembled from in-house patterns and spreadsheets.
- Age: 35
- Location: Berlin, Germany
- Occupation: CTO at seed-stage SaaS startup
- Income: €110k
- Education: MSc Computer Science
- Company size: Startup (15 employees total)
- Years in role: 3
“The elegance of a system isn't in its complexity, but in its resilience and the clarity of its design under pressure.”
Nadja Jander's journey into technology was driven by an innate curiosity about how things work and a desire to build robust systems. Growing up in a family that valued stability and hard work, she pursued her passion for computer science, culminating in a Master's degree from a reputable German university. Her early career involved roles in established tech companies, where she honed her skills in backend development and system architecture, gaining a deep appreciation for well-engineered solutions and the pitfalls of technical debt. This experience instilled in her a strong sense of responsibility and a commitment to technical control. She transitioned to the startup world seeking more direct impact and the challenge of building from the ground up. Now, as CTO at a seed-stage SaaS company, she finds herself at the forefront of a critical technical pivot. Her team is tasked with rebuilding their core internal operations portal and customer workspace in Next.js, a significant undertaking that demands meticulous planning and execution. They've adopted Supabase for their backend but are still grappling with the foundational elements of authentication, billing, user roles, and administrative workflows, relying on a patchwork of in-house patterns and spreadsheets. This situation perfectly encapsulates Nadja's current professional reality: a constant tension between the need for rapid progress and her unwavering commitment to building a technically sound, reliable, and maintainable foundation. She views time as a precious, finite resource, and money as a means to achieve technical excellence and long-term company stability, rather than a primary driver. Her approach to her work is deeply pragmatic, prioritizing solutions that are not only functional today but also scalable and manageable for years to come, reflecting her core values of reliability and lean, efficient processes.
Background & daily life
A day in their life
Nadja's typical weekday begins around 7:00 AM with a quick check of urgent emails and overnight system alerts. After a strong coffee and a light breakfast, she heads out for a 30-minute cycle to the office. Her mornings are usually packed with team stand-ups, code reviews, and deep-dive sessions on architectural challenges, particularly around the ongoing rebuild of the ops portal. Lunch is often a quick, healthy meal at her desk while reviewing documentation or planning the afternoon's tasks. Afternoons involve more focused coding, mentoring junior developers, and strategic planning meetings with the CEO. She typically leaves the office around 7:00 PM, often stopping for groceries or a short ride before heading home to prepare dinner and wind down, perhaps with a few more hours of work or personal study.
Lifestyle
Nadja lives a structured but active life in Berlin. Her Prenzlauer Berg apartment is minimalist and functional, reflecting her preference for order. Most evenings are spent either working late or cycling through the city's parks, often listening to a tech podcast. Weekends involve longer rides, catching up with a small circle of close friends, and dedicated time for personal coding projects or deep dives into technical documentation. She's conscious about her health, preferring home-cooked meals and avoiding excessive alcohol. Financially, she's saving diligently, prioritizing long-term security over immediate gratification, viewing her income as a tool for independence and future stability.
Work life
As CTO of a seed-stage SaaS startup, Nadja's days are a constant juggle between strategic technical direction and hands-on problem-solving. She leads a lean team of five engineers, currently focused on a critical rebuild of their internal ops portal and customer workspace using Next.js. The pressure is high to deliver a robust, scalable solution while managing the complexities of integrating Supabase for backend services. Her team is wrestling with building out essential features like authentication, billing, granular role management, and admin interfaces, often piecing together solutions from existing internal patterns and manual processes documented in spreadsheets. She spends significant time in architecture reviews, code reviews, and mentoring her team, striving for technical excellence under tight deadlines.
Relationships
Nadja maintains a close-knit circle of friends, primarily fellow tech professionals who understand the demands of her industry. Her family, based in a smaller town in Bavaria, is supportive but doesn't fully grasp the intricacies of her startup life. She has a few trusted mentors she occasionally consults on complex technical or career decisions, valuing their pragmatic advice.
How they decide
Nadja is a highly analytical and research-driven decision-maker. She meticulously evaluates options, weighing pros and cons based on technical merit, long-term implications, and team capacity. She prefers to gather data, consult documentation, and sometimes prototype solutions before committing. While she values her team's input, the final decision rests on her assessment of technical feasibility and strategic alignment. She is inherently skeptical of overly hyped solutions and prioritizes proven reliability and control.
How they sound
Nadja speaks with a clear, measured cadence, her German accent subtly present. She is direct and avoids jargon where possible, preferring precise technical language when necessary. Her tone is generally calm and professional, but can become more intense when discussing critical technical issues. She rarely uses slang and tends to steer clear of overly casual or effusive language, valuing clarity and substance.
Personality traits
- Analytical
- Methodical
- Pragmatic
- Detail-oriented
- Reserved
- Principled
- Resourceful
- Slightly cynical about hype
- Independent
Goals
- Establish a highly scalable and maintainable technical architecture for the company's core product.
- Foster a culture of strong engineering practices and continuous learning within her team.
- Achieve a significant reduction in operational overhead through well-designed internal tools.
- Contribute meaningfully to the open-source community in areas related to developer tooling.
- Maintain a healthy work-life balance to prevent burnout and sustain long-term career growth.
Problems & frictions
- The current ad-hoc approach to auth, billing, and admin flows is becoming increasingly brittle and time-consuming to manage.
- Balancing the need for rapid feature development with the imperative for robust, secure, and maintainable code.
- Finding reliable, well-documented, and performant solutions for common SaaS backend functionalities.
- Ensuring consistent technical vision and execution across a small, fast-moving team.
- The constant pressure to innovate and deliver value to users while operating with limited resources.
Values
- technical control
- reliability
- lean process
- code quality
- long-term maintainability
Interests
- architecture reviews
- cycling
- B2B SaaS
- privacy tech
- open-source contributions
- system design
Media habits
- Reads Hacker News daily
- Follows key figures on Twitter for tech insights
- Listens to tech podcasts during commutes
- Subscribes to newsletters on web development and cloud infrastructure
- Occasionally browses Reddit's programming subreddits