IT Project Manager
Ardham Technologies · Albuquerque, NM · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually job summary is prose. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We have job summary (prose). Then Key Responsibilities (list). Then Required Experience & Education (list). Then Preferred Project Management Certifications (list). Then About Ardham Technologies (prose). Then mention about survey (application instruction) - we must remove application instructions. So we drop that line.
We need to map content to sections.
We have no explicit Benefits, Pay, Schedule. So we should not include those sections.
We have "About Ardham Technologies" which could be "About the role"? Actually "About the role" is generic; but we have job summary describing role. Could use "About the role" heading for job summary. Or we could use "About Ardham Technologies" as a separate section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
Thus:
-
. The responsibilities are listed under "Key Responsibilities" with subheadings like Project Initiation & Planning, Project Execution & Delivery, etc. We can treat each bullet as a list item. We'll need to parse the text.
Let's extract responsibilities:
From "Key Responsibilities" section:
Project Initiation & Planning
- Lead the transition of sold work from Sales and Pre-Sales/Professional Services into delivery, confirming the statement of work, assumptions, exclusions, deliverables, acceptance criteria, budget, timeline, dependencies, and customer responsibilities before execution begins
- Conduct project kickoff meetings and establish clear governance, stakeholder roles, communication cadence, escalation paths, decision authority, and working agreements
- Develop and maintain project plans, schedules, milestones, work breakdown structures, resource forecasts, and dependency maps appropriate to project size and complexity
- Confirm that engineering resources, customer contacts, procurement requirements, licensing, equipment, site readiness, access, maintenance windows, and third-party dependencies are aligned before work is scheduled
- Establish and maintain the project record, including project charter or initiation documentation, stakeholder register, baseline schedule, budget, RAID log, change log, decision log, and communications plan
- Scope, Financial & Change Control
- Risk, Issue & Quality Management
- Customer & Stakeholder Management
- Resource, Capacity & Cross-Functional Coordination
- Documentation, Systems & Process Improvement
Project Execution & Delivery
- Manage multiple concurrent client projects across infrastructure, networking, cloud, Microsoft 365, cybersecurity, storage, virtualization, data center, endpoint, and related professional services engagements
- Coordinate day-to-day execution across engineers, customers, vendors, subcontractors, procurement, account management, and managed services while maintaining clear ownership of actions and deadlines
- Facilitate status meetings, working sessions, readiness reviews, cutover planning, and post-implementation reviews; distribute concise notes, decisions, action items, owners, and due dates promptly
- Track progress against the approved baseline, identify schedule or delivery variance, and drive corrective actions without assuming technical ownership that belongs to engineering
- Ensure customer decisions, technical prerequisites, access requirements, approvals, deliverables, and acceptance evidence are secured at the appropriate stage of the project
- Coordinate change windows, implementation communications, rollback planning, and business-impact awareness with technical leads and customer stakeholders
Thus we have many items; some are just headings like "Scope, Financial & Change Control" etc. Those appear as subheadings but not detailed. We could treat them as list items as they appear. However they may be considered headings within responsibilities; but we need to output list items only. We could keep them as list items even if they are brief.
Better to extract each line that starts with a capital letter and ends with a period? Many lines lack period. We'll just treat each bullet as list item.
We'll need to produce for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also use other headings but better to stick to those. So we need to fit Ardham Technologies description somewhere. Could be part of About the role? Or we could create a section "About Ardham Technologies" but that's not in the list; maybe we should avoid extra headings. Could we treat it as part of About the role? The About the role heading is for role description; Ardham Technologies is company description. Might be better to put under "About the role" as additional paragraph. But the instruction says "About the role" heading for section headings (e.g. About the role...). It doesn't forbid adding other headings, but we should prefer those. However we could add a heading "About Ardham Technologies" if we think it's substantive. The instruction says "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We have job summary (prose). Then Key Responsibilities (list). Then Required Experience & Education (list). Then Preferred Project Management Certifications (list). Then About Ardham Technologies (prose). Then mention about survey (application instruction) - we must remove application instructions. So we drop that line.
We need to map content to sections.
We have no explicit Benefits, Pay, Schedule. So we should not include those sections.
We have "About Ardham Technologies" which could be "About the role"? Actually "About the role" is generic; but we have job summary describing role. Could use "About the role" heading for job summary. Or we could use "About Ardham Technologies" as a separate section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
Thus:
- About the role
: contains job summary prose.
- Responsibilities
: list of key responsibilities (the bullet points). The posting has many responsibilities in paragraphs; we need to extract list items. We'll need to convert each responsibility sentence into
- ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also use other headings but better to stick to those. So we need to fit Ardham Technologies description somewhere. Could be part of About the role? Or we could create a section "About Ardham Technologies" but that's not in the list; maybe we should avoid extra headings. Could we treat it as part of About the role? The About the role heading is for role description; Ardham Technologies is company description. Might be better to put under "About the role" as additional paragraph. But the instruction says "About the role" heading for section headings (e.g. About the role...). It doesn't forbid adding other headings, but we should prefer those. However we could add a heading "About Ardham Technologies" if we think it's substantive. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed. But to be safe, we could include a heading "About Ardham Technologies". However the instruction says "Prefer a few substantive sections over many thin ones." Adding a separate heading for company description is fine.
Thus sections:
- About the role (job summary)
- Responsibilities (list)
- Requirements (Required Experience & Education)
- Qualifications (Preferred Project Management Certifications)
- About Ardham Technologies (company description)
We should not include Benefits, Pay, Schedule.
Now we need to ensure we don't include boilerplate like "As part of our hiring process, you must first complete a quick (~10-minute) online survey via Culture Index." That's application instruction; remove.
Also remove duplicated lines.
Now craft HTML.
We'll need to escape any HTML special characters? Not needed.
Let's write:
About the role
About the role
The IT Project Manager is responsible for leading client technology projects from internal handoff and initiation through planning, execution, acceptance, transition, and closeout. Operating in a fast-paced Value-Added Reseller (VAR), Managed Services Provider (MSP), and IT consulting environment, this role coordinates customers, engineers, vendors, procurement, sales, and managed services to deliver defined outcomes on time, within scope, and within approved financial parameters. The ideal candidate combines disciplined project governance with practical judgment, strong customer leadership, and enough technical fluency to manage infrastructure, cloud, cybersecurity, network, data center, and workplace technology initiatives. This position owns the project management process and project communication; technical design and engineering decisions remain with the assigned technical resources. Success requires consistent follow-up, early escalation, accurate records, and a strong commitment to customer experience and accountability.
Responsibilities
- Lead the transition of sold work from Sales and Pre-Sales/Professional Services into delivery, confirming the statement of work, assumptions, exclusions, deliverables, acceptance criteria, budget, timeline, dependencies, and customer responsibilities before execution begins
- Conduct project kickoff meetings and establish clear governance, stakeholder roles, communication cadence, escalation paths, decision authority, and working agreements
- Develop and maintain project plans, schedules, milestones, work breakdown structures, resource forecasts, and dependency maps appropriate to project size and complexity
- Confirm that engineering resources, customer contacts, procurement requirements, licensing, equipment, site readiness, access, maintenance windows, and third-party dependencies are aligned before work is scheduled
- Establish and maintain the project record, including project charter or initiation documentation, stakeholder register, baseline schedule, budget, RAID log, change log, decision log, and communications plan
- Scope, Financial & Change Control
- Risk, Issue & Quality Management
- Customer & Stakeholder Management
- Resource, Capacity & Cross-Functional Coordination
- Documentation, Systems & Process Improvement
- Manage multiple concurrent client projects across infrastructure, networking, cloud, Microsoft 365, cybersecurity, storage, virtualization, data center, endpoint, and related professional services engagements
- Coordinate day-to-day execution across engineers, customers, vendors, subcontractors, procurement, account management, and managed services while maintaining clear ownership of actions and deadlines
- Facilitate status meetings, working sessions, readiness reviews, cutover planning, and post-implementation reviews; distribute concise notes, decisions, action items, owners, and due dates promptly
- Track progress against the approved baseline, identify schedule or delivery variance, and drive corrective actions without assuming technical ownership that belongs to engineering
- Ensure customer decisions, technical prerequisites, access requirements, approvals, deliverables, and acceptance evidence are secured at the appropriate stage of the project
- Coordinate change windows, implementation communications, rollback planning, and business-impact awareness with technical leads and customer stakeholders
Requirements
- 5+ years of project management experience, including responsibility for customer-facing IT infrastructure, cloud, cybersecurity, network, or professional services projects; VAR, MSP, systems integrator, or IT consulting experience strongly preferred
- Demonstrated success managing multiple concurrent projects with competing priorities, shared technical resources, external dependencies, and customer-facing deadlines
- Working knowledge of predictive, agile, and hybrid project delivery approaches and the judgment to scale governance to the size, risk, and complexity of the engagement
- Experience managing scope, schedules, budgets, labor forecasts, risks, issues, changes, vendors, customer communications, and formal project closeout
- Information Technology, Project Management, Management Information Systems, or a related field preferred; equivalent combination of education, certification, and relevant experience will be considered
Qualifications
- Project Management Professional (PMP) certification is strongly preferred
- Certified Associate in Project Management (CAPM) may be considered for candidates with strong directly relevant IT project experience who are actively progressing toward PMP certification
- PMI Agile Certified Practitioner (PMI-ACP), Certified ScrumMaster (CSM), PRINCE2, or comparable agile/project delivery certification is beneficial
- ITIL Foundation or comparable IT service management certification is beneficial, particularly for projects transitioning into managed services
About Ardham Technologies
Ardham Technologies is headquartered in