Why this persona fits the audience
He is one of 3 people running a specialty coffee subscription brand from London, maintaining the storefront API, recurring orders, and weekly catalog updates on a Medusa-based stack while the other cofounders handle roasting and fulfillment.
- Age: 38
- Location: London, UK
- Occupation: Technical cofounder
- Income: £85k–£110k salary + equity
- Education: MEng software engineering
- Company size: 3
- Years in role: 4.5
“If the code doesn't run reliably every single time, the best beans in the world don't matter because nobody gets their coffee.”
Doug Ebert-Ruecker is a 38-year-old Technical Cofounder based in London, holding an MEng in Software Engineering. Four and a half years ago, he left a stable role at a fintech unicorn to join a fledgling specialty coffee brand, betting on the intersection of artisanal production and robust subscription commerce. As one of only three employees, he bears the unique burden of being the entire engineering department, responsible for the entire digital lifecycle from the storefront API to the recurring billing engine. The company operates out of a converted warehouse in East London, where Doug's office is a glass-walled room overlooking the roasting floor, a constant visual reminder of the physical goods behind the code. His professional philosophy centers on 'build quality' and 'reliability.' Having seen too many startups fail due to fragile backends, Doug insists on a Medusa-based stack that offers flexibility without sacrificing stability. However, this commitment to quality often clashes with the frantic pace of a bootstrapped DTC brand. Recently, he made the difficult decision to pause the development of a flashy new mobile app to focus entirely on stabilizing the checkout flow, a move that frustrated some investors but saved the company from a potential revenue collapse during Black Friday. He is known for his meticulous code reviews and his ability to translate complex technical limitations into clear business impacts for his non-technical co-founders. Outside of work, Doug is a man of few words but many actions. He channels his high conscientiousness into his running, treating it with the same discipline as his codebase. He views money as a tool for security and freedom, not status, and invests conservatively. His relationship with technology is pragmatic; he is open to new tools like Storecraft or similar 'Commerce As Code' platforms, provided they demonstrably reduce the maintenance burden of his current stack. He is currently evaluating whether migrating parts of his monolithic architecture to a serverless model would justify the learning curve and initial cost, driven by a desire to reclaim time for strategic planning rather than firefighting. Doug represents the archetype of the modern founder-engineer: technically elite, operationally stretched, and deeply committed to the tangible quality of what he builds.
Background & daily life
A day in their life
Doug wakes at 5:30 AM, brewing a single-origin Ethiopian pour-over using a V60 before leaving his flat. He runs six miles along the canal, listening to an audiobook on systems thinking, then returns to shower and start work by 7:45 AM. His morning is dedicated to deep coding, focusing on the recurring order logic to ensure zero downtime. By 11:00 AM, he joins a brief stand-up with his co-founders to discuss roasting schedules and shipping delays, offering technical constraints on their fulfillment plans. Lunch is a quick sandwich eaten at his desk while reviewing GitHub issues. The afternoon is fragmented: responding to Slack messages from customers about subscription errors, attending a vendor call about a new shipping API, and manually verifying a batch of failed transactions. He finishes work around 6:30 PM, disconnecting completely to cook dinner and spend time with his partner. Weekends are reserved for running longer distances or visiting independent coffee shops to taste-test competitors' products.
Lifestyle
Doug lives in a sunlit, slightly chaotic flat in Dalston where his partner runs a graphic design studio. Their home is filled with vintage audio equipment and a dedicated coffee bar that serves as both a workspace and a testing ground for new blends. He runs five mornings a week along the Regent's Canal, using the rhythm of the city to clear his head before work. Financially, he is disciplined; he maximizes pension contributions and treats savings as a buffer against market volatility rather than a tool for speculation. Socially, he prefers deep conversations over loud parties, often gathering close friends for dinner parties centered around food pairings or technical debates. He avoids consumer clutter, preferring high-quality, long-lasting items that serve a specific function without unnecessary ornamentation.
Work life
As the sole technical operator for a three-person specialty coffee brand, Doug's day is split between architecting the backend and troubleshooting immediate operational fires. He maintains the Medusa-based stack that powers their recurring billing logic, which is critical given their subscription model. While his co-founders are physically present grinding beans and packing boxes in East London, Doug manages the digital storefront, ensuring the API handles weekly catalog updates seamlessly. His work involves constant context switching: refactoring TypeScript services in the morning, debugging payment gateway failures at lunch, and coordinating inventory syncs with the roastery team in the afternoon. The pressure comes from the fact that if the code breaks, the revenue stops immediately; there is no middle management layer to absorb the shock. He values clean architecture but is often forced to prioritize speed of delivery over elegance when a launch is imminent.
Relationships
Doug relies heavily on his two co-founders, viewing them as the operational anchor while he provides the digital infrastructure. He has a supportive partnership with his significant other, who understands the demands of startup life. His social circle consists mostly of fellow engineers and local business owners, often meeting for coffee or runs rather than drinks. He respects data-driven advice but ultimately makes final decisions based on his own gut feeling after rigorous analysis. He is less influenced by industry trends and more by peer reviews and direct user feedback from his customer base.
How they decide
Analytical and evidence-based. Doug rarely makes impulsive decisions regarding technology or finance. He requires concrete proof of concept, detailed documentation, and clear failure modes before committing resources. He prefers to evaluate tools based on their long-term maintainability and community support rather than marketing hype. When faced with a choice, he will build a small prototype to test viability before scaling, favoring a 'measure twice, cut once' approach even under time pressure.
How they sound
Doug speaks with a clipped, precise cadence typical of someone who values efficiency. He avoids filler words and superfluous adjectives, preferring direct statements. His tone is calm and measured, even when discussing urgent problems. He rarely uses corporate jargon unless necessary for clarity, instead opting for plain English to describe technical concepts. He does not exaggerate or use emotional appeals in conversation, focusing strictly on facts, metrics, and logical outcomes. Sarcasm is minimal, reserved only for close colleagues.
Personality traits
- methodical
- stoic under pressure
- verbally concise
- systematically skeptical
- perfectionist about code hygiene
- quietly passionate
- pragmatic
- highly self-reliant
- detail-obsessed
- uncompromising on uptime
Goals
- Achieve full product-market fit within the next 18 months to secure Series A funding.
- Refactor the legacy Monolith into a microservices architecture to improve deployment velocity.
- Build a sustainable personal routine that allows for consistent long-distance running without burnout.
- Establish a mentorship network with other non-technical founders in the DTC space.
- Reduce technical debt by automating 40% of manual QA processes.
- Purchase a small plot of land in the Cotswolds for future retirement.
Problems & frictions
- Managing the cognitive load of being the only engineer while wearing the hat of product manager.
- Frustration with third-party dependencies in the Medusa ecosystem causing unexpected downtime during peak hours.
- Difficulty finding reliable talent who understand both e-commerce logistics and modern JS frameworks.
- Balancing the need for rapid feature iteration with the requirement for bulletproof financial transaction integrity.
- Time scarcity preventing deep work sessions required for complex architectural planning.
- Keeping up with the rapidly evolving landscape of serverless commerce solutions while maintaining stability.
Values
- reliability
- directness
- build quality
- customer trust
- technical autonomy
- operational transparency
Interests
- specialty coffee
- TypeScript
- running
- small-batch packaging
- mechanical keyboards
- industrial design
Media habits
- The Daily (podcast)
- Hacker News daily digest
- Specialty Coffee Association newsletters
- Local independent film screenings
- GitHub trending repositories
- Runner's World UK