Violet Ryan

Why this persona fits the audience

On a 4-person platform squad at a London fintech, she maintains a paid commercial SAST subscription alongside Jira tickets for security exceptions. She also adds hand-written regression tests for auth and input-validation issues in two Java services used by a 15-engineer product group.

• Age: 34
• Location: London, UK
• Occupation: Staff software engineer
• Income: £125k-£155k total compensation
• Education: MSc in Software Engineering
• Company size: Series B Fintech, ~200 employees
• Years in role: 3 years as Staff Engineer

“In our line of work, the cost of being wrong isn't just a bug report; it's the trust of the entire organization evaporating in a single night.”

Violet Ryan, 34, is a Staff Software Engineer based in London, operating at the intersection of high-performance system design and rigorous application security. With an MSc in Software Engineering from Imperial College London, she spent six years climbing the ranks in various fintech startups before landing her current role at a Series B company. Unlike many of her peers who chase the latest buzzwords, Violet is driven by a deep-seated need for reliability and structural integrity. She currently sits on a lean four-person platform squad, a role that forces her to wear multiple hats: architect, developer, and security guardian. Her approach to security is pragmatic yet uncompromising. While the company utilizes a paid commercial SAST subscription for broad detection, Violet knows its limitations. She dedicates significant effort to maintaining a living library of Jira tickets for security exceptions, ensuring that every bypass of a control is temporary, justified, and tracked. Furthermore, recognizing that automated tools miss context-specific logic errors, she personally writes hand-coded regression tests in Java for authentication and input validation in two critical services. These tests serve as behavioral guards for a 15-engineer product group, preventing regressions that static analysis might overlook. Outside of work, Violet channels her discipline into rowing and running. These activities provide a counterbalance to the mental load of securing financial transactions. She views her career not just as a job, but as a stewardship of the digital infrastructure that underpins modern finance. Recently, she made the strategic decision to reject a promotion to a management track, choosing instead to deepen her technical influence as a Staff Engineer, believing this path offers the most direct leverage to improve system security. She is a woman who believes that clarity is kindness, and that the best security is invisible, robust, and proven.

Background & daily life

A day in their life

Violet wakes at 5:30 AM, runs four kilometers along the river, and returns for a cold shower and breakfast. She arrives at the office by 8:30 AM, starting with a review of overnight CI/CD logs and SAST scan results. Her morning is dominated by a deep-work block focused on writing integration tests for a critical input validation patch. At noon, she joins a stand-up with her platform squad, discussing a recent security exception approval. After lunch, she conducts code reviews for the product team's Java services, focusing specifically on authentication flows. The afternoon involves a cross-functional meeting to align on a new API gateway architecture, followed by an hour of documentation updates for the team's security wiki. She leaves the office around 6:00 PM, heading to rowing practice until 7:30 PM, then winds down with reading or a podcast before bed.

Lifestyle

Violet lives in a renovated Victorian flat in Islington, where the kitchen is the only chaotic space. Her mornings begin at 5:30 AM with a 4km run along the Thames Path before work, a ritual that grounds her day. She belongs to a competitive rowing club in Mortlake, training three times a week with a focus on endurance and technique rather than pure speed. Financially, she is aggressive about saving, maxing out her pension contributions and investing surplus cash into low-cost index funds, viewing money as a tool for freedom rather than status. Socially, her circle is tight-knit, consisting mostly of colleagues from the tech sector and fellow rowers, with whom she shares a quiet appreciation for structured activity over loud socializing.

Work life

As the de facto security lead on a four-person platform squad, Violet balances architectural decisions with hands-on coding. She manages a commercial Static Application Security Testing (SAST) subscription, meticulously reviewing its alerts against internal risk profiles. A significant portion of her week is spent writing custom regression tests in Java for authentication and input validation logic within two core services used by a larger product group. She relies heavily on Jira to formalize security exceptions, ensuring every waiver has a documented business justification. Her days are filled with code reviews, architecting secure APIs, and mentoring junior engineers on how to write self-documenting, secure code without stifling their creativity.

Relationships

Violet's relationship with her partner is built on mutual professional ambition and shared quiet evenings. Her parents live in Manchester and visit monthly for dinner, providing a grounding family dynamic. She is deeply embedded in the London tech community, often attending meetups not for networking, but for knowledge exchange. Her influence extends through her mentorship of three junior engineers, who view her as a gold standard for technical integrity and calm leadership.

How they decide

Cautious, evidence-based, and systematic. Violet rarely makes impulsive decisions; she requires data, documentation, and peer consensus before committing to a new direction or tool. She values clarity and long-term implications over short-term gains, often spending hours researching the architectural impact of a decision before approving it. Peer recommendations carry weight, provided they are backed by concrete examples or case studies rather than marketing hype.

How they sound

Her speech is precise, measured, and devoid of filler words. She uses technical terminology correctly but avoids jargon when speaking to non-technical stakeholders. She tends to speak in complete sentences, often prefacing opinions with 'Based on the data...' or 'From an architectural perspective...'. She rarely raises her voice, even when discussing critical failures, preferring a calm, firm tone that commands respect. She avoids vague qualifiers like 'maybe' or 'sort of', replacing them with specific probabilities or conditions.