I/S Agile Project Manager I - Remote
for sections like 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. Remove boilerplate, navigation, legal, EEO, scam warnings, 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.
Content:
- Intro: "The I/S Project Manager I is responsible for the overall planning, execution, and delivery of Run, Grow, and Transform initiatives for a Database Infrastructure team of up to 15 members. This role serves as a servant leader and coach, leveraging Agile methodologies to foster collaboration, remove roadblocks, and help the team successfully deliver business outcomes."
- Next: "The I/S Project Manager I will lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations."
- "What We Can Offer You:" then bullet list: Salary: $112,000-$115,000, plus annual bonus eligibility. 401(k) with 2% company contribution and up to 6% match. Time Off: Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details.
- "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." This is a requirement but maybe part of Requirements.
- "What You’ll Do:" then bullet list of responsibilities.
- "What You’ll Bring:" then bullet list of qualifications/skills.
- Then "Preferred:" list of certifications/education.
- Then "We value diverse experience..." etc.
- Then application instructions and scam warnings etc to be removed.
We need to decide sections: maybe About the role (intro), Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Bring + Preferred + sponsorship requirement), Benefits (What We Can Offer You includes salary, 401k, Time Off), Pay (maybe separate but we can include salary in Benefits? The instruction: include Pay section only if posting actually states them. It does state salary. So we could have a Pay section with salary and bonus eligibility. Benefits section could include 401k, Time Off. Or combine? They said prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they have separate headings possible: Benefits, Pay, Schedule. Since we have salary and bonus, we could put in Pay. Benefits: 401k, Time Off. Schedule: not mentioned, so omit.
We need to avoid filler like "See our benefits and perks page for details." That's somewhat generic but still substantive? It's a reference; we could keep it as part of Benefits prose.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract:
About the role (intro): two paragraphs combined maybe.
Responsibilities: list from "What You’ll Do:" bullet points.
Requirements/Qualifications: from "What You’ll Bring:" bullet points plus "Preferred:" bullet points plus sponsorship requirement.
Skills: maybe part of Requirements; but we could have Skills section separate if we want. However we have many skill items; could put under Requirements or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Skills separate. But we need to avoid thin sections. Could combine Requirements and Skills into one Requirements section? But they gave both as possible headings. We need to decide based on content: we have both qualifications (experience, education) and skills (facilitation, communication, etc). Could split: Requirements (experience, education, certifications) and Skills (soft skills, technical knowledge). However the "What You’ll Bring:" includes both experience and skills. The "Preferred:" includes certifications/education. The sponsorship requirement is a requirement.
We could have:
- About the role (intro)
- Responsibilities
- Requirements (experience, education, sponsorship)
- Skills (facilitation, communication, technical knowledge, servant leadership, professional)
- Benefits (401k, Time Off)
- Pay (salary, bonus)
We must not include sections with filler. All have content.
Now format.
We need to use
for each section heading.
Inside each section, we need to use
for prose, and
- for any list of duties/requirements/benefits.
Thus:
About the role
... (two sentences combined)
Responsibilities
- ...
...
Requirements
- 1-3 years Agile/Scrum project management experience.
- 4-8 years of information technology experience and/or business experience.
- Applicants must not now, nor at any point in the future, require sponsorship for employment.
Maybe also include "Learn about and how to apply relevant aspects of the SAFe Framework." as requirement? It's under What You’ll Bring. Could be a requirement.
Thus add that.
Skills
- Strong facilitation and presentation skills.
- Strong communication and conflict resolution skills.
- Knowledge of project management, risk management, procurement management and change management.
- Credible understanding of different technology and domains (database, Windows servers, Linux servers, client server, web services, portal, data communications, etc).
- Ability to manage work across technologies, domains, and business functions.
- Interpersonal - effective verbal and written communication skills, resolves conflicts and effectively negotiates issue resolution, establishes and maintains interpersonal relationships, and displays strong facilitation skills. Actively demonstrates high personal integrity and ability to earn trust from others.
- Servant Leadership- advocates change, supports team building, recognizes contributions and celebrates accomplishments. Empowers and develops people, demonstrates humility and authenticity, provides direction rather than “giving orders.” Coaches others and seeks and applies feedback often. Creates an environment of trust where it is safe to challenge, experiment, and fail without fear.
- Professional - understands and executes Agile project management processes and industry best practices which include, but are not limited to, effective PI Planning, monitoring work, managing scope, managing resources, ensuring quality control.
But note some items are long; we can keep as list items.
Now Benefits:
Benefits
- 401(k) with 2% company contribution and up to 6% match.
- Time Off: Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details.
Pay:
Pay
Salary: $112,000-$115,000, plus annual bonus eligibility.
We should not include Schedule.
Check for any duplicated lines: we have not included the intro duplicated.
Check for any boilerplate removed: we removed "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." we kept as requirement. Good.
Removed "What We Can Offer You:" heading (we used Benefits and Pay). Removed "What You’ll Do:" heading (we used Responsibilities). Removed "What You’ll Bring:" heading (we used Requirements and Skills). Removed "Preferred:" heading (we incorporated into Requirements/Skills). Removed "We value diverse experience..." etc. Removed application instructions and scam warnings.
Check that we preserved all substantive info: Let's list original substantive pieces:
- Intro two sentences.
- Lead medium- to large-scale projects up to $2.3 million.
- What We Can Offer You: Salary, 401k, Time Off.
- Sponsorship requirement.
- What You’ll Do: list of responsibilities (many bullet points).
- What You’ll Bring: list of experience, SAFe, facilitation, communication, knowledge, ability to manage across, interpersonal, servant leadership, professional.
- Preferred: Bachelors, CAPM, PMP, CSP, PMI-ACP.
- We value diverse experience... (we removed as boilerplate? It's a statement but not specific requirement; could be considered filler but it's substantive? It's a generic statement; we can drop as it's not specific detail. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. This statement is somewhat generic but still part of posting. However it's not a specific requirement; it's a value statement. Might be considered boilerplate? It's not navigation/legal/EEO. It's a statement about valuing diverse experience. Could keep but it's not a list; could be a short p under Requirements or Skills. However we have many sections; adding a p may be okay. But we prefer few substantive sections; adding a p may be thin. I'd consider it filler and can drop as it's not specific detail. The instruction: "Prefer a few substantive sections over many thin ones." This statement is thin; we can drop.
- Application instructions etc removed.
We also missed the line about "lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations." This is part of intro? Actually it's separate sentence after first paragraph. We should include it in About the role or Responsibilities? It's about the role's responsibility for budget up to $2.3M. Could be part of About the role. Let's incorporate into About the role paragraph.
Thus About the role: combine first two sentences and the budget sentence.
Let's craft:
"The I/S Project Manager I is responsible for the overall planning, execution, and delivery of Run, Grow, and Transform initiatives for a Database Infrastructure team of up to 15 members. This role serves as a servant leader and coach, leveraging Agile methodologies to foster collaboration, remove roadblocks, and help the team successfully deliver business outcomes. The I/S Project Manager I will lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations."
Now Responsibilities list: need to capture all bullet points from "What You’ll Do:":
- Works in an Agile environment on an Infrastructure team that consists of technical resources. Serves as the Scrum Master for 3 sub-teams (of 3-6 members each), delivering database technology solutions.
- Facilitates the 3 sub-team, sprint planning cycles monthly to successfully execute on team backlogged processes improvement and team technology roadmap items.
- Serves as the process expert and helps educate the team in Scrum and Kanban. Ensures the Agile processes are being followed.
- Responsible for managing the overall planning, execution, and delivery of run, grow and transform work performed by an Infrastructure/Operations team. This may include the management of projects to include the definition of project charters, budgets, and measures as well as developing project structures and ensuring proper operations turnover.
- Facilitate the day-to-day coordination of work, removal of work impediments and escalates to Management when issues require immediate attention.
- Responsible for tracking work status and managing issues and risks to include financial analysis, evaluation of progress/quality/costs, developing action plans to address gaps or risks, adherence to compliance and procurement processes, and problem resolution.
- Responsible for building and leading high performing teams, including building strong product owner, sponsor, solution lead
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warnings, 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. Content: - Intro: "The I/S Project Manager I is responsible for the overall planning, execution, and delivery of Run, Grow, and Transform initiatives for a Database Infrastructure team of up to 15 members. This role serves as a servant leader and coach, leveraging Agile methodologies to foster collaboration, remove roadblocks, and help the team successfully deliver business outcomes." - Next: "The I/S Project Manager I will lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations." - "What We Can Offer You:" then bullet list: Salary: $112,000-$115,000, plus annual bonus eligibility. 401(k) with 2% company contribution and up to 6% match. Time Off: Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details. - "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." This is a requirement but maybe part of Requirements. - "What You’ll Do:" then bullet list of responsibilities. - "What You’ll Bring:" then bullet list of qualifications/skills. - Then "Preferred:" list of certifications/education. - Then "We value diverse experience..." etc. - Then application instructions and scam warnings etc to be removed. We need to decide sections: maybe About the role (intro), Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Bring + Preferred + sponsorship requirement), Benefits (What We Can Offer You includes salary, 401k, Time Off), Pay (maybe separate but we can include salary in Benefits? The instruction: include Pay section only if posting actually states them. It does state salary. So we could have a Pay section with salary and bonus eligibility. Benefits section could include 401k, Time Off. Or combine? They said prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they have separate headings possible: Benefits, Pay, Schedule. Since we have salary and bonus, we could put in Pay. Benefits: 401k, Time Off. Schedule: not mentioned, so omit. We need to avoid filler like "See our benefits and perks page for details." That's somewhat generic but still substantive? It's a reference; we could keep it as part of Benefits prose. We must not include duplicated lines. Ensure we preserve all substantive info. Let's extract: About the role (intro): two paragraphs combined maybe. Responsibilities: list from "What You’ll Do:" bullet points. Requirements/Qualifications: from "What You’ll Bring:" bullet points plus "Preferred:" bullet points plus sponsorship requirement. Skills: maybe part of Requirements; but we could have Skills section separate if we want. However we have many skill items; could put under Requirements or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Skills separate. But we need to avoid thin sections. Could combine Requirements and Skills into one Requirements section? But they gave both as possible headings. We need to decide based on content: we have both qualifications (experience, education) and skills (facilitation, communication, etc). Could split: Requirements (experience, education, certifications) and Skills (soft skills, technical knowledge). However the "What You’ll Bring:" includes both experience and skills. The "Preferred:" includes certifications/education. The sponsorship requirement is a requirement. We could have: - About the role (intro) - Responsibilities - Requirements (experience, education, sponsorship) - Skills (facilitation, communication, technical knowledge, servant leadership, professional) - Benefits (401k, Time Off) - Pay (salary, bonus) We must not include sections with filler. All have content. Now format. We need to use
for each section heading. Inside each section, we need to use
for prose, and
- for any list of duties/requirements/benefits.
Thus:
About the role
... (two sentences combined)
Responsibilities
- ... ...
Requirements
- 1-3 years Agile/Scrum project management experience.
- 4-8 years of information technology experience and/or business experience.
- Applicants must not now, nor at any point in the future, require sponsorship for employment.
Skills
- Strong facilitation and presentation skills.
- Strong communication and conflict resolution skills.
- Knowledge of project management, risk management, procurement management and change management.
- Credible understanding of different technology and domains (database, Windows servers, Linux servers, client server, web services, portal, data communications, etc).
- Ability to manage work across technologies, domains, and business functions.
- Interpersonal - effective verbal and written communication skills, resolves conflicts and effectively negotiates issue resolution, establishes and maintains interpersonal relationships, and displays strong facilitation skills. Actively demonstrates high personal integrity and ability to earn trust from others.
- Servant Leadership- advocates change, supports team building, recognizes contributions and celebrates accomplishments. Empowers and develops people, demonstrates humility and authenticity, provides direction rather than “giving orders.” Coaches others and seeks and applies feedback often. Creates an environment of trust where it is safe to challenge, experiment, and fail without fear.
- Professional - understands and executes Agile project management processes and industry best practices which include, but are not limited to, effective PI Planning, monitoring work, managing scope, managing resources, ensuring quality control.
Benefits
- 401(k) with 2% company contribution and up to 6% match.
- Time Off: Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details.
Pay
Salary: $112,000-$115,000, plus annual bonus eligibility.
We should not include Schedule. Check for any duplicated lines: we have not included the intro duplicated. Check for any boilerplate removed: we removed "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." we kept as requirement. Good. Removed "What We Can Offer You:" heading (we used Benefits and Pay). Removed "What You’ll Do:" heading (we used Responsibilities). Removed "What You’ll Bring:" heading (we used Requirements and Skills). Removed "Preferred:" heading (we incorporated into Requirements/Skills). Removed "We value diverse experience..." etc. Removed application instructions and scam warnings. Check that we preserved all substantive info: Let's list original substantive pieces: - Intro two sentences. - Lead medium- to large-scale projects up to $2.3 million. - What We Can Offer You: Salary, 401k, Time Off. - Sponsorship requirement. - What You’ll Do: list of responsibilities (many bullet points). - What You’ll Bring: list of experience, SAFe, facilitation, communication, knowledge, ability to manage across, interpersonal, servant leadership, professional. - Preferred: Bachelors, CAPM, PMP, CSP, PMI-ACP. - We value diverse experience... (we removed as boilerplate? It's a statement but not specific requirement; could be considered filler but it's substantive? It's a generic statement; we can drop as it's not specific detail. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. This statement is somewhat generic but still part of posting. However it's not a specific requirement; it's a value statement. Might be considered boilerplate? It's not navigation/legal/EEO. It's a statement about valuing diverse experience. Could keep but it's not a list; could be a short p under Requirements or Skills. However we have many sections; adding a p may be okay. But we prefer few substantive sections; adding a p may be thin. I'd consider it filler and can drop as it's not specific detail. The instruction: "Prefer a few substantive sections over many thin ones." This statement is thin; we can drop. - Application instructions etc removed. We also missed the line about "lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations." This is part of intro? Actually it's separate sentence after first paragraph. We should include it in About the role or Responsibilities? It's about the role's responsibility for budget up to $2.3M. Could be part of About the role. Let's incorporate into About the role paragraph. Thus About the role: combine first two sentences and the budget sentence. Let's craft: "The I/S Project Manager I is responsible for the overall planning, execution, and delivery of Run, Grow, and Transform initiatives for a Database Infrastructure team of up to 15 members. This role serves as a servant leader and coach, leveraging Agile methodologies to foster collaboration, remove roadblocks, and help the team successfully deliver business outcomes. The I/S Project Manager I will lead medium- to large-scale projects with internal labor costs of up to $2.3 million, ensuring projects are effectively planned, executed, monitored, and delivered on time and within established budgets and expectations." Now Responsibilities list: need to capture all bullet points from "What You’ll Do:": - Works in an Agile environment on an Infrastructure team that consists of technical resources. Serves as the Scrum Master for 3 sub-teams (of 3-6 members each), delivering database technology solutions. - Facilitates the 3 sub-team, sprint planning cycles monthly to successfully execute on team backlogged processes improvement and team technology roadmap items. - Serves as the process expert and helps educate the team in Scrum and Kanban. Ensures the Agile processes are being followed. - Responsible for managing the overall planning, execution, and delivery of run, grow and transform work performed by an Infrastructure/Operations team. This may include the management of projects to include the definition of project charters, budgets, and measures as well as developing project structures and ensuring proper operations turnover. - Facilitate the day-to-day coordination of work, removal of work impediments and escalates to Management when issues require immediate attention. - Responsible for tracking work status and managing issues and risks to include financial analysis, evaluation of progress/quality/costs, developing action plans to address gaps or risks, adherence to compliance and procurement processes, and problem resolution. - Responsible for building and leading high performing teams, including building strong product owner, sponsor, solution lead