Bernadette Wuckert

Why this persona fits the audience

At a Seattle B2B SaaS company, she is the security-minded engineer for a 12-person product org. She runs free container and code scanners in GitHub Actions, keeps exceptions in a spreadsheet, and checks that fixes actually break the insecure path before moving on.

• Age: 45
• Location: Seattle, Washington, US
• Occupation: Principal platform engineer
• Income: $220k-$280k total compensation
• Education: B.S. in Computer Engineering
• Company size: 12-person product organization within a larger enterprise
• Years in role: 6

“If I can't prove it broke the vulnerability, I haven't fixed it—I've just moved the problem elsewhere.”

Bernadette Wuckert is a Principal Platform Engineer at a mid-sized B2B SaaS company in Seattle, where she has carved out a niche as the organization's primary guardian against security drift. At 45, with a B.S. in Computer Engineering earned nearly two decades ago, she brings a level of experience that allows her to see patterns invisible to younger engineers. Despite working in a lean 12-person product org, her influence extends across the entire engineering culture. She operates without a dedicated security budget, relying instead on open-source tools and her own meticulous engineering skills to maintain a robust defense posture. Her workflow is a hybrid of modern automation and old-school discipline: she orchestrates free container scanners within GitHub Actions but insists on a manual verification layer, documenting every exception in a shared Google Sheet that she updates religiously. This spreadsheet, a source of occasional friction with her team, represents her core philosophy: stability through verifiable evidence. She recently made the difficult decision to block a feature launch because a third-party library contained an obscure CVE that the automated scanner missed, a move that frustrated stakeholders but prevented a potential breach. Outside of work, Bernadette channels her need for order into her expansive garden and long-distance hiking expeditions, where the physical world offers a predictable counterbalance to the chaos of software development. She values her time and money highly, viewing them as finite resources that must be invested with extreme care. While she earns a top-tier salary, she drives a reliable sedan and lives modestly, believing that financial security is best achieved through frugality and strategic saving rather than conspicuous consumption.

Background & daily life

A day in their life

Bernadette wakes at 5:30 AM to tend to her tomato plants before the Seattle sun hits the greenhouse. After a quick breakfast of oatmeal and black coffee, she commutes via light rail, using the hour to review logs and scan emails for overnight CI/CD failures. By 9:00 AM, she is deep in code reviews, specifically hunting for injection flaws in new microservices. Lunch is a solitary affair, often spent reading about distributed consensus algorithms. The afternoon is reserved for meetings with product managers, where she negotiates timeline adjustments to accommodate necessary security patches. She spends her evenings either debugging a persistent race condition in a side project or hiking the nearby trails to decompress. Dinner is usually a simple meal prepared from her garden harvest, followed by a few hours of puzzle solving or reading technical whitepapers before bed.

Lifestyle

Bernadette lives in a quiet, tree-lined neighborhood in Ballard, where her home serves as both a sanctuary and a workspace. Her days are punctuated by the rhythmic care of her extensive vegetable garden, a passion project requiring the same precision she applies to code. She maintains a rigorous fitness routine, favoring long-distance hiking trails like the Pacific Crest Trail sections near Snoqualmie Pass over gym memberships. Financially, she is conservative yet secure, prioritizing retirement contributions and emergency funds over luxury spending. Her social circle is small but deeply trusted, consisting mostly of fellow engineers and neighbors who share her appreciation for low-key, intellectually stimulating conversation rather than loud networking events.

Work life

As the de facto security gatekeeper for a lean product team, Bernadette operates without a dedicated security department, forcing her to build robust infrastructure from scratch. Her day is a constant balancing act between shipping features and hardening the pipeline. She spends hours debugging GitHub Actions workflows, manually verifying that free scanning tools aren't generating false positives that waste developer time. The absence of a formal budget means every tool must prove its worth through raw utility. She frequently collaborates with developers who find her scrutiny frustrating, requiring her to explain complex risk vectors in plain English. Her office is cluttered with printed architectural diagrams and a physical spreadsheet that tracks security exceptions, a system she refuses to abandon despite its manual nature.

Relationships

Bernadette's primary support system is her husband, Mark, a civil engineer who shares her love for structured problem-solving and outdoor weekends. They rely on each other for emotional grounding during high-stress release cycles. Her closest friends are a mix of former colleagues from previous roles and neighbors from the local community garden, where trust is built over seasons of shared labor rather than digital connections. She rarely seeks advice from peers outside her immediate circle, preferring to validate her own conclusions against documented evidence before acting.

How they decide

Bernadette is an ultra-cautious, evidence-based decision-maker who relies heavily on historical data and reproducible results. She avoids impulsive choices, preferring to run small-scale pilots or simulate outcomes before committing resources. Her process is linear: define the problem, gather empirical data, test hypotheses, and only then implement a solution. She is largely immune to social proof or marketing narratives; if a claim cannot be verified through code or documentation, she dismisses it immediately.

How they sound

Her speech is measured, precise, and devoid of filler words. She uses technical jargon accurately but explains it clearly when addressing non-engineers. She rarely raises her voice, even when discussing critical security breaches, preferring a calm, factual tone that commands respect through certainty. She avoids absolutes like 'always' or 'never' unless backed by data, and she frequently pauses to formulate her next sentence. Her cadence is steady, reflecting her high conscientiousness, and she tends to correct others gently but firmly if their logic contains a flaw.