Manager, Professional Services
Collibra · Washington, DC · 1 mo ago
RemoteRemoteProject Management$128k–$160k/yrFull-time
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. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
First paragraph: "Joining Collibra’s Professional Services Team At Collibra Public Sector, our Professional Services team relies on Federal Solution Architects to deliver on customer expectations for the services we sell, working directly with customer key projects stakeholders throughout the entire customer journey. Ensuring growth, adoption and renewal, Federal Solution Architects act as customer champions, ensuring customers are onboarded and realizing value rapidly."
That's about the role.
Next: "Managers, Professional Services at Collibra are responsible for Supporting federal customer engagements by delivering mission-aligned architectural design and execution of Collibra products that adhere to Collibra Public Sector’s Delivery Models, Engagement Processes, Methodologies, and Artifacts, while ensuring compliance with applicable government regulations and security standards (e.g., FedRAMP, FISMA, GovCloud)."
That's responsibilities.
Then bullet-like list: "Providing federal agencies with tailored data governance strategies that incorporate best practices, enable knowledge transfer, and drive measurable business and mission outcomes.Partnering cross-functionally with Collibra Sales, Customer Engineering, Product, Support, and Executive teams to ensure alignment with federal acquisition cycles and stakeholder priorities.Identifying opportunities to expand Collibra’s footprint within agencies by aligning product capabilities to evolving agency mandates, modernization efforts, and compliance requirements.Meeting or exceeding utilization goals in support of federal client success, long-term program engagement, and repeatable delivery excellence.Contributing to the growth of Collibra’s public sector services and licensing business through account expansion, strategic planning, and customer advocacy."
These are responsibilities.
Then "You have5-10 years of consulting experience supporting U.S. federal agencies with knowledge in the areas of Data Governance, Data Management or Data Quality.An understanding of the leading PaaS providers, Data Lakes, Databases, and Integration platforms commonly adopted by federal agencies.A minimum of 2 years of experience working with cloud platforms, network-based API integration (REST/JSON), and deployment automation.Linux CLI proficiency.Hands-on experience with AWS/Azure, Kubernetes, infrastructure and platform.Experience with big data technologies such as Spark, and Hadoop.Familiarity in enterprise security solutions such as LDAP or Kerberos.Hands-on experience with Data Quality, Data Pipelines, Data Orchestration, and/or Job Control tools.Knowledgeable of at least least two or three of the following: data management processes, including data governance, data stewardship, master data management, data cataloging, and business rules managementProficiency in leveraging APIs via Java, Python, or similar scripting language for custom software implementations in Enterprise Linux or Unix environments. Experience with data warehousing, ETL, data integration.Skilled in developing functional and technical specifications.Experienced with Collibra or comparable technologies.Because this role supports the U.S. government business, it is required that this candidate be a U.S. citizen who resides on U.S. soil and holds active security clearance (Secret/TS/TS-SCI)."
These are requirements/qualifications/skills.
Then "You arePreferably located in the Washington, D.C. metro area to support in-person federal customer engagements, with an on-site requirement of up to 50%.An effective communicator across business and technical stakeholders and able to tailor to different audiences.Always customer-focused and personally hold yourself accountable for the customer’s success.Masterful at troubleshooting, navigating, and facilitating resolution of challenging client connectivity and technical software issues. Self-starting and interested in learning new software skills to support intricacies of Collibra’s application stack. Able to work with business and IT owners to identify and align on solutions to data challenges, advocating for the importance of preserving data governance and quality.Able to lead blueprinting, design workshops, and requirements gathering activities."
These are skills/qualities.
Then "Measures of successWithin the first 30 days of employment, be able toClearly understand the roles and responsibilities of the reporting employees and the account assignments.Present the services offering, understanding the different deliverables and the value provided.Present the Customer Journey framework, understanding the different phases and roles and responsibilities within each phase.Clearily understand the roles and responsibilities of all delivery personnel including an Engagement Manager, Solution Architect, Account Program Manager, Premium Support Engineer, Sales Engineer and Account Executive.Within the first 60 days of employmentNavigate Salesforce including opportunities, utilization, projects, and quotes.Identify customers and services engagements at Risk and build a plan to remediate.Identify process gaps and inefficiencies within the services organization.Present the services offering to a customer.Within the first 90 days of employment be able toAdvise Sales on proposed services engagements.Build Salesforce reports for visibility into Services engagements including utilization.Build playbooks to address process gaps and inefficiencies within the services organization.Execute remediation plan for customers at risk collaborating with the sales, support, and technical teams.Understand and convey to customers how Collibra's suite product capabilities and the projects being delivered provide value to customers."
These could be responsibilities or performance expectations; maybe we can put under Responsibilities or a separate "Performance Expectations" but not in allowed headings. Could fit under Responsibilities.
Then "Compensation for this roleThe standard base salary range for this position is $128,000 - 160,000 per year. This position is eligible for additional commission-based compensation. Salary offers are based on a combination of factors, including, but not limited to, experience, skills, and location.In addition to base salary, we offer a competitive total rewards package, including bonus potential, equity for eligible roles, a Flex Fund monthly stipend, pension/401k plans, and more."
That's Pay and Benefits.
Then "Benefits at CollibraCollibra recognizes and values that everyone has different needs, interests, and life goals. We built our benefits program with flexibility in mind to support you and your loved ones through a diverse range of circumstances and life events. These flexible offerings sit on a foundation of competitive compensation, health coverage, and time off. Learn more about Collibra’s benefits."
That's Benefits.
Then inclusion/diversity/EEO boilerplate: we must remove.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Pay: base salary range $128k-160k plus commission.
Benefits: description.
Schedule: on-site requirement up to 50% (i.e., hybrid). Also mention preferably located in Washington DC metro area. That's schedule/location.
We need to avoid filler like "commensurate with experience". Not present.
We need to use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title. Not include Job ID.
We must preserve all substantive info; do not invent or summarize away detail.
We need to decide what goes where.
About the role: first paragraph maybe plus the sentence about Managers? Actually "Managers, Professional Services at Collibra are responsible for..." is more responsibilities. So About the role could be the introductory paragraph: "Joining Collibra’s Professional Services Team At Collibra Public Sector, our Professional Services team relies on Federal Solution Architects to deliver on customer expectations for the services we sell, working directly with customer key projects stakeholders throughout the entire customer journey. Ensuring growth, adoption and renewal, Federal Solution Architects act as customer champions, ensuring customers are onboarded and realizing value rapidly."
That's about the role.
Responsibilities: list of duties: Supporting federal customer engagements..., Providing federal agencies..., Partnering cross-functionally..., Identifying opportunities..., Meeting or exceeding utilization goals..., Contributing to growth..., Measures of success (30/60/90 days) maybe also responsibilities.
We could break responsibilities into two: core duties and performance expectations. But we only have one Responsibilities heading allowed; we can include all.
We need to use
- for any list of duties/requirements/benefits. So we should put each duty as
- . For prose we can use
. But if we have a list, we should use
. The instructions: "Use - for any list of duties/requirements/benefits, and
for prose." So if we have multiple items, we should use list.
Thus for Responsibilities we can create a
with each duty as - . Similarly for Requirements (experience, knowledge, etc.) we can list.
Qualifications maybe overlapping with Requirements; but we need to decide distinct sections. The posting includes requirements like years of experience, understanding of PaaS, etc. Also qualifications like "You are Preferably located..." etc. Also skills like communication, troubleshooting, etc.
We could map:
- Requirements: mandatory experience (5-10 years consulting, 2 years cloud platforms, Linux CLI, hands-on AWS/Azure, Kubernetes, Spark/Hadoop, LDAP/Kerberos, Data Quality etc., proficiency in APIs via Java/Python, data warehousing ETL, functional/technical specs, Collibra experience, US citizenship, active security clearance).
- Qualifications: maybe education? Not present. Could be "Preferred location Washington DC metro area, on-site up to 50%"? That's schedule.
- Skills: communication, customer-focused, troubleshooting, self-starting, working with business/IT owners, leading workshops, etc.
But we need to avoid duplication. Let's extract explicit lists.
From "You have5-10 years of consulting experience supporting U.S. federal agencies with knowledge in the areas of Data Governance, Data Management or Data Quality." => requirement.
"An understanding of the leading PaaS providers, Data Lakes, Databases, and Integration platforms commonly adopted by federal agencies." => requirement.
"A minimum of 2 years of experience working with cloud platforms, network-based API integration (REST/JSON), and deployment automation." => requirement.
"Linux CLI proficiency." => requirement.
"Hands-on experience with AWS/Azure, Kubernetes, infrastructure and platform." => requirement.
"Experience with big data technologies such as Spark, and Hadoop." => requirement.
"Familiarity in enterprise security solutions such as LDAP or Kerberos." => requirement.
"Hands-on experience with Data Quality, Data Pipelines, Data Orchestration, and/or Job Control tools." => requirement.
"Knowledgeable of at least least two or three of the following: data management processes, including data governance, data stewardship, master data management, data cataloging, and business rules management" => requirement.
"Proficiency in leveraging APIs via Java, Python, or similar scripting language for custom software implementations in Enterprise Linux or Unix environments. Experience with data warehousing, ETL, data integration." => requirement.
"Skilled in developing functional and technical specifications." => requirement.
"Experienced with Collibra or comparable technologies." => requirement.
"Because this role supports the U.S. government business, it is required that this candidate be a U.S. citizen who resides on U.S. soil and holds active security clearance (Secret/TS/TS-SCI)." => requirement.
Then "You arePreferably located in the Washington, D.C. metro area to support in-person federal customer engagements, with an on-site requirement of up to 50%." => schedule/location.
"An effective communicator across business and technical stakeholders and able to tailor to different audiences." => skill.
"Always customer-focused and personally hold yourself accountable for the customer’s success." => skill.
"Masterful at troubleshooting, navigating, and facilitating resolution of challenging client connectivity and technical software issues." => skill.
"Self-starting and interested in learning new software skills to support intricacies of Collibra’s application stack." => skill.
"Able to work with business and IT owners to identify and align
for prose. We must not repeat job title. Not include Job ID. We must preserve all substantive info; do not invent or summarize away detail. We need to decide what goes where. About the role: first paragraph maybe plus the sentence about Managers? Actually "Managers, Professional Services at Collibra are responsible for..." is more responsibilities. So About the role could be the introductory paragraph: "Joining Collibra’s Professional Services Team At Collibra Public Sector, our Professional Services team relies on Federal Solution Architects to deliver on customer expectations for the services we sell, working directly with customer key projects stakeholders throughout the entire customer journey. Ensuring growth, adoption and renewal, Federal Solution Architects act as customer champions, ensuring customers are onboarded and realizing value rapidly." That's about the role. Responsibilities: list of duties: Supporting federal customer engagements..., Providing federal agencies..., Partnering cross-functionally..., Identifying opportunities..., Meeting or exceeding utilization goals..., Contributing to growth..., Measures of success (30/60/90 days) maybe also responsibilities. We could break responsibilities into two: core duties and performance expectations. But we only have one Responsibilities heading allowed; we can include all. We need to use
- for any list of duties/requirements/benefits. So we should put each duty as
- . For prose we can use
. But if we have a list, we should use
- . The instructions: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have multiple items, we should use list. Thus for Responsibilities we can create a
- with each duty as
- . Similarly for Requirements (experience, knowledge, etc.) we can list. Qualifications maybe overlapping with Requirements; but we need to decide distinct sections. The posting includes requirements like years of experience, understanding of PaaS, etc. Also qualifications like "You are Preferably located..." etc. Also skills like communication, troubleshooting, etc. We could map: - Requirements: mandatory experience (5-10 years consulting, 2 years cloud platforms, Linux CLI, hands-on AWS/Azure, Kubernetes, Spark/Hadoop, LDAP/Kerberos, Data Quality etc., proficiency in APIs via Java/Python, data warehousing ETL, functional/technical specs, Collibra experience, US citizenship, active security clearance). - Qualifications: maybe education? Not present. Could be "Preferred location Washington DC metro area, on-site up to 50%"? That's schedule. - Skills: communication, customer-focused, troubleshooting, self-starting, working with business/IT owners, leading workshops, etc. But we need to avoid duplication. Let's extract explicit lists. From "You have5-10 years of consulting experience supporting U.S. federal agencies with knowledge in the areas of Data Governance, Data Management or Data Quality." => requirement. "An understanding of the leading PaaS providers, Data Lakes, Databases, and Integration platforms commonly adopted by federal agencies." => requirement. "A minimum of 2 years of experience working with cloud platforms, network-based API integration (REST/JSON), and deployment automation." => requirement. "Linux CLI proficiency." => requirement. "Hands-on experience with AWS/Azure, Kubernetes, infrastructure and platform." => requirement. "Experience with big data technologies such as Spark, and Hadoop." => requirement. "Familiarity in enterprise security solutions such as LDAP or Kerberos." => requirement. "Hands-on experience with Data Quality, Data Pipelines, Data Orchestration, and/or Job Control tools." => requirement. "Knowledgeable of at least least two or three of the following: data management processes, including data governance, data stewardship, master data management, data cataloging, and business rules management" => requirement. "Proficiency in leveraging APIs via Java, Python, or similar scripting language for custom software implementations in Enterprise Linux or Unix environments. Experience with data warehousing, ETL, data integration." => requirement. "Skilled in developing functional and technical specifications." => requirement. "Experienced with Collibra or comparable technologies." => requirement. "Because this role supports the U.S. government business, it is required that this candidate be a U.S. citizen who resides on U.S. soil and holds active security clearance (Secret/TS/TS-SCI)." => requirement. Then "You arePreferably located in the Washington, D.C. metro area to support in-person federal customer engagements, with an on-site requirement of up to 50%." => schedule/location. "An effective communicator across business and technical stakeholders and able to tailor to different audiences." => skill. "Always customer-focused and personally hold yourself accountable for the customer’s success." => skill. "Masterful at troubleshooting, navigating, and facilitating resolution of challenging client connectivity and technical software issues." => skill. "Self-starting and interested in learning new software skills to support intricacies of Collibra’s application stack." => skill. "Able to work with business and IT owners to identify and align
- for any list of duties/requirements/benefits, and