Mission Engineer II - Raleigh

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 as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the job posting. First paragraph: "Join Axon and be a Force for Good." etc. That's about the company. Could be "About the role" or "About Axon". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading. Then "Your Impact" section: description of role. Could be "Responsibilities". Actually "Your Impact" describes what you'll do. Could be under "Responsibilities". We'll treat as Responsibilities. Then "What You’ll Do" with subheadings: Location: On Site with travel Reports To: Manager or Senior Manager of Mission Engineering. Then bullet points under sections: Discover the Mission, Build With the Platform, Transform Builds Into Outcomes, Be the Agency's Go-To Technical Resource, Learn in the Field. Improve Axon. Those are responsibilities/duties. Then "What You Bring" with Required and Preferred. That's Requirements/Qualifications/Skills. Then "What Success Looks Like" maybe could be part of Responsibilities or separate? Could be a section but not in list. Might be omitted if not needed. But we can include as "Success Criteria" maybe not required. The instruction: include a section ONLY when the posting has real, specific content for it. We have content for Success Looks Like. Could be a separate section like "What Success Looks Like". But not in the example list. However we can still use

for any heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those categories. We can map content to those. Thus: - About the role: company mission description. - Responsibilities: all the "What You’ll Do" bullet points and subpoints. - Requirements: Required experience. - Qualifications: maybe Preferred? Could combine Requirements and Qualifications. But we have both Required and Preferred. Could put Required under Requirements, Preferred under Qualifications or Skills. Or we could have Requirements (Required) and Qualifications (Preferred). Skills maybe separate: technical skills like Python, JavaScript etc. But we can put them under Skills. - Benefits: list of benefits. - Pay: not specified (just "Competitive salary"). That's vague but it's mentioned: "Competitive salary and 401k with employer match". That's compensation. Could be Pay section. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Competitive salary and 401k with employer match. So we can include Pay. - Schedule: not specified (no mention of schedule). So omit. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include details like location, reports to, etc. Those could be part of Responsibilities or maybe a separate "Details". But we can embed location and reports to within Responsibilities as a paragraph. We must not include boilerplate: EEO, legal, privacy, phishing alert, etc. Remove those. Also remove duplicated lines: there may be duplicates? Not obvious. Now craft HTML. Structure:

About the role

Join Axon and be a Force for Good. At Axon, we’re on a mission to Protect Life. We’re explorers, pursuing society’s most critical safety and justice issues with our ecosystem of devices and cloud software. Like our products, we work better together. We connect with candor and care, seeking out diverse perspectives from our customers, communities and each other. Life at Axon is fast-paced, challenging and meaningful. Here, you’ll take ownership and drive real change. Constantly grow as you work hard for a mission that matters at a company where you matter.

Responsibilities

Location: On Site with travel. Reports To: Manager or Senior Manager of Mission Engineering.

• Discover the Mission: Embed with assigned agencies to understand their mission, people, workflows, systems, and priorities; develop broad knowledge of the Axon ecosystem and deeper expertise in the products deployed at your agency; work with frontline users, technical teams, and agency leadership to uncover operational friction; translate customer problems into clear technical requirements and measurable success criteria; identify opportunities for AI, automation, data, and Axon capabilities to improve how the agency operates; understand what the customer needs—not simply what they initially ask for.
• Build With the Platform: Build applications, dashboards, workflows, automations, and using Axon products and other approved Axon tools; apply foundational software engineering concepts including APIs, data structures, scripting, testing, debugging, and version control; use AI and AI-assisted development tools responsibly within Axon's approved development and security environment; configure and extend capabilities across Axon's technology ecosystem; understand when you can solve the problem yourself and when deeper Product or Engineering partnership is required; build with Axon—not around it.
• Transform Builds Into Outcomes: Move solutions from discovery into real customer use; test and iterate alongside the people who will actually use what you build; drive adoption and measure results against agreed success criteria; continue improving solutions until they create sustained operational value; document successful solutions so they can be maintained, improved, and reused.
• Be the Agency's Go-To Technical Resource: Maintain a consistent onsite presence and deep understanding of the agency's Axon environment; lean into critical customer needs when your technical context or involvement can materially improve the outcome; help quarterback technical alignment around important deployments without replacing the teams responsible for deployment execution; serve as a liaison when complex technical issues require coordination beyond standard Support; help customers navigate capabilities across products such as Records, Fusus, AI Era, and the broader Axon ecosystem; connect the right resources across Product, Engineering, Support, Deployment, Training, Mission Operations, Mission Success, and Sales; continuously ask: What are we learning, what could work better, and what could we build so this is easier next time?; return to the highest-value build opportunities once immediate customer needs are addressed.
• Learn in the Field. Improve Axon: Capture recurring customer needs, workflow patterns, and technical friction; share successful builds and lessons across Mission Engineering; bring platform limitations and customer insights back to Product and Engineering; identify solutions that could be reused by other MEs and agencies.

Requirements

• Typically 3–5+ years of experience in solutions engineering, software engineering, systems, technical consulting, implementation engineering, or another hands-on technical role.
• Foundational software engineering capability and demonstrated experience building technical solutions.
• Working knowledge of APIs, scripting/programming, data, testing, debugging, and modern development practices.
• Understanding of AI concepts and practical applications.
• Strong technical curiosity and ability to rapidly learn emerging platforms and tools.
• Ability to solve ambiguous problems rather than simply execute predefined tasks.
• Strong communication skills across technical and non-technical audiences.
• Customer-facing mindset and curiosity about how organizations actually operate.
• Ability to obtain and maintain CJIS compliance and satisfy applicable agency background requirements.
• Ability to maintain the onsite presence required by the engagement.

Qualifications

• Experience with Python, JavaScript, SQL, REST APIs, cloud platforms, or modern frameworks.
• Experience with AI platforms, workflow automation, low-code development, or data.
• Experience in public safety, defense, military, intelligence, government, or other mission-critical environments.

Skills

(Optional) Could list but we already have qualifications. Might skip Skills to avoid thin section. But we have content for Skills? Not explicitly. Could combine Qualifications as Skills. But we already have Qualifications. Might omit Skills section to avoid thin. Better to have Requirements (Required) and Qualifications (Preferred). That's fine.

Benefits

• Competitive salary and 401k with employer match
• Discretionary paid time off
• Paid parental leave for all
• Medical, Dental, Vision plans
• Fitness Programs
• Emotional & Mental Wellness support
• Learning & Development programs

Pay

Competitive salary and 401k with employer match (as noted in Benefits).

But we duplicated salary info. Better to keep Pay separate maybe just mention competitive salary. However Benefits already includes Competitive salary and 401k with employer match. To avoid duplication, we could move salary to Pay and keep benefits other items. Let's restructure: Pay: Competitive salary and 401k with employer match. Benefits: Discretionary paid time off, Paid parental leave for all, Medical, Dental, Vision plans, Fitness Programs, Emotional & Mental Wellness support, Learning & Development programs. That avoids duplication. Now ensure we didn't include boilerplate: removed EEO, legal, privacy, phishing alert, etc. Check for any leftover boilerplate like "Don’t meet every single requirement? That's ok." That's a motivational statement; it's substantive? It's encouraging to apply. Could be considered part of the posting but not a section. Might be okay to keep as a paragraph under something like "Encouragement". But we don't have a section for that. Could include under About the role or maybe a separate paragraph after Requirements. However it's not a heading; we can include as a

after Qualifications maybe. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that statement. Where to place? Could be after Qualifications as a

encouraging applicants. Also the line "Studies have shown that women and people of color are less likely to apply to jobs unless they check every box in the job description. If you’re excited about this role and our mission to Protect Life but your experience doesn’t align perfectly with every qualification listed here, we encourage you to apply anyways. You may be just the right candidate for this or other roles." That's also substantive. Also "Important Notes" etc includes legal stuff we should remove. But the "Important Notes" includes some non-boilerplate like "The above job description is not intended as, nor should it be construed as, exhaustive of all duties, responsibilities, skills, efforts, or working conditions associated with this job. The job description may change or be supplemented at any time in accordance with business needs and conditions." That's a generic disclaimer but maybe considered boilerplate? It's a standard disclaimer. Likely should be removed as it's legal boilerplate. Also "Some roles may also require legal eligibility to work in a firearms environment." That's specific? Might be considered a requirement. Could be included under Requirements. But it's a note. Might be kept. Also "We collect personal information from applicants to evaluate candidates for employment. You may request access, deletion, or exercise other CCPA rights at axongreenhousesupport@axon.com or via our Axon Privacy Web Form. For more information, please see the Your California Privacy Rights section of our Applicant and Candidate Privacy Notice." That's privacy boilerplate, remove. "Axon’s mission is to Protect Life and