Technical Project Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The "Position Overview/Mandate" and "Make an Impact with Us" maybe. Could be combined as About the role.
- Responsibilities: "What You'll Be Doing:" bullet list.
- Requirements: "Who You Are:" bullet list (minimum experience, degree, etc.)
- Qualifications: maybe "Completed or working towards PMP is an asset", "Completion of an Engineering degree and previous technical engineering experience is an asset". Could be Qualifications.
- Skills: maybe "Excellent organizational, communication, and interpersonal skills", "Proven track record managing large projects using project management methodologies", "Experience using project management tracking software, such as Microsoft Project". Could be Skills.
- Benefits: "Benefits Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits."
- Pay: Not specified. No mention of salary. So we should NOT include Pay section.
- Schedule: Not specified. No mention of schedule. So no Schedule.
- Location and travel: Could be part of About the role or maybe separate but not in list. Not required heading.
We must not create sections with placeholder text. So only include sections with content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info; do not invent or summarize away detail.
Let's extract content precisely.
First, "About the role": combine Position Overview/Mandate and Make an Impact with Us.
Position Overview/Mandate text:
"The Project Manager plays a key role in planning, coordinating, and delivering complex development projects for Fidus clients, from initial scope through to final delivery. You will work directly with customers, Sales, and Fidus's technical teams to manage project scope, schedule, and budget, and to keep everyone aligned as the project moves from design through implementation. This role is ideal for someone who thrives on project diversity, enjoys building strong relationships across technical and business teams, and takes pride in delivering projects on time, on budget, and to a high standard."
Make an Impact with Us:
"At Fidus, you'll lead high-speed, high-complexity electronic system projects, often built on emerging technologies before they reach the broader market. You'll coordinate cross-functional teams spanning FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout, and mechanical/thermal design to deliver real products for our clients. In practice, that means managing projects in areas such as space and satellite systems, next-generation communications and networking, high-performance compute and storage platforms, advanced video, imaging, VR/AR applications, and industrial, medical, and automotive systems. You won't be limited to a single product or industry — your work will follow the technology, not just one roadmap."
We need to preserve all details. Let's copy exactly.
Now Responsibilities: "What You'll Be Doing:" list:
- Plan, deliver, and manage multiple concurrent projects ranging in size from medium to large
- Coordinate project teams that may be distributed across multiple location sites and disciplines
- Forge strong partnerships with Sales, the Customer, and the Project Team to ensure efficiency across all aspects of the project
- Work closely with Sales and Technical Leads to understand project requirements
- Take independent ownership of project decisions related to scope, schedule, and budget
- Regularly update customers and internal management on project status via meetings and/or reports
- Manage project process and resources, including budget and schedules, from design and development through implementation
- Identify process gaps and implement process improvements at the project level
- Manage technical negotiations with suppliers
We need to preserve bullet points exactly.
Now Requirements: "Who You Are:" list:
- Minimum of five (5) years of relevant technical industry experience, including at least three (3) years of Project Management experience
- University degree or equivalent
- Proven track record managing large projects using project management methodologies
- Excellent organizational, communication, and interpersonal skills
- Demonstrated delivery of innovative solutions to project challenges
- Experience using project management tracking software, such as Microsoft Project
- Completed or working towards PMP is an asset
- Completion of an Engineering degree and previous technical engineering experience is an asset
Note: Some of these could be Qualifications or Skills. But we can separate.
We need sections: Requirements, Qualifications, Skills. The instruction says use headings for those if content exists.
We need to decide what goes where.
Typically: Requirements = mandatory qualifications. Qualifications = preferred qualifications. Skills = specific abilities.
From list, mandatory: Minimum 5 years experience inc 3 years PM, University degree or equivalent, Proven track record managing large projects using PM methodologies, Excellent organizational, communication, interpersonal skills, Demonstrated delivery of innovative solutions, Experience using PM tracking software such as MS Project.
Preferred/assets: Completed or working towards PMP is an asset, Completion of an Engineering degree and previous technical engineering experience is an asset.
Thus:
Requirements (mandatory) list those 6 items.
Qualifications (preferred) list the two asset items.
Skills: maybe we could list "Excellent organizational, communication, and interpersonal skills" but that's already in Requirements. Could also list "Proven track record managing large projects using project management methodologies" etc. But we might not need a separate Skills section if we already covered. However instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. But we have headings for Skills; we could omit if no distinct content beyond what's already covered. However we have "Excellent organizational, communication, and interpersonal skills" which is a skill; but it's also a requirement. Could still be in Requirements.
Thus we may not need a separate Skills section. But we need to check if any skill not captured elsewhere: maybe "Experience using project management tracking software, such as Microsoft Project" is a skill. Could be in Requirements.
Thus we can omit Skills section.
Now Benefits: we have paragraph.
Now Location and travel: Not a required heading; we could embed in About the role as a paragraph? The instruction: only include sections when posting has real, specific content for it. Location and travel is not in the list of headings we must use; we could just include as a paragraph under About the role or separate
without heading. It's okay to have extra paragraphs not under headings? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid other paragraphs without heading. So we can include location/travel as a
after About the role.
Now we need to remove boilerplate: navigation, cookie, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "About Fidus & Why Work Here" etc? That's company description; maybe we can keep as part of About the role? But it's not about the role; it's about company. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep company description? It's substantive but not about the role. However the headings list does not include "About the company". Could we include it as a paragraph without heading? Probably yes. But we need to decide if we should include it. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description. It's not boilerplate; it's about Fidus. So we can include a
about Fidus after the role sections.
But we must not include EEO/equal-opportunity/scam-warning boilerplate. The later part includes: "Fidus has a commitment to ensure a fair and transparent recruitment process..." and "Thank you for your interest..." and "We welcome and encourage diverse candidates..." and "Accommodations are available..." and "Fidus is committed to creating a diverse environment..." That's EEO boilerplate; we should remove that.
Also remove "Automated tools (including AI) support our initial screening..." etc. That's also boilerplate.
Thus we keep: company description since 2001, projects completed, Premier Adaptive Computing Partner for AMD, etc. That's substantive.
Now we need to format.
Structure:
About the role
Position Overview/Mandate: ...
Make an Impact with Us: ...
Location and travel: Fully remote role and travel may be required domestically and internationally to support customer engagements and project delivery.
Then Responsibilities
list items.
Then Requirements
list mandatory items.
Then Qualifications
list preferred/assets.
Then Benefits
Benefits Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits.
Then maybe About Fidus
but not in allowed headings list. Could we use About Fidus
? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; but we could still use other headings? Safer to stick to those. So we should not create a heading for About Fidus; we can just put a
about Fidus without heading.
Thus final HTML fragment:
About the role
Position Overview/Mandate: The Project Manager plays a key role in planning, coordinating, and delivering complex development projects for Fidus clients, from initial scope through to final delivery. You will work directly with customers, Sales, and Fidus's technical teams to manage project scope, schedule, and budget, and to keep everyone aligned as the project moves from design through implementation. This role is ideal for someone who thrives on project diversity, enjoys building strong relationships across technical and business teams, and takes pride in delivering projects on time, on budget, and to a high standard.
Make an Impact with Us: At Fidus, you'll lead high-speed, high-complexity electronic system projects, often built on emerging technologies before they reach the broader market. You'll coordinate cross-functional teams spanning FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout, and mechanical/thermal design to deliver real products for our clients. In practice, that means managing projects in areas such as space and satellite systems, next-generation communications and networking, high-performance compute and storage platforms, advanced video, imaging, VR/AR applications, and industrial, medical, and automotive systems. You won't be limited to a single product or industry — your work will follow the technology, not just one roadmap.
Location and travel: Fully remote role and travel may be required domestically and internationally to support customer engagements and project delivery.
Responsibilities
- Plan, deliver, and manage multiple concurrent projects ranging in size from medium to large
- Coordinate project teams that may be distributed across multiple location sites and disciplines
- Forge strong partnerships with Sales, the Customer, and the
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive info; do not invent or summarize away detail. Let's extract content precisely. First, "About the role": combine Position Overview/Mandate and Make an Impact with Us. Position Overview/Mandate text: "The Project Manager plays a key role in planning, coordinating, and delivering complex development projects for Fidus clients, from initial scope through to final delivery. You will work directly with customers, Sales, and Fidus's technical teams to manage project scope, schedule, and budget, and to keep everyone aligned as the project moves from design through implementation. This role is ideal for someone who thrives on project diversity, enjoys building strong relationships across technical and business teams, and takes pride in delivering projects on time, on budget, and to a high standard." Make an Impact with Us: "At Fidus, you'll lead high-speed, high-complexity electronic system projects, often built on emerging technologies before they reach the broader market. You'll coordinate cross-functional teams spanning FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout, and mechanical/thermal design to deliver real products for our clients. In practice, that means managing projects in areas such as space and satellite systems, next-generation communications and networking, high-performance compute and storage platforms, advanced video, imaging, VR/AR applications, and industrial, medical, and automotive systems. You won't be limited to a single product or industry — your work will follow the technology, not just one roadmap." We need to preserve all details. Let's copy exactly. Now Responsibilities: "What You'll Be Doing:" list: - Plan, deliver, and manage multiple concurrent projects ranging in size from medium to large - Coordinate project teams that may be distributed across multiple location sites and disciplines - Forge strong partnerships with Sales, the Customer, and the Project Team to ensure efficiency across all aspects of the project - Work closely with Sales and Technical Leads to understand project requirements - Take independent ownership of project decisions related to scope, schedule, and budget - Regularly update customers and internal management on project status via meetings and/or reports - Manage project process and resources, including budget and schedules, from design and development through implementation - Identify process gaps and implement process improvements at the project level - Manage technical negotiations with suppliers We need to preserve bullet points exactly. Now Requirements: "Who You Are:" list: - Minimum of five (5) years of relevant technical industry experience, including at least three (3) years of Project Management experience - University degree or equivalent - Proven track record managing large projects using project management methodologies - Excellent organizational, communication, and interpersonal skills - Demonstrated delivery of innovative solutions to project challenges - Experience using project management tracking software, such as Microsoft Project - Completed or working towards PMP is an asset - Completion of an Engineering degree and previous technical engineering experience is an asset Note: Some of these could be Qualifications or Skills. But we can separate. We need sections: Requirements, Qualifications, Skills. The instruction says use headings for those if content exists. We need to decide what goes where. Typically: Requirements = mandatory qualifications. Qualifications = preferred qualifications. Skills = specific abilities. From list, mandatory: Minimum 5 years experience inc 3 years PM, University degree or equivalent, Proven track record managing large projects using PM methodologies, Excellent organizational, communication, interpersonal skills, Demonstrated delivery of innovative solutions, Experience using PM tracking software such as MS Project. Preferred/assets: Completed or working towards PMP is an asset, Completion of an Engineering degree and previous technical engineering experience is an asset. Thus: Requirements (mandatory) list those 6 items. Qualifications (preferred) list the two asset items. Skills: maybe we could list "Excellent organizational, communication, and interpersonal skills" but that's already in Requirements. Could also list "Proven track record managing large projects using project management methodologies" etc. But we might not need a separate Skills section if we already covered. However instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. But we have headings for Skills; we could omit if no distinct content beyond what's already covered. However we have "Excellent organizational, communication, and interpersonal skills" which is a skill; but it's also a requirement. Could still be in Requirements. Thus we may not need a separate Skills section. But we need to check if any skill not captured elsewhere: maybe "Experience using project management tracking software, such as Microsoft Project" is a skill. Could be in Requirements. Thus we can omit Skills section. Now Benefits: we have paragraph. Now Location and travel: Not a required heading; we could embed in About the role as a paragraph? The instruction: only include sections when posting has real, specific content for it. Location and travel is not in the list of headings we must use; we could just include as a paragraph under About the role or separate
without heading. It's okay to have extra paragraphs not under headings? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid other paragraphs without heading. So we can include location/travel as a
after About the role. Now we need to remove boilerplate: navigation, cookie, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "About Fidus & Why Work Here" etc? That's company description; maybe we can keep as part of About the role? But it's not about the role; it's about company. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep company description? It's substantive but not about the role. However the headings list does not include "About the company". Could we include it as a paragraph without heading? Probably yes. But we need to decide if we should include it. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description. It's not boilerplate; it's about Fidus. So we can include a
about Fidus after the role sections. But we must not include EEO/equal-opportunity/scam-warning boilerplate. The later part includes: "Fidus has a commitment to ensure a fair and transparent recruitment process..." and "Thank you for your interest..." and "We welcome and encourage diverse candidates..." and "Accommodations are available..." and "Fidus is committed to creating a diverse environment..." That's EEO boilerplate; we should remove that. Also remove "Automated tools (including AI) support our initial screening..." etc. That's also boilerplate. Thus we keep: company description since 2001, projects completed, Premier Adaptive Computing Partner for AMD, etc. That's substantive. Now we need to format. Structure:
About the role
Position Overview/Mandate: ...
Make an Impact with Us: ...
Location and travel: Fully remote role and travel may be required domestically and internationally to support customer engagements and project delivery.
ThenResponsibilities
- list items.
Then
- Plan, deliver, and manage multiple concurrent projects ranging in size from medium to large
- Coordinate project teams that may be distributed across multiple location sites and disciplines
- Forge strong partnerships with Sales, the Customer, and the
Requirements
- list mandatory items.
Then
Qualifications
- list preferred/assets.
Then
Benefits
Benefits Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits.
Then maybeAbout Fidus
but not in allowed headings list. Could we useAbout Fidus
? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; but we could still use other headings? Safer to stick to those. So we should not create a heading for About Fidus; we can just put a
about Fidus without heading. Thus final HTML fragment:
About the role
Position Overview/Mandate: The Project Manager plays a key role in planning, coordinating, and delivering complex development projects for Fidus clients, from initial scope through to final delivery. You will work directly with customers, Sales, and Fidus's technical teams to manage project scope, schedule, and budget, and to keep everyone aligned as the project moves from design through implementation. This role is ideal for someone who thrives on project diversity, enjoys building strong relationships across technical and business teams, and takes pride in delivering projects on time, on budget, and to a high standard.
Make an Impact with Us: At Fidus, you'll lead high-speed, high-complexity electronic system projects, often built on emerging technologies before they reach the broader market. You'll coordinate cross-functional teams spanning FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout, and mechanical/thermal design to deliver real products for our clients. In practice, that means managing projects in areas such as space and satellite systems, next-generation communications and networking, high-performance compute and storage platforms, advanced video, imaging, VR/AR applications, and industrial, medical, and automotive systems. You won't be limited to a single product or industry — your work will follow the technology, not just one roadmap.
Location and travel: Fully remote role and travel may be required domestically and internationally to support customer engagements and project delivery.
Responsibilities
- for any list of duties/requirements/benefits, and