Project Manager for Software

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About PassiveLogic (company description) maybe not needed as a heading? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include sections that correspond to those headings if content exists. We have "About The Role" heading in the posting. That's "About the role". So we can create

About the role

with content describing role. Then "What You’ll Do" is responsibilities. So

Responsibilities

with list. Then "What You’ll Bring" includes requirements, qualifications, skills, etc. We need to split into Requirements, Qualifications, Skills maybe. The posting includes many bullet-like statements. We need to decide how to categorize. We have "You must have Proven experience:" list: 5+ years experience managing software projects, technical background BS/MS, experience using project management methods, exceptional communication skills, organized and strategic, collaborative mindset, adaptability, problem solving. Then "You should have Experience shipping software:" list: Demonstrated ability to deliver reliable software releases, strong software project management skills, documentation and user stories experience, leadership abilities, commitment to continual self-investment, alignment with leadership, passion for software quality and sustainability. Then "It’s helpful to have Technical knowledge:" list: Working knowledge of SDLC, APIs, cloud platforms, CI/CD, QA, release management, collaboration tools; ability to explain strengths/weaknesses; Experience with managing Agile or hybrid software delivery; tracking dependencies, risks, budgets, release readiness; using delivery metrics and retrospectives. Thus we can categorize: Requirements (must have), Qualifications (should have), Skills (helpful to have). Or we could combine. We also have Compensation, Benefits & Perks section: includes Competitive compensation, Generous equity share package, Medical, dental and vision coverage, Disability and life Insurance options, Flex PTO, Team-building events, Free catered lunch, Free ski pass, Free National Park pass. That's benefits. No explicit Pay or Schedule details besides maybe compensation but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, so we can include Benefits section. Pay: not specific numbers, just "Competitive compensation" which is vague but maybe considered stating compensation? It says "Competitive compensation". That is a statement about pay but not specific. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive compensation" could be considered placeholder? It's vague but not exactly placeholder like "commensurate with experience". Might be okay but safer to omit Pay section because not specific. Schedule: not mentioned. So we omit Pay and Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all points from each section. We need to be careful not to include boilerplate like "Diversity and inclusion" etc. That's EEO boilerplate; we should remove. Also remove application instructions (cover letter, resume, extra mile). Also remove "When applying, include:" etc. Also remove "Diversity and inclusion" paragraph. Also remove "We know there are candidates who might not fit everything..." maybe that's not boilerplate but it's encouraging to apply; could be considered part of "What You’ll Bring"? It's more about flexibility. Might be considered substantive? It's encouraging to apply even if not meet all requirements. Could be kept under Requirements? But it's more about flexibility. Might be considered boilerplate? I'd say it's not essential detail about the role; it's a generic statement. Safer to remove. Also remove "PassiveLogic can sometimes be flexible enough to shift responsibilities..." etc. That's also generic. Thus we keep only the core descriptive content. Now craft HTML. Structure:

  About the role

  ... content from About The Role paragraph(s).

  Then

  Responsibilities

  • ... each duty from What You’ll Do.
  Then

  Requirements

  • ... from "You must have Proven experience:" list.
  Then

  Qualifications

  • ... from "You should have Experience shipping software:" list.
  Then

  Skills

  • ... from "It’s helpful to have Technical knowledge:" list.
  Then

  Benefits

  • ... from Compensation, Benefits & Perks list (excluding "Competitive compensation" maybe? but that is compensation; we could include as benefit? It's compensation. Since we omitted Pay, we could include compensation as part of Benefits? Might be okay. But better to include compensation as a bullet under Benefits? The instruction says only create Benefits section if posting actually states them. It does state benefits and compensation. So we can include compensation as a bullet. We'll include all items: Competitive compensation, Generous equity share package, Medical, dental and vision coverage, Disability and life Insurance options, Flex PTO, Team-building events, Free catered lunch in the office Monday — Friday, Free ski pass (We are at the base of Big Cottonwood Canyon), Free National Park pass.
  Make sure to preserve punctuation. Now write the prose for About the role: The posting says: "About The Role This is a career-defining opportunity to play a crucial role in a hyper-scale AI company that is transforming the future of autonomous systems, energy, and the built environment. As a Software Project Manager at PassiveLogic, you will guide cross-functional teams through the software delivery lifecycle. You will maintain delivery plans, coordinate dependencies, manage risks, and balance long-term platform goals with near-term releases." We can combine into a paragraph. Now responsibilities list: each bullet from "What You’ll Do". Let's extract: - Help software teams move forward when complexity slows progress: Use your technical fluency and project leadership to clear blockers, resolve dependencies, and keep teams focused on valuable, reliable releases. - Approach problem-solving with a bias for action and data-driven decision-making, even when conditions are imperfect. - Lead software planning and execution: Build and maintain project plans, milestones, and delivery roadmaps. Guide cross-functional teams through structured workstreams, clarify ownership, and keep stakeholders accountable to scope, schedule, quality, and business outcomes. - Drive delivery with a focus on exceptional user experience: Partner with product, design, and engineering to translate customer needs into sequenced work while balancing user experience, technical constraints, quality, and timely delivery. - Support design and validate readiness: Help product, design, engineering, and quality teams turn approved designs into clear requirements, acceptance criteria, and release plans. Verify that delivered software aligns with the intended experience. - Give teams the visibility they need to make good decisions: Clearly communicate plans, progress, risks, dependencies, decisions, and roadblocks. Produce concise reporting that supports timely decisions and keeps stakeholders aligned. - Improve delivery with modern tools and practices: Evaluate software delivery trends and introduce practical improvements that help teams plan and release more effectively. We need to keep each as separate
• . Ensure we keep the colon and details. Now Requirements list from "You must have Proven experience:": - Proven experience: 5+ years of experience managing software projects, programs, or product delivery. - A technical background, including a BS/MS or equivalent experience in computer science, software engineering, information systems, or a related field - Experience using project management methods and understanding when to apply each approach (Agile, Scrum, Kanban, or waterfall) - Exceptional Communication Skills: You translate business and technical goals into clear plans, decisions, and next steps. You communicate risks, dependencies, and tradeoffs with precision, adapting the level of detail for engineering teams, partners, and leadership. - Organized and strategic: Skilled in creating project roadmaps, managing timelines, and ensuring deliverables meet both technical and user expectations. - Collaborative mindset: Work closely with UI/UX, front end, back end, sales, and customer success teams to define work streams that align with customer releases. You will work hand in glove with the project managers to ensure the work plan supports the technical road map. - Adaptability: Comfortable in a fast-paced startup environment, eager to learn, iterate, and innovate. - Problem solving: You own this role. When issues arise, be the empowered force that solves them, rolling-up. (The text: "You should have Experience shipping software:" Actually that's later. Wait the problem solving bullet is under "You must have"? Let's re-check: In the text: "Problem solving: You own this role. When issues arise, be the empowered force that solves them, rolling-up." Actually that appears under "You should have Experience shipping software:"? Let's scroll: After "Adaptability:" there is "Problem solving: You own this role. When issues arise, be the empowered force that solves them, rolling-up." Then "You should have Experience shipping software:" So the problem solving bullet is part of "You must have"? Actually the original text: "You must have Proven experience: 5+ years of experience managing software projects, programs, or product delivery. A technical background, including a BS/MS or equivalent experience in computer science, software engineering, information systems, or a related field Experience using project management methods and understanding when to apply each approach (Agile, Scrum, Kanban, or waterfall) Exceptional Communication Skills: You translate business and technical goals into clear plans, decisions, and next steps. You communicate risks, dependencies, and tradeoffs with precision, adapting the level of detail for engineering teams, partners, and leadership. Organized and strategic: Skilled in creating project roadmaps, managing timelines, and ensuring deliverables meet both technical and user expectations. Collaborative mindset: Work closely with UI/UX, front end, back end, sales, and customer success teams to define work streams that align with customer releases. You will work hand in glove with the project managers to ensure the work plan supports the technical road map. Adaptability: Comfortable in a fast-paced startup environment, eager to learn, iterate, and innovate. Problem solving: You own this role. When issues arise, be the empowered force that solves them, rolling-up. You should have Experience shipping software: Demonstrated ability to deliver reliable software releases in a complex, cross-functional environment. Strong software project management skills: Proven expertise aligning scope, schedules, resources, risks, and delivery with business goals. Documentation and user stories experience: Skilled at creating clear project documentation, actionable user stories, acceptance criteria, and test cases that support successful execution. Leadership abilities and aspirations: You build trust, create accountability, and help teams succeed by sharing context, resolving blockers, and improving how work gets done. You are eager to grow as a software delivery leader and champion. Commitment to continual self-investment in software delivery: A track record of staying current with emerging practices, tools, and technologies in software development and project management. Alignment with leadership: Ability to keep leaders aligned on product vision, priorities, risks, and delivery goals throughout the development process. Passion for software quality and sustainability: Strong interest in building dependable, human-centered software while considering maintainability, efficiency, and long-term impact." Thus the "Problem solving:" bullet belongs to the "You must have" list (since it's before "You should have Experience shipping software:"). Thus Requirements