Project/Program Manager IT 3
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate.
We need to parse the posting.
Job Title: Project/Program Manager IT 3 (but we don't output heading for title). Location: Irving, TX. Job Type: W2 Contract. Expected hours per week: 40 hours per week. Schedule: On-site (M-F). Pay Range: $57-64 per hour.
Then Job Description includes Position’s Contributions to Work Group: ... etc. Then sections: Typical Task Breakdown Key Responsibilities (list). Then Education & Experience Required: Release Planning & Calendar Support (list). Then Years of experience: with 3-5 years' experience... Degree requirement: BS Degree. Do you accept internships as job experience: No. Are there past or additional job titles... Top 3 Skills Good business acumen... Familiarity with Power BI... Strong organisational and coordination skills... Excellent written and verbal communication skills... Additional Technical Skills Familiarity with DevOps practices and intent Soft Skills Excellent communication skills... Ability to be flexible...
We need to map to sections: About the role (maybe the Position’s Contributions paragraph). Responsibilities (list of tasks). Requirements (maybe years of experience, degree, internships). Qualifications (maybe degree requirement? but we can combine). Skills (list of skills). Benefits (none given). Pay (we have Pay Range). Schedule (we have Schedule: On-site (M-F) and Expected hours per week). Also location and job type maybe can be included in About the role paragraph or a short p.
We must not create sections with placeholder text. So we include About the role (with location, job type, maybe contributions). Responsibilities (list). Requirements (years experience, degree, internships). Qualifications (maybe degree requirement? but we already have degree in Requirements; maybe we can skip Qualifications if redundant). Skills (list). Pay (section with pay range). Schedule (section with schedule and hours). Benefits: none, so omit.
We must not repeat job title as heading. Use for each section heading.
We need to preserve all substantive info: location, job type, expected hours, schedule, pay range, position contributions, responsibilities list, education/experience details, degree requirement, internships acceptance, top 3 skills, additional technical skills, soft skills.
We need to format lists with - . For prose use
.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not include duplicated lines.
Let's extract content.
Position’s Contributions to Work Group paragraph:
"As part of digital strategy, the integrated MineStar portfolio delivers enterprise-grade software to support mining operations through data-driven insights, system integrations, and scalable platforms. MineStar Office plays a critical role in enabling configuration, analytics, workflows, and integrations across the MineStar ecosystem. The Release Coordinator – MineStar Office supports the Solution Train in the day-to-day coordination and execution of release activities across all MineStar Office products. Working under the direction of the Release Manager, the Release Coordinator provides input into the operational cadence of releases, acting as a coordination hub between teams and global MineStar Office teams."
That's prose.
Typical Task Breakdown Key Responsibilities: then list items:
1. Release Planning & Calendar Support
- Maintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders.
- Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability).
- Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows).
- Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation).
- Track entry/exit criteria for each release gate and escalate gaps to the Release Manager.
- Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment.
2. Release Readiness & Checklist Management (maybe part of above? Actually they enumerated 2. Release Readiness & Checklist Management but then they gave details under 1? The text seems messy. Let's parse:
"Typical Task Breakdown Key Responsibilities2. Release Readiness & Checklist Management3. Release Execution Coordination4. Release Documentation & Communications5. Process Compliance, Quality Support and MetricsEducation & Experience Required: Release Planning & Calendar SupportMaintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders.Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability).Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows).Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation).Track entry/exit criteria for each release gate and escalate gaps to the Release Manager.Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment.Coordinate deployment sequencing across products, components, and environments under the direction of the Release Manager.Liaise with DevOps and Platform teams during release windows to ensure smooth handoffs and environment promotions.Monitor deployment progress and communicate real-time status updates to the Release Manager and stakeholders during release execution.Maintain release documentation repositories ensuring historical release records are accurate and searchable.Prepare release health dashboards and status reports for the Release Manager to present to engineering leadership.Document lessons learned from each release cycle and feed into retrospective discussions.Support adherence to the MineStar SDLC and Scaled Agile methodology by tracking artefact completion and flagging non-compliance to the Release Manager.Assist the Release Manager in maintaining and improving release guardrails, templates, and process documentation.Collect and maintain data for key release metrics as defined by the Release Manager (e.g., release predictability, defect escape rate, rollback frequency, cycle time, deployment frequency)."
It seems they enumerated sections but then gave a big block of responsibilities under Release Planning & Calendar Support, then more items after that (coordinate deployment sequencing, liaise with DevOps, monitor progress, maintain documentation, prepare dashboards, document lessons learned, support adherence, assist Release Manager, collect metrics). So we need to capture all those bullet points as responsibilities.
Thus responsibilities list includes:
- Maintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders.
- Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability).
- Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows).
- Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation).
- Track entry/exit criteria for each release gate and escalate gaps to the Release Manager.
- Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment.
- Coordinate deployment sequencing across products, components, and environments under the direction of the Release Manager.
- Liaise with DevOps and Platform teams during release windows to ensure smooth handoffs and environment promotions.
- Monitor deployment progress and communicate real-time status updates to the Release Manager and stakeholders during release execution.
- Maintain release documentation repositories ensuring historical release records are accurate and searchable.
- Prepare release health dashboards and status reports for the Release Manager to present to engineering leadership.
- Document lessons learned from each release cycle and feed into retrospective discussions.
- Support adherence to the MineStar SDLC and Scaled Agile methodology by tracking artefact completion and flagging non-compliance to the Release Manager.
- Assist the Release Manager in maintaining and improving release guardrails, templates, and process documentation.
- Collect and maintain data for key release metrics as defined by the Release Manager (e.g., release predictability, defect escape rate, rollback frequency, cycle time, deployment frequency).
That's a comprehensive list.
Education & Experience Required: then they list:
"Years of experience: with 3-5 years' experience in a release coordination, release management, or SDLC support role within a software development environment.
Degree requirement: BS Degree
Do you accept internships as job experience: No
Are there past or additional job titles or roles that would provide comparable background to this role:"
Then they list "Top 3 Skills Good business acumen, understanding how software development and release management support business goals and strategyFamiliarity with Power BI, or a willingness to learn, in order to support Program level reporting and health radiatorsStrong organisational and coordination skills with the ability to track multiple concurrent release streams. Excellent written and verbal communication skills, including the ability to produce clear release notes, status reports, and stakeholder communications. Additional Technical Skills Familiarity with DevOps practices and intent Soft Skills Excellent communication skills: verbal and writtenAbility to be flexible and to adapt to the changing needs of a large-scale complex Program"
We need to extract skills: Good business acumen, understanding how software development and release management support business goals and strategy; Familiarity with Power BI, or a willingness to learn, in order to support Program level reporting and health radiators; Strong organisational and coordination skills with the ability to track multiple concurrent release streams; Excellent written and verbal communication skills, including the ability to produce clear release notes, status reports, and stakeholder communications; Additional Technical Skills Familiarity with DevOps practices and intent; Soft Skills Excellent communication skills: verbal and written; Ability to be flexible and to adapt to the changing needs of a large-scale complex Program.
We can combine into a skills list.
Now we need to decide sections.
About the role: include location, job type, maybe position contributions paragraph. Could also include a short p with location and job type.
Responsibilities: the bullet list.
Requirements: years of experience, degree requirement, internships acceptance. Could also include "Are there past or additional job titles..." but that's not a requirement, it's more about comparable background; maybe we can include in Requirements or Qualifications. But we can treat as part of Requirements (alternative backgrounds). However the instruction: "Preserve ALL substantive information". So we need to include that statement: "Are there past or additional job titles or roles that would provide comparable background to this role:" but they didn't list any specific titles; they just asked the question. Actually the posting includes that line but no answer. It's just a question. It's substantive? It's a question but no answer. Might be considered boilerplate? It's not a list of comparable backgrounds. It's just a question. Might be considered filler? The instruction says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This line is not metadata but a question. It might be considered part of the posting but not providing specific info. Since there is no answer, it's not substantive detail. Safer to omit it because it's not providing any info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit a question that has no answer, we are not losing substantive info. So we can drop.
Skills: list.
Pay: section with pay range.
Schedule: section with schedule and expected hours.
We should not create Benefits section.
Now produce HTML.
Structure:
About the role
Location: Irving, TX. Job Type: W2 Contract. Expected hours: 40 hours per week. Schedule: On-site (Monday‑Friday).
[Position’s Contributions paragraph]
Responsibilities
- ...
...
Requirements
- 3‑5 years’ experience in release coordination, release management, or SDLC
- . For prose use
. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not include duplicated lines. Let's extract content. Position’s Contributions to Work Group paragraph: "As part of digital strategy, the integrated MineStar portfolio delivers enterprise-grade software to support mining operations through data-driven insights, system integrations, and scalable platforms. MineStar Office plays a critical role in enabling configuration, analytics, workflows, and integrations across the MineStar ecosystem. The Release Coordinator – MineStar Office supports the Solution Train in the day-to-day coordination and execution of release activities across all MineStar Office products. Working under the direction of the Release Manager, the Release Coordinator provides input into the operational cadence of releases, acting as a coordination hub between teams and global MineStar Office teams." That's prose. Typical Task Breakdown Key Responsibilities: then list items: 1. Release Planning & Calendar Support - Maintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders. - Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability). - Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows). - Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation). - Track entry/exit criteria for each release gate and escalate gaps to the Release Manager. - Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment. 2. Release Readiness & Checklist Management (maybe part of above? Actually they enumerated 2. Release Readiness & Checklist Management but then they gave details under 1? The text seems messy. Let's parse: "Typical Task Breakdown Key Responsibilities2. Release Readiness & Checklist Management3. Release Execution Coordination4. Release Documentation & Communications5. Process Compliance, Quality Support and MetricsEducation & Experience Required: Release Planning & Calendar SupportMaintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders.Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability).Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows).Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation).Track entry/exit criteria for each release gate and escalate gaps to the Release Manager.Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment.Coordinate deployment sequencing across products, components, and environments under the direction of the Release Manager.Liaise with DevOps and Platform teams during release windows to ensure smooth handoffs and environment promotions.Monitor deployment progress and communicate real-time status updates to the Release Manager and stakeholders during release execution.Maintain release documentation repositories ensuring historical release records are accurate and searchable.Prepare release health dashboards and status reports for the Release Manager to present to engineering leadership.Document lessons learned from each release cycle and feed into retrospective discussions.Support adherence to the MineStar SDLC and Scaled Agile methodology by tracking artefact completion and flagging non-compliance to the Release Manager.Assist the Release Manager in maintaining and improving release guardrails, templates, and process documentation.Collect and maintain data for key release metrics as defined by the Release Manager (e.g., release predictability, defect escape rate, rollback frequency, cycle time, deployment frequency)." It seems they enumerated sections but then gave a big block of responsibilities under Release Planning & Calendar Support, then more items after that (coordinate deployment sequencing, liaise with DevOps, monitor progress, maintain documentation, prepare dashboards, document lessons learned, support adherence, assist Release Manager, collect metrics). So we need to capture all those bullet points as responsibilities. Thus responsibilities list includes: - Maintain and publish the MineStar Office release calendar, ensuring dates, milestones, and dependencies are current and visible to all stakeholders. - Track and chase cross-team inputs required for release planning (scope confirmation, dependency declarations, environment availability). - Prepare and distribute release schedule communications (upcoming releases, freeze windows, deployment windows). - Own and maintain release readiness checklists, ensuring all required artefacts are in place before a release proceeds (requirements traceability, test evidence, security sign-off, approvals, release notes, documentation). - Track entry/exit criteria for each release gate and escalate gaps to the Release Manager. - Ensure all change records and release tickets are correctly raised, linked, and approved in Azure DevOps prior to deployment. - Coordinate deployment sequencing across products, components, and environments under the direction of the Release Manager. - Liaise with DevOps and Platform teams during release windows to ensure smooth handoffs and environment promotions. - Monitor deployment progress and communicate real-time status updates to the Release Manager and stakeholders during release execution. - Maintain release documentation repositories ensuring historical release records are accurate and searchable. - Prepare release health dashboards and status reports for the Release Manager to present to engineering leadership. - Document lessons learned from each release cycle and feed into retrospective discussions. - Support adherence to the MineStar SDLC and Scaled Agile methodology by tracking artefact completion and flagging non-compliance to the Release Manager. - Assist the Release Manager in maintaining and improving release guardrails, templates, and process documentation. - Collect and maintain data for key release metrics as defined by the Release Manager (e.g., release predictability, defect escape rate, rollback frequency, cycle time, deployment frequency). That's a comprehensive list. Education & Experience Required: then they list: "Years of experience: with 3-5 years' experience in a release coordination, release management, or SDLC support role within a software development environment. Degree requirement: BS Degree Do you accept internships as job experience: No Are there past or additional job titles or roles that would provide comparable background to this role:" Then they list "Top 3 Skills Good business acumen, understanding how software development and release management support business goals and strategyFamiliarity with Power BI, or a willingness to learn, in order to support Program level reporting and health radiatorsStrong organisational and coordination skills with the ability to track multiple concurrent release streams. Excellent written and verbal communication skills, including the ability to produce clear release notes, status reports, and stakeholder communications. Additional Technical Skills Familiarity with DevOps practices and intent Soft Skills Excellent communication skills: verbal and writtenAbility to be flexible and to adapt to the changing needs of a large-scale complex Program" We need to extract skills: Good business acumen, understanding how software development and release management support business goals and strategy; Familiarity with Power BI, or a willingness to learn, in order to support Program level reporting and health radiators; Strong organisational and coordination skills with the ability to track multiple concurrent release streams; Excellent written and verbal communication skills, including the ability to produce clear release notes, status reports, and stakeholder communications; Additional Technical Skills Familiarity with DevOps practices and intent; Soft Skills Excellent communication skills: verbal and written; Ability to be flexible and to adapt to the changing needs of a large-scale complex Program. We can combine into a skills list. Now we need to decide sections. About the role: include location, job type, maybe position contributions paragraph. Could also include a short p with location and job type. Responsibilities: the bullet list. Requirements: years of experience, degree requirement, internships acceptance. Could also include "Are there past or additional job titles..." but that's not a requirement, it's more about comparable background; maybe we can include in Requirements or Qualifications. But we can treat as part of Requirements (alternative backgrounds). However the instruction: "Preserve ALL substantive information". So we need to include that statement: "Are there past or additional job titles or roles that would provide comparable background to this role:" but they didn't list any specific titles; they just asked the question. Actually the posting includes that line but no answer. It's just a question. It's substantive? It's a question but no answer. Might be considered boilerplate? It's not a list of comparable backgrounds. It's just a question. Might be considered filler? The instruction says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This line is not metadata but a question. It might be considered part of the posting but not providing specific info. Since there is no answer, it's not substantive detail. Safer to omit it because it's not providing any info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit a question that has no answer, we are not losing substantive info. So we can drop. Skills: list. Pay: section with pay range. Schedule: section with schedule and expected hours. We should not create Benefits section. Now produce HTML. Structure:
About the role
Location: Irving, TX. Job Type: W2 Contract. Expected hours: 40 hours per week. Schedule: On-site (Monday‑Friday).
[Position’s Contributions paragraph]
Responsibilities
- ... ...
Requirements
- 3‑5 years’ experience in release coordination, release management, or SDLC