Why this persona fits the audience
She is one of six engineers at a London B2B startup using PlanetScale in production. She often asks ChatGPT to draft or explain SQL, then records the final steps in a shared spreadsheet with migration notes and handoff comments for the rest of the team.
- Age: 34
- Location: London, UK
- Occupation: Senior full-stack engineer
- Income: £88k salary
- Education: Master's degree in software engineering
- Company size: 6 engineers (startup)
- Years in role: 4
“Code can be rewritten, but once you lose trust in your data structure, you've lost the foundation of everything we build.”
Alyssa Mante-Bergstrom is a Senior Full-Stack Engineer navigating the chaotic yet rewarding landscape of a six-person London B2B startup. Holding a Master's degree in Software Engineering, she brings four years of specialized experience in backend systems to her current role. Unlike many peers who prioritize velocity above all else, Alyssa operates on a philosophy of 'reliable speed,' believing that the fastest way forward is through meticulous planning and documentation. Her daily reality is defined by a unique hybrid workflow: she leverages generative AI to accelerate the drafting of complex SQL queries but insists on a human-in-the-loop verification process. This results in her signature artifact—a shared, living spreadsheet that serves as the team's source of truth for database migrations, containing granular handoff comments and migration notes that no other team member would dare omit. Living in a vibrant, albeit noisy, flat in Shoreditch, Alyssa balances her high-income status (£88k) with a frugal, pragmatic approach to money, prioritizing savings and stability over lifestyle inflation. Her personality profile reveals a highly conscientious individual (0.86) who finds peace in order and clarity, contrasting sharply with the inherent disorder of a growing startup. She is not merely a coder but a systems thinker, deeply invested in the longevity of the platform she helps build. Recently, she made the strategic decision to standardize the team's documentation practices, forcing a shift away from ad-hoc Slack discussions toward structured, searchable records. This move was born from a recent near-miss incident where a misconfigured index caused a minor outage, reinforcing her belief that clarity is the ultimate form of reliability. While she enjoys the intellectual stimulation of B2B SaaS challenges, she remains wary of the 'move fast and break things' mentality, advocating instead for a culture where breaking things is prevented, not just fixed.
Background & daily life
A day in their life
Alyssa starts her day at 6:30 AM with a run along the canal, using the time to mentally decompress before the digital noise begins. By 8:45 AM, she's settled at her desk in the Shoreditch office, the first email already flagged for immediate attention. Her morning block is dedicated to code reviews, specifically focusing on SQL queries submitted by teammates, where she cross-references AI drafts against actual table structures. Lunch is a quick sandwich eaten while scanning industry news on Hacker News. Afternoons are consumed by deep work: designing schema migrations, updating her master spreadsheet with detailed migration notes, and explaining complex database concepts to the rest of the team. She often stays until 7 PM, not out of obligation, but because she finds satisfaction in solving the puzzle of data integrity. The day ends with a walk home, reviewing the day's logs and planning the next morning's priorities.
Lifestyle
Alyssa lives in a converted warehouse flat in Shoreditch, surrounded by exposed brick and the constant hum of London life. Her routine is disciplined: she wakes early to jog along the Regent's Canal before the commute, preferring a quiet start to manage her high conscientiousness. She enjoys cooking elaborate meals on Sundays, viewing it as a creative outlet distinct from her logical work. Financially, she is conservative, maximizing her pension contributions despite the tight startup budget, and avoids flashy spending. Socially, she maintains a close-knit circle of three friends who are also in tech, meeting monthly for dinner rather than frequent clubbing. She values health and consistency over social volume, often skipping happy hours to read or code personal projects late into the evening.
Work life
At the core of her day is the tension between rapid iteration and structural integrity. As the de facto database architect for a team of six, Alyssa spends mornings reviewing pull requests and afternoons deep-diving into query performance. She relies heavily on AI assistants to generate initial SQL drafts but refuses to deploy them without rigorous manual verification. Her workflow involves a unique ritual of translating these AI-generated snippets into a meticulously maintained Confluence-style spreadsheet, documenting every migration step and potential failure point. This 'handoff' document is her lifeline, ensuring that when the other five engineers need context, they find absolute clarity. The pressure comes from the startup's growth trajectory; a single schema change could break a client integration, so her meticulous nature is both a shield and a burden.
Relationships
Alyssa's family is supportive but distant; she has weekly video calls with her parents in the Midlands who worry about her stress levels but respect her career choice. Her closest friend is a product manager she met during university, providing a necessary counterbalance to her technical rigidity. She influences her younger colleagues primarily through her documentation standards, often becoming the 'go-to' person for database questions. In the broader community, she participates in local London meetups but remains an observer rather than a speaker, preferring to learn from others before contributing her own insights.
How they decide
Analytical and evidence-based. Alyssa rarely makes decisions based on hype or peer pressure. She requires concrete data, reproducible results, and a clear understanding of the long-term implications before committing to a new technology or process. She tends to prototype solutions quickly but validates them extensively against existing constraints. Her decision-making is iterative: she gathers information, builds a mental model, tests it against her team's capacity, and then executes with a focus on minimizing future friction.
How they sound
Her speech is precise and measured, avoiding unnecessary filler words. She uses technical terminology naturally but explains complex concepts simply when addressing non-technical colleagues. She rarely uses slang, preferring professional phrasing even in casual settings. She avoids hyperbole, often qualifying statements with 'based on current data' or 'in my experience.' Her tone is calm and reassuring, especially when discussing errors or delays, reflecting her low neuroticism. She speaks with a slight London inflection but keeps her vocabulary formal and articulate.
Personality traits
- meticulously organized
- pragmatic optimist
- systematic thinker
- collaborative but independent
- detail-oriented
- direct communicator
- risk-averse regarding data loss
- process-driven
- mentally resilient under pressure
- curious about automation
Goals
- Achieve architectural autonomy to lead the next major system refactoring without external dependency
- Reduce the team's technical debt by 20% over the next fiscal year through automated testing
- Mentor two junior engineers to seniority within the next two years
- Build a public portfolio of open-source database tools that solves common B2B scaling issues
- Secure a partnership role in a mid-stage startup where process maturity is prioritized over speed
- Complete a Master's level certification in Distributed Systems Architecture
Problems & frictions
- Balancing the speed of AI-assisted coding with the necessity of human verification to prevent subtle bugs
- Managing the cognitive load of being the sole guardian of complex database schemas in a small team
- Fragmented documentation where critical migration logic exists only in chat logs and spreadsheets rather than code comments
- Resistance from some team members to adopt strict documentation standards in favor of faster deployment
- Limited bandwidth to attend conferences due to the heavy operational load of the startup
- Difficulty quantifying the value of her preventative maintenance work to non-technical stakeholders
Values
- clarity
- reliability
- team coordination
- technical debt reduction
- efficiency
- intellectual honesty
Interests
- backend systems
- spreadsheets
- SQL review
- B2B SaaS
- data modeling
- open-source tooling
Media habits
- The Changelog podcast
- Hacker News threads
- PlanetScale documentation
- Substack newsletters on database architecture
- GitHub issue trackers
- LinkedIn tech groups