Director, Enterprise Applications
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Sections present:
- "Who We Are": description of TNTP. That's about the organization, maybe "About the role"? Actually "About the role" is typical heading for description of role. But we have "Who We Are" describing organization. Could map to "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have "Who We Are" which is about the organization, not the role. Might be considered "About the role"? Not exactly. But we could still include an "About the role" section summarizing the role description. However we have a "What You’ll Do" section which is responsibilities. So we can map:
- About the role: maybe a brief overview of the role? The posting includes "The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday..." That's more like responsibilities. Could be "About the role" summarizing the role purpose. But we have a dedicated "What You’ll Do" which is responsibilities. So we could have sections: Responsibilities (from "What You’ll Do"), Qualifications (from "Your Qualifications"), Benefits (from "What We Offer" includes salary range and benefits), Pay (maybe separate salary?), Schedule (not present). Skills maybe from qualifications? Could combine.
We need to avoid filler sections. If we don't have specific content for a heading, we should omit it.
Thus we need to decide which headings have real content.
Content:
- About the role: Could be a short paragraph summarizing the role: "The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday..." That's substantive. Could be placed under About the role.
- Responsibilities: The bullet list under "Specifically, You Will Own ..." etc. That's a list of duties.
- Requirements: Could be the qualifications? Actually "Your Qualifications" includes education, experience, required and preferred. That could be Requirements or Qualifications. We have both Requirements and Qualifications headings possible. We need to decide which to use. The posting includes "Your Qualifications" with bullet points: Bachelor's degree..., Master's or graduate degree required..., 3+ years..., Proven success..., Required: Direct experience..., Preferred: Experience..., Experience with software development lifecycle..., Strong project..., Demonstrated ability..., Excellent communication..., Experience operating within governance..., Strong commitment to TNTP's mission.
Thus we could put that under Qualifications (or Requirements). Since we have both headings available, we need to avoid duplication. Perhaps we put education/experience under Qualifications, and required/preferred skills under Skills? But the instruction says use headings as examples; we can choose which to include based on content.
We have specific content for:
- About the role (summary)
- Responsibilities (list)
- Qualifications (education, experience, required/preferred)
- Benefits (salary range, total rewards, PTO, benefits, note about closed last two weeks of December)
- Pay (salary range) maybe separate from Benefits? The posting includes salary range under "What We Offer". Could treat Pay as separate section with salary range, and Benefits as other benefits (PTO, comprehensive benefits, accommodation). But we need to avoid thin sections. Could combine Pay and Benefits into one Benefits section? But we have separate headings; we could include both if they have substantive content. The salary range is specific numbers; we can put under Pay. Benefits: "generous PTO, comprehensive benefits, range of plans and programs designed to support physical, mental, and financial wellness... closed last two weeks of December". That's substantive.
Schedule: Not mentioned. So omit Schedule.
Skills: Could be extracted from qualifications like "Strong project and program management skills, including familiarity with agile methodologies and change management practices. Demonstrated ability to manage budgets, optimize costs, and make investment recommendations grounded in financial analysis. Excellent communication skills..." That's skills. But we already have qualifications covering education/experience; we could split: Qualifications for education/experience, Skills for abilities. However the posting lumps them together; we could still separate if we want to avoid thin sections. But we need to avoid filler. If we split, each section will have substantive content. That's okay.
But we must not invent headings without content. So we need to see if we have enough content for Skills: yes, we have bullet points about skills. So we can include Skills.
Thus we could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
Check for duplication: Qualifications includes education, experience, required/preferred. Skills includes project management, budget management, communication, governance experience. Benefits includes PTO, benefits, wellness programs, closed weeks. Pay includes salary range.
We must ensure we preserve all substantive information. Let's extract all substantive info from posting, removing boilerplate.
Boilerplate to remove: "Flexible Location Who We Are TNTP is the nation's preeminent education nonprofit..." Actually "Flexible Location" maybe a tag; we can ignore. Also "Learn more about us, what we do, and working here." That's navigation. Also "We suggest learning more about our benefits! (Spoiler alert: we’re closed the last two weeks of December)." That's part of benefits; we keep the closed weeks note. Also "We also ensure that individuals with disabilities are provided reasonable accommodation for the interview process. Email talent@tntp.org to request accommodation." That's accommodation info; could be part of Benefits or maybe we keep as part of Benefits (accommodation). It's substantive. Also "How To Apply Submit your resume online through Workday..." etc. That's application instructions; we must remove. Also "Priority application deadline..." etc. Remove. Also "Position Type Regular". Remove. Also EEO statement etc. Remove. Also "Applicants for employment with TNTP must have valid work authorization..." Remove.
Thus we keep:
- Who We Are description (organization overview)
- What You’ll Do (role responsibilities)
- Specifically, You Will Own ... (list of duties)
- Your Qualifications (education, experience, required, preferred)
- What We Offer (salary range, total rewards, PTO, benefits, wellness, closed weeks, accommodation)
We also have "Learn more about us, what we do, and working here." (remove). Also "We suggest learning more about our benefits! (Spoiler alert: we’re closed the last two weeks of December)." Keep the closed weeks note as part of benefits.
Now we need to format into HTML with headings and lists - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes into which section.
Let's define:
About the role: Could be a brief paragraph summarizing the role purpose: maybe combine "Who We Are" and the first sentence of "What You’ll Do"? But "Who We Are" is about the organization, not the role. The instruction says use headings e.g. About the role, Responsibilities... So we could put organization description under About the role? Might be okay. However "About the role" typically describes the role, not the organization. But we have no separate organization description heading; we could still use About the role to include both organization and role overview. But we must not repeat job title as heading. It's fine.
Alternatively we could omit About the role and start with Responsibilities. But we have substantive content about the organization that we should preserve. Where to put it? Could be a preceding
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having prose outside headings, but likely they expect sections. We could include an initial
for the organization description, then headings for Responsibilities etc. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must wrap everything in headings, but likely they want sections. We could treat the organization description as part of About the role section.
Thus:
About the role
TNTP is the nation's preeminent education nonprofit that brings research, policy, and consulting together to meet the needs and aspirations of young people, families, communities, and the nation. We are educators, researchers, and innovators working to ensure every young person has the chance to reach their full potential, every educator and leader is set up for success, and every community has the resources necessary to connect young people to paths of opportunity. We work at every level of the PK-12 system, side by side with educators, system leaders, and communities across 41 states and more than 4,000 systems nationwide to reach ambitious goals for student success. Our vision pushes beyond school walls, catalyzing cross-sector collaboration to create pathways for young people to achieve academic, economic, and social mobility.
That's substantive.
Now Responsibilities: from "What You’ll Do" and the list under "Specifically, You Will Own". We can combine.
Responsibilities heading: Responsibilities
The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday, a core enterprise platform critical to TNTP’s operations and growth, including its roadmap, governance, prioritization, and overall health. This role serves as a key partner to functional leaders across Finance, HR, and other business teams, translating organizational needs into clear platform direction and ensuring that changes are well-governed, intentionally prioritized, and aligned to business outcomes—balancing speed, risk, and long-term sustainability. The Director is the primary decision owner for platform-level work, operating within the broader portfolio strategy defined by the Partner, Enterprise Applications. This role is critical to ensuring that enterprise systems scale effectively alongside the organization, with clear accountability for how decisions are made and executed. This role reports to TNTP's Partner, Enterprise Applications.
Then a list of specific duties: - Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time.
... etc.
We need to include all bullet points from "Specifically, You Will Own". Let's list them:
- Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time.
- Establish and maintain clear governance and operating expectations, including how work is prioritized, how decisions are made, and how changes are managed.
- Partner with business leaders to define problems, evaluate options, and drive decisions, balancing business needs, platform capabilities, and organizational risk.
- Ensure work is evaluated in the context of end-to-end business processes and outcomes, not individual requests or point solutions.
- Lead prioritization and trade-off decisions, making constraints visible and focusing the organization on the highest-value work.
- Lead and develop a team of functional and technical delivery experts, ensuring the right work is prioritized, delivered effectively, and continuously improved.
- Provide clear direction and decision-making, ensuring delivery teams are not required to arbitrate business trade-offs or assume implicit risk ownership.
- Oversee the full lifecycle of the platform, including enhancements, releases, and ongoing improvement, ensuring it remains reliable, scalable, and fit for purpose.
- Maintain strong platform health and integrity
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Sections present: - "Who We Are": description of TNTP. That's about the organization, maybe "About the role"? Actually "About the role" is typical heading for description of role. But we have "Who We Are" describing organization. Could map to "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have "Who We Are" which is about the organization, not the role. Might be considered "About the role"? Not exactly. But we could still include an "About the role" section summarizing the role description. However we have a "What You’ll Do" section which is responsibilities. So we can map:
- About the role: maybe a brief overview of the role? The posting includes "The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday..." That's more like responsibilities. Could be "About the role" summarizing the role purpose. But we have a dedicated "What You’ll Do" which is responsibilities. So we could have sections: Responsibilities (from "What You’ll Do"), Qualifications (from "Your Qualifications"), Benefits (from "What We Offer" includes salary range and benefits), Pay (maybe separate salary?), Schedule (not present). Skills maybe from qualifications? Could combine.
We need to avoid filler sections. If we don't have specific content for a heading, we should omit it.
Thus we need to decide which headings have real content.
Content:
- About the role: Could be a short paragraph summarizing the role: "The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday..." That's substantive. Could be placed under About the role.
- Responsibilities: The bullet list under "Specifically, You Will Own ..." etc. That's a list of duties.
- Requirements: Could be the qualifications? Actually "Your Qualifications" includes education, experience, required and preferred. That could be Requirements or Qualifications. We have both Requirements and Qualifications headings possible. We need to decide which to use. The posting includes "Your Qualifications" with bullet points: Bachelor's degree..., Master's or graduate degree required..., 3+ years..., Proven success..., Required: Direct experience..., Preferred: Experience..., Experience with software development lifecycle..., Strong project..., Demonstrated ability..., Excellent communication..., Experience operating within governance..., Strong commitment to TNTP's mission.
Thus we could put that under Qualifications (or Requirements). Since we have both headings available, we need to avoid duplication. Perhaps we put education/experience under Qualifications, and required/preferred skills under Skills? But the instruction says use headings as examples; we can choose which to include based on content.
We have specific content for:
- About the role (summary)
- Responsibilities (list)
- Qualifications (education, experience, required/preferred)
- Benefits (salary range, total rewards, PTO, benefits, note about closed last two weeks of December)
- Pay (salary range) maybe separate from Benefits? The posting includes salary range under "What We Offer". Could treat Pay as separate section with salary range, and Benefits as other benefits (PTO, comprehensive benefits, accommodation). But we need to avoid thin sections. Could combine Pay and Benefits into one Benefits section? But we have separate headings; we could include both if they have substantive content. The salary range is specific numbers; we can put under Pay. Benefits: "generous PTO, comprehensive benefits, range of plans and programs designed to support physical, mental, and financial wellness... closed last two weeks of December". That's substantive.
Schedule: Not mentioned. So omit Schedule.
Skills: Could be extracted from qualifications like "Strong project and program management skills, including familiarity with agile methodologies and change management practices. Demonstrated ability to manage budgets, optimize costs, and make investment recommendations grounded in financial analysis. Excellent communication skills..." That's skills. But we already have qualifications covering education/experience; we could split: Qualifications for education/experience, Skills for abilities. However the posting lumps them together; we could still separate if we want to avoid thin sections. But we need to avoid filler. If we split, each section will have substantive content. That's okay.
But we must not invent headings without content. So we need to see if we have enough content for Skills: yes, we have bullet points about skills. So we can include Skills.
Thus we could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay.
Check for duplication: Qualifications includes education, experience, required/preferred. Skills includes project management, budget management, communication, governance experience. Benefits includes PTO, benefits, wellness programs, closed weeks. Pay includes salary range.
We must ensure we preserve all substantive information. Let's extract all substantive info from posting, removing boilerplate.
Boilerplate to remove: "Flexible Location Who We Are TNTP is the nation's preeminent education nonprofit..." Actually "Flexible Location" maybe a tag; we can ignore. Also "Learn more about us, what we do, and working here." That's navigation. Also "We suggest learning more about our benefits! (Spoiler alert: we’re closed the last two weeks of December)." That's part of benefits; we keep the closed weeks note. Also "We also ensure that individuals with disabilities are provided reasonable accommodation for the interview process. Email talent@tntp.org to request accommodation." That's accommodation info; could be part of Benefits or maybe we keep as part of Benefits (accommodation). It's substantive. Also "How To Apply Submit your resume online through Workday..." etc. That's application instructions; we must remove. Also "Priority application deadline..." etc. Remove. Also "Position Type Regular". Remove. Also EEO statement etc. Remove. Also "Applicants for employment with TNTP must have valid work authorization..." Remove.
Thus we keep:
- Who We Are description (organization overview)
- What You’ll Do (role responsibilities)
- Specifically, You Will Own ... (list of duties)
- Your Qualifications (education, experience, required, preferred)
- What We Offer (salary range, total rewards, PTO, benefits, wellness, closed weeks, accommodation)
We also have "Learn more about us, what we do, and working here." (remove). Also "We suggest learning more about our benefits! (Spoiler alert: we’re closed the last two weeks of December)." Keep the closed weeks note as part of benefits.
Now we need to format into HTML with headings and lists - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes into which section.
Let's define:
About the role: Could be a brief paragraph summarizing the role purpose: maybe combine "Who We Are" and the first sentence of "What You’ll Do"? But "Who We Are" is about the organization, not the role. The instruction says use headings e.g. About the role, Responsibilities... So we could put organization description under About the role? Might be okay. However "About the role" typically describes the role, not the organization. But we have no separate organization description heading; we could still use About the role to include both organization and role overview. But we must not repeat job title as heading. It's fine.
Alternatively we could omit About the role and start with Responsibilities. But we have substantive content about the organization that we should preserve. Where to put it? Could be a preceding
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having prose outside headings, but likely they expect sections. We could include an initial
for the organization description, then headings for Responsibilities etc. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must wrap everything in headings, but likely they want sections. We could treat the organization description as part of About the role section.
Thus:
About the role
TNTP is the nation's preeminent education nonprofit that brings research, policy, and consulting together to meet the needs and aspirations of young people, families, communities, and the nation. We are educators, researchers, and innovators working to ensure every young person has the chance to reach their full potential, every educator and leader is set up for success, and every community has the resources necessary to connect young people to paths of opportunity. We work at every level of the PK-12 system, side by side with educators, system leaders, and communities across 41 states and more than 4,000 systems nationwide to reach ambitious goals for student success. Our vision pushes beyond school walls, catalyzing cross-sector collaboration to create pathways for young people to achieve academic, economic, and social mobility.
That's substantive.
Now Responsibilities: from "What You’ll Do" and the list under "Specifically, You Will Own". We can combine.
Responsibilities heading: Responsibilities
The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday, a core enterprise platform critical to TNTP’s operations and growth, including its roadmap, governance, prioritization, and overall health. This role serves as a key partner to functional leaders across Finance, HR, and other business teams, translating organizational needs into clear platform direction and ensuring that changes are well-governed, intentionally prioritized, and aligned to business outcomes—balancing speed, risk, and long-term sustainability. The Director is the primary decision owner for platform-level work, operating within the broader portfolio strategy defined by the Partner, Enterprise Applications. This role is critical to ensuring that enterprise systems scale effectively alongside the organization, with clear accountability for how decisions are made and executed. This role reports to TNTP's Partner, Enterprise Applications.
Then a list of specific duties: - Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time.
... etc.
We need to include all bullet points from "Specifically, You Will Own". Let's list them:
- Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time.
- Establish and maintain clear governance and operating expectations, including how work is prioritized, how decisions are made, and how changes are managed.
- Partner with business leaders to define problems, evaluate options, and drive decisions, balancing business needs, platform capabilities, and organizational risk.
- Ensure work is evaluated in the context of end-to-end business processes and outcomes, not individual requests or point solutions.
- Lead prioritization and trade-off decisions, making constraints visible and focusing the organization on the highest-value work.
- Lead and develop a team of functional and technical delivery experts, ensuring the right work is prioritized, delivered effectively, and continuously improved.
- Provide clear direction and decision-making, ensuring delivery teams are not required to arbitrate business trade-offs or assume implicit risk ownership.
- Oversee the full lifecycle of the platform, including enhancements, releases, and ongoing improvement, ensuring it remains reliable, scalable, and fit for purpose.
- Maintain strong platform health and integrity
- for any list of duties/requirements/benefits, and
for prose. We need to decide which content goes into which section. Let's define: About the role: Could be a brief paragraph summarizing the role purpose: maybe combine "Who We Are" and the first sentence of "What You’ll Do"? But "Who We Are" is about the organization, not the role. The instruction says use headings e.g. About the role, Responsibilities... So we could put organization description under About the role? Might be okay. However "About the role" typically describes the role, not the organization. But we have no separate organization description heading; we could still use About the role to include both organization and role overview. But we must not repeat job title as heading. It's fine. Alternatively we could omit About the role and start with Responsibilities. But we have substantive content about the organization that we should preserve. Where to put it? Could be a preceding
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having prose outside headings, but likely they expect sections. We could include an initial
for the organization description, then headings for Responsibilities etc. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must wrap everything in headings, but likely they want sections. We could treat the organization description as part of About the role section. Thus:
About the role
TNTP is the nation's preeminent education nonprofit that brings research, policy, and consulting together to meet the needs and aspirations of young people, families, communities, and the nation. We are educators, researchers, and innovators working to ensure every young person has the chance to reach their full potential, every educator and leader is set up for success, and every community has the resources necessary to connect young people to paths of opportunity. We work at every level of the PK-12 system, side by side with educators, system leaders, and communities across 41 states and more than 4,000 systems nationwide to reach ambitious goals for student success. Our vision pushes beyond school walls, catalyzing cross-sector collaboration to create pathways for young people to achieve academic, economic, and social mobility.
That's substantive. Now Responsibilities: from "What You’ll Do" and the list under "Specifically, You Will Own". We can combine. Responsibilities heading:Responsibilities
The Director, Enterprise Applications is responsible for the end-to-end ownership of Workday, a core enterprise platform critical to TNTP’s operations and growth, including its roadmap, governance, prioritization, and overall health. This role serves as a key partner to functional leaders across Finance, HR, and other business teams, translating organizational needs into clear platform direction and ensuring that changes are well-governed, intentionally prioritized, and aligned to business outcomes—balancing speed, risk, and long-term sustainability. The Director is the primary decision owner for platform-level work, operating within the broader portfolio strategy defined by the Partner, Enterprise Applications. This role is critical to ensuring that enterprise systems scale effectively alongside the organization, with clear accountability for how decisions are made and executed. This role reports to TNTP's Partner, Enterprise Applications.
Then a list of specific duties:- Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time. ... etc. We need to include all bullet points from "Specifically, You Will Own". Let's list them: - Own the strategy, roadmap, and prioritization for Workday, ensuring work is aligned to organizational priorities and delivers sustained value over time. - Establish and maintain clear governance and operating expectations, including how work is prioritized, how decisions are made, and how changes are managed. - Partner with business leaders to define problems, evaluate options, and drive decisions, balancing business needs, platform capabilities, and organizational risk. - Ensure work is evaluated in the context of end-to-end business processes and outcomes, not individual requests or point solutions. - Lead prioritization and trade-off decisions, making constraints visible and focusing the organization on the highest-value work. - Lead and develop a team of functional and technical delivery experts, ensuring the right work is prioritized, delivered effectively, and continuously improved. - Provide clear direction and decision-making, ensuring delivery teams are not required to arbitrate business trade-offs or assume implicit risk ownership. - Oversee the full lifecycle of the platform, including enhancements, releases, and ongoing improvement, ensuring it remains reliable, scalable, and fit for purpose. - Maintain strong platform health and integrity