Why this persona fits the audience
Works as the internal automation lead at a Berlin fintech startup with a 3-person product-ops pod. He runs Claude Code on his MacBook Air for data cleanup scripts and ticket templates, and keeps the queue in spreadsheets and Jira.
- Age: 29
- Location: Berlin, DE
- Occupation: Product operations / automation lead
- Income: €78k
- Education: Master's in Information Systems
- Company size: approx. 150 employees
- Years in role: 2.5 years
“The real win isn't just automating a task; it's building a system that makes that task obsolete for good.”
Luc Felke, 29, is the dedicated Internal Automation Lead at a burgeoning Berlin fintech startup, a role he’s held for two and a half years. His journey into this specialized niche began with a Master's in Information Systems, where he developed a deep appreciation for efficient systems and data integrity. Growing up in a modest household in a smaller German town, Luc learned early on the value of meticulous planning and resourcefulness. He moved to Berlin for university and found himself drawn to the fast-paced, innovative environment of the startup scene. His current position within a compact 3-person product-ops pod means he wears many hats, constantly juggling the demands of improving internal efficiency. His primary workstation is a MacBook Air, a device he’s optimized for his workflow, running Claude Code for everything from intricate data cleanup scripts to generating standardized ticket templates. He manages the team's operational backlog through a combination of spreadsheets and Jira, a system he’s continuously refining. Luc is driven by a core belief in process order and the power of low-friction automation to eliminate repetitive drudgery. He's particularly focused on reproducibility, ensuring that any automation he builds is robust and easily maintainable. This meticulous approach extends to his personal life; he saves diligently, aiming for a future where he can afford a small apartment with a dedicated, quiet workspace, a stark contrast to his current shared living situation in Prenzlauer Berg. He views time as a valuable, finite resource, and his work is a direct reflection of his desire to optimize its use, both for himself and his colleagues. His recent efforts have focused on standardizing the onboarding process for new employees through automated documentation generation and streamlining the bug reporting pipeline, a project that has consumed significant attention due to the complexity of integrating disparate data sources.
Background & daily life
A day in their life
Luc's typical weekday begins around 7:30 AM with a quick check of his personal scripts and any overnight alerts. After a strong coffee and a light breakfast, he cycles to the office, arriving by 9:00 AM. The morning is usually dedicated to focused work: writing or debugging Python scripts for data validation, refining Jira automation rules, or documenting a new process. He has a brief stand-up with his product-ops pod around 11:00 AM to sync on priorities. Lunch is a quick affair, often a packed meal eaten at his desk while scanning tech news. The afternoon might involve a meeting with another department to understand their workflow pain points, followed by more coding or troubleshooting. He aims to leave by 6:00 PM, but often stays later if a critical script needs immediate attention. Evenings are for personal projects or unwinding.
Lifestyle
Luc lives in a shared apartment in Prenzlauer Berg, a compromise for Berlin rent prices, though he dreams of a quiet place with a dedicated home office. His evenings are often spent refining scripts or exploring new automation techniques, sometimes losing track of time. He cycles to work, prioritizing health and avoiding public transport delays. Money is managed carefully; he's saving for a down payment on a small apartment but enjoys the occasional craft beer and good meal out with friends. Social life is structured, preferring smaller gatherings over large parties.
Work life
As the internal automation lead, Luc's days are a constant battle against manual processes and data inconsistencies within the fintech startup. He operates within a lean 3-person product-ops pod, meaning his scope is broad but resources are tight. His primary tool is a MacBook Air, where he leverages Claude Code for crafting data cleanup scripts and generating ticket templates. He meticulously manages task queues using a combination of spreadsheets and Jira, constantly seeking ways to streamline workflows. The pressure is on to deliver tangible efficiency gains without significant budget increases, making every script and automation a critical contribution.
Relationships
Luc maintains a close but not overly demonstrative relationship with his parents in Hamburg, speaking to them weekly. His core social circle consists of about five close friends from university, with whom he shares a passion for technology and board games. Within the company, he collaborates closely with his two product-ops colleagues but generally keeps to himself, preferring focused work over office politics. His direct manager, the Head of Product, is a key influencer on his project priorities.
How they decide
Luc is a highly analytical and research-driven decision-maker. He meticulously gathers data, compares options based on technical feasibility and long-term maintainability, and often prototypes solutions before committing. He values reproducibility and low-friction implementation, preferring tools that integrate seamlessly with his existing macOS environment and workflow. Peer opinions are considered but rarely sway him from a data-backed conclusion.
How they sound
Speaks with a measured, precise cadence, often using technical jargon naturally within conversation. Avoids overly casual slang or effusive language. His tone is generally calm and objective, even when discussing frustrations. He tends to pause to formulate his thoughts before answering complex questions. When explaining something, he prioritizes clarity and logical flow, sometimes using analogies related to systems or engineering.
Personality traits
- methodical
- detail-oriented
- analytical
- reserved
- persistent
- pragmatic
- self-reliant
- skeptical of hype
- organized
Goals
- Establish a robust, self-service automation framework for internal teams.
- Reduce manual ticket handling by 40% within the next fiscal year.
- Achieve a personal certification in advanced cloud automation.
- Transition to a more senior role with greater strategic input on tooling.
- Own a small, quiet apartment with a dedicated workspace.
Problems & frictions
- Inconsistent data quality across different internal systems.
- Resistance to adopting new automated workflows from some teams.
- Limited budget for specialized automation software or enterprise tools.
- The overhead of maintaining and updating numerous small scripts.
- Balancing urgent ad-hoc requests with long-term automation projects.
- Lack of standardized documentation for existing processes.
Values
- process order
- low-friction automation
- reproducibility
- efficiency
- data integrity
Interests
- internal tooling
- Jira workflows
- macOS productivity
- scripting languages (Python, Shell)
- data pipelines
Media habits
- Reads tech blogs (e.g., Hacker News, specific automation forums)
- Listens to productivity podcasts during commute
- Follows key figures in DevOps and product ops on LinkedIn
- Watches YouTube tutorials for new scripting techniques
- Uses Reddit for niche technical problem-solving