Sr. AI Engineer

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, job title is Senior AI Engineer (not to be repeated as heading). We need sections: - About the role: likely the introductory paragraph describing the role, mission, etc. The posting starts with description of Fieldpiece, then "We're looking for a Senior AI Engineer...". So we can have About the role covering that. - Responsibilities: bullet list of duties from "What You'll Do" section. - Requirements / Qualifications: The posting has "Qualifications" section with bullet list. Also "Even Better If You Have" maybe considered preferred qualifications. Could combine into Requirements (must-have) and maybe Skills? But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have Qualifications (must have) and maybe Skills (technical skills). Could separate: Requirements (maybe education + experience) and Skills (technical). But we can also just have Qualifications covering all. However we need to avoid thin sections. Let's see content: Qualifications bullet list includes: - Bachelor’s degree in CS, AI, or related fields. - 5+ years of professional software engineering experience, including ownership of production applications. - 2+ years of hands-on experience building solutions using modern AI technologies, including large language models. - Experience taking ambiguous business problems and translating them into practical technical solutions. - Hands-on experience with prompt design, retrieval architectures, AI application testing, and model/system evaluation. - Experience building AI agents, multi-agent systems, tool-using agents, RAG solutions, or complex agentic workflows. - Experience integrating APIs, cloud services, enterprise applications, and data sources. - Strong proficiency in Python or another modern language used for AI application development. - Experience with data engineering, analytics, BI, MLOps/LLMOps, observability, or cloud deployment. - Experience with source control, testing, deployment, monitoring, and modern software delivery practices. - Excellent communication skills with the ability to work directly with both technical and nontechnical stakeholders and explain complex technical decisions in business terms. - A practical, curious mindset - you enjoy learning how a business works, asking the right questions, and figuring out how technology can make it better. Then "Even Better If You Have" list: - Experience with Microsoft Dynamics 365 Business Central or integrating solutions with ERP systems, Azure OpenAI, Microsoft Copilot, Power Platform, Fabric, or Dataverse. - Experience working in a product, manufacturing, distribution, or field-service environment. - Exposure to Lean, continuous improvement, or business process reengineering. We could treat "Even Better If You Have" as preferred qualifications, maybe under Skills or Additional Qualifications. But we have headings: Skills could capture technical skills like Python, AI tech, etc. However we already have many technical items in Qualifications. Might be better to have Qualifications (must have) and Skills (preferred/nice-to-have). Or combine. We also have Benefits & Perks section with bullet list. Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section. Schedule: The posting mentions hybrid work schedule: employees typically working onsite three days per week. Additional in-office days may be required... So we have schedule info. So we can include Schedule section. Also location: Orange, CA office with move to Tustin, CA in 2028. Could be part of About the role or maybe separate but not required. We need to remove boilerplate: EOE etc at end. Also remove navigation, cookie, legal, EEO, duplicated lines, application instructions. There's no explicit application instructions besides maybe at end? Not present. We need to preserve all substantive information. Thus produce HTML:

About the role

Fieldpiece is a privately held, global leader in professional HVACR tools and test instruments... We're looking for a Senior AI Engineer to help us turn the potential of AI into practical solutions that help teams increase their efficiency, speed, and accuracy in their everyday jobs. This is a unique opportunity to become our first dedicated AI engineering hire and help shape how AI and automation are used across the organization. You'll partner with teams throughout the business—from Sales, Marketing, Finance, and HR to Product Development, Supply Chain, Operations, Customer Experience, and IT—to understand how they work, identify opportunities for improvement, and build solutions that deliver measurable value. This position is in our Orange, CA office with an exciting move to Tustin, CA in 2028. This role follows a hybrid work schedule, with employees typically working onsite three days per week. Additional in-office days may be required from time to time for onboarding, training, team meetings, project collaboration, or other business needs.

But schedule info maybe better in Schedule section. However About the role can include location and schedule brief. But we also have Schedule section later. We need to avoid duplication. Could put location and hybrid schedule in About the role, and Schedule section just detail? Might duplicate. Better to keep About the role focusing on role purpose, and Schedule section for work arrangement. Thus About the role: description of role, mission, partnership, location, move to Tustin. Schedule: hybrid work schedule details. Responsibilities: bullet list from "What You'll Do". Qualifications: bullet list from "Qualifications" (must have). Skills: bullet list from "Even Better If You Have" (preferred). Benefits: bullet list from "Benefits & Perks". We must not include Pay. Check for any other sections: maybe "Why This Role?" and "Why You'll Enjoy Working at Fieldpiece" and "Our Culture". Those could be considered part of About the role or separate sections like "Why Join" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate "Why This Role?" and "Why You'll Enjoy Working at Fieldpiece" and "Our Culture" into About the role or maybe into a separate section like "About the company". But not in list; we should avoid creating extra headings not in list. So we should fold that content into About the role or maybe into a paragraph within About the role. Thus About the role will include: company description, role purpose, why this role, why you'll enjoy, culture. We must preserve all substantive information, so we need to include those points. Let's extract: - Fieldpiece description: privately held, global leader in professional HVACR tools and test instruments, known for innovative products, investing in people, technology, future. Named one of Best Places to Work in Southern California for four consecutive years. - Why This Role?: not just evaluating AI tools; you'll sit with business teams, understand needs, translate to technical requirements, build, deploy, improve; projects vary; technology agnostic; Microsoft ecosystem experience valuable. - What You'll Do: list of responsibilities. - Qualifications: list. - Even Better If You Have: list. - Why You'll Enjoy Working at Fieldpiece: private company invests long term, focus on innovation, continuous improvement, lasting careers; meaningful impact; ideas heard; expertise valued; contributions shape future; benefits & perks (list). Also culture bullet list. - Our Culture: values list. - Benefits & Perks: list. Thus we need to incorporate all. We'll create sections: About the role: includes company description, role purpose, why this role, why you'll enjoy, culture (maybe summarised). Could be long but okay. Responsibilities: bullet list from What You'll Do. Qualifications: bullet list from Qualifications. Skills: bullet list from Even Better If You Have. Benefits: bullet list from Benefits & Perks. Schedule: hybrid work schedule details. We must not repeat job title as heading. Now ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. We need to use

• for any list of duties/requirements/benefits. For prose use

  . Thus:

  About the role

  Fieldpiece is a privately held, global leader in professional HVACR tools and test instruments. We're known for developing innovative products that technicians rely on every day—and for investing in our people, our technology, and our future. Named one of the Best Places to Work in Southern California for four consecutive years, we're looking for talented people who want to make an impact while growing their careers.

  We're looking for a Senior AI Engineer to help us turn the potential of AI into practical solutions that help teams increase their efficiency, speed, and accuracy in their everyday jobs. This is a unique opportunity to become our first dedicated AI engineering hire and help shape how AI and automation are used across the organization. You'll partner with teams throughout the business—from Sales, Marketing, Finance, and HR to Product Development, Supply Chain, Operations, Customer Experience, and IT—to understand how they work, identify opportunities for improvement, and build solutions that deliver measurable value.

  This role follows a hybrid work schedule, with employees typically working onsite three days per week. Additional in-office days may be required from time to time for onboarding, training, team meetings, project collaboration, or other business needs. The position is based in our Orange, CA office, with an exciting move to Tustin, CA planned for 2028.

  Why this role? This isn't a role where you'll spend your time simply evaluating AI tools or developing proofs of concept that never make it into production. You'll sit down with business teams, understand what they're trying to accomplish and where their processes are slowing them down, translate those needs into technical requirements, determine the right solution, and then build, deploy, and improve it. The projects will vary widely—one may involve automating a manual workflow; another could involve creating an AI agent, improving access to company knowledge, connecting AI to an enterprise system, or building a decision‑support application. The common thread is using technology to solve meaningful business problems. We're technology agnostic and want someone who can choose the right solution for the problem rather than force every problem into the same technology stack. That said, experience within the Microsoft ecosystem—particularly Dynamics 365 Business Central, Azure, Copilot, Power Platform, Fabric, Dataverse, and Microsoft 365—is highly valuable in our environment.

  Why you'll enjoy working at Fieldpiece: As a privately held company, we invest for the long term—in our people, our products, and our future. That means we can focus on innovation, continuous improvement, and building lasting careers rather than chasing short‑term results. Make a meaningful impact with a company where your ideas are heard, your expertise is valued, and your contributions help shape the future of our products and business.

  Our culture at Fieldpiece is built on values that shape how we work, collaborate, and serve our customers every day: Teamwork – we collaborate, support one another, and win as a team; Urgency – we move quickly, stay agile, and focus on what matters most; Respect – we value diverse perspectives and treat everyone with professionalism and integrity; Trust – we build strong relationships through accountability and transparency; Learning – we embrace curiosity, continuous improvement, and personal growth; No Ego – we leave titles and egos at the door, value the best ideas regardless of where they come from, and work together with humility, openness, and mutual respect.

  Then Responsibilities:

  Responsibilities

  • Partner with teams across Fieldpiece to understand their workflows, pain points, and business needs and identify opportunities where AI, automation, or better technology can make a meaningful difference.
  • Take business requirements from concept to solution—designing, developing, implementing, and supporting production-ready applications and automations.
  • Build AI agents, copilots, workflow automations, decision-support tools,