producer (contract)

We need to output only HTML fragment, no html/body tags, no markdown fences. We need to include sections only if posting has real specific content. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading (the page already shows it) and not put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section only when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We need to prefer a few substantive sections over many thin ones. We need to output only HTML fragment. Let's parse the posting. Key content: - Summary paragraph: "We are seeking a highly organized and technically fluent Producer/Technical Program Manager to join a fast-paced Engineering Systems team within a leading game development studio. In this role, you will serve as the operational backbone of a team responsible for ensuring builds, tests, and engineering pipelines run smoothly for developers. You will facilitate sprint ceremonies, own feature delivery schedules, manage cross-functional dependencies, and keep stakeholders aligned from day-to-day standups through major release milestones. This is a fully remote, full-time contract position operating on Pacific Standard Time hours." That's prose. - Job Responsibilities: a list of bullet points (starting with "Facilitate sprint ceremonies..." etc). We need to output as

  • each bullet. - Requirements: list of bullet points (starting with "2+ years of experience..." etc). We need to output as
    • . - Additional Details: includes Location, Duration, Pay Range, Weekly Schedule, Job Status, Application Deadline, Benefits list. We need to decide sections. We have: - About the role: could be the summary paragraph. - Responsibilities: the list. - Requirements: the list. - Benefits: list of benefits. - Pay: pay range. - Schedule: weekly schedule. - Possibly Duration? Not a standard heading but could be included in About the role or maybe we could add a separate section like "Details" but not in allowed headings. The allowed headings are limited to those listed. We could incorporate Duration and Location into About the role paragraph or maybe a separate

      after summary. We must not create sections with filler. So we need to include sections only if we have real content. We have content for About the role (summary). We have Responsibilities (list). We have Requirements (list). We have Benefits (list). We have Pay (range). We have Schedule (weekly schedule). Also we have Duration and Location; we could embed them in About the role paragraph or maybe a separate

      after summary. We must not repeat job title as heading. So we will not have

      Producer (Contract) etc. We need to output only HTML fragment, no or . So we can start with

      About the role

      then

      ... etc. We need to ensure we don't include boilerplate like EEO, accommodation, etc. Remove those. Also remove duplicated lines, application instructions like "Apply within 72 hours..." maybe we can keep as part of Additional Details? It's not a standard heading; but we could include it in a

      after summary maybe as part of details. However "Application Deadline: Apply within 72 hours of the posting date to ensure consideration." That's application instruction; we should remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the Application Deadline line. Also remove "Job Status: Non-Exempt" maybe not needed? It's not boilerplate but could be considered metadata; but we can keep if we want. However we might incorporate into About the role or a separate

      . The instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can fold minor metadata like Location, Duration, Pay Range, Weekly Schedule, Job Status into a short

      or drop it. But we also have dedicated Pay and Schedule sections allowed. So we could put Pay and Schedule as separate sections. Location and Duration could be folded into About the role paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the pay range, schedule, location, duration, benefits list, responsibilities list, requirements list, summary. We must not create sections with filler like "commensurate with experience". Not present. Now we need to decide which sections to emit. We have: - About the role: summary paragraph + maybe location and duration. - Responsibilities: list. - Requirements: list. - Benefits: list. - Pay: pay range. - Schedule: weekly schedule. We could also include a section for "Qualifications" but that's similar to Requirements; we can just use Requirements. We could also include "Skills" but we have skills embedded in Requirements; we could separate but not needed. We need to avoid thin sections; prefer few substantive sections. However we have multiple distinct categories; it's okay. Now we need to format. We'll produce:

      About the role

      We are seeking a highly organized and technically fluent Producer/Technical Program Manager to join a fast-paced Engineering Systems team within a leading game development studio. In this role, you will serve as the operational backbone of a team responsible for ensuring builds, tests, and engineering pipelines run smoothly for developers. You will facilitate sprint ceremonies, own feature delivery schedules, manage cross-functional dependencies, and keep stakeholders aligned from day-to-day standups through major release milestones. This is a fully remote, full-time contract position operating on Pacific Standard Time hours. Location: Remote. Duration: 9 months.

      Then Responsibilities:

      Responsibilities

      • Facilitate sprint ceremonies including stand-ups, sprint planning, triage sessions, office hours, and retrospectives — both live and asynchronously
      • Create and maintain sprint and milestone dashboards, calendars, trackers, and transition checklists
      • Own feature delivery schedules and work item assignments across the team
      • Create user story stubs, tasks, and bugs in collaboration with leads and PMs; scrub the backlog and clear stale work
      • Prepare meeting invites, agendas, pre-reads, and status questions for recurring and ad hoc meetings
      • Update work items with decisions, owners, status, and next steps after every meeting or sync
      • Maintain action logs, reminders, and workflows; proactively follow up on blocked or at-risk work
      • Identify, escalate, and track risks, dependencies, and blockers; maintain up-to-date documentation in ADO
      • Represent features or workstreams in release forums alongside leads and PMs
      • Review release queries, clear stale work, update fields, and confirm next actions with feature owners
      • Consolidate changelog review posts, track feedback and open items, and confirm follow-up with feature owners
      • Partner with QA to coordinate validation and test plans, reproductions, regression tracking, and release dependencies
      • Track critical-path work, validation dependencies, readiness signals, release risks, and unresolved bugs
      • Coordinate dependencies, partner commitments, and technical initiatives across teams; escalate decisions when needed
      • Manage team velocity and capacity planning to support milestone delivery
      Then Requirements:

      Requirements

      • 2+ years of experience in engineering, product or technical program management, data analysis, product development, or as a producer (required)
      • 4+ years of experience in engineering, product or technical program management, data analysis, or product development, or equivalent experience (preferred)
      • 4+ years of experience managing cross-functional and/or cross-team projects (preferred)
      • Producer or TPM experience within a gaming studio (strongly preferred)
      • Bachelor's Degree in a relevant field required; equivalent professional experience will be considered
      • Deep familiarity with project tracking and documentation tools such as ADO, Jira, or Confluence for task management, sprint planning, and pipeline documentation
      • Strong working knowledge of Agile and Scrum frameworks including sprint planning, backlog grooming, velocity tracking, and retrospectives
      • Ability to bridge communication gaps between creative artists, engineers, and executive stakeholders
      • Proven capacity to motivate cross-functional teams and resolve conflicts under tight deadlines
      • Strong organizational skills with the ability to manage multiple workstreams simultaneously
      • Excellent written and verbal communication skills for status reporting, meeting facilitation, and async collaboration
      • Flexibility and adaptability to thrive in a fast-moving, evolving environment
      • Ability to identify risks early and escalate appropriately with clear context and proposed solutions
      Then Benefits:

      Benefits

      • Medical, dental & vision
      • Hospital plans
      • 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
      • Life Insurance (Company paid Basic Life and AD&D as well as voluntary Life & AD&D for the employee and dependents)
      • Company paid short and long-term disability
      • Health & Dependent Care Spending Accounts (HSA & DCFSA)
      • Employee Assistance Program
      • Time Off/Leave (PTO, Allegis Group Paid Family Leave, Parental Leave)
      Then Pay:

      Pay

      Pay Range*: $34.50 - $39 per hour

      Then Schedule:

      Schedule

      Weekly Schedule: 40 hours

      We need to ensure we don't include any boilerplate like "Benefits are subject to change..." etc. We removed that. We also need to ensure we didn't include "Job Status: Non-Exempt" or "Application Deadline". We omitted those. We also need to ensure we didn't include any duplicated lines. Now check if any content missing: The summary also mentioned "This is a fully remote, full-time contract position operating on Pacific Standard Time hours." We included that in About the role paragraph. We also included Location: Remote and Duration: 9 months in same paragraph. We preserved all substantive information: responsibilities list, requirements list, benefits list, pay range, schedule. We omitted the note about "Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's boilerplate; we removed. We omitted the EEO statement etc. We omitted the accommodation request line. We omitted the AI screening note. We omitted the Form I-9 etc. We omitted the "This Role Is Eligible For The Following Benefits" heading; we just used Benefits section. We omitted the "Additional Details" heading; we folded location/duration into About the role. We omitted the "Job Status: Non-Exempt". Could we include it as a minor metadata? The instruction says fold minor metadata into a short

      or drop it. We could add a short

      after About the role maybe containing "Job Status: Non-Exempt". But we already have About the role paragraph; we could add it there. However it's not essential; we can drop it as minor metadata. The instruction says we can drop it. So fine. Now check if any content about "Contract role providing services to Microsoft through external staffing partners of Allegis Global Solutions." That's substantive? It describes