IT Technical Lead (Annapolis, MD - onsite)
Chaney Enterprises · Annapolis, MD · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output only 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 as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove EEO etc. Also remove duplicated lines, navigation, cookie, etc.
We need to parse the posting.
Key sections:
- Department: Information Technology Leadership
- Reports To: CTO or Director of Information Technology
- Location: Onsite — Annapolis, Maryland
- FLSA Status: Exempt (Not Eligible for Overtime) — description.
- Schedule: Full-time, 40 hours per week — schedule to be confirmed upon hire
- Supervisory Responsibility: description.
- Compensation Grade: TBD — Pending Compensation Grade Structure (this is TBD, so we should NOT include Pay section because it's not specific; we only include Pay if posting actually states them. It says TBD, so we should not include Pay.)
- Position Summary (could be About the role)
- Essential Duties & Responsibilities (Responsibilities)
- Required Qualifications (Requirements)
- Preferred Qualifications (maybe Qualifications? Actually we have Required Qualifications and Preferred Qualifications; we can combine into Requirements and Qualifications? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: Position Summary (maybe also Department, Reports To, Location, FLSA Status, Schedule, Supervisory Responsibility). But we need to decide what goes where. Usually About the role includes summary and maybe basic info. We'll include Position Summary and maybe basic info like Department, Reports To, Location, FLSA Status, Schedule, Supervisory Responsibility.
- Responsibilities: Essential Duties & Responsibilities list.
- Requirements: Required Qualifications (minimum years, etc.)
- Qualifications: Preferred Qualifications (maybe also Education? Actually Education is listed separately but it's similar to Preferred Qualifications. Could go under Qualifications.
- Skills: maybe we can extract from Required Qualifications: problem-solving, analytical, cross-functional collaboration, executive presentation skills, etc. Could also include technical skills like cloud migration, API integration, etc. But we can also put them under Requirements. However we need to follow instruction: Use headings for those sections only if there is real specific content. We can create Skills section if we have specific skill list.
- Benefits: Not mentioned; no benefits specifics. So omit Benefits.
- Pay: Not specific (TBD). Omit.
- Schedule: we have schedule info: Full-time, 40 hours per week — schedule to be confirmed upon hire. That's specific enough? It says schedule to be confirmed upon hire, but still states full-time 40 hours per week. That's specific. So we can include Schedule section.
We must not include placeholder like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Schedule is not TBD; it's given as full-time 40 hours per week. So we can include.
Now we need to output HTML fragment with
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 as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove EEO etc. Also remove duplicated lines, navigation, cookie, etc.
We need to parse the posting.
Key sections:
- Department: Information Technology Leadership
- Reports To: CTO or Director of Information Technology
- Location: Onsite — Annapolis, Maryland
- FLSA Status: Exempt (Not Eligible for Overtime) — description.
- Schedule: Full-time, 40 hours per week — schedule to be confirmed upon hire
- Supervisory Responsibility: description.
- Compensation Grade: TBD — Pending Compensation Grade Structure (this is TBD, so we should NOT include Pay section because it's not specific; we only include Pay if posting actually states them. It says TBD, so we should not include Pay.)
- Position Summary (could be About the role)
- Essential Duties & Responsibilities (Responsibilities)
- Required Qualifications (Requirements)
- Preferred Qualifications (maybe Qualifications? Actually we have Required Qualifications and Preferred Qualifications; we can combine into Requirements and Qualifications? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: Position Summary (maybe also Department, Reports To, Location, FLSA Status, Schedule, Supervisory Responsibility). But we need to decide what goes where. Usually About the role includes summary and maybe basic info. We'll include Position Summary and maybe basic info like Department, Reports To, Location, FLSA Status, Schedule, Supervisory Responsibility.
- Responsibilities: Essential Duties & Responsibilities list.
- Requirements: Required Qualifications (minimum years, etc.)
- Qualifications: Preferred Qualifications (maybe also Education? Actually Education is listed separately but it's similar to Preferred Qualifications. Could go under Qualifications.
- Skills: maybe we can extract from Required Qualifications: problem-solving, analytical, cross-functional collaboration, executive presentation skills, etc. Could also include technical skills like cloud migration, API integration, etc. But we can also put them under Requirements. However we need to follow instruction: Use headings for those sections only if there is real specific content. We can create Skills section if we have specific skill list.
- Benefits: Not mentioned; no benefits specifics. So omit Benefits.
- Pay: Not specific (TBD). Omit.
- Schedule: we have schedule info: Full-time, 40 hours per week — schedule to be confirmed upon hire. That's specific enough? It says schedule to be confirmed upon hire, but still states full-time 40 hours per week. That's specific. So we can include Schedule section.
We must not include placeholder like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Schedule is not TBD; it's given as full-time 40 hours per week. So we can include.
Now we need to output HTML fragment with headings and appropriate - for lists,
for prose.
We must not include any markdown code fences.
Let's craft:
About the role
Department: Information Technology Leadership. Reports To: CTO or Director of Information Technology. Location: Onsite — Annapolis, Maryland. FLSA Status: Exempt (Not Eligible for Overtime). Schedule: Full-time, 40 hours per week (to be confirmed upon hire). Supervisory Responsibility: Oversees cross‑functional engineering teams (network, security, integration, plant automation) and coordinates third‑party systems integrators and software vendor resources.
But we might want to split some into separate paragraphs? It's okay.
Now Responsibilities: list of duties from Essential Duties & Responsibilities.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each duty as a list item.
Let's extract duties:
- Leads technical design and architecture discussions encompassing network infrastructure, cloud migrations, cybersecurity frameworks, and API integrations to ensure solutions align with enterprise standards and business objectives.
- Translates corporate goals into scalable technical roadmaps and enterprise reference architectures that support current operations and anticipate future growth requirements.
- Evaluates emerging technologies — including AI-driven logistics engines and edge analytics platforms — and delivers formal recommendations to executive leadership regarding strategic technology investments and upgrades.
- Standardizes technology architectures, development guidelines, and security baselines across all regional operating divisions to ensure consistency, compliance, and operational resilience.
- Chairs the corporate Change Advisory Board (CAB), coordinating software upgrade cycles, release windows, and system cutovers to minimize operational disruption across business units.
- Enforces code review practices, CI/CD pipeline standards, and technical documentation requirements across all development teams to uphold engineering quality and auditability.
- Directs, mentors, and evaluates cross-functional engineering teams — including network, security, integration, and plant automation engineers — establishing skills matrices, performance objectives, and career development frameworks.
- Coordinates resource allocation among internal engineering teams, third-party systems integrators, and software vendors to ensure timely and on-budget project delivery.
- Serves as the primary technical interface for software and hardware vendors, external contractors, and internal executive leadership, facilitating clear communication of technical risks, decisions, and project status.
- Manages project deliverables, technical risk registers, and system budgets for large-scale digital transformation initiatives, ensuring alignment with financial, operational, and timeline constraints.
- Develops and maintains enterprise IT/OT governance documentation, including architecture decision records, standards policies, and technology lifecycle plans.
- Monitors industry trends, regulatory developments, and competitive technology landscapes to inform continuous improvement of the enterprise technology environment.
We'll put each as - .
Now Requirements: Required Qualifications list.
Extract:
- Minimum of 8 years of engineering experience in IT and/or OT environments.
- Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role.
- Minimum of 3 years of experience in transport, logistics, construction, materials handling, or a closely related industry.
- Proven experience leading complex cloud migration projects, API integration programs, and heavy industrial automation initiatives.
- Demonstrated ability to develop and govern enterprise reference architectures and technology roadmaps.
- Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders.
- Exceptional problem-solving, analytical, and cross-functional collaboration skills.
We'll list as
- .
Now Qualifications: Preferred Qualifications and Education.
Preferred Qualifications list:
- Bachelor's or Master's degree in Computer Science, Systems Engineering, Electrical Engineering, Software Engineering, or a related technical field.
- TOGAF certification or equivalent enterprise architecture framework credential.
- ITIL v4 Managing Professional certification.
- AWS Certified Solutions Architect or equivalent cloud platform certification.
- Certified ScrumMaster (CSM) or SAFe Agilist certification.
- Experience with edge analytics platforms and AI-driven logistics or operational intelligence solutions.
Education: Actually repeats similar to first bullet; but we can combine.
We'll list as
- under Qualifications.
Now Skills: Could extract from Required Qualifications: problem-solving, analytical, cross-functional collaboration, executive presentation skills, ability to communicate complex technical concepts, etc. Also maybe technical skills like cloud migration, API integration, etc. But we already have those in Requirements. To avoid duplication, maybe we can omit Skills section if not distinct. However instruction says we can include Skills if we have real specific content. We could create a Skills section listing: executive presentation, problem-solving, analytical, cross-functional collaboration, technical architecture, cloud migration, API integration, etc. But that may duplicate content. Safer to omit Skills if not clearly separate. However we have "Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders." and "Exceptional problem-solving, analytical, and cross-functional collaboration skills." Those are skills. We could put them under Skills. But then Requirements would lose those items. However we could keep them in Requirements and also have Skills; but that would duplicate. Better to move them to Skills and keep Requirements focused on experience/years etc. Let's decide.
We have Required Qualifications includes both experience and skills. We could split: Requirements: experience/years etc. Skills: presentation, problem-solving, analytical, collaboration.
Let's extract experience items:
- Minimum of 8 years of engineering experience in IT and/or OT environments.
- Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role.
- Minimum of 3 years of experience in transport, logistics, construction, materials handling, or a closely related industry.
- Proven experience leading complex cloud migration projects, API integration programs, and heavy industrial automation initiatives.
- Demonstrated ability to develop and govern enterprise reference architectures and technology roadmaps.
These are more about experience/ability.
Skills items:
- Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders.
- Exceptional problem-solving, analytical, and cross-functional collaboration skills.
We'll put those under Skills.
Now Qualifications (Preferred) includes education and certifications.
Now Schedule: we have schedule info.
Now we need to ensure we don't include any boilerplate like EEO, ADA, etc.
Now produce HTML.
Let's craft:
About the role
Department: Information Technology Leadership. Reports To: CTO or Director of Information Technology. Location: Onsite — Annapolis, Maryland. FLSA Status: Exempt (Not Eligible for Overtime). Schedule: Full-time, 40 hours per week (to be confirmed upon hire). Supervisory Responsibility: Oversees cross‑functional engineering teams (network, security, integration, plant automation) and coordinates third‑party systems integrators and software vendor resources.
Responsibilities
- Leads technical design and architecture discussions encompassing network infrastructure, cloud migrations, cybersecurity frameworks, and API integrations to ensure solutions align with enterprise standards and business objectives.
- Translates corporate goals into scalable technical roadmaps and enterprise reference architectures that support current operations and anticipate future growth requirements.
- Evaluates emerging technologies — including AI-driven logistics engines and edge analytics platforms — and delivers formal recommendations to executive leadership regarding strategic technology investments and upgrades.
- Standardizes technology architectures, development guidelines, and security baselines across all regional operating divisions to ensure consistency, compliance, and operational resilience.
- Chairs the corporate Change Advisory Board (CAB), coordinating software upgrade cycles, release windows, and system cutovers to minimize operational disruption across business units.
- Enforces code review practices, CI/CD pipeline standards, and technical documentation requirements across all development teams to uphold engineering quality and auditability.
- Directs, mentors, and evaluates cross-functional engineering teams — including network, security, integration, and plant automation engineers — establishing skills matrices, performance objectives, and career development frameworks.
- Coordinates resource allocation among internal engineering teams, third-party systems integrators, and software vendors to ensure timely and on-budget project delivery.
- Serves as the primary technical interface for software and hardware vendors, external contractors, and internal executive leadership, facilitating clear communication of technical risks, decisions, and project status.
- Manages project deliverables, technical risk registers, and system budgets for large-scale digital transformation initiatives, ensuring alignment with financial, operational, and timeline constraints.
- Develops and maintains enterprise IT/OT governance documentation, including architecture decision records, standards policies, and technology lifecycle plans.
- Monitors industry trends, regulatory developments, and competitive technology landscapes to inform continuous improvement of the enterprise technology environment.
Requirements
- Minimum of 8 years of engineering experience in IT and/or OT environments.
- Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role.
- Minimum of 3 years of experience in transport
- for lists,
for prose. We must not include any markdown code fences. Let's craft:
About the role
Department: Information Technology Leadership. Reports To: CTO or Director of Information Technology. Location: Onsite — Annapolis, Maryland. FLSA Status: Exempt (Not Eligible for Overtime). Schedule: Full-time, 40 hours per week (to be confirmed upon hire). Supervisory Responsibility: Oversees cross‑functional engineering teams (network, security, integration, plant automation) and coordinates third‑party systems integrators and software vendor resources.
But we might want to split some into separate paragraphs? It's okay. Now Responsibilities: list of duties from Essential Duties & Responsibilities. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each duty as a list item. Let's extract duties: - Leads technical design and architecture discussions encompassing network infrastructure, cloud migrations, cybersecurity frameworks, and API integrations to ensure solutions align with enterprise standards and business objectives. - Translates corporate goals into scalable technical roadmaps and enterprise reference architectures that support current operations and anticipate future growth requirements. - Evaluates emerging technologies — including AI-driven logistics engines and edge analytics platforms — and delivers formal recommendations to executive leadership regarding strategic technology investments and upgrades. - Standardizes technology architectures, development guidelines, and security baselines across all regional operating divisions to ensure consistency, compliance, and operational resilience. - Chairs the corporate Change Advisory Board (CAB), coordinating software upgrade cycles, release windows, and system cutovers to minimize operational disruption across business units. - Enforces code review practices, CI/CD pipeline standards, and technical documentation requirements across all development teams to uphold engineering quality and auditability. - Directs, mentors, and evaluates cross-functional engineering teams — including network, security, integration, and plant automation engineers — establishing skills matrices, performance objectives, and career development frameworks. - Coordinates resource allocation among internal engineering teams, third-party systems integrators, and software vendors to ensure timely and on-budget project delivery. - Serves as the primary technical interface for software and hardware vendors, external contractors, and internal executive leadership, facilitating clear communication of technical risks, decisions, and project status. - Manages project deliverables, technical risk registers, and system budgets for large-scale digital transformation initiatives, ensuring alignment with financial, operational, and timeline constraints. - Develops and maintains enterprise IT/OT governance documentation, including architecture decision records, standards policies, and technology lifecycle plans. - Monitors industry trends, regulatory developments, and competitive technology landscapes to inform continuous improvement of the enterprise technology environment. We'll put each as - . Now Requirements: Required Qualifications list. Extract: - Minimum of 8 years of engineering experience in IT and/or OT environments. - Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role. - Minimum of 3 years of experience in transport, logistics, construction, materials handling, or a closely related industry. - Proven experience leading complex cloud migration projects, API integration programs, and heavy industrial automation initiatives. - Demonstrated ability to develop and govern enterprise reference architectures and technology roadmaps. - Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders. - Exceptional problem-solving, analytical, and cross-functional collaboration skills. We'll list as
- . Now Qualifications: Preferred Qualifications and Education. Preferred Qualifications list: - Bachelor's or Master's degree in Computer Science, Systems Engineering, Electrical Engineering, Software Engineering, or a related technical field. - TOGAF certification or equivalent enterprise architecture framework credential. - ITIL v4 Managing Professional certification. - AWS Certified Solutions Architect or equivalent cloud platform certification. - Certified ScrumMaster (CSM) or SAFe Agilist certification. - Experience with edge analytics platforms and AI-driven logistics or operational intelligence solutions. Education: Actually repeats similar to first bullet; but we can combine. We'll list as
- under Qualifications.
Now Skills: Could extract from Required Qualifications: problem-solving, analytical, cross-functional collaboration, executive presentation skills, ability to communicate complex technical concepts, etc. Also maybe technical skills like cloud migration, API integration, etc. But we already have those in Requirements. To avoid duplication, maybe we can omit Skills section if not distinct. However instruction says we can include Skills if we have real specific content. We could create a Skills section listing: executive presentation, problem-solving, analytical, cross-functional collaboration, technical architecture, cloud migration, API integration, etc. But that may duplicate content. Safer to omit Skills if not clearly separate. However we have "Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders." and "Exceptional problem-solving, analytical, and cross-functional collaboration skills." Those are skills. We could put them under Skills. But then Requirements would lose those items. However we could keep them in Requirements and also have Skills; but that would duplicate. Better to move them to Skills and keep Requirements focused on experience/years etc. Let's decide.
We have Required Qualifications includes both experience and skills. We could split: Requirements: experience/years etc. Skills: presentation, problem-solving, analytical, collaboration.
Let's extract experience items:
- Minimum of 8 years of engineering experience in IT and/or OT environments.
- Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role.
- Minimum of 3 years of experience in transport, logistics, construction, materials handling, or a closely related industry.
- Proven experience leading complex cloud migration projects, API integration programs, and heavy industrial automation initiatives.
- Demonstrated ability to develop and govern enterprise reference architectures and technology roadmaps.
These are more about experience/ability.
Skills items:
- Strong executive presentation skills and the ability to communicate complex technical concepts clearly to non-technical stakeholders.
- Exceptional problem-solving, analytical, and cross-functional collaboration skills.
We'll put those under Skills.
Now Qualifications (Preferred) includes education and certifications.
Now Schedule: we have schedule info.
Now we need to ensure we don't include any boilerplate like EEO, ADA, etc.
Now produce HTML.
Let's craft:
About the role
Department: Information Technology Leadership. Reports To: CTO or Director of Information Technology. Location: Onsite — Annapolis, Maryland. FLSA Status: Exempt (Not Eligible for Overtime). Schedule: Full-time, 40 hours per week (to be confirmed upon hire). Supervisory Responsibility: Oversees cross‑functional engineering teams (network, security, integration, plant automation) and coordinates third‑party systems integrators and software vendor resources.
Responsibilities
- Leads technical design and architecture discussions encompassing network infrastructure, cloud migrations, cybersecurity frameworks, and API integrations to ensure solutions align with enterprise standards and business objectives.
- Translates corporate goals into scalable technical roadmaps and enterprise reference architectures that support current operations and anticipate future growth requirements.
- Evaluates emerging technologies — including AI-driven logistics engines and edge analytics platforms — and delivers formal recommendations to executive leadership regarding strategic technology investments and upgrades.
- Standardizes technology architectures, development guidelines, and security baselines across all regional operating divisions to ensure consistency, compliance, and operational resilience.
- Chairs the corporate Change Advisory Board (CAB), coordinating software upgrade cycles, release windows, and system cutovers to minimize operational disruption across business units.
- Enforces code review practices, CI/CD pipeline standards, and technical documentation requirements across all development teams to uphold engineering quality and auditability.
- Directs, mentors, and evaluates cross-functional engineering teams — including network, security, integration, and plant automation engineers — establishing skills matrices, performance objectives, and career development frameworks.
- Coordinates resource allocation among internal engineering teams, third-party systems integrators, and software vendors to ensure timely and on-budget project delivery.
- Serves as the primary technical interface for software and hardware vendors, external contractors, and internal executive leadership, facilitating clear communication of technical risks, decisions, and project status.
- Manages project deliverables, technical risk registers, and system budgets for large-scale digital transformation initiatives, ensuring alignment with financial, operational, and timeline constraints.
- Develops and maintains enterprise IT/OT governance documentation, including architecture decision records, standards policies, and technology lifecycle plans.
- Monitors industry trends, regulatory developments, and competitive technology landscapes to inform continuous improvement of the enterprise technology environment.
Requirements
- Minimum of 8 years of engineering experience in IT and/or OT environments.
- Minimum of 2 to 3 years in a technical leadership, solution architecture, or engineering management role.
- Minimum of 3 years of experience in transport