Norman Johns

Why this persona fits the audience

Works on a 7-person product team in Seattle building a B2B app with an AI support agent and a containerized API stack. He relies on GitHub alerts, manual review, and a few free scanners, and he documents edge cases in a shared notes file rather than a formal security program.

• Age: 34
• Location: Seattle, Washington, US
• Occupation: Senior Backend Engineer
• Income: $175,000/year
• Education: B.S. in Computer Engineering
• Company size: 7 employees
• Years in role: 6

“If you can't explain why this line of code needs to exist in five years, don't write it today.”

Norman Johns is a 34-year-old Senior Backend Engineer based in Seattle, Washington, who has spent the last decade navigating the shifting tides of software development. Holding a B.S. in Computer Engineering from a state university, he entered the industry during the rise of cloud-native architectures and has since specialized in building resilient, scalable backends. Currently, he serves as the technical backbone for a lean, seven-person B2B startup in Fremont, where he is instrumental in developing a proprietary AI support agent and managing a containerized API stack. Unlike many of his peers, Norman eschews the allure of heavy, enterprise-grade security platforms, viewing them as bureaucratic obstacles that stifle velocity. Instead, he has curated a bespoke, low-overhead security posture relying on GitHub Actions alerts, manual code reviews, and a handful of free, open-source scanners. His approach is deeply personal and pragmatic; he maintains a shared, unstructured notes file that tracks every known edge case and potential vulnerability, a practice born from frustration with formal programs that felt disconnected from daily reality. Financially stable with an annual income of $175,000, Norman prioritizes financial independence over conspicuous consumption. He owns a modest condo in a neighborhood known for its tech-savvy residents, choosing a life that allows him to focus on his craft rather than his status. His personality profile reveals a high degree of conscientiousness coupled with moderate openness, making him a reliable but cautious innovator. He is skeptical of rapid technological shifts that lack proven stability, particularly in the realm of AI security, where the landscape changes daily. This skepticism drives his independent judgment; he trusts his own analysis of code and dependencies more than third-party dashboards. While he enjoys the camaraderie of his small team, he often feels the weight of being the sole guardian of the system's integrity, a burden he accepts with a quiet sense of duty. His recent decisions reflect a desire to streamline his workflow further, seeking solutions that integrate seamlessly into his existing mental model rather than forcing him to adapt to a new paradigm. For Norman, true security isn't about buying a platform; it's about understanding the system so thoroughly that the system cannot surprise you.

Background & daily life

A day in their life

Norman wakes up at 6:00 AM, brewing pour-over coffee while reviewing overnight build logs on his second monitor. By 7:30 AM, he is cycling to work, listening to a podcast on distributed systems. At the office, his first hour is dedicated to clearing GitHub notifications, manually inspecting pull requests for dependency updates, and updating his local `edge_cases.md`. The morning stand-up is brief; he focuses on unblocking the junior engineer working on the AI agent's context window. Lunch is a quick sandwich eaten at his desk while reading a paper on LLM prompt injection vectors. Afternoon hours involve refactoring the container orchestration scripts and debugging a race condition in the payment service. He leaves by 5:30 PM, avoiding late-night crunches unless absolutely necessary, spending his evening on his side project or tending to his mechanical keyboard switches. He ends the day by planning tomorrow's tasks to ensure no critical security review is skipped.

Lifestyle

Norman lives alone in a renovated craftsman-style condo in Seattle's Fremont neighborhood, a choice that balances commute proximity with quietude. His mornings are ritualistic: black coffee, a 20-minute spin bike session, and checking the news before opening his laptop. He avoids the chaos of the downtown tech scene, preferring the local breweries where he meets one or two close friends weekly for low-key drinks. Financially, he is disciplined, maxing out retirement contributions early and investing in index funds rather than chasing crypto trends. He treats his car as a utility, not a status symbol, and his hobbies revolve around maintaining his mechanical keyboard collection and organizing his home office for maximum ergonomic efficiency. Socially, he is selective, valuing depth over breadth in relationships.

Work life

At his small startup, Norman is the de facto infrastructure lead despite having no direct reports. The team of seven moves fast, deploying multiple times a day, which forces him to balance speed with safety. His day is split between architecting the AI support agent's reasoning pipeline and manually auditing dependency trees for known vulnerabilities. He rejects the idea of a dedicated security officer, believing it creates bottlenecks. Instead, he maintains a sprawling, unstructured `SECURITY_EDGE_CASES.md` file in the repo root, cross-referencing GitHub Actions logs and running lightweight, open-source scanning tools locally before merges. He spends significant time explaining technical debt to non-technical founders, often feeling the friction of their desire for 'shiny new features' versus his need for robust, boring reliability.

Relationships

Norman is estranged from his immediate family, living primarily in the Pacific Northwest, though he visits his parents in Ohio once a year. His closest bond is with Sarah, a frontend developer he met at a previous job; they share a deep professional respect and occasionally discuss architectural patterns over dinner. He has a small circle of three friends from college who still meet monthly for board games. He rarely engages in broader community networking events, preferring to contribute anonymously to open-source projects or answer questions on Stack Overflow when he finds a unique solution to a problem.

How they decide

Norman operates on a 'measure twice, cut once' philosophy. He is highly research-heavy, preferring to read documentation, source code, and technical whitepapers before adopting any new workflow. He is skeptical of marketing claims and peer pressure, often waiting to see if a tool survives a six-month trial period before fully committing. Decisions are made independently after gathering data from trusted technical peers, but he values consensus only when it aligns with logical necessity. He avoids impulsive choices and will often delay a decision until he has personally validated the efficacy of a proposed solution through a small-scale pilot.

How they sound

His speech is clipped, precise, and devoid of filler words. He speaks in complete sentences, often using analogies related to plumbing or traffic flow to explain abstract concepts. He avoids corporate jargon like 'synergy' or 'disruption,' preferring terms like 'latency,' 'bottleneck,' and 'throughput.' When frustrated, his tone drops an octave, becoming flat and factual rather than emotional. He rarely raises his voice, even in disagreement, instead pausing to ask clarifying questions that expose logical gaps in others' arguments. He tends to speak in the present tense regarding technical realities, treating them as immutable laws rather than suggestions.