Jared Deckow

Why this persona fits the audience

Works on a 4-person B2B SaaS team in Austin that is adding an AI drafting feature. He compares token counts from staging logs with official OpenAI and Anthropic rate cards, then keeps a shared spreadsheet for monthly budget planning and feature estimates.

• Age: 31
• Location: Austin, TX, USA
• Occupation: Full-stack engineer
• Income: $145k base
• Education: BS Computer Science
• Company size: 4
• Years in role: 3

“The most satisfying part of building software is seeing a well-architected system hum along, predictable and efficient, long after the initial rush of shipping.”

Jared Deckow, 31, embodies the diligent, analytical full-stack engineer archetype thriving in Austin's tech scene. He landed his BS in Computer Science from a reputable state university, cultivating a deep appreciation for elegant code and efficient algorithms. His career path led him to his current role at a seed-stage SaaS startup, where he's one of four engineers responsible for building out their core product. His $145k base salary reflects his expertise, but Jared isn't driven by ostentatious displays of wealth. Instead, his financial discipline is rooted in a desire for security and future autonomy. He meticulously tracks his expenses and saves a substantial portion of his income, viewing his financial health as a direct byproduct of his professional competence and a hedge against unforeseen career shifts. His work is characterized by a high degree of conscientiousness; he prioritizes shipping reliable software with clean, maintainable systems. Recently, his team's focus has been on integrating an AI drafting feature, a project that demands his keen attention to detail. He's been diligently comparing token counts from staging environments against official OpenAI and Anthropic rate cards, maintaining a shared spreadsheet to meticulously plan monthly budgets and estimate feature costs. This hands-on approach to cost management reflects his value of practical budgeting and his inherent desire to understand the granular details of the systems he builds. Beyond his professional life, his interests in backend architecture and indie SaaS are complemented by a passion for home espresso, where he applies a similar systematic approach to achieving the perfect brew. He's not overly extroverted, preferring focused work and quality time with a few close friends, but he's agreeable and a collaborative team member. His decision-making is heavily data-driven; he researches thoroughly, values empirical evidence, and often builds small prototypes to validate his choices, demonstrating a preference for well-reasoned, practical solutions over fleeting trends.

Background & daily life

A day in their life

Jared's typical weekday starts around 7:30 AM with a pour-over coffee and reviewing overnight system metrics. He bikes to the office by 9 AM, grabbing another coffee from a local spot. The morning is usually spent coding, tackling tickets from their project board, with a brief stand-up meeting around 10 AM to sync with the team. He dedicates a block of time to analyzing API token usage data for the new AI feature, updating their budget spreadsheet, and estimating the cost implications of potential parameter changes. Lunch is often a quick meal at his desk while catching up on Hacker News. The afternoon might involve pair programming, code reviews, or deep dives into documentation for the AI model integrations. He typically wraps up around 6 PM, cycles home, and might spend an hour working on a personal coding project or reading before making dinner.

Lifestyle

Jared lives a fairly ordered life in his Austin apartment, prioritizing efficiency and routine. His evenings often involve tinkering with his home espresso setup, perfecting latte art, or reading technical blogs. He's not a big spender on material goods, preferring to invest in quality tools for his hobbies and career. Socially, he enjoys occasional meetups with other engineers or quiet evenings with a few close friends. He's conscious about his finances, tracking expenses with a budgeting app and aiming to save a significant portion of his income, viewing it as a buffer and a means to future freedom rather than immediate gratification. He cycles to work most days, valuing the quiet contemplation it provides before and after his workday.

Work life

As one of four engineers at a rapidly growing seed-stage SaaS startup, Jared is deeply involved in both frontend and backend development. His current focus is integrating a new AI drafting feature, which involves meticulous tracking of API token usage. He spends significant time comparing costs across different LLM providers, meticulously logging data into a shared spreadsheet for budget projections and feature cost estimations. The small team dynamic means he wears multiple hats, often jumping between bug fixes, new feature development, and infrastructure concerns. The pressure to deliver quickly is palpable, but he strives to maintain code quality and system stability.

Relationships

Jared maintains a close-knit circle of friends, many of whom are also in tech and share similar interests. His parents, living in a different state, are proud of his career success. He has a cordial but not overly close relationship with his coworkers; they are a high-functioning team but maintain professional boundaries. He occasionally seeks advice on complex technical challenges from a former university professor he stays in touch with.

How they decide

Jared is a research-heavy decision-maker, especially when it comes to technical implementation and financial planning. He thoroughly investigates options, compares data points, and often builds small proofs-of-concept before committing. He values logic and empirical evidence, preferring solutions that are well-documented and have a clear track record. He’s not easily swayed by hype or trends unless backed by solid data. He’s willing to invest time upfront to avoid costly mistakes or inefficiencies later.

How they sound

Speaks with a clear, steady cadence. His tone is generally measured and thoughtful, rarely raising his voice. He uses precise technical language when discussing work but can be more relaxed and conversational with friends. He tends to avoid hyperbole or overly emotional language, preferring factual statements. He might say things like, 'Based on the logs, the average token cost per generated response is X,' or 'We need to ensure the architecture can scale horizontally.' He dislikes vague pronouncements and seeks concrete details.