Data Cloud Governance Manager
Novartis · East Hanover, NJ · 3 wk ago
Hybrid$80–$100/hrContract
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, accommodation, etc. Must preserve all substantive info.
We need to parse the posting.
First part: "This role is offered through [MSP/supplier/third party provider], who, if selected, will be your employer. If your services are retained, you will be assigned to provide services to Novartis as the end client. This is not an offer of employment with Novartis. If you are selected for this Temporary/External opportunity, you will not be an employee of Novartis and will not be eligible for any Novartis employee benefits or incentives." This is about the role (contract type). Could be part of About the role.
Then: "Novartis touches the lives of a tenth of the world’s population. Every role here, regardless of contract type, makes an impact on human life! Novartis US partners with external managed service provider Magnit Global to offer engaging temporary contractor opportunities like this, to those who are looking for flexibility in their career while looking to gain new skills and experiences providing services to an inclusive global medicines company. Click here to learn more about Magnit www.magnitglobal.com Ready to work with/through Magnit at Novartis? Please read on..." This is also about the role/company.
Then job title line: "Data Cloud Governance Manager". Not to be used as heading.
Then description: "Novartis is on a mission to transform medicine and improve lives worldwide. As a global leader in healthcare, we leverage advanced technology and data to deliver patient-centric solutions, enhance customer engagement, and drive innovation. We collaborate closely with the US business, bringing insights and challenging ideas to empower smarter, data-driven decision-making. The US CRM organization sits within Strategy, Platforms & Transformation (SPT) – AI & Platform Products and plays a crucial role in driving the transformation to a next-generation Customer360 operating model. Novartis seeks an accomplished product leader with a track record of turning business demand from multiple commercial functions into a well-managed data product backlog. Strong prioritization judgment, stakeholder partnership, and hands-on data fluency are essential to success in this role. Reporting to Director, PO Audience Activation & Marketing Intelligence, Data Cloud Governance Lead owns the enterprise governance framework for shared Data Cloud capabilities, ensuring that access, data protection, security, privacy, tagging, masking, and cross-boundary data sharing are designed and operated consistently. The role translates enterprise policies and regulatory expectations into actionable platform guardrails, partners with the IT Center of Excellence and architecture teams, and enables responsible delivery across Data Spaces without creating unnecessary friction."
That's responsibilities.
Then "Major Accountabilities" list bullet points.
Then "Key Performance Indicators / What Good Looks Like" list.
Then "Requirements" list bullet points.
Then "Preferred" bullet points.
Then "Leadership Competencies" bullet points.
Then location, hybrid schedule, pay rate, contract length, benefits.
We need to map to sections: About the role (intro), Responsibilities (major accountabilities + maybe earlier description), Requirements (Bachelor's degree etc), Qualifications (maybe Preferred?), Skills (maybe Leadership Competencies?), Benefits (health, dental, vision, 401k), Pay (pay rate), Schedule (location hybrid). Also maybe include "Qualifications" separate from Requirements? The instruction says use headings for sections e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have Requirements (Bachelor's degree etc). Preferred (hands-on familiarity etc). Could treat Preferred as Qualifications? Or Skills? Usually Qualifications are the required and preferred. But we have separate headings: Requirements and Qualifications. Could put required under Requirements, preferred under Qualifications. Skills could be Leadership Competencies? Or maybe combine leadership competencies under Skills. Or we could put leadership competencies under Skills.
We need to avoid filler sections. Ensure each heading has substantive content.
Let's extract content.
About the role: combine the introductory paragraphs about Novartis, Magnit, contract nature, mission, etc. Should be prose.
Responsibilities: include the paragraph describing role, plus the Major Accountabilities bullet list, plus maybe KPI list? KPI could be under Responsibilities or separate? Could be under Responsibilities as well. But we have a separate heading for KPI? Not in list. So we can include KPI under Responsibilities as a sub-list? But we must use
- for any list of duties/requirements/benefits. So we can include KPI as a list under Responsibilities.
Requirements: Bachelor's degree etc list.
Qualifications: Preferred list.
Skills: Leadership Competencies list.
Benefits: Health, dental, vision, 401k (provided minimum eligibility hours are met). Also maybe mention contract length? Not benefit. Could include contract length under Benefits? Probably not. We'll just list those.
Pay: Pay Rate: $80/hour - $100/hour W-2 Only (based on Education/Experience)
Schedule: Location: East Hanover, NJ Hybrid (3 days (Mon-Thurs), 2 remote). Also Contract: 12-month maybe under Schedule? Could be separate but we don't have a heading for contract length. Could include under Schedule as additional info.
We must not include boilerplate like EEO, accommodation, etc.
Now produce HTML fragment.
Structure:
About the role
... prose ...
Responsibilities
... prose description ...
- ... major accountabilities ... ...
- under same section? Could combine but better separate? The instruction: Use
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll include Major Accountabilities as list, then KPI list as another list.
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
Schedule
...
Make sure not to add empty sections. Now craft prose. About the role prose: combine: "This role is offered through a third‑party provider (MSP/supplier), who, if selected, will be your employer. If your services are retained, you will be assigned to provide services to Novartis as the end client. This is not an offer of employment with Novartis; selected candidates will not be Novartis employees and will not be eligible for Novartis employee benefits or incentives. Novartis touches the lives of a tenth of the world’s population, and every role—regardless of contract type—impacts human life. Novartis US partners with external managed service provider Magnit Global to offer engaging temporary contractor opportunities for those seeking flexibility while gaining new skills and experiences supporting an inclusive global medicines company." We can also mention mission: "Novartis is on a mission to transform medicine and improve lives worldwide..." but that could be responsibilities. We'll keep it in About the role maybe. But we already have responsibilities paragraph that includes mission. Let's split: About the role: contract nature, company context, Magnit partnership. Responsibilities: mission, role description, major accountabilities, KPI. Ok. Now Responsibilities prose: "Novartis is on a mission to transform medicine and improve lives worldwide. As a global leader in healthcare, we leverage advanced technology and data to deliver patient‑centric solutions, enhance customer engagement, and drive innovation. We collaborate closely with the US business, bringing insights and challenging ideas to empower smarter, data‑driven decision‑making. The US CRM organization sits within Strategy, Platforms & Transformation (SPT) – AI & Platform Products and plays a crucial role in driving the transformation to a next‑generation Customer360 operating model. Novartis seeks an accomplished product leader with a track record of turning business demand from multiple commercial functions into a well‑managed data product backlog. Strong prioritization judgment, stakeholder partnership, and hands‑on data fluency are essential to success in this role. Reporting to the Director, PO Audience Activation & Marketing Intelligence, the Data Cloud Governance Lead owns the enterprise governance framework for shared Data Cloud capabilities, ensuring that access, data protection, security, privacy, tagging, masking, and cross‑boundary data sharing are designed and operated consistently. The role translates enterprise policies and regulatory expectations into actionable platform guardrails, partners with the IT Center of Excellence and architecture teams, and enables responsible delivery across Data Spaces without creating unnecessary friction." Now Major Accountabilities list items: - Own and evolve central attribute‑based access control policies, tagging standards, dynamic masking rules, encryption expectations, and cross‑space data‑sharing guardrails. - Receive and qualify requests for new access policies, tags, privacy controls, compliance rules, and exceptions; document scope, rationale, risk, and decision requirements. - Evaluate proposed Data Streams, Data Lake Objects, integrations, and use cases for privacy, security, data protection, and regulated‑data considerations, including PHI and PII where applicable. - Convert governance needs into clear epics, features, policy updates, acceptance criteria, and implementation plans for platform and engineering teams. - Prioritize enterprise governance work based on risk, strategic value, dependencies, and platform capacity; maintain a transparent governance backlog and decision log. - Validate compliance and complete security reviews for new Data Streams, shared Data Lake Objects, and related enterprise capabilities before committed delivery. - Partner with IT, architecture, privacy, legal, security, and engineering teams to design practical controls and verify that controls are implemented as intended. - Establish evidence‑based reviews of platform configurations, access, encryption, masking, tagging, and cross‑boundary sharing; drive remediation of identified gaps. - Publish reusable standards, decision criteria, templates, and guidance that allow Data Space teams to design compliant solutions earlier in the lifecycle. - Explain policy intent, trade‑offs, approvals, conditions, and exceptions clearly to business and technical stakeholders. Now KPI list items: - Governance controls are implemented, testable, and operating as designed. - Security, privacy, and compliance reviews support planning and release decisions without avoidable delays. - Shared Data Cloud capabilities are covered by current access, tagging, masking, encryption, and sharing standards. - Findings, exceptions, and remediation actions are documented, owned, and closed transparently. - Governance decisions are consistent, risk‑based, traceable, and clearly communicated. - Data Space and delivery teams use governance guidance early and report clear, actionable support. Now Requirements list: - Bachelor's degree in data, technology, business, engineering, computer science, or a related field required; advanced degree preferred. - Fluent English; other languages are desirable. - 5+ years of experience in data governance, privacy, security, risk, compliance, product management, or platform governance roles. - Strong understanding of enterprise data controls, including access management, classification and tagging, masking, encryption, consent, retention, and controlled data sharing. - Experience translating policy and regulatory requirements into platform standards, technical requirements, and delivery acceptance criteria. - Demonstrated success working across business, IT, architecture, security, privacy, legal, data engineering, and product teams in a matrixed environment. - Strong written and verbal communication skills, with the ability to explain complex control requirements to both technical and business audiences. Now Qualifications (Preferred) list: - Hands‑on familiarity with Salesforce Data Cloud governance capabilities, data models, Data Streams, Data Lake Objects, and platform access patterns. - Experience in pharma, life sciences, healthcare, or another regulated and data‑intensive industry. - Knowledge of agile product delivery, risk‑