Terrance Zboncak

Why this persona fits the audience

Self-employed software engineer in Austin, US, managing multiple client projects with irregular hours. Currently tracks sleep and energy levels manually using a basic spreadsheet and a free fitness tracker app to optimize coding sprints, but finds the data fragmented and lacks automated circadian insights.

• Age: 29
• Location: Austin, Texas, USA
• Occupation: Freelance Full-Stack Developer
• Income: $85,000 - $110,000
• Education: Bachelor's Degree in Computer Science
• Company size: N/A (Solo)
• Years in role: 4 years as full-time freelancer

“I don't believe in laziness; I believe in misaligned biology trying to run on an operating system that doesn't support it.”

Terrance Zboncak is a 29-year-old freelance full-stack developer navigating the volatile waters of the independent contractor economy in Austin, Texas. With a Bachelor's degree in Computer Science and four years of solo practice under his belt, Terrance has carved out a niche building robust backend systems and scalable front-end interfaces for startups and mid-sized enterprises. Unlike his corporate peers who had structured schedules and HR departments, Terrance operates as a one-person startup, managing everything from client acquisition to server deployment. His income fluctuates between $85,000 and $110,000 annually, a range he views as a baseline to be optimized rather than a ceiling. His approach to life is deeply rooted in the philosophy of biohacking and systemic efficiency. Terrance treats his body as hardware that requires constant tuning. He currently employs a rudimentary stack of manual tracking methods: a Google Sheet for logging sleep duration and subjective energy scores, paired with a free tier of a fitness tracker app that monitors heart rate variability. While this system provides raw data, it fails to synthesize the correlations between his circadian rhythms and his coding output. He frequently notices patterns—afternoon crashes, early morning clarity—that he cannot act upon because the data is siloed and unconnected. Terrance is driven by a need for autonomy but constrained by the unpredictability of client demands. He recently rejected a lucrative six-month contract because it required weekend availability, a decision that cost him potential revenue but preserved his mental health. He is currently experimenting with a new morning light timer setup and a strict caffeine cutoff protocol, yet he lacks a unified dashboard to visualize the results. His frustration lies not in the lack of effort, but in the fragmentation of his tools. He wants to understand the 'why' behind his energy fluctuations to build a sustainable career, not just survive it. For Terrance, the gap between knowing he should sleep better and actually optimizing his schedule based on scientific insight is the biggest bottleneck in his professional and personal evolution.

Background & daily life

A day in their life

Terrance wakes up at 6:15 AM, not because an alarm rings, but because his internal clock hits its nadir. He immediately checks the weather and his calendar, then does 20 minutes of mobility work before brewing cold brew coffee. By 7:30 AM, he is at his desk, tackling the most cognitively demanding tasks while his brain is sharpest. He takes a long lunch break around 12:30 PM to walk outside, seeking sunlight to reset his circadian rhythm, often listening to a podcast on cognitive science. Afternoon meetings are scheduled deliberately between 2:00 and 4:00 PM to align with his natural dip in alertness. Dinner is eaten at 6:30 PM sharp, followed by a block of 'deep work' until 9:00 PM. He winds down by reading physical books, avoiding screens to ensure melatonin production, and aims to be asleep by 10:30 PM to hit a 7.5-hour window.

Lifestyle

Terrance lives in a minimalist, tech-filled studio in East Austin, where every gadget serves a specific utility. He runs three mornings a week, using the time to decompress from screen glare, often logging his pace and heart rate variability in a custom Notion database. His diet is functional; he cooks simple, high-protein meals on Sundays to avoid decision fatigue during the week. Financially, he maintains a healthy emergency fund but is frugal with subscriptions, preferring one-off purchases over recurring fees unless the ROI is undeniable. Socially, he prefers deep conversations over parties, often meeting friends for coffee or at co-working spaces rather than loud bars, valuing quality of interaction over quantity.

Work life

As a solo full-stack developer, Terrance juggles three concurrent contracts: a fintech API migration, a health-tech MVP, and a maintenance retainer. His days are non-linear, dictated by client timezone overlaps and his own peak cognitive windows. He relies heavily on VS Code extensions, Jira for ticket management, and Slack for communication. The pressure stems from the lack of a safety net; missed deadlines mean immediate revenue loss. He spends roughly 60% of his day in deep work mode, 20% in meetings, and 20% in administrative overhead. Recently, he implemented a strict 'no-code after 9 PM' rule to protect his sleep, though he frequently breaks it when debugging a critical production issue.

Relationships

Terrance is close to his older sister, who works in healthcare, and they discuss lifestyle changes frequently. He has a small circle of four close friends from university who meet quarterly for hiking trips. He participates in an online community of indie hackers where he shares code snippets and wins small challenges. He avoids heavy family obligations, having moved to Austin specifically to minimize them. His primary influence is a former mentor from college who now runs a successful agency, whose advice on work-life balance Terrance tries to emulate but adapts to his own biological needs.

How they decide

Terrance approaches decisions with a rigorous, evidence-based methodology. He rarely buys based on marketing copy; instead, he seeks out third-party reviews, technical specifications, and peer testimonials before committing. He treats his wallet like a budget constraint in a system architecture—every dollar must serve a defined purpose. If a tool promises a benefit, he looks for the underlying mechanism. He is willing to pay for premium solutions if the long-term efficiency gains are mathematically clear, but he remains highly skeptical of vague claims or subscription traps.

How they sound

Terrance speaks in a measured, articulate cadence, often using precise terminology like 'latency,' 'throughput,' or 'optimization' even in casual conversation. He avoids hyperbolic language, preferring qualifiers like 'likely,' 'statistically significant,' or 'in my experience.' He rarely uses slang, except for specific tech jargon that has permeated his vocabulary. When frustrated, he gets quiet and analytical rather than emotional. He tends to explain the 'why' behind his actions, often breaking down complex problems into first principles. He values brevity and clarity, often cutting to the chase in emails or messages.