Charlie Kulas

Why this persona fits the audience

He manages an open-source compliance and contributor program for a mid-size security company in Manchester; a 3-person internal group reviews licenses, contributor agreements, and occasional grant payouts using spreadsheets and email.

• Age: 37
• Location: Manchester, UK
• Occupation: Open Source Program Manager
• Income: £95k
• Education: MSc Information Security
• Company size: 200-500 employees
• Years in role: 4

“The integrity of our software starts with the integrity of its components; it's about building trust, piece by piece.”

Charlie Kulas has carved out a niche for himself in the critical, often overlooked, domain of open-source program management within the cybersecurity sector. Born and raised in the North West of England, he developed an early aptitude for logical problem-solving, which led him to pursue a Master's degree in Information Security from a reputable UK university. His career began in a more general IT security role, but he soon found himself drawn to the complexities and inherent risks associated with the widespread use of open-source software. Recognizing a gap in structured management for these components, he transitioned into his current role four years ago at a mid-sized security firm based in Manchester. His position is a testament to his meticulous nature and his commitment to robust governance. Charlie leads a lean team of three, tasked with the unenviable job of ensuring the company's products are built on a foundation of legally compliant and ethically sourced open-source code. This involves a rigorous review of software licenses, the drafting and management of contributor agreements, and the occasional disbursement of funds for community projects or bug bounties. His team operates primarily using spreadsheets and email, a system Charlie is acutely aware is reaching its limits as the company grows and the open-source landscape becomes more intricate. He is driven by a deep-seated belief in the importance of auditability and consistency, viewing his work not just as a compliance function, but as a fundamental aspect of the company's security posture and reputation. He sees the current manual processes as a significant bottleneck and a potential point of failure, a challenge he is actively seeking to address. Charlie is not motivated by status or overt displays of success; his satisfaction comes from the quiet assurance that the systems he oversees are sound, secure, and defensible.

Background & daily life

A day in their life

Charlie's day typically begins around 7:00 AM with getting his children ready for school. After dropping them off, he might cycle to the office, arriving by 8:30 AM. His mornings are usually packed with back-to-back meetings: a sync with his team to review pending license requests, a discussion with engineering leads about upcoming project dependencies, and a call with legal counsel. Lunch is often a quick sandwich at his desk while reviewing a batch of contributor agreements. Afternoons involve deeper dives into policy documentation, researching specific license clauses, and responding to urgent queries. He aims to leave by 5:30 PM to collect his children, but late-breaking issues can sometimes extend his day. Evenings are for family, though he might check emails briefly before bed.

Lifestyle

Charlie lives in a comfortable semi-detached house in a suburb of Manchester. His evenings are typically spent with his wife and two young children, helping with homework or watching a bit of TV. He's a keen cyclist, often using his road bike for weekend rides to clear his head, and occasionally cycles to work when the weather permits. He's mindful of his health, aiming for balanced meals, though busy days can lead to quick, less ideal choices. Financially, he's responsible, saving for his children's future and the occasional family holiday, but doesn't chase luxury items.

Work life

Charlie's role is pivotal but often invisible to the wider company. He leads a small, dedicated team of three responsible for navigating the complex world of open-source licensing and contributor agreements. Their current focus is on refining the internal review process for new open-source components integrated into their security products, ensuring strict adherence to license terms and managing contributor relations. He spends a significant portion of his day in meetings, reviewing legal documents, and coordinating with engineering and legal departments, often feeling the pressure to balance speed of development with rigorous compliance.

Relationships

Charlie is married to Sarah, a marketing manager, and they are a solid team managing their household and children. His closest work relationships are with his two team members, a junior compliance analyst and a legal liaison, with whom he collaborates daily. He also interacts regularly with the head of engineering and the company's general counsel, who rely on his team's expertise.

How they decide

Charlie is highly analytical and research-driven. He prefers to gather all available data, consult relevant policies, and assess potential risks before making a decision. He values input from his team and trusted colleagues in legal and engineering but ultimately bases his choices on thorough evaluation and a strong sense of due diligence. He is not impulsive and will often take time to deliberate, especially when significant compliance or security implications are involved.

How they sound

Charlie speaks with a measured, clear cadence, typical of a professional in the UK. His tone is generally calm and factual, avoiding overly casual slang or jargon unless speaking with technical colleagues. He tends to be precise with his language, especially when discussing legal or technical matters, and is careful not to overstate his team's capabilities or make definitive pronouncements without full information. He might use phrases like 'from a compliance perspective,' 'our current understanding is,' or 'we need to ensure.'