Senior Technical Program Manager

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title. Must preserve all substantive info, remove boilerplate, duplicated lines, application instructions, EEO etc. We need to parse the posting. Content: - About Nebius: description of company. Could be "About the role"? Actually "About Nebius" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (maybe includes company overview and role description). We need to include substantive content. We have sections: - About Nebius (company description) - The role (description) - Travel note - Your Responsibilities Will Include (list) - Technical Scope & Expectations (paragraph + bullet list) - You are not expected to be an engineer... (paragraph) - We Expect You To Have (list) - It Will Be An Added Bonus If You Have (list) - Key Employee Benefits In The US (list) - Compensation (paragraph) - Join Nebius Today! Benefits & Perks (list) - What's It Like To Work At Nebius (list of adjectives) - Equal Opportunity Statement (boilerplate to remove) - Applicants must be authorized... (boilerplate to remove? It's about work authorization, maybe keep? It's not EEO but still legal. Probably remove as boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This includes work authorization? Might be considered legal. Safer to remove. We need to keep all substantive info: company description, role description, responsibilities, technical scope, expectations, bonus, benefits, compensation, perks, work culture. We must not include sections with filler like "commensurate with experience". Not present. We need to decide which sections to output. Potential sections: - About the role (could combine company overview and role description) - Responsibilities (list) - Technical Scope & Expectations (maybe under Requirements or Qualifications? Could be a separate section like "Technical Scope". But allowed headings are limited to those examples; we can still use those headings but we can also use other headings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? Likely we should only use those headings. So we need to map content to those headings. Thus we need to decide which of those headings have content. - About the role: can include company overview and role description. - Responsibilities: list of responsibilities. - Requirements: maybe the "We Expect You To Have" list (experience, background). - Qualifications: maybe the "It Will Be An Added Bonus If You Have" list (bonus qualifications). - Skills: maybe technical scope expectations? Could be skills. - Benefits: Key Employee Benefits In The US list. - Pay: Compensation paragraph. - Schedule: maybe travel note? Or schedule info? Not given. Could omit Schedule if no specific content. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have, Pay we have, Schedule we don't have explicit schedule (maybe travel note). So we omit Schedule. We must not emit a heading followed by filler/placeholder text. So ensure each heading has substantive content. Now we need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the lists. Let's extract content. Company overview: "About Nebius Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure. Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI. Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D." Role description: "The role As a Senior Technical Program Manager, you will own the end-to-end delivery of GPU clusters and other critical IT infrastructure components that power next-generation AI workloads. In this high-impact role, you’ll coordinate engineering, networking, construction, and operations teams to deliver GPU clusters and critical IT infrastructure at hyperscale. You’ll work closely with infrastructure leadership to define strategy, manage risk, and ensure on-time, high-quality launches. You’ll play a key role in scaling our global infrastructure footprint across the United States market. Travel: This position may require on-site presence at data centers during key deployment phases." Responsibilities list: "Your Responsibilities Will Include Lead end-to-end delivery of new data center programs, from design through handover to operations.Define and manage scope, schedule, and risks, maintaining focus on critical paths and proactive issue resolution.Translate business and technical requirements into actionable project plans and measurable deliverables.Oversee vendor and contractor execution, ensuring quality, budget, and schedule.Provide structured program reporting, including dashboards, documentation, and executive updates." Note there are missing periods; we need to keep as is but maybe add punctuation? We should preserve exactly; but we can keep as sentences separated by periods. The original had no spaces after periods? Actually there is missing spaces after periods. We'll keep as is but maybe we can add spaces for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding spaces is not changing meaning, but could be considered altering. Safer to keep exactly as given, but it's hard to read. However we can keep the text as is; it's still substantive. Technical Scope & Expectations: "This role requires hands-on experience with physical infrastructure delivery, not only software or coordination-based program management. You should be comfortable working across multiple layers of infrastructure, including: Data center environments: understanding of IT infrastructure readiness (power, cooling, space, and networking dependencies before hardware installation);Compute infrastructure: experience with large-scale server deployments (GPU-based systems are a strong plus);Networking: familiarity with high-bandwidth fabrics (e.g., InfiniBand or equivalent), cabling, and integration dependencies;Commissioning & bring-up: exposure to system validation, burn-in testing, and readiness criteria before handover to operations." Then paragraph: "You are not expected to be an engineer, but you should be able to: Engage in technical discussions confidently.Identify risks related to infrastructure readiness and sequencing.Challenge assumptions and drive resolution across engineering teams." We Expect You To Have list: "We Expect You To Have 7+ years of experience in technical program or project management, with direct involvement in large-scale IT infrastructure deployments.Solid technical background in relevant domains, with the ability to engage deeply in technical discussions and challenge solutions where needed.Proven ability to stay focused on critical paths and drive results in fast-paced, changing environments.Communication and stakeholder management skills; able to translate complex topics clearly.Leadership by influence and example in cross-functional or matrixed teams.Proficient with modern project management tools and methodologies (e.g., Jira, Asana, hybrid Agile/Waterfall)." It Will Be An Added Bonus If You Have list: "It Will Be An Added Bonus If You Have Understanding of construction projects structure and key risk factors in facility build-outs.Knowledge of HPCExperience in business processes design or automation tools development.PMP, PRINCE2, or similar industry certifications." Key Employee Benefits In The US list: "Key Employee Benefits In The US Health Insurance: 100% company-paid medical, dental, and vision coverage for employees and families.401(k) Plan: Up to 4% company match with immediate vesting.Parental Leave: 20 weeks paid for primary caregivers, 12 weeks for secondary caregivers.Remote Work Reimbursement: Up to $85/month for mobile and internet.Disability & Life Insurance: Company-paid short-term, long-term, and life insurance coverage." Compensation paragraph: "Compensation We offer competitive salaries ranging from $115K to $275K OTE, which includes base salary and performance bonus. Equity in the form of RSUs may be available at certain salary grades." Join Nebius Today! Benefits & Perks list: "Benefits & Perks Competitive compensationCareer growth and learning opportunitiesFlexibility and ownershipCollaborative and innovative cultureOpportunity to work on impactful AI projectsInternational environment and talented teams" What's It Like To Work At Nebius list: "What's It Like To Work At Nebius Fast moving - Bold thinking - Constant growth - Meaningful impact - Trust and real ownership - Opportunity to shape the future of AI" We need to avoid duplication: Benefits & Perks overlaps with Benefits section; but we have already Benefits section (Key Employee Benefits In The US). The Benefits & Perks list includes items like Competitive compensation (already covered in Pay), Career growth..., Flexibility..., Collaborative..., Opportunity..., International..., etc. These are substantive and not in Benefits section. So we could include them under Skills? Or maybe under Qualifications? But we have limited headings. Could we create a section "Skills" for these? The Skills heading could contain these perks? Not exactly skills. But we could put them under "Skills" as they are not skills but perks. However instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but suggests using those. Safer to stick to those. We could put the "Benefits & Perks" under Benefits heading as additional benefits beyond the US-specific ones. But we already have Benefits heading for US benefits; we can combine both under Benefits heading, listing both US-specific benefits and general perks. That would be okay. Similarly, "What's It Like To Work At Nebius" could be under Skills? Not really. Could be under Qualifications? Not. Could be under About the role? Maybe we can add a short paragraph about work culture under About the role. But we already have About the role with company overview and role description; we could append culture description there. Thus we can have sections: - About the role (company overview + role description + travel + work culture description) - Responsibilities (list) - Requirements (We Expect You To Have) - Qualifications (It Will Be An Added Bonus If You Have) - Skills (Technical Scope & Expectations + the "You are not expected to be an engineer..." paragraph) - Benefits (Key Employee Benefits In The US + Benefits & Perks list) - Pay (Compensation paragraph) We must not include Schedule. Now we need to format lists with

• . For each bullet, we need to separate items. The original lists are semicolon-separated or period-separated without clear bullet. We need to parse into items. Responsibilities list: items separated by periods? Actually each responsibility ends with a period but missing spaces. Let's split by period then trim. Text: "Lead end-to-end delivery of new data center programs, from design through handover to operations.Define and manage scope, schedule, and risks, maintaining focus on critical paths and proactive issue resolution.Translate business and technical requirements into actionable project plans and measurable deliverables.Oversee vendor and contractor execution, ensuring quality, budget, and schedule.Provide structured program reporting, including dashboards, documentation, and executive updates." Split by '.' yields: 1. Lead end-to-end delivery of new data center programs, from design through handover to operations 2. Define and manage scope, schedule, and risks, maintaining focus on critical paths and proactive issue resolution