Why this persona fits the audience
At a 15-person fintech in London, he maintains animated UI icons for web and mobile. He previews and edits Lottie JSON in the browser, keeps a paid subscription to a competing animation tool, and sometimes tweaks recolors and font weights by hand before shipping to the app team.
- Age: 34
- Location: London, UK
- Occupation: Frontend Engineer
- Income: £88k/year
- Education: MSc Computer Science
- Company size: 15 people (Series A Fintech)
- Years in role: 6
“Efficiency isn't just about speed; it's about removing the possibility of human error from the process entirely.”
Wayne Gleichner is a 34-year-old Frontend Engineer based in London, operating within the high-stakes environment of a Series A fintech. With an MSc in Computer Science from Imperial College London, he has spent the last decade bridging the gap between fluid design and rigid code. Currently, he carries the dual burden of engineering and motion design, a reality born of the startup's lean staffing model. His workspace is a sanctuary of order: a mechanical keyboard, dual 4K monitors, and a meticulously organized folder structure. Despite earning £88k annually, Wayne remains frugal, viewing money as a tool for purchasing time and reliability rather than status symbols. His professional life is defined by a relentless pursuit of predictability. While his team relies on various external tools, Wayne maintains a paid subscription to a competitor's animation suite, yet he frequently bypasses its GUI features to edit raw Lottie JSON directly in the browser. This habit stems from a deep-seated skepticism of black-box automation; he needs to see the underlying data structure to trust the output. Recently, he spent three days manually tweaking font weights and recolors for a marketing campaign because the export tool failed to handle a specific variable font axis correctly. This experience reinforced his belief that until tooling becomes truly deterministic, manual intervention remains necessary. Wayne is not driven by the allure of new technology for its own sake. He evaluates every new dependency through the lens of maintenance cost and stability. He is currently weighing the pros and cons of migrating his animation workflow to a more integrated system but fears the disruption to his established, albeit inefficient, processes. His relationships are built on competence and reliability; he is the person his team calls when a render breaks in production. However, this reliance creates pressure, as he feels personally responsible for the smoothness of the user experience. Outside of work, he finds solace in the tactile satisfaction of coding clean interfaces and the quiet rhythm of cycling through East London streets, where the city's chaos is replaced by the predictable flow of traffic lights.
Background & daily life
A day in their life
Wayne starts his day with a quiet cup of coffee, reviewing Jira tickets and checking CI/CD logs for any overnight failures. By 9:30 AM, he joins the daily stand-up, offering concise updates on the animation performance metrics. His core work block involves diving into Lottie JSON files, manually adjusting color hex codes and font-weight properties to match the design spec exactly. Around noon, he meets with the product designer to discuss a new interaction pattern, pushing back gently on feasibility. After lunch, he focuses on writing unit tests for the animation hooks. Late afternoon is reserved for code reviews and optimizing CSS variables. He leaves the office by 6 PM, cycling home to cook dinner, often listening to tech podcasts. Evenings are for winding down, perhaps tinkering with a side project or reading, ensuring he disconnects completely before sleep.
Lifestyle
Wayne lives in a converted warehouse flat in Shoreditch, characterized by exposed brick and a minimalist aesthetic that reflects his professional taste. His routine is highly structured: he wakes at 6:15 AM, brews pour-over coffee while scanning technical newsletters, and cycles to work to manage stress. Health-wise, he prioritizes functional fitness over aesthetics, doing heavy lifting three times a week. Financially, he is prudent; he tracks every penny via spreadsheets but splurges on high-quality hardware when it guarantees long-term utility. Socially, he is selective, preferring one-on-one dinners or small board game nights with a tight circle of childhood friends rather than large networking events. He avoids debt and keeps an emergency fund covering six months of expenses.
Work life
At a lean fintech startup, Wayne operates as the bridge between abstract design concepts and functional code. His days are split between building React components and obsessively refining micro-interactions for the mobile app. He frequently finds himself acting as the de facto motion designer, despite having no formal training in graphic arts. The team relies on him to ensure animations don't introduce jank or increase battery drain. He spends significant time manually inspecting Lottie JSON files because he distrusts automated exports to hit exact pixel-perfect standards. Recent weeks have involved negotiating with designers who want complex effects that strain the browser's rendering engine, forcing him to find middle-ground solutions that maintain performance without sacrificing visual fidelity.
Relationships
Wayne shares a close partnership with Elena, a UX researcher who often challenges his rigid approach to implementation. They are each other's primary support system. Professionally, he has a mentorship relationship with the CTO, though they rarely socialize outside of work. He maintains sporadic contact with university peers, mostly exchanging niche technical insights. He feels a strong sense of responsibility toward his junior colleagues, often staying late to review their pull requests, though he rarely seeks help for his own struggles, preferring to solve problems independently.
How they decide
Wayne approaches decisions with a hypothesis-driven methodology. He rarely acts on impulse; instead, he gathers data, reads documentation, and runs small-scale experiments before committing to a new tool or strategy. He values peer validation but only from sources he trusts technically. If a proposed solution lacks transparency in its mechanics or introduces unpredictability, he will default to the known quantity, even if it is less efficient. He is willing to pay for a solution only after verifying it solves a specific friction point better than his current manual workaround.
How they sound
Wayne speaks with a clipped, precise British cadence, avoiding filler words like 'um' or 'like'. His vocabulary is heavily technical, leaning on terms like 'latency', 'rendering pipeline', and 'tokenization'. He tends to speak in conditional statements ('If we do X, then Y might happen') rather than absolutes. He avoids hyperbole and emotional language, preferring factual descriptions of system behavior. In conversation, he pauses frequently to formulate the most accurate technical description, sometimes appearing silent while others talk. He respects brevity and dislikes small talk that doesn't serve a purpose.
Personality traits
- meticulous about file structures
- silent observer in meetings
- prone to over-optimizing code paths
- respects boundaries of scope
- values deterministic outcomes
- technically self-sufficient
- dislikes ambiguous requirements
- quietly competitive about efficiency
- methodical in debugging
- selective with new software adoption
Goals
- Reduce technical debt in the legacy animation library
- Achieve full automation of the design-to-code handoff process
- Transition into a Staff Engineer role within two years
- Build a personal open-source project focused on developer tooling
- Maintain a work-life balance that prevents burnout
- Master advanced TypeScript patterns for state management
Problems & frictions
- Frustration with manual JSON editing taking up billable hours
- Inconsistency between design tools and production rendering
- Lack of clear version control history for animation assets
- Difficulty estimating time for complex motion implementations
- Reliance on a paid external tool that feels disconnected from the workflow
- Ambiguity in how new font weights render across different OS environments
Values
- engineering quality
- speed
- predictability
- technical autonomy
- cost-efficiency
Interests
- react
- design tokens
- web animation
- developer tooling
- mechanical keyboards
- scandinavian minimalism
Media habits
- Listening to 'The Changelog' podcast during commute
- Browsing GitHub trending repositories
- Reading Hacker News early morning
- Following specific design system accounts on Twitter/X
- Watching deep-dive technical YouTube tutorials
- Occasional gaming sessions with low-fidelity indie titles