Why this persona fits the audience
She is a technical co-founder at an 11-person Amsterdam API startup and handles developer onboarding, API-key setup, and late-night troubleshooting for customers in North America. Support runs through Notion docs, Slack, and a shared inbox, with a manual handoff from product to support.
- Age: 27
- Location: Amsterdam, Netherlands
- Occupation: Technical Co-founder, API startup
- Income: €58k-€82k
- Education: Master's degree in computer science
- Company size: 11
- Years in role: 3
“The elegance of a well-designed API is in its ability to disappear, letting the developer focus purely on their own creation.”
Salomë van der Wal grew up in Utrecht, the daughter of a university librarian and a software engineer. From a young age, she was drawn to the logic and structure of computers, spending hours disassembling old hardware and teaching herself to code. Her academic path was clear: a Master's degree in Computer Science from Delft University of Technology, where she excelled, particularly in distributed systems and API design. During her studies, she met her future co-founders, bonding over late-night coding sessions and a shared frustration with the complexity of existing developer tools. After a brief stint at a larger tech firm, she felt stifled by the bureaucracy and yearned for the agility and direct impact of a startup. Three years ago, they launched their API startup, focusing on simplifying complex data integrations. Salomë immediately took on the role of Technical Co-founder, driven by a passion for building robust, high-quality software. Her days are a testament to her commitment: she meticulously handles developer onboarding, ensuring new users understand the API's nuances, and sets up secure API key management. The most demanding aspect of her role, however, is the late-night troubleshooting for their North American customer base. This often means sacrificing personal time, a trade-off she accepts for the sake of customer satisfaction and the company's reputation. She views her income as a means to reinvest in her skills and the company's future, rather than for personal extravagance. Her apartment, shared with her co-founders, reflects a similar pragmatic approach – functional, organized, and optimized for productivity. She recently pushed for a more standardized documentation process within Notion, aiming to reduce the time spent answering repetitive questions, a small step towards alleviating the constant pressure of being the primary technical support.
Background & daily life
A day in their life
Salomë's day typically begins around 6:30 AM with a brisk cycle commute, listening to a tech podcast. After a quick coffee, she dives into code reviews and architectural planning until lunch. Post-lunch is often spent on developer onboarding calls, refining documentation in Notion, or responding to Slack queries. As the afternoon progresses, she monitors system performance and prepares for the inevitable influx of North American support requests. Her evenings are dedicated to troubleshooting, often until 11 PM or later, before a late dinner and a brief wind-down with a book or some light coding on a personal project. She aims for 7-8 hours of sleep but often falls short during peak demand periods.
Lifestyle
Salomë lives in the Oost district of Amsterdam, sharing a spacious, sunlit canal-side apartment with fellow founders. Her routine is rigid around performance: she cycles 25 kilometers to work every morning regardless of weather, often listening to tech podcasts. Evenings are a mix of deep work, quick dinners, and occasional social outings with her co-founders or friends from university. She prioritizes efficiency, meal-prepping on Sundays and meticulously organizing her digital life. While she enjoys the occasional music festival, her primary focus remains on building and refining the startup's core product, viewing personal time as a resource to be managed for optimal output.
Work life
As the technical co-founder, Salomë is deeply embedded in the day-to-day operations of the API startup. Her role is a constant juggle between strategic development and hands-on problem-solving. She spends her mornings architecting new features and refining existing code, often collaborating with her small engineering team. Afternoons are dedicated to developer onboarding, meticulously documenting API usage, and ensuring smooth integration for new clients. The late evenings are the most challenging, as she fields urgent support requests from North American customers, diving into logs and debugging issues that arise outside of European business hours. The current support system, a blend of Notion, Slack, and a shared inbox, feels increasingly strained as the user base grows.
Relationships
Salomë's closest relationships are with her two co-founders, with whom she shares a deep professional and personal bond, often discussing work over shared meals. Her parents, both academics, are supportive but don't fully grasp the startup grind. She maintains a small circle of close friends from her university days, though coordinating schedules for social events can be challenging.
How they decide
Salomë is a highly analytical and research-driven decision-maker, especially concerning technical matters. She weighs evidence, considers long-term implications, and often prototypes solutions before committing. For operational or team-related decisions, she values input from her co-founders and relevant team members, seeking consensus but ultimately trusting her data-informed judgment.
How they sound
Speaks with a clear, measured cadence, often using precise technical terminology. Her Dutch accent is subtle but present. She avoids overly casual slang in professional contexts but is direct and to the point. She tends to explain the 'why' behind technical decisions. When stressed, her speech might become slightly faster, but she maintains composure.
Personality traits
- Methodical yet rapid
- Quietly authoritative
- Technically obsessive
- Pragmatically idealistic
- Resilient under pressure
- Direct communicator
- Systematic thinker
- Self-sufficient
- Empathetic to developers
- Time-conscious
Goals
- Achieve a stable, scalable architecture for the API that can handle 10x current load.
- Develop a more streamlined and automated developer onboarding process.
- Reduce the time spent on reactive troubleshooting by 50% within the next year.
- Mentor junior developers within the team to foster a culture of shared ownership and learning.
- Secure a Series A funding round to expand the engineering team and product capabilities.
Problems & frictions
- The current manual handoff from product to support creates bottlenecks and potential for missed information.
- Late-night troubleshooting sessions disrupt sleep patterns and lead to burnout risk for herself and the small team.
- Lack of dedicated, 24/7 support resources means critical customer issues can linger during off-hours.
- Scaling the onboarding process without sacrificing quality is becoming increasingly difficult.
- Balancing the urgent needs of existing customers with the development of new features is a constant tension.
Values
- build quality
- independence
- learning
- speed
- transparency
Interests
- coding
- design systems
- cycling
- music festivals
- indie game development
Media habits
- Hacker News daily digest
- TypeScript podcast 'Syntax'
- Local cycling club Strava segments
- GitHub trending repositories
- Spotify 'Deep Focus' playlists