The company's Governance, Risk, and Compliance team sits within Security. It links obligations and customer commitments to working controls and reliable evidence, and it works with other teams to make security practical and understandable.
This is a Technical Product Manager role focused on the vision and the systems behind GRC and Security. You will find out what users need, decide what gets built and in what order, and hands-on build the data models, integrations, and workflows yourself. You will also take each product through testing, adoption, and ongoing operation.
Much of the work is about data: knowing what exists, how it changes, which information can be relied on, and what action should follow. You will combine product design with solution architecture so security controls become part of daily work and generate trustworthy evidence as they run. That evidence needs to serve internal excellence, audits, customers, and regulators, and help each audience find and understand the security information that concerns them.
You need to move comfortably between implementation detail and high-stakes decisions. One part of your day may be spent debugging a data flow, and another explaining architecture, evidence, and tradeoffs to leadership or outside parties. You start as a hands-on individual contributor who sets direction and helps colleagues build well.
Responsibilities
Set the product vision and technical direction for an agreed set of GRC systems, including user research, deciding what to build, and choosing the release order.
Design and build scalable data models, integrations, and workflows that link requirements, systems, people, controls, actions, and evidence.
Set up practices for data quality, ownership, history, and freshness so that changes and missing data lead to accurate, useful results.
Turn approved security requirements into workable processes, automate suitable checks and actions, and confirm with the owning teams that controls run as designed.
Build clear employee experiences that cut down duplicate requests and make the secure option the easy one.
Build evidence features for auditors, regulators, and customers, including readable views and structured outputs with suitable access, scope, and disclosure limits.
Own work through testing, release, adoption, monitoring, and upkeep, and improve the system when scale or new requirements reveal gaps.
Explain architecture, security outcomes, evidence, and tradeoffs to engineers and to senior or external audiences, and create reusable patterns so others can deliver on their own.
Requirements
You have personally designed, built, and scaled products or operational systems, and can walk through the decisions, failures, and results you were responsible for.
You can still build and troubleshoot data models, queries, integrations, or workflows, even if your current job is not in software engineering.
You understand how data identity, relationships, quality, history, and access affect whether a system and its outputs are correct.
You can take an unclear need and turn it into a product direction, buildable requirements, a practical first release, and evidence that people are getting value.
You understand security controls and assurance well enough to link a requirement to its implementation and operating evidence, and to state a claim at the right scope. You bring in domain experts where your knowledge runs out.
You explain complex systems and risk clearly to engineers, executives, and external audiences without losing the facts or limitations.
You take ownership of your work through operation, learn from feedback, and help others take ownership of and extend what you build.
Engineering, data architecture, technical product ownership, internal systems, and security or compliance engineering are all relevant backgrounds. Prior engineering experience is valued but not required. A current engineering title, a specific degree, a certification, management history, or experience with the company's tools is not required.
Conditions
Equal opportunity employer. Hiring does not discriminate on the basis of race, religion, color, national origin, sex, sexual orientation, age, veteran status, disability, genetic information, or other legally protected characteristics.
Background checks follow applicable law. For US-based candidates, applicants with arrest or conviction records are considered in line with the San Francisco Fair Chance Ordinance, the Los Angeles County Fair Chance Ordinance for Employers, and the California Fair Chance Act. For unincorporated Los Angeles County roles, a conditional offer may be withdrawn if criminal history is found to have a direct, adverse, and negative relationship with the duties to protect entrusted hardware from theft, loss, or damage, to return all hardware and its data at termination or end of assignment, and to keep non-public information confidential; the role also requires access to secure, protected IT systems and related data security obligations.
Candidates who believe this posting does not comply can file a report through the company's form. Inquiries unrelated to posting compliance receive no reply.
Reasonable accommodations are available to applicants with disabilities on request.