Lead, Application
Aecon U.S. · Charlotte, NC · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, EEO, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see if posting mentions Pay, Schedule, Benefits. It mentions benefits: "At Aecon We Ensure you and your family receive the services and benefits needed to support your mental, emotional, and physical well-being." Also mentions Aecon University, tuition reimbursement, Leadership Programs. So benefits exist. Pay? Not mentioned. Schedule? Not mentioned. So we can include Benefits section. Also maybe "About the role" could be a summary. The posting includes introductory paragraphs about Aecon, safety, values, etc. That could be "About the role" or "About Aecon". But we need to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which are appropriate. The posting includes "What is the Opportunity?" then description of role. That could be About the role. Then "What You'll Do Here" is responsibilities. Then "What You Bring To The Team" includes requirements, qualifications, skills. Could split into Requirements (experience), Qualifications (maybe education?), Skills (competencies). The posting includes "Key Competencies". Also "Additional Requirements". We'll need to map.
We must not invent sections; only include if there is real specific content. So we can include About the role (the opportunity description). Responsibilities (What You'll Do Here). Requirements (What You Bring To The Team - experience). Qualifications maybe not distinct; could combine with Requirements. Skills (Key Competencies). Benefits (the paragraph about benefits, tuition reimbursement, etc.). No Pay or Schedule.
We must preserve all substantive info; not omit details. Must not include boilerplate like EEO statements, safety always repeated, etc. Must remove duplicated lines. Must not include navigation/cookie etc. Must not include application instructions. Must not include EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
First, introductory fluff about Aecon: "Come Build Your Career at Aecon! Aecon delivers some of the most complex and impactful infrastructure projects — from transformative transportation networks to critical energy, industrial and nuclear programs. The projects we build connect communities and power future generations. With deep roots in North America and a strong footprint internationally, Aecon brings global expertise and proudly serves public and private sector clients through its Construction and Concessions segment. Safety Always is not only our #1 core value – it is the standard that anchors our culture. We believe the most ambitious projects deserve the most committed people. At Aecon, you won’t just build your career — you’ll help build what matters to enable future generations to thrive. At Aecon, You Can Count On Safety Always. Our number one core value. The safety of our people, projects, partners, and stakeholders is our priority focus – today and always.Integrity. We lead by example, with humility and courage.Accountability. We’re passionate about delivering on our commitments.Inclusion. We provide opportunities where people feel valued, supported, and empowered to contribute fully. We deliver infrastructure with purpose, and our people are at the heart of everything we do. Aecon employees are incredibly proud to build some of the most impactful infrastructure of this generation – we call it Aecon Proud. At Aecon We Ensure you and your family receive the services and benefits needed to support your mental, emotional, and physical well-being.Are intentional when it comes to investing in your development. We help you build your career and advance your skills through our Aecon University, tuition reimbursement, and Leadership Programs.Are committed to creating work environments focused on mutual respect, teamwork, collaboration, and new ideas, through meaningful initiatives, training, and partnerships with Veteran groups, to ensure we are building with top talent and harnessing our collective strengths within every aspect of our culture.Operate responsibly by managing risk, safety, and environmental considerations across all our projects and surrounding communities. Our success is built on the passion, expertise, and dedication of our people. Together, we embrace strong execution, innovation, and continuous improvement — values that come to life through the unique talents and collaborative spirit of every team member."
We need to strip safety always repeated etc. But we can keep a concise "About the role" maybe summarizing the opportunity. However we must preserve ALL substantive information; we cannot summarize away detail. But we can keep the original sentences; we just need to format them. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. However we need to avoid boilerplate like repeated safety statements? The safety statements are part of the company description; they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. Safety statements might be considered boilerplate? Not sure. It says "remove duplicated lines". The safety always appears multiple times; maybe we should deduplicate. But we need to preserve substantive info; safety always is part of company values, maybe substantive. However it's repeated; we can keep one instance.
Given the complexity, maybe we can keep the introductory paragraph but remove duplicate safety lines. Let's try to produce a concise but still substantive "About the role" that includes the opportunity description (What is the Opportunity?) plus maybe a brief about Aecon. But we must not summarize away detail; we can keep the original sentences but maybe we can keep them as is, just deduplicate.
Better approach: Use sections:
items, maybe each bullet as separate . However the instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, EEO, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see if posting mentions Pay, Schedule, Benefits. It mentions benefits: "At Aecon We Ensure you and your family receive the services and benefits needed to support your mental, emotional, and physical well-being." Also mentions Aecon University, tuition reimbursement, Leadership Programs. So benefits exist. Pay? Not mentioned. Schedule? Not mentioned. So we can include Benefits section. Also maybe "About the role" could be a summary. The posting includes introductory paragraphs about Aecon, safety, values, etc. That could be "About the role" or "About Aecon". But we need to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which are appropriate. The posting includes "What is the Opportunity?" then description of role. That could be About the role. Then "What You'll Do Here" is responsibilities. Then "What You Bring To The Team" includes requirements, qualifications, skills. Could split into Requirements (experience), Qualifications (maybe education?), Skills (competencies). The posting includes "Key Competencies". Also "Additional Requirements". We'll need to map.
We must not invent sections; only include if there is real specific content. So we can include About the role (the opportunity description). Responsibilities (What You'll Do Here). Requirements (What You Bring To The Team - experience). Qualifications maybe not distinct; could combine with Requirements. Skills (Key Competencies). Benefits (the paragraph about benefits, tuition reimbursement, etc.). No Pay or Schedule.
We must preserve all substantive info; not omit details. Must not include boilerplate like EEO statements, safety always repeated, etc. Must remove duplicated lines. Must not include navigation/cookie etc. Must not include application instructions. Must not include EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
First, introductory fluff about Aecon: "Come Build Your Career at Aecon! Aecon delivers some of the most complex and impactful infrastructure projects — from transformative transportation networks to critical energy, industrial and nuclear programs. The projects we build connect communities and power future generations. With deep roots in North America and a strong footprint internationally, Aecon brings global expertise and proudly serves public and private sector clients through its Construction and Concessions segment. Safety Always is not only our #1 core value – it is the standard that anchors our culture. We believe the most ambitious projects deserve the most committed people. At Aecon, you won’t just build your career — you’ll help build what matters to enable future generations to thrive. At Aecon, You Can Count On Safety Always. Our number one core value. The safety of our people, projects, partners, and stakeholders is our priority focus – today and always.Integrity. We lead by example, with humility and courage.Accountability. We’re passionate about delivering on our commitments.Inclusion. We provide opportunities where people feel valued, supported, and empowered to contribute fully. We deliver infrastructure with purpose, and our people are at the heart of everything we do. Aecon employees are incredibly proud to build some of the most impactful infrastructure of this generation – we call it Aecon Proud. At Aecon We Ensure you and your family receive the services and benefits needed to support your mental, emotional, and physical well-being.Are intentional when it comes to investing in your development. We help you build your career and advance your skills through our Aecon University, tuition reimbursement, and Leadership Programs.Are committed to creating work environments focused on mutual respect, teamwork, collaboration, and new ideas, through meaningful initiatives, training, and partnerships with Veteran groups, to ensure we are building with top talent and harnessing our collective strengths within every aspect of our culture.Operate responsibly by managing risk, safety, and environmental considerations across all our projects and surrounding communities. Our success is built on the passion, expertise, and dedication of our people. Together, we embrace strong execution, innovation, and continuous improvement — values that come to life through the unique talents and collaborative spirit of every team member."
We need to strip safety always repeated etc. But we can keep a concise "About the role" maybe summarizing the opportunity. However we must preserve ALL substantive information; we cannot summarize away detail. But we can keep the original sentences; we just need to format them. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. However we need to avoid boilerplate like repeated safety statements? The safety statements are part of the company description; they might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. Safety statements might be considered boilerplate? Not sure. It says "remove duplicated lines". The safety always appears multiple times; maybe we should deduplicate. But we need to preserve substantive info; safety always is part of company values, maybe substantive. However it's repeated; we can keep one instance.
Given the complexity, maybe we can keep the introductory paragraph but remove duplicate safety lines. Let's try to produce a concise but still substantive "About the role" that includes the opportunity description (What is the Opportunity?) plus maybe a brief about Aecon. But we must not summarize away detail; we can keep the original sentences but maybe we can keep them as is, just deduplicate.
Better approach: Use sections:
About the role
What is the Opportunity? The Applications Lead will support enterprise application delivery and operations, primarily focused on U.S. applications including federal projects operating within a secure enclave environment. This role is accountable for the support, enhancement, and administration of U.S. applications in the CMMC environment. In addition, this role will work with the IS Enterprise Solutions team on implementing and supporting corporate projects both in the U.S. and Canada. When necessary, the successful candidate will ensure solutions are delivered and operated in compliance with CMMC, NIST, and Controlled Unclassified Information (CUI) requirements, while aligning to Aecon’s construction, infrastructure, and modernization business processes. This role acts as the primary bridge between business and IT, working closely with Enterprise Architecture, Cybersecurity, Infrastructure, and delivery teams to ensure solutions are fit-for-purpose, compliant, stable, and scalable.
That captures the opportunity.Responsibilities
- Domain Ownership & Application Lifecycle: Administer and support all Enterprise applications within the CMMC environment; Liaise with third-party systems integrators as required; Contribute to application roadmaps; Contribute to enhancement backlog; Contribute to release planning aligned to business priorities.
- Functional Leadership & Solution Design: Act as subject matter expert (SME) for the assigned domain (e.g., CMMC, construction platform tools such as the InEight Product Suite, Oracle Primavera P6, Takeoff tools, etc.); Lead functional analysis and requirements definition; Lead solution design and blueprinting; Lead configuration and functional documentation in alignment with Aecon standards and governance.
- Business Engagement & Requirements Management: Partner with business stakeholders to gather, validate, and prioritize requirements; Partner with business stakeholders to translate needs into functional and technical solutions; Develop strong understanding of Aecon business processes and operating model.
- Delivery Execution & Integration: Lead or coordinate end-to-end delivery of enhancements and projects; Ensure alignment to enterprise architecture; Ensure integration across enterprise platforms; Ensure adherence to Aecon delivery standards.
- Testing, Quality & Deployment: Own or coordinate unit testing; Own or coordinate system integration testing; Own or coordinate user acceptance testing (UAT); Ensure delivery meets quality, compliance, and business expectations.
- Application Support & Operational Stability: Accountable for application performance, availability, and service quality; Accountable for incident, problem, and change management (ITIL-aligned); Drive root cause analysis; Drive issue resolution; Drive continuous service improvement; Provide administration and support for non-FedRAMP instances of Primavera P6 and InEight Estimate as capacity exists.
- Secure Enclave & Compliance Execution: Ensure applications meet Aecon and federal compliance requirements, including CMMC; Ensure applications meet NIST 800-171 / 800-53 frameworks; Ensure applications meet CUI data handling standards; Support audit readiness; Support control validation and remediation; Maintain documentation, including system artifacts, control evidence, and access records; Maintain user provisioning and assignments to specific applications within the CMMC enclave.
- Governance & Access Management: Enforce application governance standards; Enforce role-based access control (RBAC); Enforce segregation of duties (SoD); Partner with Cybersecurity and IAM teams on access provisioning and reviews.
- Stakeholder Engagement: Serve as the primary liaison for business stakeholders and federal project teams in the U.S.; Provide delivery status updates; Provide risk and issue reporting; Provide compliance and audit readiness updates.
- Team Leadership & Vendor Coordination: Lead and coordinate a cross-functional team including vendors and system integrators on U.S. projects; Lead and coordinate support resources; Ensure delivery aligns to security, compliance, and quality expectations.
- for any list of duties/requirements/benefits. So we can flatten all duty items into a single list, or we can have subheadings? The instruction only says use
- for any list; doesn't forbid headings inside list? Probably better to keep each duty as separate
- . We'll lose the subheadings but we can include them inside the
- text. Similarly for Requirements/Qualifications/Skills. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We have "What You Bring To The Team" includes experience requirements: 5+ years of experience in enterprise applications, 5+ years of experience in application delivery and support, experience in regulated or secure environments, strong knowledge of application lifecycle management, strong knowledge of IT service management (ITIL), strong knowledge of CMMC and/or NIST frameworks, experience working with third-party service providers. Also "Preferred Experience with construction/project systems (e.g., project controls, asset management). Familiarity with secure enclave/segregated environments. Familiarity with U.S. federal program delivery. Exposure to identity and access management tools (Entra ID, SailPoint, Saviynt)." Those could be Requirements or Qualifications. Also "Key Competencies" are skills. We could make Requirements = the mandatory experience items. Qualifications = maybe education? Not present. Could skip Qualifications if no specific content. Skills = Key Competencies. But we must not create a section with filler. If we skip Qualifications, that's fine. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to include Benefits: "At Aecon We Ensure you and your family receive the services and benefits needed to support your mental, emotional, and physical well-being.Are intentional when it comes to investing in your development. We help you build your career and advance your skills through our Aecon University, tuition reimbursement, and Leadership Programs.Are committed to creating work environments focused on mutual respect, teamwork, collaboration, and new ideas, through meaningful initiatives, training, and partnerships with Veteran groups, to ensure we are building with top talent and harnessing our collective strengths within every aspect of our culture.Operate responsibly by managing risk, safety, and environmental considerations across all our projects and surrounding