Why this persona fits the audience
Manages a 7-person product engineering team in Amsterdam; has team members using paid Cursor seats alongside VS Code, while architecture decisions are tracked in Miro and a shared spreadsheet.
- Age: 39
- Location: Amsterdam, Netherlands
- Occupation: Engineering manager
- Income: €100k-€125k
- Education: Master's degree in software engineering
- Company size: Small product company (approx. 30 employees)
- Years in role: 4
“The elegance isn't in the complexity we can create, but in the clarity we can achieve while shipping value.”
Inaya de Corte’s journey into software engineering began not with a childhood fascination for computers, but with a fascination for systems – how things fit together, how they could be improved. Growing up in Utrecht, her parents, a librarian and a civil engineer, instilled in her a deep appreciation for both knowledge and practical problem-solving. This duality guided her through her Master's degree in Software Engineering at Delft University of Technology. Upon graduation, she joined a small, fast-paced product company in Amsterdam, initially as a senior developer, quickly demonstrating a knack for not just writing code, but for understanding the broader technical landscape and the team dynamics required to build great software. Four years ago, she stepped into the Engineering Manager role, where she now leads a team of seven. Her philosophy centers on pragmatism and incremental progress; she believes strongly in 'shipping incrementally,' ensuring the team constantly delivers value rather than getting lost in theoretical perfection. Accountability is paramount, both for herself and her team members. She champions simplicity in design and process, viewing overly complicated solutions as a sign of unclear thinking. Her workdays are often packed, demanding a sharp focus on balancing immediate delivery pressures with the long-term health of the codebase and the growth of her team. She actively encourages exploration of new tools that promise to boost developer productivity, leading to the team’s current mixed usage of VS Code and Cursor, and their reliance on Miro and spreadsheets for architectural decision-making. Inaya views time as her most precious, non-renewable resource, carefully allocating it between deep work, team collaboration, and strategic planning. While she earns a comfortable income, her spending habits are deliberate, prioritizing experiences and long-term security over ostentatious displays of wealth. She sees her career not just as a job, but as a continuous process of learning, building, and enabling others.
Background & daily life
A day in their life
Inaya's day begins around 7:30 AM with coffee and a brief check of urgent messages. After her cycle commute, she starts with a 15-minute stand-up with her team. The next few hours are a blend of code reviews, one-on-one mentoring sessions with junior engineers focusing on specific design challenges, and architectural discussions often happening asynchronously via Miro comments. Lunch is usually a quick, healthy meal at her desk while catching up on Hacker News. The afternoon might involve a planning meeting with product management, refining sprint goals, or diving into a complex problem that requires focused attention, perhaps exploring how a new AI coding assistant could streamline a repetitive task. She aims to wrap up by 6:00 PM, often cycling home while mentally debriefing the day.
Lifestyle
Inaya shares a renovated canal house apartment in the Jordaan with her partner, a graphic designer. Her mornings start early with a strong espresso and a quick scan of tech news before a brisk 20-minute cycle to work. Evenings are a mix of cooking healthy meals, attending occasional tech meetups (though she prefers smaller, focused gatherings), or unwinding with a book. Weekends often involve longer cycling trips outside the city or exploring Amsterdam's cultural offerings. She's financially responsible, saving diligently for future travel and home improvements, viewing money as a tool for security and experiences rather than status.
Work life
As an engineering manager at a growing SaaS startup, Inaya leads a seven-person product engineering team. Her days are a constant juggle between hands-on technical guidance, strategic planning, and people management. She champions incremental releases, believing in rapid feedback loops. Architecture discussions are lively, often beginning in Miro boards, then meticulously documented in a shared spreadsheet that serves as their informal RFC process. While she encourages experimentation, she's mindful of tool sprawl; some team members have embraced paid Cursor seats for AI assistance alongside their established VS Code workflows, a decision she’s monitoring for ROI. The pressure is to ship features that directly impact customer acquisition and retention, a constant balancing act.
Relationships
Inaya has a close, supportive relationship with her partner, who understands the demands of her career. Her core social circle consists of a few long-term friends from university, a mix of tech professionals and creatives. Within her team, she fosters a collaborative environment, valuing open communication and mutual respect. Her direct manager, the CTO, provides strategic direction and trusts her judgment on team-level execution.
How they decide
Inaya is primarily research-driven and consensus-oriented when it comes to significant technical decisions. She weighs evidence, analyzes trade-offs, and seeks input from her team and relevant stakeholders. For tooling, she's pragmatic, evaluating based on demonstrated productivity gains and long-term maintainability, though she's willing to pilot promising new technologies if the initial investment is manageable and the potential upside is clear.
How they sound
Speaks with a clear, steady cadence, occasionally with a slight Dutch accent. Her vocabulary is precise and professional, avoiding excessive jargon or slang unless discussing highly technical concepts with peers. She tends to be measured in her responses, preferring to articulate a complete thought rather than interrupting. She avoids overly casual language and is generally reserved about personal opinions unless directly relevant to a discussion.
Personality traits
- Methodical
- Pragmatic
- Patient
- Detail-oriented
- Proactive
- Empathetic leader
- Slightly reserved
- Data-driven
Goals
- Scale the engineering team effectively without losing agility
- Develop a robust, scalable microservices architecture for the company's core product
- Mentor junior engineers to become confident system designers
- Achieve a better work-life integration, perhaps by delegating more operational tasks
- Contribute to open-source projects in her spare time
Problems & frictions
- Keeping technical debt manageable while prioritizing new feature development
- Ensuring consistent architectural adherence across a distributed team
- Balancing the adoption of new, potentially productivity-enhancing tools with budget constraints
- Finding time for deep, uninterrupted technical design work amidst constant meetings
- Navigating the evolving landscape of AI-assisted development and its integration into existing workflows
Values
- accountability
- simplicity
- shipping incrementally
- technical excellence
- team growth
Interests
- developer productivity
- mentoring
- urban cycling
- system architecture
- AI in software development
Media habits
- Reads Hacker News daily
- Listens to "Syntax" and "Software Engineering Daily" podcasts during commutes
- Follows key figures in software architecture on Twitter/X
- Subscribes to O'Reilly newsletters
- Occasional deep dives into academic papers on distributed systems