Software buyers: target customers (?)

Marty Mitchell

Marty Mitchell, 38, has always been drawn to the intricate logic of systems. Growing up in a household where his parents, both electrical engineers, valued problem-solving, he naturally gravitated towards computer science. After earning his B.S. from a state university, he spent several years at a mid-sized tech company, honing his skills in backend development and eventually leading small teams. The desire to build something from the ground up, with more autonomy and direct impact, led him to co-found his current SaaS venture four years ago in Austin. His role as CTO is a natural fit for his methodical and ownership-driven personality. He's deeply invested in the company's success, viewing its technical foundation as his personal responsibility. He lives in a modest but comfortable home with his wife and daughter, a space that also houses his extensive home lab setup – a testament to his hands-on approach and fascination with how things work. Financially, he's pragmatic, balancing his comfortable income with saving for the future and investing in tangible assets rather than flashy trends. His current focus is on refining their development and deployment processes, particularly the security checks, which feel increasingly cumbersome and leave him with a nagging sense of incomplete assurance. He recently spent a weekend wrestling with a complex CI pipeline optimization, a typical example of how he dedicates personal time to solve work-related challenges that pique his technical curiosity and align with his values of reliability and efficiency. He sees time as a finite resource to be optimized, not squandered, and values solutions that contribute to that optimization, both at work and in his personal life.

Violet Ryan

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.

Lennox Balnuweit

Lennox Balnuweit earned his Master’s in Computer Science from TU Berlin, specializing in systems security. After stints at a large automotive firm and a fintech startup, he joined a Berlin B2B SaaS company as its first dedicated DevSecOps lead three years ago. The role appealed to his process-driven nature—the team’s ad-hoc security practices needed structure, and his background in automating workflows made him a natural fit. Initially, he tried implementing commercial security tools, but budget constraints and the team’s resistance to change pushed him toward a hybrid approach: open-source scanners for testing, spreadsheets for tracking, and manual review for critical findings. His meticulous documentation (e.g., a 45-page Confluence guide on 'How to Reproduce a Broken Access Control') has earned him a reputation for thoroughness, though some devs grumble about the '[his name] tax' on their velocity. Recently, he’s been advocating for a shift-left approach, embedding security checks earlier in the pipeline. His biggest frustration is the team’s tendency to treat security as a 'check-the-box' exercise rather than a continuous practice. He’s currently designing a proof-of-concept for a framework-agnostic test suite that would auto-generate regression tests from findings. Outside work, Lennox is a privacy advocate who tests new encryption tools obsessively. He’s also a cyclist who logs 80 km weekly, though he admits his posture could use work. His partner, a UX researcher, teases him for 'turning everything into a workflow audit,' including their weekly grocery list. Lennox’s ideal future involves full pipeline automation, a stable team, and less time manually reproducing edge cases in staging. He’s skeptical of companies that oversell security products but respects tools that demonstrate measurable impact. His current focus is proving that guardrail testing isn’t just about catching bugs—it’s about building a culture where security is part of every iteration.

Charumati Butt

Charumati Butt, a 29-year-old Senior Backend Engineer based in Bengaluru, embodies a blend of technical rigor and pragmatic problem-solving. Holding a B.Tech in Information Technology, she has steadily climbed the ranks, currently serving as the main API owner for critical functionalities—authentication, rate limits, and file uploads—within her six-person product team at a mid-sized tech firm. Her approach to ensuring code quality and security is deeply ingrained in her conscientious nature (0.84). She meticulously manages these vital API paths using a combination of free Static Application Security Testing (SAST) tools for initial scans, comprehensive Postman collections for functional and security testing, and a shared Google Sheet that acts as her central hub for tracking the manual verification status of various code branches. This system, while functional, highlights her resourcefulness in leveraging available tools to meet demanding quality standards under pressure. Her income places her comfortably within the professional bracket, allowing for a degree of financial planning, though she remains mindful of budget constraints when evaluating solutions. Charumati's values of ownership and quality drive her to meticulously oversee the APIs under her purview, ensuring they are not only performant but also secure. She actively seeks opportunities for learning, attending tech meetups when possible and dedicating personal time to reading tech blogs and listening to podcasts during her commute. Her recent focus has been on streamlining the manual verification process, recognizing it as a bottleneck that impacts deployment speed. She's been researching potential automation strategies, though budget limitations for advanced tooling remain a significant consideration. Charumati's life is characterized by a disciplined routine, balancing her demanding career with family responsibilities and personal interests like cooking and mobile photography. She views her role not just as writing code, but as building robust, trustworthy systems, a perspective shaped by her analytical mind and a deep-seated desire to deliver excellence.

Moïse Rousseau

Born and raised in Lyon, Moïse Rousseau developed an early fascination with how complex systems work, which led him to pursue a Master's degree in Computer Science at a reputable Parisian university. After graduation, he spent several years as a software engineer at a large e-commerce firm, honing his skills in backend development and learning the importance of scalable, reliable systems. He then transitioned into a team lead role, discovering a knack for mentoring and process improvement. Five years ago, he joined his current healthtech startup, initially as a senior engineer, and was promoted to Engineering Manager within two years. His current role is demanding, managing a team of ten engineers split between Ruby on Rails and TypeScript, working on a platform that impacts patient care. He feels a strong sense of responsibility to ensure the security and integrity of the data handled by their application. Moïse’s meticulous nature, reflected in his hobby of French cooking where precision is key, translates directly into his professional life. He meticulously plans his sprints and personal time, driven by a strong sense of accountability. Despite the team having a commercial security platform, Moïse remains unconvinced it covers all bases, leading him to personally consolidate issues in Linear and mandate extra developer checks on sensitive code, a process that causes some friction but which he views as essential. He values patient impact above all, believing that robust engineering directly contributes to better health outcomes. He is financially pragmatic, focused on long-term security for his family through diligent saving rather than speculative investments, and sees his income as a means to support his family and fund his personal interests like cycling and exploring new technologies.

Bernadette Wuckert

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.

Daryl Bahringer

Daryl Bahringer’s journey into full-stack development began not with a grand ambition, but with a pragmatic need for a stable career after his IT degree. He gravitated towards the web early on, fascinated by its boundless potential and the tangible results of coding. After a few years cutting his teeth at a small agency in Leeds, he saw an opportunity in Manchester's burgeoning tech scene. Around ten years ago, he and a fellow developer, Liam, pooled their savings and launched their two-person consultancy. Daryl quickly became the de facto security lead, driven by the realization that many small businesses were unknowingly exposing themselves to significant risks. His approach is built on diligence and a deep-seated aversion to cutting corners, especially when client data is involved. He champions adaptable, open-source solutions and meticulously crafts his own processes, like his comprehensive Notion security checklist, to manage the diverse and often budget-constrained needs of his clientele. He views his role as a guardian, albeit one operating on lean resources and considerable personal effort. The constant need to balance client budgets with security imperatives has made him exceptionally resourceful, often finding creative workarounds rather than defaulting to expensive commercial tools. He recently turned down a potential client who insisted on a proprietary, high-cost security suite, preferring to stick with his proven, albeit more labor-intensive, methods that he knew he could deliver within their means. This decision, while financially prudent in the short term, reflects his commitment to client trust and his own practical, hands-on methodology.

Deepali Ahuja

Deepali Ahuja, 33, is a dedicated Application Security Engineer based in Hyderabad, India, where she plays a critical role within an eight-person fintech product squad. Her journey into cybersecurity began during her M.Tech in Cybersecurity, where she discovered a fascination for the intricate logic of systems and the art of uncovering vulnerabilities. This academic foundation was quickly built upon with practical experience, leading her to her current position where she is the primary owner of the vulnerability triage process. Her compensation places her firmly in the professional tier, reflecting her expertise and the high stakes of the fintech industry. Deepali's current workflow is a testament to her conscientious nature and commitment to thoroughness. She navigates a complex landscape using a paid application security subscription for automated scanning, detailed notes meticulously compiled from Burp Suite sessions, and a comprehensive, albeit manual, spreadsheet that tracks remediation efforts across three distinct microservices and two mobile backends. This system, while functional, represents a significant personal investment of time and attention to detail. She recently made a conscious decision to dedicate an extra two hours each week to manually verifying the effectiveness of critical remediations, a step she felt was necessary given the sensitive nature of the financial data her company handles. This initiative stems from her core values of accuracy and responsibility, ensuring that every fix truly strengthens the product's security posture. Outside of her demanding professional life, Deepali finds balance through her interests in reverse engineering, which sharpens her analytical skills, and a surprising penchant for true crime podcasts, which she listens to during her commute. She is also an avid badminton player, using the sport to maintain physical health and mental clarity. Her approach to life is characterized by a desire for order and a deep-seated sense of duty, making her a reliable and highly valued member of her team.

Mathijs van Veen

Mathijs van Veen grew up in a small town just outside of Utrecht, developing an early fascination with how things work, which naturally led him to computers. He pursued a Bachelor's degree in Computer Science at the University of Amsterdam, where he excelled in theoretical subjects and practical programming. Upon graduation, he joined a promising e-commerce startup as a junior developer, quickly demonstrating a knack for identifying subtle bugs and a meticulous approach to coding. His aptitude for detail and responsibility saw him promoted to Senior Software Engineer within three years. He's now a key member of a lean engineering team at an Amsterdam-based marketplace startup, where he's been instrumental in building out their technical infrastructure. Mathijs is highly conscientious, approaching his work with a deep sense of ownership, particularly over the security of the payment and login systems. This responsibility weighs on him, especially given the company's limited budget for specialized security tools. He's had to become incredibly resourceful, leveraging open-source scanners, implementing rigorous pull-request checklists, and dedicating significant time to manual reproduction of potential vulnerabilities in staging environments. This approach, while effective, often strains his time and requires him to forgo some of the leisure activities he enjoys, like longer cycling trips or spontaneous urban explorations. He values efficiency and clean code, believing that well-structured software is inherently more secure and maintainable. Independence is also a core value; he prefers to solve problems himself rather than wait for external solutions. His income allows for a comfortable life, but he remains pragmatic and avoids unnecessary spending, prioritizing savings for future travel and financial security. He views his role not just as writing code, but as actively defending the platform and its users against threats.

Isabel Bashirian

Isabel Bashirian is a seasoned engineering leader whose career spans nearly two decades, evolving from a backend developer to a Director overseeing critical ecommerce infrastructure in Chicago. Holding both a B.S. in Computer Science and an MBA, she bridges the gap between technical execution and strategic business goals with remarkable fluency. Her tenure at her current company began six years ago, coinciding with a period of aggressive scaling that forced her to build security practices from the ground up. Unlike many peers who rely solely on external audits, Isabel championed an internal culture where security is a product feature, not a gatekeeper. Currently, she navigates a complex landscape where the team utilizes free dependency scanners in CI but lacks a unified system to track the resulting findings. This has resulted in a hybrid workflow: two senior developers rotate as security stewards, manually validating fixes and documenting proofs in a combination of Jira tickets and a fragile, locally maintained spreadsheet. While this approach has kept the team compliant so far, the overhead is mounting, and the reliance on manual proof steps for checkout-critical code introduces a non-trivial risk of human error. Isabel is acutely aware of the limitations of this 'good enough' state, constantly weighing the cost of implementing a more robust solution against the immediate pressure of delivery deadlines. Her personal life reflects her professional discipline; she is a marathon runner who treats training with the same rigor as a software release cycle. She is deeply protective of her team's well-being, often stepping in to shield them from executive pressure, yet she remains uncompromising on standards that affect customer trust. Isabel is not looking for a magic bullet; she seeks a sustainable, verifiable method to codify security behavior into the development lifecycle itself, ensuring that every fix is backed by a test that proves the vulnerability is gone, forever.