Kelli Tillman

Why this persona fits the audience

Builds product features at a New York fintech with a seven-person engineering team. She joins ad hoc pair-debugging sessions a few times a week in VS Code Live Share and keeps a running chat thread open for context while remote.

• Age: 28
• Location: New York, NY, US
• Occupation: Product engineer
• Income: US$148k base + bonus
• Education: B.S. Software Engineering
• Company size: 7-person engineering team within a 45-person startup.
• Years in role: 3 years in current role; 6 years total post-graduation.

“Code isn't just syntax; it's a promise you make to the user that the numbers will add up exactly right, every single time.”

Kelli Tillman is a twenty-eight-year-old product engineer embedded in the high-stakes environment of a New York-based fintech startup. With a B.S. in Software Engineering from Penn State, she entered the workforce during the tail end of the pandemic boom, adapting quickly to the hybrid work culture that now defines her daily reality. Currently earning a base salary of $148,000 plus performance bonuses, she represents the archetype of the modern 'product engineer'—someone who bridges the gap between pure software development and business requirements. She works within a lean seven-person engineering team, a structure that demands extreme versatility; she doesn't just write code, she designs databases, configures CI/CD pipelines, and frequently sits in on product strategy meetings to ensure technical feasibility. Her professional life is characterized by a relentless pursuit of pragmatism and fast feedback loops. In a sector where a millisecond delay or a rounding error can trigger regulatory scrutiny, Kelli's approach is grounded in meticulous verification. She is known for her ability to jump into ad-hoc pair-debugging sessions, often utilizing VS Code Live Share to collaborate remotely with teammates across different time zones. Unlike many developers who isolate themselves in 'flow states,' Kelli thrives on the collaborative friction of solving complex problems in real-time, maintaining a running chat thread to preserve context as the conversation shifts between high-level architecture and low-level syntax. Recently, she made the strategic decision to refactor a legacy payment reconciliation module, a move that required convincing skeptical stakeholders to pause feature shipping for a week of refactoring. This decision underscores her long-term vision; she understands that technical debt is a silent killer of velocity. Outside of her code editor, Kelli is an avid cyclist who navigates the city streets with the same precision she applies to her algorithms. She balances her high-income lifestyle with a frugal mindset, prioritizing savings and experiences over luxury goods. Her world is one of constant optimization, whether it's optimizing a SQL query or optimizing her commute to avoid traffic, driven by a belief that efficiency is the highest form of respect for one's own time and the company's resources.

Background & daily life

A day in their life

The day starts with a double-shot oat milk latte and a quick scan of the overnight CI/CD logs on her phone. By 9:00 AM, she's in the office, reviewing the Jira board and pulling three tickets for the payments module. The morning is dominated by a live pair-debugging session with a colleague in London regarding a race condition in the settlement logic; they use VS Code Live Share, navigating the cursor together while keeping a running chat log for context. Lunch is a quick falafel wrap eaten at her desk while skimming a Substack article on React server components. The afternoon involves a code review for a junior dev's PR, focusing on error handling patterns, followed by a frantic 15-minute sync with the product manager to scope a last-minute compliance fix. She leaves by 6:30 PM, taking the bike path home to decompress before cooking a simple meal and reading fiction until sleep.

Lifestyle

Kelli lives in a sun-drenched loft in Long Island City, trading the Manhattan subway chaos for a view of the East River. Her routine is disciplined: she cycles to work at 7:45 AM, avoiding the train's unpredictability, and spends her evenings either tending to a sprawling succulent collection or hiking the nearby waterfront trails. Financially, she is aggressive but calculated, maxing out her 401(k) match and contributing to a high-yield savings account for a down payment on a condo. She socializes primarily with colleagues who share her technical intensity, often meeting for dinner at casual spots in Astoria where conversation drifts from market trends to the best espresso in Queens. Health is maintained through consistent yoga and an occasional spin class, prioritizing mental clarity over aesthetic fitness goals.

Work life

As a product engineer in a seven-person team, Kelli wears the hat of both builder and bridge. Her days are split between deep-focus coding sprints and rapid-fire synchronization meetings. She relies heavily on VS Code, often utilizing Live Share to jump into a peer's terminal instantly when a production issue spikes. The pressure comes from the fintech sector's zero-tolerance for transactional errors; a single bug can mean compliance violations. She manages her own feature lifecycle from conception to deployment, constantly negotiating with product managers about scope versus speed. Her workspace is a dual-monitor setup with a physical keyboard, always paired with a persistent Slack thread that acts as her external brain, ensuring no context is lost during the chaotic handoffs between design and QA.

Relationships

Kelli is the anchor of her immediate circle, often organizing weekend hikes or game nights for her college friends. She maintains a close, supportive relationship with her younger brother, who is still in grad school, offering him career advice and financial planning tips. At work, she has a symbiotic but occasionally tense relationship with the lead product manager, driven by their shared goal of shipping reliable products. Her influence stems from her reputation for solving impossible bugs quickly; she is the person others call when they are stuck, making her a de facto leader despite her individual contributor title. She values authenticity and rarely engages in office politics, preferring direct problem-solving.

How they decide

Kelli operates on a 'verify then commit' basis. She is not impulsive; before adopting a new tool or methodology, she runs a small-scale proof-of-concept to validate performance claims against her specific stack. She relies heavily on peer validation, asking trusted colleagues how a solution performed in production rather than reading marketing copy. Her decisions are data-driven and pragmatic, weighing the immediate cost of implementation against long-term maintenance burdens. She dislikes black-box solutions and prefers tools that offer transparency into their underlying mechanics.

How they sound

Her speech is crisp and efficient, favoring active voice and concrete nouns over abstract fluff. She uses industry slang naturally ('that's a hairy edge case,' 'let's spin up a sandbox') but avoids jargon when speaking to non-technical stakeholders. She tends to pause briefly to gather thoughts rather than filler words like 'um.' She rarely speaks in absolutes, preferring qualifiers like 'based on the logs' or 'it seems.' She avoids emotional venting in professional settings, channeling frustration directly into actionable steps.