Jerry Heaney

Why this persona fits the audience

Works on a 6-person team building an image-plus-text assistant for a B2B SaaS product. He maintains Python evaluation scripts, reviews model failures in spreadsheets, and helps compare candidate models before weekly releases. The team also curates hard examples from real user logs and a small set of synthetic prompts.

• Age: 31
• Location: Austin, TX, US
• Occupation: Applied ML Engineer
• Income: $165k
• Education: MS in Computer Science
• Company size: Mid-sized tech company (approx. 500 employees)
• Years in role: 4

“The real challenge isn't building the model; it's understanding precisely *why* it fails, so we can build it better next time.”

Jerry Heaney, 31, is an Applied ML Engineer based in Austin, Texas, where he works for a mid-sized SaaS company. Holding an MS in Computer Science, he has carved out a niche in the demanding field of multimodal AI. His current role places him on a six-person team dedicated to enhancing an image-plus-text assistant, a critical component of their B2B offering. Jerry's daily reality is steeped in the meticulous craft of model validation. He is the custodian of Python evaluation scripts, the architect of processes that scrutinize model performance, and the diligent reviewer of failure logs, often presented in the stark clarity of spreadsheets. His work is intrinsically tied to the product's release cycle; he plays a key role in comparing candidate models, ensuring that only the most robust versions are deployed weekly. This responsibility extends to the crucial task of curating challenging examples, a process that draws from both real-world user interactions and carefully constructed synthetic prompts. This focus on rigor and reliability is not merely professional; it reflects a deeper personal value system. Jerry is driven by a desire for clear ownership and the satisfaction of shipping dependable software. His income of $165k allows for a comfortable lifestyle, which he manages with a disciplined approach, prioritizing long-term financial health. While his career demands significant intellectual energy, he finds balance through his passion for cycling and a commitment to staying abreast of the latest advancements in multimodal ML and open-source tooling. He views his work not just as a job, but as a continuous process of learning and refinement, deeply invested in the technical integrity of the products he helps build.

Background & daily life

A day in their life

Jerry's typical weekday begins around 7:00 AM with a quick breakfast and scanning tech news. He's usually at his desk by 8:30 AM, diving into Slack and email before his first stand-up meeting at 9:00 AM. The morning is often spent refining evaluation scripts or analyzing results from overnight model runs. Lunch is a quick, healthy meal at his desk while reading a research paper. Afternoons involve team syncs, code reviews, and deep dives into model failure analysis, often involving debugging or identifying patterns in spreadsheets. He might spend an hour experimenting with a new open-source library or discussing potential improvements with a colleague. He logs off around 6:00 PM, often heading out for a bike ride, followed by dinner and an evening of personal study or relaxation.

Lifestyle

Jerry leads a structured life in Austin, balancing his demanding tech career with personal pursuits. His weekdays revolve around work, but evenings are reserved for cycling rides along Lady Bird Lake or catching up on research papers. He enjoys cooking simple, healthy meals and occasionally meeting up with a small group of friends for board games or trivia nights. Financial discipline is important; he saves a significant portion of his income, prioritizing long-term security over immediate gratification, though he does allow himself occasional splurges on high-quality cycling gear. His social circle is relatively small but close-knit, valuing deep conversations over superficial interactions.

Work life

Jerry's days are intensely focused on the practical application of machine learning within his team. He spends a considerable amount of time writing and refining Python scripts for model evaluation, meticulously tracking performance metrics and identifying regressions. A significant portion of his week involves deep dives into spreadsheets, categorizing and analyzing model failures based on user-submitted examples and synthetic test cases. He collaborates closely with two other engineers and a product manager, engaging in detailed discussions about candidate models, trade-offs, and the implications of potential bugs. The pressure to ship reliably before the weekly release cycle is a constant, driving his focus on thorough testing and validation.

Relationships

Jerry maintains a close but geographically dispersed relationship with his parents, calling them weekly. His core social group in Austin consists of about five friends from university, mostly in tech, with whom he shares technical interests and occasional social outings. He has a cordial but professional relationship with his immediate team members, respecting their expertise and contributions.

How they decide

Jerry is a highly analytical and research-driven decision-maker. He prioritizes empirical evidence, thoroughly investigating options, comparing data points, and considering potential long-term implications. He is not easily swayed by hype or superficial claims, preferring to rely on objective metrics and logical reasoning. While he values input from trusted colleagues, the final decision rests on his own rigorous assessment of the available information.

How they sound

Speaks clearly and precisely, with a measured cadence. Tends to use technical jargon naturally within work contexts but avoids unnecessary complexity in general conversation. His tone is generally calm and objective, even when discussing challenging problems. He's not prone to hyperbole or overly casual slang, preferring direct and accurate language. He often pauses to formulate his thoughts carefully before responding.