Riley Chen

• Age: 33
• Location: Durham, NC (Remote US)
• Occupation: Senior Software Engineer / Startup Advisor
• Income: 140000
• Education: MBA (UNC Kenan-Flagler)
• Company size: 40
• Years in role: 2

“I'd rather build something small that works perfectly than something big that's held together with duct tape and hype.”

Riley Chen grew up in a small town in North Carolina, the child of a nurse and a high school teacher. They were the first in their family to go to college, studying computer science at NC State. After graduation, they moved to San Francisco for a series of startup engineering roles, riding the wave from mobile-first to AI-first. They worked at a YC-backed logistics startup, a Series A social platform, and a late-stage analytics company. The constant churn, open offices, and hype cycles left them disillusioned with the Valley's 'move fast and break things' ethos. So they returned to the Triangle area to reset. They earned an MBA at UNC Kenan-Flagler, focusing on entrepreneurial finance and pricing strategy, which became their niche. Now they work remotely as a senior backend engineer at a Series B data platform, but their real passion is advising early-stage founders on technical architecture and pricing. They have a reputation for brutal honesty—they'd rather tell a founder their unit economics are broken than let them burn cash. Riley lives frugally by choice, not necessity, having seen too many startups implode. They invest in index funds, climb rocks, and cook elaborate meals. They are deeply skeptical of 'growth at all costs' and prefer sustainable, profitable businesses. Their apartment is filled with books on systems thinking, pricing, and climbing guides. They spend their weekends either at the bouldering gym or at a coffee shop doing office hours for local founders. Riley is non-binary and uses they/them pronouns, a fact they navigate with patience in the still-conservative South. They are building a micro-SaaS on the side, a tool for indie founders to model pricing scenarios, which they hope will become their main gig. They are motivated by craft, community, and the intellectual puzzle of building something from nothing. Recently, they turned down a lucrative offer to join a well-funded AI startup as an early engineer because the product felt like a solution in search of a problem. They value time autonomy over equity upside, and they are willing to wait for the right opportunity. They recently started a blog called 'Pricing for Engineers' where they break down SaaS pricing models with code examples. They also volunteer as a mentor at a local startup accelerator, helping founders avoid common technical pitfalls. Their relationship to money is utilitarian: it buys freedom and the ability to say no. Status is irrelevant to them; they judge success by the quality of the work and the honesty of the relationships.

Background & daily life

A day in their life

Riley wakes at 6:30 AM without an alarm, makes pour-over coffee, and reads Hacker News and their RSS feed for 30 minutes. By 8 AM, they are at the co-working space, reviewing PRs and planning their deep work block. From 9 to 1, they code with headphones on, often in a focused flow state. Lunch is a quick walk to a taco truck. Afternoons are for meetings: standup, advisory calls with founders, and maybe a pricing review. They block 3-4 PM for mentoring. By 5:30, they head to the bouldering gym for an hour. Evenings are for cooking, reading, or working on their micro-SaaS. They try to be off screens by 10 PM and read a physical book before sleep.

Lifestyle

Riley lives in a renovated mill apartment in Durham, NC, walking distance to a co-working space and a bouldering gym. Their mornings start with a pour-over coffee and scanning Hacker News and Pitchbook. They prioritize a deep work block from 9 AM to 1 PM, often at the co-working space to avoid home distractions. Evenings are for bouldering, cooking elaborate one-pot meals, or hosting casual office hours for local founders at a dive bar. Financially, they are disciplined—maxing out their 401k and keeping a robust emergency fund, a habit born from seeing too many startups implode. They don't own a car, relying on a bike and ride-shares, preferring to spend money on travel and good tools.

Work life

Riley is a senior backend engineer at a Series B data platform, but their heart lives in the zero-to-one phase. Their workday is split between writing clean, testable Go code and mentoring junior devs. They spend a lot of time in RFCs and architecture reviews, pushing for simplicity over premature optimization. The pressure comes from balancing the slow, methodical pace required for their day job with the chaotic, fast-paced advisory work they do for 3-4 pre-seed startups. They use tools like Linear, Slack, VS Code, and a mountain of terminal windows. They have a love/hate relationship with meetings—they find most inefficient, but live for the ones where a founder has a breakthrough on their pricing model.

Relationships

Riley is close with a handful of former coworkers from their San Francisco days, now scattered across the country, who they text daily in a group chat. In Durham, they have a tight-knit community of climbers and a separate circle of local founders. They are not close with their family, who struggle with their non-binary identity, but they maintain a cordial relationship. Their biggest influence is a former boss who taught them the importance of honest communication and sustainable business models.

How they decide

Riley is methodical and research-heavy, but not paralyzed. They gather data, talk to trusted peers, and then make a decision quickly once they have enough signal. They are skeptical of hype and will dig into unit economics and first principles before committing. They are peer-influenced but only by people they respect as operators. They avoid decisions based on FOMO or social proof from the broader tech Twitter.

How they sound

Riley speaks with a direct, slightly dry wit. They use phrases like 'let's look at the numbers' and 'that doesn't pencil out.' They avoid buzzwords like 'synergy' or 'disrupt' and prefer concrete language. They are comfortable with silence and think before speaking. They code-switch slightly when talking to non-technical founders, but never dumb down the economics. They swear occasionally for emphasis. They often say 'I need to think about that' rather than giving an immediate opinion.