Why this persona fits the audience
Works at a marketplace company in New York and pulls data from MySQL and SQL Server for weekly metrics, support investigations, and launch checks. Uses a lightweight free SQL client, spreadsheets, and shared docs to move between analysis and stakeholder updates, and is the main non-engineer in the data workflow.
- Age: 28
- Location: New York, NY, US
- Occupation: Product Operations Analyst
- Income: $105k
- Education: B.A. in Statistics
- Company size: Mid-sized (approx. 300 employees)
- Years in role: 3
“The real value isn't just in the numbers themselves, but in understanding what they mean and how we can use them to build something better.”
Jeremy Purdy, 28, is a Product Operations Analyst at a rapidly growing marketplace company based in New York City. Holding a B.A. in Statistics from a state university, he landed his current role three years ago, drawn by the dynamic environment and the opportunity to work directly with product development teams. His income of $105k allows for a comfortable life in Brooklyn, where he rents a one-bedroom apartment, and supports his passion for travel and experiences. Jeremy is the primary non-engineer responsible for extracting and analyzing data from the company's MySQL and SQL Server databases. His daily work involves generating crucial weekly metrics, investigating customer support issues, and performing pre-launch checks to ensure product stability and performance. He navigates this complex data workflow using a lightweight, free SQL client, meticulously organizing his findings in spreadsheets and shared documents before presenting them to stakeholders. This role demands a high degree of accuracy and responsiveness, as product decisions and issue resolutions often hinge on the data he provides. Recently, he spearheaded the data validation process for a significant new feature rollout, working closely with engineering to ensure all tracking was implemented correctly and that the initial performance metrics aligned with projections. He also made a conscious decision to invest in a more robust spreadsheet software subscription to improve his charting and pivot table capabilities, recognizing it as a critical bottleneck in his current reporting process. Jeremy is driven by a desire for clarity and practical problem-solving, constantly seeking ways to make data more accessible and actionable for his colleagues. He views his role as a critical bridge between raw data and strategic product decisions, a responsibility he takes very seriously. His career aspirations are focused on deepening his analytical expertise and potentially moving into a leadership position where he can mentor others and influence data strategy at a higher level. He’s also saving diligently, aiming to fund future international travel adventures and build a solid financial foundation for long-term security.
Background & daily life
A day in their life
Jeremy's typical weekday starts around 7:30 AM with a quick check of urgent emails and Slack messages before his commute. He grabs a coffee and listens to a podcast on the subway to his Brooklyn office. By 9 AM, he's diving into his first set of SQL queries for the daily dashboard. Mid-morning might involve a meeting with the product team to discuss upcoming launch metrics or an investigation into a customer support ticket requiring data analysis. Lunch is usually a quick affair at his desk or a nearby deli. The afternoon is a mix of ad-hoc requests, refining weekly reports, and documenting his findings. He often stays until 6:30 PM, ensuring all critical tasks are handled before heading home to make dinner and unwind.
Lifestyle
Jeremy lives a structured but not rigid life in Brooklyn, balancing his demanding job with personal pursuits. He’s diligent about his finances, saving a portion of his salary for future travel and potential down payments, but isn't overly frugal. His evenings often involve a mix of unwinding with a basketball game on TV, catching up on industry news, or planning his next trip. Weekends are for exploring the city, meeting friends for brunch, or occasionally diving deep into a personal data project. He prioritizes experiences over material possessions, finding satisfaction in learning and growth.
Work life
As a Product Operations Analyst at a bustling NYC marketplace company, Jeremy is the go-to for extracting and interpreting data. His days are a constant flow of SQL queries against MySQL and SQL Server databases, generating weekly performance metrics, assisting with urgent support investigations, and validating new feature launches. He's the primary non-engineer navigating the data pipeline, translating raw numbers into actionable insights for product managers and engineers. The pressure is on for quick, accurate reporting, often requiring him to juggle multiple urgent requests simultaneously. He relies heavily on his free SQL client, spreadsheets, and shared documents to manage this workflow.
Relationships
Jeremy maintains strong connections with his close-knit group of college friends, many of whom are also in tech or finance, providing a valuable peer network for professional advice. He’s close with his parents, who live upstate, and calls them weekly. His primary professional influence comes from his direct manager and a senior data engineer he collaborates with frequently, both of whom he respects for their technical acumen and pragmatic approach.
How they decide
Jeremy tends to be research-heavy and methodical when making decisions, especially those involving tools or significant time investments. He weighs options carefully, seeks out peer recommendations, and looks for evidence of practical utility and long-term value. He’s not impulsive but will act decisively once he’s confident in his analysis and the expected outcome.
How they sound
Jeremy speaks with a clear, measured cadence, avoiding overly technical jargon when speaking to non-engineers. He uses precise language and is comfortable with a moderate level of formality, but can also be conversational. He tends to be direct and avoids hyperbole, preferring to stick to facts and logical reasoning. He might occasionally use mild tech-related slang with peers but generally keeps his communication professional and focused.
Personality traits
- Analytical
- Methodical
- Detail-oriented
- Proactive
- Reliable
- Pragmatic
- Resourceful
- Calm under pressure
- Independent
Goals
- Become a senior data analyst or manager within his company
- Develop expertise in advanced data modeling and statistical analysis
- Travel to at least two new countries per year
- Achieve financial independence to pursue passion projects
- Mentor junior analysts entering the field
Problems & frictions
- The constant need to switch between different data tools and formats slows down his workflow.
- Occasional data inconsistencies or access issues require time-consuming troubleshooting.
- Balancing urgent ad-hoc requests with long-term analytical projects.
- Communicating complex data findings clearly to non-technical stakeholders.
- Feeling the pressure to be available for data requests outside of standard working hours.
Values
- clarity
- responsiveness
- practical problem-solving
- efficiency
- accuracy
Interests
- marketplace metrics
- basketball
- travel
- data visualization
- tech trends
Media habits
- Reads industry blogs (e.g., TechCrunch, Hacker News)
- Listens to podcasts during commute (e.g., The Indicator, Pivot)
- Follows data analytics influencers on LinkedIn
- Uses Reddit for niche tech discussions
- Watches YouTube tutorials for new tools