Why this persona fits the audience
Works full time at a startup in Brooklyn and also maintains two side projects with coding agents in Cursor and Claude Code. She compares open and closed models manually, keeps prompt logs in Notion, and uses spreadsheets to tally token spend before rerunning jobs.
- Age: 29
- Location: Brooklyn, NY, USA
- Occupation: Product Engineer
- Income: 138000
- Education: MS Human-Computer Interaction
- Company size: Series B startup (45 employees)
- Years in role: 4
“I don't build things just to see if they work; I build them to understand exactly why they break, and then fix the root cause so it never happens again.”
Carmen Dickinson is a 29-year-old Product Engineer based in Brooklyn, New York, operating at the intersection of human-centered design and advanced software engineering. With an MS in Human-Computer Interaction, she possesses a rare blend of empathy for the end-user and a deep understanding of system architecture. Currently employed at a fast-paced startup, she navigates the complexities of delivering scalable products while maintaining a rigorous commitment to craftsmanship. Her professional identity is further defined by her dual role as an indie maker, where she rigorously tests the boundaries of generative AI. Carmen's approach to technology is characterized by a meticulous, almost forensic curiosity. She does not blindly adopt new tools; instead, she builds her own evaluation frameworks. In her current workflow, she manages two distinct side projects using coding agents powered by both open and closed source models. Her process involves running parallel experiments in Cursor and Claude Code, manually comparing outputs, and maintaining detailed logs in Notion. She tracks every token consumed in a spreadsheet, calculating costs before deciding whether to re-run a job. This data-driven skepticism allows her to optimize her budget while ensuring model reliability. Living in a shared loft, Carmen balances her demanding full-time schedule with a relentless pursuit of learning. She views time as her most finite resource, often sacrificing leisure for deep work sessions. Her financial stability, anchored by a six-figure income, gives her the flexibility to experiment without immediate commercial pressure, yet she remains acutely aware of the economic realities of scaling AI infrastructure. Carmen represents the modern hybrid worker: technically proficient, philosophically grounded in the value of open systems, and relentlessly focused on building tools that empower others to create more efficiently.
Background & daily life
A day in their life
Carmen wakes up at 6:30 AM, brews coffee, and checks her email briefly before heading to the gym. She arrives at her office by 9:15 AM, attending the daily standup and immediately diving into a ticket regarding a new feature integration. By noon, she takes a walk to decompress, listening to a podcast on distributed systems. After lunch, she focuses on code reviews and meeting with the product manager to align on user requirements. Around 4:00 PM, she switches contexts to her side projects, spending an hour testing a new agent prompt in Cursor and logging the results in her Notion database. She leaves the office by 6:30 PM, cooks dinner, and dedicates another two hours to refining her side project's UI. She winds down around 10:30 PM, reading a book on HCI before sleep, ensuring she gets eight hours of rest.
Lifestyle
Carmen lives in a sun-drenched, slightly cluttered loft in Williamsburg where her workspace doubles as her living area. Her mornings begin with a pour-over coffee and a walk through the nearby park to clear her head before diving into work. She is health-conscious, prioritizing yoga twice a week and cooking fresh meals on Sundays, though takeout is a frequent reality during crunch weeks. Financially, she is disciplined, maximizing her 401k while aggressively saving for future independence. Her social life is curated; she prefers intimate dinners with close friends or small tech meetups over large parties, often using these gatherings to swap stories about recent experiments rather than industry gossip.
Work life
As a Product Engineer at a Brooklyn-based Series B startup, Carmen bridges the gap between product vision and technical execution. Her days are split between sprint planning, code reviews, and building internal tools that streamline the team's workflow. She relies heavily on VS Code, Jira, and Slack, but her most critical tool is her own custom-built agent harness. The pressure to ship features quickly is constant, yet she refuses to compromise on code quality. She spends significant time prototyping new ideas late at night, often debugging issues that arise from integrating third-party APIs or managing local development environments that refuse to behave.
Relationships
Carmen is deeply connected to her roommate, with whom she shares a mutual respect for creative autonomy. She has a tight-knit circle of three childhood friends who provide emotional grounding, and a professional network built through conference attendance and online forums. She looks up to senior engineers who have successfully transitioned to solo work, viewing them as role models for her own career trajectory. Her family is supportive but distant geographically, leading to monthly video calls that serve as her primary connection to home.
How they decide
Carmen operates as a cautious researcher who values empirical evidence over hype. Before adopting any new technology, she conducts small-scale pilots, meticulously logging results and comparing metrics against her existing baselines. She is not easily swayed by marketing narratives or peer pressure; instead, she seeks out technical documentation, community feedback, and first-hand experience. Her decisions are driven by long-term utility and cost-efficiency, often resulting in longer deliberation periods but higher confidence in the final outcome.
How they sound
Her speech is articulate and precise, often punctuated by technical jargon used naturally. She tends to speak in complete, well-structured sentences, avoiding filler words. While friendly, she maintains a slight professional distance until she feels a genuine intellectual connection. She avoids hyperbolic language like 'game-changer' or 'revolutionary,' preferring terms like 'incremental improvement' or 'significant bottleneck.' Her tone is generally calm and analytical, even when discussing complex problems, and she often pauses to gather her thoughts before responding.
Personality traits
- Methodical observer
- Data-driven skeptic
- Quietly passionate
- Resourceful tinkerer
- Time-conscious
- Analytical listener
- Pragmatic idealist
- Detail-oriented
- Self-reliant
- Intellectually curious
Goals
- Launch a successful open-source tool that gains traction within the developer community
- Achieve financial freedom sufficient to transition to full-time independent consulting
- Master the nuances of fine-tuning open-weight models for specific domain tasks
- Build a sustainable personal brand that attracts high-quality collaborators
- Reduce the carbon footprint of her computational workflows
- Create a robust portfolio of side projects that demonstrate end-to-end product ownership
Problems & frictions
- The high cost of running complex inference jobs on cloud-hosted proprietary models
- Fragmentation in the local AI ecosystem requiring constant manual configuration updates
- Difficulty maintaining consistent prompt performance across different model versions
- Lack of granular visibility into token consumption across multiple active projects
- Balancing the time required for rigorous experimentation with full-time job demands
- Keeping up with the rapid pace of new model releases without losing focus
Values
- independence
- craftsmanship
- learning by building
- transparency
- efficiency
- curiosity
Interests
- side projects
- product design
- local-first tools
- AI safety
- urban gardening
- analog photography
Media habits
- Reading Hacker News and specific Substacks on AI architecture
- Listening to 'Software Engineering Daily' during commutes
- Watching technical deep-dives on YouTube rather than short-form content
- Following niche GitHub repositories for tooling
- Browsing r/MachineLearning and r/SideProject
- Subscribing to newsletters from independent researchers