Technical Project Manager - Enterprise AI Solutions
under Requirements or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Locations could be minor metadata; we could include in a
under Requirements or maybe a separate short
after Requirements. But we should not create a heading for Locations unless it's a section like "Locations". Not required. We'll include a
after Requirements maybe. We must not include filler like "commensurate with experience". Not present. We must output only HTML fragment, no /. Use
for section headings. Use - for lists. Use
for prose.
We need to preserve all substantive information. Let's extract:
About The Role paragraph: "As a Technical Project Manager at Snorkel AI, you will lead the day-to-day delivery of high-impact AI projects for some of the world’s largest organizations. You will work directly with customers and technical teams to turn ambitious AI use cases into successful, production-ready solutions. You will own project plans, milestones, dependencies, risks, decisions, and action items, creating the structure and accountability needed to keep fast-moving engagements on schedule, within scope, and within budget. This is a front-row opportunity to work on frontier AI projects involving agents, RAG, evaluation, knowledge bases, classification, and extraction. You will learn from experienced AI practitioners, stay close to the latest research and industry developments, and see how advanced AI systems are built and deployed in real-world enterprise environments. The ideal candidate is organized, customer-focused, comfortable with ambiguity, and excited to build deep technical fluency in AI."
That's the About the role content.
Responsibilities list: bullet points from "Main Responsibilities". Let's list them:
- Manage the day-to-day delivery of enterprise AI engagements, keeping projects aligned with scope, schedule, budget, milestones, and customer outcomes.
- Build and maintain project plans covering workstreams, deliverables, dependencies, ownership, timelines, and resource needs.
- Maintain Jira and project documentation as accurate, organized sources of truth for work, decisions, commitments, risks, and status.
- Lead project cadences, translate discussions into clear actions and decisions, and drive commitments to completion across Snorkel and customer teams.
- Identify risks, blockers, dependencies, and scope changes early; establish mitigation plans, drive resolution, and escalate when needed.
- Provide clear project reporting and serve as a day-to-day customer contact for delivery progress, risks, decisions, and next steps.
- Build enough technical fluency in agents, RAG, evaluation, knowledge bases, classification, and extraction to ask thoughtful questions and connect technical work to customer goals.
- Partner with Operations on project financials, coordinate project closeout, and improve delivery standards, tools, and playbooks.
We'll put each as
- .
Minimum Qualifications list:
- 2+ years of experience in project management, delivery, project coordination, or technical program management, preferably in professional services, consulting, or enterprise software.
- Proven ability to manage multiple workstreams, drive commitments to completion, and deliver projects on schedule and within budget.
- Strong organization, communication, and stakeholder-management skills, with experience working directly with senior enterprise customers.
- Technical aptitude and curiosity, with the ability to quickly develop working knowledge of AI concepts such as agents, RAG, evaluation, knowledge bases, classification, and extraction.
- Proficiency with project-management and collaboration tools such as Jira, with strong discipline around documentation and data accuracy.
- Comfort operating in ambiguity, adapting as priorities evolve, and helping build repeatable processes in a fast-growing environment.
- Annual travel up to 15%.
We could also include Locations: New York; Atlanta; Nashville; Remote - US. Could be a short
after Qualifications.
Pay: "The total cash compensation range for this role is $110,000–$150,000, including target bonus. All offers include equity in the form of employee stock options. Compensation ranges are determined by role, level, and location. Individual compensation is based on work location and additional factors, including job-related skills, experience, and relevant education or training. Actual compensation will be determined based on factors including skills, qualifications, experience, and geographic location. Salary range(s) for this role $110,000—$150,000 USD"
We can summarize: Pay range $110,000–$150,000 USD plus equity (employee stock options). We'll keep that.
We should not include repetitive sentences. We'll produce a concise Pay section.
Now produce HTML:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Locations: New York; Atlanta; Nashville; Remote - US
Pay
The total cash compensation range is $110,000–$150,000 USD, including target bonus, with equity offered as employee stock options.
We should not include Schedule or Benefits sections as no specific content.
Check for any boilerplate: we removed EEO etc. Also removed "Be Your Best at Snorkel" etc. Good.
Now ensure we didn't miss any substantive info: The "About Snorkel" intro paragraph is maybe not needed as it's about company; but could be considered part of About the role? The instruction: "About Snorkel" is introductory; but we already have About the role section. The "About Snorkel" is generic company description; could be omitted as not specific to role? The instruction says preserve ALL substantive information; but we can consider it as company overview, not role-specific. However it's still substantive. But we might include it as a before About the role? There's no heading for it; we could just include a
after the opening? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow that pattern. Could add a About Snorkel
but not in list; but they gave examples; we could still use for any section heading. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also add other headings if needed. Safer to include About Snorkel as a
maybe under a heading? But they didn't list About Snorkel as example; but we could still use
About Snorkel
. However they might expect only those headings. I'd rather keep it as a before About the role, without a heading, as it's just introductory paragraph. That preserves info.
Thus final HTML:
At Snorkel, we believe meaningful AI doesn’t start with the model, it starts with the data. We’re on a mission to help enterprises transform expert knowledge into specialized AI at scale. The AI landscape has gone through incredible changes since 2015, when Snorkel started as a research project in the Stanford AI Lab, to the generative AI breakthroughs of today. But one thing has remained constant: the data you use to build AI is the key to achieving differentiation, high performance, and production-ready systems. We work with some of the world’s largest organizations to empower scientists, engineers, financial experts, product creators, journalists, and more to build custom AI with their data faster than ever before. Excited to help us redefine how AI is built? Apply to be the newest Snorkeler!
About the role
As a Technical Project Manager at Snorkel AI, you will lead the day-to-day delivery of high-impact AI projects for some of the world’s largest organizations. You will work directly with customers and technical teams to turn ambitious AI use cases into successful, production-ready solutions. You will own project plans, milestones, dependencies, risks, decisions, and action items, creating the structure and accountability needed to keep fast-moving engagements on schedule, within scope, and within budget. This is a front-row opportunity to work on frontier AI projects involving agents, RAG, evaluation, knowledge bases, classification, and extraction. You will learn from experienced AI practitioners, stay close to the latest research and industry developments, and see how advanced AI systems are built and deployed in real-world enterprise environments. The ideal candidate is organized, customer-focused, comfortable with ambiguity, and excited to build deep technical fluency in AI.
Responsibilities
- Manage the day-to-day delivery of enterprise AI engagements, keeping projects aligned with scope, schedule, budget, milestones, and customer outcomes.
- Build and maintain project plans covering workstreams, deliverables, dependencies, ownership, timelines, and resource needs.
- Maintain Jira and project documentation as accurate, organized sources of truth for work, decisions, commitments, risks, and status.
- Lead project cadences, translate discussions into clear actions and decisions, and drive commitments to completion across Snorkel and customer teams.
- Identify risks, blockers, dependencies, and scope changes early; establish mitigation plans, drive resolution, and escalate when needed.
- Provide clear project reporting and serve as a day-to-day customer contact for delivery progress, risks, decisions, and next steps.
- Build enough technical fluency in agents, RAG, evaluation, knowledge bases, classification, and extraction to ask thoughtful questions and connect technical work to customer goals.
- Partner with Operations on project financials, coordinate project closeout, and improve delivery standards, tools, and playbooks.
Requirements
for prose. We need to preserve all substantive information. Let's extract: About The Role paragraph: "As a Technical Project Manager at Snorkel AI, you will lead the day-to-day delivery of high-impact AI projects for some of the world’s largest organizations. You will work directly with customers and technical teams to turn ambitious AI use cases into successful, production-ready solutions. You will own project plans, milestones, dependencies, risks, decisions, and action items, creating the structure and accountability needed to keep fast-moving engagements on schedule, within scope, and within budget. This is a front-row opportunity to work on frontier AI projects involving agents, RAG, evaluation, knowledge bases, classification, and extraction. You will learn from experienced AI practitioners, stay close to the latest research and industry developments, and see how advanced AI systems are built and deployed in real-world enterprise environments. The ideal candidate is organized, customer-focused, comfortable with ambiguity, and excited to build deep technical fluency in AI." That's the About the role content. Responsibilities list: bullet points from "Main Responsibilities". Let's list them: - Manage the day-to-day delivery of enterprise AI engagements, keeping projects aligned with scope, schedule, budget, milestones, and customer outcomes. - Build and maintain project plans covering workstreams, deliverables, dependencies, ownership, timelines, and resource needs. - Maintain Jira and project documentation as accurate, organized sources of truth for work, decisions, commitments, risks, and status. - Lead project cadences, translate discussions into clear actions and decisions, and drive commitments to completion across Snorkel and customer teams. - Identify risks, blockers, dependencies, and scope changes early; establish mitigation plans, drive resolution, and escalate when needed. - Provide clear project reporting and serve as a day-to-day customer contact for delivery progress, risks, decisions, and next steps. - Build enough technical fluency in agents, RAG, evaluation, knowledge bases, classification, and extraction to ask thoughtful questions and connect technical work to customer goals. - Partner with Operations on project financials, coordinate project closeout, and improve delivery standards, tools, and playbooks. We'll put each as
after Qualifications. Pay: "The total cash compensation range for this role is $110,000–$150,000, including target bonus. All offers include equity in the form of employee stock options. Compensation ranges are determined by role, level, and location. Individual compensation is based on work location and additional factors, including job-related skills, experience, and relevant education or training. Actual compensation will be determined based on factors including skills, qualifications, experience, and geographic location. Salary range(s) for this role $110,000—$150,000 USD" We can summarize: Pay range $110,000–$150,000 USD plus equity (employee stock options). We'll keep that. We should not include repetitive sentences. We'll produce a concise Pay section. Now produce HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Locations: New York; Atlanta; Nashville; Remote - US
Pay
The total cash compensation range is $110,000–$150,000 USD, including target bonus, with equity offered as employee stock options.
We should not include Schedule or Benefits sections as no specific content. Check for any boilerplate: we removed EEO etc. Also removed "Be Your Best at Snorkel" etc. Good. Now ensure we didn't miss any substantive info: The "About Snorkel" intro paragraph is maybe not needed as it's about company; but could be considered part of About the role? The instruction: "About Snorkel" is introductory; but we already have About the role section. The "About Snorkel" is generic company description; could be omitted as not specific to role? The instruction says preserve ALL substantive information; but we can consider it as company overview, not role-specific. However it's still substantive. But we might include it as abefore About the role? There's no heading for it; we could just include a
after the opening? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow that pattern. Could add a About Snorkel
but not in list; but they gave examples; we could still use for any section heading. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also add other headings if needed. Safer to include About Snorkel as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also add other headings if needed. Safer to include About Snorkel as a
maybe under a heading? But they didn't list About Snorkel as example; but we could still use
About Snorkel
. However they might expect only those headings. I'd rather keep it as abefore About the role, without a heading, as it's just introductory paragraph. That preserves info. Thus final HTML:
At Snorkel, we believe meaningful AI doesn’t start with the model, it starts with the data. We’re on a mission to help enterprises transform expert knowledge into specialized AI at scale. The AI landscape has gone through incredible changes since 2015, when Snorkel started as a research project in the Stanford AI Lab, to the generative AI breakthroughs of today. But one thing has remained constant: the data you use to build AI is the key to achieving differentiation, high performance, and production-ready systems. We work with some of the world’s largest organizations to empower scientists, engineers, financial experts, product creators, journalists, and more to build custom AI with their data faster than ever before. Excited to help us redefine how AI is built? Apply to be the newest Snorkeler!
About the role
As a Technical Project Manager at Snorkel AI, you will lead the day-to-day delivery of high-impact AI projects for some of the world’s largest organizations. You will work directly with customers and technical teams to turn ambitious AI use cases into successful, production-ready solutions. You will own project plans, milestones, dependencies, risks, decisions, and action items, creating the structure and accountability needed to keep fast-moving engagements on schedule, within scope, and within budget. This is a front-row opportunity to work on frontier AI projects involving agents, RAG, evaluation, knowledge bases, classification, and extraction. You will learn from experienced AI practitioners, stay close to the latest research and industry developments, and see how advanced AI systems are built and deployed in real-world enterprise environments. The ideal candidate is organized, customer-focused, comfortable with ambiguity, and excited to build deep technical fluency in AI.
Responsibilities
- Manage the day-to-day delivery of enterprise AI engagements, keeping projects aligned with scope, schedule, budget, milestones, and customer outcomes.
- Build and maintain project plans covering workstreams, deliverables, dependencies, ownership, timelines, and resource needs.
- Maintain Jira and project documentation as accurate, organized sources of truth for work, decisions, commitments, risks, and status.
- Lead project cadences, translate discussions into clear actions and decisions, and drive commitments to completion across Snorkel and customer teams.
- Identify risks, blockers, dependencies, and scope changes early; establish mitigation plans, drive resolution, and escalate when needed.
- Provide clear project reporting and serve as a day-to-day customer contact for delivery progress, risks, decisions, and next steps.
- Build enough technical fluency in agents, RAG, evaluation, knowledge bases, classification, and extraction to ask thoughtful questions and connect technical work to customer goals.
- Partner with Operations on project financials, coordinate project closeout, and improve delivery standards, tools, and playbooks.