Director of Enterprise Architecture and Applications
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Iridium is an Equal Opportunity Employer..." etc. Also remove "Additional Information" maybe keep pay and benefits. We need to map content to appropriate sections.
We have:
Company Overview: description of company. Could be "About the role"? Actually "About the role" is generic; but we have company overview. Could put under About the role
maybe not ideal but we can use "About the role" as heading for company overview? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. So we need sections: About the role (company overview + what we're looking for?), Responsibilities (What You'll Do), Requirements (What You'll Need to Succeed), Qualifications (maybe education/experience?), Skills (Things That Would be Great if You Brought to the Table?), Benefits, Pay, Schedule.
We need to avoid filler like "commensurate with experience". We have actual pay range: Base Pay Range: $200,000 - $260,000. Also mention eligibility for company stock and annual bonus. Benefits: medical, dental, vision insurance; 401(k); paid time off and paid holidays; paid parental leave; other discounts and perks. Also mention hybrid schedule: at least 4 days in office, travel up to 25% internationally, on call approx 10%, US Citizenship required, work environment office setting largely sedentary.
We need to include Schedule section if posting actually states schedule: they mention hybrid schedule: at least four days per week in office, travel up to 25%, on call approx 10%. So schedule info exists. So we can create Schedule section with those details.
Benefits section: we have benefits listed.
Pay section: base pay range and mention stock and bonus.
Qualifications: maybe education and experience? Requirements: maybe the "What You'll Need to Succeed" includes degree, years experience, etc. Could treat that as Requirements. Qualifications could be maybe "Things That Would be Great if You Brought to the Table" (TOGAF). But we need to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping.
Let's map:
- About the role: Company Overview + What We're Looking For (summary of role). Could combine.
- Responsibilities: What You'll Do.
- Requirements: What You'll Need to Succeed (mandatory qualifications).
- Qualifications: maybe education? But we already used education in Requirements. Could treat Qualifications as "Things That Would be Great if You Brought to the Table" (nice-to-have). Or we could treat Skills as that. But we have both Skills and Qualifications headings. We need to decide.
Given typical job posting: Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = specific skills. But we have limited headings.
We have "Things That Would be Great if You Brought to the Table: Open Group Architecture Framework – TOGAF". That's a nice-to-have skill. Also we have "Be on call (approximately 10%)", "Be able to travel up to 25%, including internationally", "Be able to work a hybrid schedule that includes at least 4 days in office", "US Citizenship required". Those are more like requirements or schedule.
We also have "Work environment: ..." maybe part of About the role or Schedule.
We need to avoid duplication.
Let's structure:
About the role
About the role
Company overview paragraph(s) + what we're looking for summary.
Responsibilities
- list each responsibility from "What You'll Do"
Requirements
- list each item from "What You'll Need to Succeed"
Qualifications
Maybe we can put education? But we already included education in Requirements. Could put "Bachelor's degree in Computer Science, Computer Engineering, Business, or a related field." as qualification. But we need to avoid duplication. Perhaps we treat Requirements as experience and skills, Qualifications as education. Let's split: Requirements: experience and technical expertise; Qualifications: education. However the instruction says use those headings when appropriate; we can have both. Let's extract: Education: Bachelor’s degree in Computer Science, Computer Engineering, Business, or a related field. Experience: 15+ years of relevant experience in enterprise architecture, solution architecture, cloud architecture, or a related technology leadership role. Experience with major enterprise and cloud platforms, including ServiceNow, Microsoft Azure, Microsoft Dynamics, and AWS. Broad understanding of software development, testing methodologies, change management, and configuration management across both on-premises and cloud environments. Strong understanding of cloud architecture fundamentals, including IaaS, PaaS, and SaaS. Knowledge of data protection, security, and compliance requirements for cloud-hosted applications. Experience with automated deployment, continuous integration, release management, and DevOps practices. Strong knowledge of infrastructure automation and modern application delivery tools. Demonstrated experience leading projects in Agile environments, including planning, execution, risk management, and resource management. Strong understanding of DevOps strategy, practices, and solution delivery. Excellent communication and presentation skills, with the ability to lead discussions, explain complex topics, and respond effectively in challenging situations. Ability to build strong working relationships with business and technology leaders at all levels of the organization. Proven ability to build consensus, influence decisions, and drive collaboration across multiple departments. Strong judgment, decisiveness, and the ability to work through complex or ambiguous situations. Ability to manage multiple priorities while maintaining a high standard of quality. Proactive approach to learning, staying current with emerging technologies, and sharing knowledge across the organization. That's a lot; we can keep as list. Qualifications: maybe "Things That Would be Great if You Brought to the Table: Open Group Architecture Framework – TOGAF". Also maybe "US Citizenship required" could be a requirement but we could put in Requirements as well. But we already have many items; we can add US Citizenship as a requirement. Schedule: hybrid schedule (at least 4 days in office), travel up to 25% internationally, on call approx 10%. Benefits: medical, dental, vision insurance; 401(k) retirement plan options; paid time off and paid holidays; paid parental leave; other discounts and perks; also eligibility for company stock and annual bonus (though that could be Pay). We'll put stock and bonus in Pay. Pay: Base Pay Range: $200,000 - $260,000; eligibility for company stock and annual bonus. Now we need to ensure we don't include boilerplate like "Additional Information This job description outlines the general nature..." etc. Remove that. Also remove "Iridium is an Equal Opportunity Employer..." etc. Now produce HTML fragment with sections only if they have content. We'll produce:
About the role
Company overview paragraphs... plus what we're looking for summary.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include the company overview text exactly? We can paraphrase? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep the details, but we can rephrase? It says do NOT invent or summarize away detail. Summarizing away detail would be removing details. We can keep the details but maybe we can condense? It says prefer a few substantive sections over many thin ones. But we must not lose detail. So we need to include all details from company overview and what we're looking for. We could include them as paragraphs, maybe bullet points? But we should not lose any detail. So we need to include the full text of company overview and what we're looking for. However that could be lengthy but okay. We need to avoid duplication: there may be repeated lines. We'll just include the content as is, maybe split into paragraphs. Let's extract company overview text: "Company Overview Iridium is an award-winning and innovative satellite communications company with bragging rights to the only network that offers voice and data connectivity anywhere in the world. For over 20 years, Iridium’s unique network and services have supported critical communications needs for individuals, businesses, and the evolving Internet of Things. At Iridium, we understand the importance of staying connected and the limitations of traditional communications networks. People across the globe, including first responders, humanitarians, global militaries, scientific researchers, and lone workers, as well as ships, aircraft and remote operations all rely on Iridium to stay connected. We take our responsibility for providing these essential communications very seriously and pride ourselves on offering a reliable lifeline when needed. Likewise, Iridium is committed to providing an exciting and innovative workplace, where employees are challenged to think outside the box and collaborate on new, bold ideas and solutions. Our talented teams are passionate about their work and the impact our company makes around the world. Iridium fosters an empowering and inclusive culture that allows employees to genuinely be their best selves. We are looking for others who want to join this truly unique company that celebrates our employees and provides the opportunity to truly make a difference in the world." Then "What We’re Looking For: Are you a senior technology leader with deep experience in enterprise architecture, applications, and technology transformation? Iridium is looking for a Director of Enterprise Architecture and Applications to help shape and execute our technology strategy. In this role, you will translate business priorities into clear target-state architecture, platforms, and roadmaps, while building the standards and governance to support it. You’ll lead the Applications team and own the applications portfolio end-to-end, from strategy and selection through integration, modernization, and ongoing lifecycle management. We need someone who is both strategic and hands-on. Someone who can influence across the organization, dive into complex technical decisions, and drive simplification and modernization. If you’re excited by the chance to shape the technology foundation of a global satellite communications company and to bring vision and execution together, then we want to hear from you." We can combine these into About the role section. Now Responsibilities: list each bullet from "What You’ll Do:": - Define the enterprise architecture vision and roadmap, including platforms, services, standards, integration patterns, and technology selections. - Connect business strategy to technology decisions, working closely with business leaders, project teams, developers, infrastructure, security, and operations. - Establish and enforce architecture standards and governance, while still being pragmatic enough to help teams get things done. - Own the enterprise applications portfolio, including application selection, implementation, integration, modernization, lifecycle management, and ongoing enhancement. - Lead and develop the Applications team, setting priorities, coaching people, managing performance, and building stronger technical capability. - Drive modernization and simplification, eliminating unnecessary complexity, improving processes, reducing technical debt, and improving the user experience. - Provide hands-on technical leadership when needed not just produce architecture diagrams, but help design solutions and resolve difficult technical decisions. - Lead major application initiatives with accountability for execution, risk, schedule, and business outcomes. - Manage strategic vendors, including product direction, performance, contracts, and commercial relationships. - Collaborate with business leaders and end-users to grasp requirements, address concerns, and synchronize tech solutions with operational needs. - Manage CapEx and