Mission Engineer II - Albuquerque
maybe under About the role? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out the long EEO, privacy, phishing alert, etc. Also remove "Don’t meet every single requirement? That's ok." maybe that's not boilerplate? It's encouraging to apply; might be considered boilerplate? It's part of the posting but not a list; but it's somewhat generic encouragement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Don’t meet every single requirement? That's ok." is not exactly EEO but it's encouraging to apply; might be considered application instructions? It's not exactly instructions to apply, but it's encouraging. Safer to keep? Might be considered fluff but not prohibited. However we should aim to keep substantive info. I'd keep it as a
maybe under "What You Bring" or separate? But it's more of a note. Could be considered boilerplate? Not sure. I'd keep it as a
under "What You Bring" maybe.
We need sections only when posting has real specific content. So we need sections: About the role (maybe a brief intro), Responsibilities (What You’ll Do), Requirements (What You Bring - Required), Qualifications (maybe Preferred?), Skills (maybe list of skills), Benefits (Benefits that Benefit You). Also maybe "What Success Looks Like" could be a section? Not in the list of allowed headings but we could map to something like "How Success is Measured"? But instruction says use those headings as examples; we can use others? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also use other headings if needed? Probably better to stick to those. So we need to map content.
- About the role: could include the introductory paragraph: "Join Axon and be a Force for Good..." plus mission description, life at Axon, etc. Also maybe "Your Impact" section could be part of About the role.
- Responsibilities: "What You’ll Do" includes sub-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. We can turn each bullet into - .
- Requirements: Required qualifications list: "Typically 3–5+ years of experience..." etc. We'll list each as
- .
- Qualifications: Preferred qualifications list: "Experience with Python, JavaScript, SQL..." etc.
- Skills: maybe combine required and preferred? But we already have Requirements and Qualifications. Could also have Skills section for technical skills like APIs, scripting, etc. But we already covered in Required. Might be redundant. Better to have Requirements (required experience) and Qualifications (preferred). Skills maybe not needed. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections.
- Benefits: list from "Benefits that Benefit You": 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. Also note "Benefits listed herein may vary depending on the nature of your employment and the location where you work". That's a qualifier; we could include as a
after list.
We must not include Pay or Schedule sections because not specified.
We must not repeat job title as heading.
We must not include metadata like Location: On Site with travel Reports To: Manager or Senior Manager of Mission Engineering as a heading; we can fold into a short
maybe under About the role or Responsibilities. Probably include as a
after About the role intro.
We must remove boilerplate: the long EEO, privacy, phishing alert, etc. Also remove "Important Notes" etc. Also remove "Some roles may also require legal eligibility to work in a firearms environment." That's maybe relevant? It's a note about eligibility; could be considered boilerplate? It's a condition; maybe keep as a short note under Requirements? But it's not a requirement per se; it's a note. Might be considered boilerplate? I'd drop it.
Also remove "We collect personal information..." etc.
Also remove "Axon’s mission is to Protect Life..." etc.
Also remove "We are an equal opportunity employer..." etc.
Also remove "If you have a disability..." etc.
Also remove "Phishing alert:" etc.
Also remove "Don’t meet every single requirement? That's ok." maybe keep as encouragement but it's not boilerplate; but it's kind of generic. I'd keep it as a
under Requirements or Qualifications.
Now produce HTML fragment.
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.
Location: On Site with travel. Reports To: Manager or Senior Manager of Mission Engineering.
Then Responsibilities:
Responsibilities
- 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:
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.
Don’t meet every single requirement? That's ok. At Axon, we Aim Far. We think big with a long‑term view because we want to reinvent the world to be a safer, better place. We are also committed to building diverse teams that reflect the communities we serve.
Qualifications (Preferred):
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.
Benefits:
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
Benefits listed herein may vary depending on the nature of your employment and the location where you work.
We should not include any extra sections like "What Success Looks Like". Could we incorporate that into Responsibilities? It's about measuring success; maybe we could add a note under Responsibilities but it's okay to omit as it's not required heading. However we need to preserve ALL substantive information; we cannot omit "What Success Looks Like". That is substantive. So we need to include it somewhere. Could be a section "How Success is Measured" but not in allowed headings. However we could embed it under Responsibilities as a subsection? The instruction: Use for section headings (e.g. About the role, Responsibilities
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). So we need to strip out the long EEO, privacy, phishing alert, etc. Also remove "Don’t meet every single requirement? That's ok." maybe that's not boilerplate? It's encouraging to apply; might be considered boilerplate? It's part of the posting but not a list; but it's somewhat generic encouragement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Don’t meet every single requirement? That's ok." is not exactly EEO but it's encouraging to apply; might be considered application instructions? It's not exactly instructions to apply, but it's encouraging. Safer to keep? Might be considered fluff but not prohibited. However we should aim to keep substantive info. I'd keep it as a
maybe under "What You Bring" or separate? But it's more of a note. Could be considered boilerplate? Not sure. I'd keep it as a
under "What You Bring" maybe. We need sections only when posting has real specific content. So we need sections: About the role (maybe a brief intro), Responsibilities (What You’ll Do), Requirements (What You Bring - Required), Qualifications (maybe Preferred?), Skills (maybe list of skills), Benefits (Benefits that Benefit You). Also maybe "What Success Looks Like" could be a section? Not in the list of allowed headings but we could map to something like "How Success is Measured"? But instruction says use those headings as examples; we can use others? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we could also use other headings if needed? Probably better to stick to those. So we need to map content.
- About the role: could include the introductory paragraph: "Join Axon and be a Force for Good..." plus mission description, life at Axon, etc. Also maybe "Your Impact" section could be part of About the role.
- Responsibilities: "What You’ll Do" includes sub-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. We can turn each bullet into - .
- Requirements: Required qualifications list: "Typically 3–5+ years of experience..." etc. We'll list each as
- .
- Qualifications: Preferred qualifications list: "Experience with Python, JavaScript, SQL..." etc.
- Skills: maybe combine required and preferred? But we already have Requirements and Qualifications. Could also have Skills section for technical skills like APIs, scripting, etc. But we already covered in Required. Might be redundant. Better to have Requirements (required experience) and Qualifications (preferred). Skills maybe not needed. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections.
- Benefits: list from "Benefits that Benefit You": 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. Also note "Benefits listed herein may vary depending on the nature of your employment and the location where you work". That's a qualifier; we could include as a
after list.
We must not include Pay or Schedule sections because not specified.
We must not repeat job title as heading.
We must not include metadata like Location: On Site with travel Reports To: Manager or Senior Manager of Mission Engineering as a heading; we can fold into a short
maybe under About the role or Responsibilities. Probably include as a
after About the role intro.
We must remove boilerplate: the long EEO, privacy, phishing alert, etc. Also remove "Important Notes" etc. Also remove "Some roles may also require legal eligibility to work in a firearms environment." That's maybe relevant? It's a note about eligibility; could be considered boilerplate? It's a condition; maybe keep as a short note under Requirements? But it's not a requirement per se; it's a note. Might be considered boilerplate? I'd drop it.
Also remove "We collect personal information..." etc.
Also remove "Axon’s mission is to Protect Life..." etc.
Also remove "We are an equal opportunity employer..." etc.
Also remove "If you have a disability..." etc.
Also remove "Phishing alert:" etc.
Also remove "Don’t meet every single requirement? That's ok." maybe keep as encouragement but it's not boilerplate; but it's kind of generic. I'd keep it as a
under Requirements or Qualifications.
Now produce HTML fragment.
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.
Location: On Site with travel. Reports To: Manager or Senior Manager of Mission Engineering.
Then Responsibilities:
Responsibilities
- 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:
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.
Don’t meet every single requirement? That's ok. At Axon, we Aim Far. We think big with a long‑term view because we want to reinvent the world to be a safer, better place. We are also committed to building diverse teams that reflect the communities we serve.
Qualifications (Preferred):
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.
Benefits:
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
Benefits listed herein may vary depending on the nature of your employment and the location where you work.
We should not include any extra sections like "What Success Looks Like". Could we incorporate that into Responsibilities? It's about measuring success; maybe we could add a note under Responsibilities but it's okay to omit as it's not required heading. However we need to preserve ALL substantive information; we cannot omit "What Success Looks Like". That is substantive. So we need to include it somewhere. Could be a section "How Success is Measured" but not in allowed headings. However we could embed it under Responsibilities as a subsection? The instruction: Use for section headings (e.g. About the role, Responsibilities
after list. We must not include Pay or Schedule sections because not specified. We must not repeat job title as heading. We must not include metadata like Location: On Site with travel Reports To: Manager or Senior Manager of Mission Engineering as a heading; we can fold into a short
maybe under About the role or Responsibilities. Probably include as a
after About the role intro. We must remove boilerplate: the long EEO, privacy, phishing alert, etc. Also remove "Important Notes" etc. Also remove "Some roles may also require legal eligibility to work in a firearms environment." That's maybe relevant? It's a note about eligibility; could be considered boilerplate? It's a condition; maybe keep as a short note under Requirements? But it's not a requirement per se; it's a note. Might be considered boilerplate? I'd drop it. Also remove "We collect personal information..." etc. Also remove "Axon’s mission is to Protect Life..." etc. Also remove "We are an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "Phishing alert:" etc. Also remove "Don’t meet every single requirement? That's ok." maybe keep as encouragement but it's not boilerplate; but it's kind of generic. I'd keep it as a
under Requirements or Qualifications. Now produce HTML fragment. 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.
Location: On Site with travel. Reports To: Manager or Senior Manager of Mission Engineering.
Then Responsibilities:Responsibilities
- 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.
Don’t meet every single requirement? That's ok. At Axon, we Aim Far. We think big with a long‑term view because we want to reinvent the world to be a safer, better place. We are also committed to building diverse teams that reflect the communities we serve.
Qualifications (Preferred):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.
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
Benefits listed herein may vary depending on the nature of your employment and the location where you work.
We should not include any extra sections like "What Success Looks Like". Could we incorporate that into Responsibilities? It's about measuring success; maybe we could add a note under Responsibilities but it's okay to omit as it's not required heading. However we need to preserve ALL substantive information; we cannot omit "What Success Looks Like". That is substantive. So we need to include it somewhere. Could be a section "How Success is Measured" but not in allowed headings. However we could embed it under Responsibilities as a subsection? The instruction: Use