Principal Security Design Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Overview, What We’re Looking For, What You’ll Do, What You’ll Need to Succeed, Things That Would be Great if You Brought to the Table, Work Environment, Additional Information (including Base Pay Range, benefits). We must only include sections when posting has real, specific content. Must not include filler like "commensurate with experience". We have Base Pay Range: they gave a description but not actual numbers. They say "Base Pay Range: Actual compensation will be determined based on a variety of factors and this range represents an estimate of compensation at the time of posting." That's vague, not a specific range. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. They didn't give actual numbers, just a statement. So we should not include Pay section. Benefits: they list benefits: medical, dental, vision insurance; 401(k); paid time off; paid holidays; paid parental leave; other discounts and perks. That's specific enough to include Benefits section. Schedule: they mention hybrid work policy: expected to work at least four days per week (approximately 80%) in an Iridium office. That's schedule info. So we can include Schedule section. We must not repeat job title as heading. No Job ID. Must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "Iridium is an Equal Opportunity Employer..." that's EEO boilerplate; should be removed. Also "Additional Information This job description outlines the general nature..." maybe keep? It's generic but maybe not boilerplate? It's a standard disclaimer; could be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Additional Information" paragraph is not exactly EEO but it's a generic disclaimer; might be considered legal boilerplate. Safer to remove it? But we need to preserve ALL substantive information; that paragraph is not substantive about the role. It's a generic disclaimer. I'd remove it. We need to include sections: About the role? The posting has "Company Overview" and "What We’re Looking For". Could treat "About the role" as heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these standard headings where appropriate. We have: - About the role: could combine Company Overview and What We’re Looking For? Actually "About the role" is a summary of the role. We have "What We’re Looking For:" which describes the role. Could use that as About the role. - Responsibilities: corresponds to "What You’ll Do:" (list of duties). Use

  • . - Requirements/Qualifications/Skills: "What You’ll Need to Succeed:" is requirements. Also "Things That Would be Great if You Brought to the Table:" could be Skills or preferred qualifications. Could split: Requirements (mandatory) and Skills (preferred). Or combine into Requirements and Skills. We need to decide sections to emit: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Possibly also Qualifications? But we can map. We must not emit a heading followed by filler/placeholder text. Ensure each heading has substantive content. Let's extract content. Company Overview: Iridium is an award-winning satellite communications company... (paragraph). That's substantive about company, not role. Could be part of About the role? Might be better as About the role includes company overview and what we're looking for. What We’re Looking For: paragraph describing role: building security-critical infrastructure, Principal Security Engineer, etc. That's substantive. What You’ll Do: list of duties (multiple paragraphs). We'll turn each bullet into
  • . The text includes multiple paragraphs each starting with a bold heading? Actually the text: "Security Architecture & Threat Modeling Analyze our AWS-based cloud infrastructure..." It's a paragraph with multiple sentences. Then "Adversarial Testing & Red Team Assessments Conduct or commission..." etc. Then "Identity & Access Flow Security Evaluate how..." etc. Then "Cross‑Functional & External Influence Serve as a tier‑2 security SME..." etc. Then "Foundational Security Practices & Mentorship Help establish early security practices..." etc. We can treat each as a separate duty item. What You’ll Need to Succeed: list of requirements (numbered 1-? plus bullet points). We'll extract each requirement as
  • . The list includes: - 10+ years of experience in network and information security, with demonstrated depth in offensive or adversarial security; red team experience strongly preferred. - Strong applied expertise in AWS security fundamentals (IAM, VPC architecture, common cloud misconfigurations and exploitation patterns). - Solid hands on understanding of modern identity and access protocols (SAML, OIDC, OAuth 2.0, WebAuthn, CTAP), including how these flows can be attacked or strengthened. - Demonstrated ability to communicate security risk clearly to both engineers and non technical stakeholders, including customers and partners. - Experience operating as an individual contributor in a high ambiguity, high trust, small team environment. - Excellent communication skills, with the ability to convey products, deliverables, analyses, and/or issues clearly and confidently, and recognize and adapt to different communication techniques - Can easily build meaningful relationships with others, including senior leadership outside of your own department, and comfortable providing constructive feedback to your team members and management - Be able to analyze a situation or problem, generate effective solutions, and see those solutions through to completion - Must possess the creativity and resourcefulness needed to make reliable decisions and determine methods on new assignments - Can thrive in a dynamic environment by handling multiple tasks and managing shifting priorities - Be proactive in sharing knowledge you’ve learned with others That's many items. Things That Would be Great if You Brought to the Table: list: - Experience with hardware root‑of‑trust, secure elements, or embedded device attestation concepts. - Experience in regulated or compliance‑sensitive industries (financial services, gaming/gambling, critical infrastructure). - Industry certifications (OSCP, CISSP, or similar) are welcome but not a substitute for demonstrated hands‑on depth. - Active security clearance not required; ability to obtain and maintain one is a plus. - We’ll also need you to : Be able to travel up to 20% - This position directly performs under, supports, or is exposed to a U.S. government contract. To comply with the requirements of that U.S. government contract, applicants for this position must be U.S. citizen We need to decide if travel and citizenship are requirements or preferred. They are likely requirements. Could put them under Requirements as well. But they appear in "Things That Would be Great if You Brought to the Table". However travel and citizenship are more like requirements. We'll keep them under Requirements maybe. But we need to avoid duplication. We'll treat "Things That Would be Great if You Brought to the Table" as Skills/Preferred qualifications. Work Environment: description about office setting, hybrid work policy (four days per week). That's schedule info. Benefits: list of benefits. Now we need to output HTML fragment with headings

    and content. We must not include any markdown fences. Let's craft:

    About the role

    Company overview paragraph + What We’re Looking For paragraph combined? Might be too long but okay. We'll put two paragraphs: first company overview, then what we're looking for.

    Responsibilities

    • Security Architecture & Threat Modeling: Analyze our AWS-based cloud infrastructure, APIs, and supporting services to identify realistic attack paths and translate findings into clear defensive priorities. Advise engineering leadership on secure design decisions across cloud infrastructure, application logic, and device/key‑management touchpoints early in the development lifecycle. Develop and maintain service‑specific threat models and guide an emerging threat‑modeling culture for a small, fast‑moving pre‑launch engineering team.
    • Adversarial Testing & Red Team Assessments: Conduct or commission red‑team style assessments spanning network, application, cloud configuration, identity flows, and adjacent supply‑chain vectors. Communicate security findings in terms of business impact, driving pragmatic prioritization and informed decision‑making.
    • Identity & Access Flow Security: Evaluate how Iridium’s service integrates into partner identity and access systems (SAML, OIDC, OAuth 2.0, WebAuthn, CTAP). Identify how these integrations could be attacked, misused, or strengthened, particularly in step‑up authentication and assurance contexts.
    • Cross‑Functional & External Influence: Serve as a tier‑2 security SME in select partner or prospective‑customer conversations where deep technical expertise is required beyond sales engineering capabilities. Collaborate closely with engineering, product, and partner‑facing teams to ensure security decisions are incorporated throughout the service architecture.
    • Foundational Security Practices & Mentorship: Help establish early security practices, lightweight processes, and technical standards appropriate for a pre‑launch product environment. Provide mentorship and guidance to engineers and future security team members as the capability grows.

    Requirements

    • 10+ years of experience in network and information security, with demonstrated depth in offensive or adversarial security; red team experience strongly preferred.
    • Strong applied expertise in AWS security fundamentals (IAM, VPC architecture, common cloud misconfigurations and exploitation patterns).
    • Solid hands‑on understanding of modern identity and access protocols (SAML, OIDC, OAuth 2.0, WebAuthn, CTAP), including how these flows can be attacked or strengthened.
    • Demonstrated ability to communicate security risk clearly to both engineers and non‑technical stakeholders, including customers and partners.
    • Experience operating as an individual contributor in a high ambiguity, high trust, small team environment.
    • Excellent communication skills, with the ability to convey products, deliverables, analyses, and/or issues clearly and confidently, and recognize and adapt to different communication techniques.
    • Can easily build meaningful relationships with others, including senior leadership outside of your own department, and comfortable providing constructive feedback to your team members and management.
    • Able to analyze a situation or problem, generate effective solutions, and see those solutions through to completion.
    • Possess the creativity and resourcefulness needed to make reliable decisions and determine methods on new assignments.
    • Can thrive in a dynamic environment by handling multiple tasks and managing shifting priorities.
    • Proactive in sharing knowledge you’ve learned with others.
    • Willing to travel up to 20% of the time.
    • Must be a U.S. citizen due to U.S. government contract requirements.

    Skills

    • Experience with hardware root‑of‑trust, secure elements, or embedded device attestation concepts.
    • Experience in regulated or compliance‑sensitive industries (financial services, gaming/gambling, critical infrastructure).
    • Industry certifications (OSCP, CISSP, or similar) are welcome but not a substitute for demonstrated hands‑on depth.
    • Ability to obtain and maintain an active security clearance is a plus.

    Benefits

    • Medical, dental, and vision insurance coverage.
    • 401(k) retirement plan options.
    • Paid time off and paid holidays.
    • Paid parental leave.
    • Other discounts and perks