Radio Communications Engineering Manager

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Position Summary, Key Duties & Responsibilities, Qualifications, Core Skills, Core Competencies, Work Environment, Requirements (export control, etc.), Physical Requirements, Equipment and Machines, etc. Also mentions "Management has the prerogative..." etc. We need to map content to headings. We should not repeat job title as heading. No Job ID. We need to preserve all substantive info, but can combine similar sections. We need to decide which headings to use. Potential sections: - About the role: About the role (maybe from Position Summary and intro). Could include description of company and role summary. - Responsibilities: Key Duties & Responsibilities. - Qualifications: Education & Experience list. - Skills: Core Skills and Core Competencies maybe combined. - Benefits: Not mentioned; no benefits specifics. So omit Benefits. - Pay: Not mentioned; omit. - Schedule: Not mentioned; maybe mention willingness to work evenings/weekends as needed. That's schedule info. Could include under Schedule heading: "May require working evenings and weekends as needed to meet critical project milestones." That's specific. So include Schedule. Also Work Environment: mention office environment, inside/outside work, physical requirements, equipment. Could be under Work Environment heading but not in list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Work Environment heading. But we could fold work environment details into About the role or Responsibilities? Probably better to include under About the role or maybe under Requirements? However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying these are examples but we should use those headings when appropriate. It says "include a section ONLY when the posting has real, specific content for it". So we can use those headings; we shouldn't invent other headings like Work Environment. So we need to map content to those headings. Thus we need to decide where to put work environment, physical requirements, equipment, export control, etc. Possibly under Requirements (since those are requirements). Or under About the role (general). The heading "Requirements" likely for job requirements like education, experience, etc. But we already have Qualifications for education/experience. The posting separates Qualifications and Requirements (export control, etc.). So we can put education/experience under Qualifications, and other requirements (export control, willingness to work evenings/weekends, physical requirements, equipment) under Requirements. Skills: core skills and core competencies. Thus sections: - About the role: company description and position summary. - Responsibilities: Key Duties & Responsibilities. - Qualifications: Education & Experience bullet list. - Skills: Core Skills and Core Competencies (maybe combine). - Requirements: Export control, willingness to work evenings/weekends, physical requirements, equipment, etc. - Schedule: maybe mention evenings/weekends already in Requirements; but we could also put schedule there. Since schedule is about working hours, we could put under Schedule heading: "May require working evenings and weekends as needed to meet critical project milestones." But we already have that in Requirements. To avoid duplication, we could put schedule info under Schedule heading and not duplicate elsewhere. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we put it under Schedule, we still need to keep other requirements elsewhere. That's fine. Thus we will have:

About the role

... company description and position summary ...

Responsibilities

• ... each duty ...

Qualifications

• ... education/experience bullets ...

Skills

• ... core skills and core competencies ...

Requirements

• ... export control, physical requirements, equipment, etc. ...

Schedule

May require working evenings and weekends as needed to meet critical project milestones.

We must not include headings with empty content. Now we need to extract substantive content. Let's parse the posting. Intro paragraph: "Axiom Space is a human space exploration company, building era-defining space infrastructure and delivering technology-driven solutions that will empower civilization to transcend Earth. Beginning with Axiom Station, successor to the International Space Station, the company is pioneering a next-generation orbital settlement that will foster groundbreaking innovation and research in microgravity and drive the global space economy of tomorrow. Today, guided by the vision of leading humanity's expansion off planet, Axiom Space is the principal provider of commercial human spaceflight services and developer of advanced spacesuits for the Moon and beyond. For more information about Axiom Space, visit www.axiomspace.com. Axiom Space fosters a work environment inclusive of all perspectives. We are the pioneers of commercial space, leading the transformation of low-Earth orbit into a global space marketplace. Our mission-driven team is seeking a bold and dynamic Manager, Radio Communications who is fueled by high accountability, execution horsepower, and driven to understand our world, science/technology, and life itself, for the benefit of all on Earth and beyond." We can combine that into About the role. Position Summary: "Since Axiom Space is a very complex work environment, we are looking for a resilient, high-energy Manager, Radio Communications, who leads the design, development, integration, and testing of advanced radio frequency (RF) communication systems supporting aerospace and defense platforms. The role manages a team of engineers responsible for RF architecture, wireless communication technologies, system performance, and regulatory compliance. The position partners closely with cross-functional teams to deliver reliable, high-performance communication solutions for airborne, spaceborne, airborne, and ground-based applications. The ideal candidate combines deep technical expertise in RF systems with strong leadership, project management, and customer engagement skills. This role drives innovation, technical excellence, and successful program execution in a fast-paced aerospace environment. This position blends people leadership with hands-on technical insight to advance an industry benchmark Radio Communications organization." We can include that in About the role as well. Now Responsibilities: list of duties. Let's extract each bullet from "Key Duties & Responsibilities": - Lead the design, development, integration, and deployment of RF communication systems for aerospace, defense, satellite, and airborne platforms. - Manage and mentor a team of RF, systems, and communications engineers, fostering technical excellence and professional development. - Define RF system architecture, requirements, and performance specifications to meet mission and customer objectives. - Oversee system-level analysis, modeling, simulation, testing, and validation of RF communication solutions. - Ensure compliance with applicable aerospace, government, spectrum management, and regulatory standards. - Collaborate with program management, engineering, manufacturing, and customer stakeholders throughout the product lifecycle. - Drive technical reviews, risk assessments, trade studies, and root-cause investigations to ensure program success. - Manage project schedules, budgets, resource planning, and technical deliverables across multiple programs. - Support business development activities, including proposal development, customer presentations, and technical roadmap planning. - Evaluate emerging RF, wireless, satellite communications, and electronic warfare technologies to identify innovative opportunities. - Oversee laboratory, field, flight, and environmental testing activities and ensure successful system qualification. - Promote continuous improvement, quality, safety, and engineering best practices across RF communications programs. - Communicating project progress, status, and potential issues to stakeholders and leadership - Implementing and maintaining agile project management methodologies throughout the project lifecycle - Perform additional job duties as assigned Note some verbs are gerund vs infinitive; we keep as is. Now Qualifications: Education & Experience list: - Bachelor’s degree in Electrical Engineering, Telecommunications Engineering, Aerospace Engineering, or a related technical field; Master’s degree preferred. - 8+ years of progressive experience in RF communications, wireless systems, satellite communications, aerospace, defense, or a related industry; or an equivalent combination of education and experience. - 3+ years of experience leading technical teams, projects, or engineering programs. - Demonstrated experience designing, developing, integrating, and testing RF communication systems and subsystems. - Strong understanding of RF system architecture, link budgets, antennas, propagation, spectrum management, and communication protocols. - Experience using RF modeling and simulation tools (ANSYS HFSS, Keysight Pathway ADR, Cadence, MATLAB RF Toolbox, ADIsimRF) - Experience supporting full product lifecycle development from requirements definition through validation, deployment, and sustainment. - Experience collaborating effectively with cross-functional teams, customers, suppliers, and program stakeholders. - Knowledge of aerospace, defense, FAA, FCC, DoD, or other applicable industry standards and regulatory requirements. - Strong written, verbal, and presentation communication skills with the ability to influence technical and business decisions - Track record of making things happen in ambiguous, fast-moving environments - Uses good judgement to problem-solve proactively, positively impacting hard challenges - Demonstrated organization skills to meet tight deadlines with high quality results Now Skills: Core Skills and Core Competencies. Core Skills list: - Passion for space and the mission - Entrepreneurial, growth mindset - High EQ and ability to collaborate within teams and cross-functionally - Tech-solutioning in using systems and tools to move smarter and faster Core Competencies list: - Embody our core values of leadership, innovation, and teamwork. - In addition, to perform the job successfully, an individual should demonstrate the following competencies: - Accountability - Technical Rigor - Execution Discipline - Pride of Delivery We can combine into a single list. Now Requirements: includes export control, willingness to work evenings/weekends, physical requirements, equipment. From posting: "Requirements This position may require access to export controlled technical data or technology subject to NASA regulations, International Traffic in Arms Regulations (ITAR), or Export Administration Regulations (EAR). In accordance with U.S. export control laws, final candidates may be required to undergo additional export control screening to determine eligibility for access. Meeting these requirements is a condition of employment. Management has the prerogative to select at any level for which the position is advertised Must be willing to work evenings and weekends as needed to meet critical project milestones Physical Requirements Work may involve sitting or standing for extended periods (90% of the time) May require lifting and carrying up to 25 lbs. (5% of the time) Equipment and Machines Standard office equipment (PC, phone, printer, etc.)" We need to preserve all substantive info. So we can make list items: - May require access to export controlled technical data or technology subject to NASA regulations, ITAR, or EAR; final candidates may undergo additional export control screening. - Management may select candidates at any level for which the position is advertised. - Must be willing to work evenings and weekends as needed to meet critical project milestones. - Work may involve sitting or standing for extended periods (approximately 90% of the time). - May require lifting and carrying up to 25 lbs. (approximately 5% of the time). - Standard office equipment (PC, phone, printer, etc.) used. We could also include "Meeting these requirements is a condition of employment." as a note. Now Schedule: we already used evenings/weekends in Requirements; but we could move that to Schedule and remove from Requirements. However the instruction: "Prefer a few substantive sections over many thin ones." We have many sections already. If we move schedule to its own section, we still have Requirements with other items. That's fine. Thus we will have Schedule heading with that specific sentence. Now we need to ensure we don't repeat content. So we will not include evenings/weekends in Requirements; we will put it under Schedule. Thus Requirements will contain export control, management prerog