AI Developer / Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Title, Location, Duration, Compensation, Work Requirements, Skillset/Experience (Role Overview, Key Responsibilities, Must-Have Qualifications, Preferred/Nice to Have, Ideal Candidate Profile, Benefits package). Also includes About INSPYR Solutions (company description) but that's boilerplate? It's not required but could be considered "About the role"? Actually "About the role" could be the Role Overview. We'll need to map. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive info, not invent. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop the EEO statements, privacy policy, accommodation contact, etc. Also drop "About INSPYR Solutions" maybe? It's not about the role but company description; could be considered filler but maybe we keep as "About the company"? Not required heading. The instruction says we can include sections only when posting has real specific content. The posting includes "About INSPYR Solutions" paragraph; that's specific content about the company. Could be included under a heading like "About the Company" but not in the list of allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. Thus: - About the role: Role Overview paragraph. - Responsibilities: Key Responsibilities list. - Requirements: Work Requirements (US Citizen, GC Holders or Authorized to Work in the U.S.) plus maybe Duration? Duration is not a requirement but could be included elsewhere? Not in list. Could be omitted? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include Duration and Location somewhere. Where? Could be in a short

under About the role? Or maybe we can create a "Schedule" section? Schedule is about onsite days: Hybrid, 2 days onsite (Tuesday & Wednesday). That's schedule info. So we can put Schedule section with that detail. - Pay: Compensation: $100/hr. - Benefits: Benefits package includes: Comprehensive medical benefits, Competitive pay, 401(k) retirement plan…and much more! That's vague but includes specific items. We can list those. - Requirements: maybe also include Must-Have Qualifications and Preferred/Nice to Have. Those are qualifications/skills. The headings: Requirements, Qualifications, Skills. We need to decide distribution. We have Must-Have Qualifications (6+ years software dev, 1+ year hands-on AI, strong Python/LangChain/LangGraph, experience building/deploying AI agents into production, understanding of RAG, vector DBs, LLM-based apps, experience designing scalable multi-agent architectures). Preferred/Nice to Have: CIAM experience, AI identity and governance, MCP servers/API/tool integrations, U.S. educational background. Ideal Candidate Profile: hands-on AI engineer with architect-level thinking, experience taking AI agent from dev through production, understand agents interact with tools/APIs, capable of designing scalable multi-agent platform. We could put Requirements as the mandatory qualifications (Must-Have). Qualifications as Preferred/Nice to Have? Or Skills as specific technical skills (Python, LangChain, LangGraph, etc). But we need to avoid duplication. Better: Use Requirements for mandatory qualifications (Must-Have). Use Qualifications for Preferred/Nice to Have. Use Skills for technical skills list (Python, LangChain, LangGraph, etc). However Must-Have already includes those skills. Might be okay to have overlapping but we need to preserve all info; duplication is okay if it's from source? The instruction: do not repeat job title as heading, do not put Job ID etc. It didn't forbid repeating content across sections, but better to avoid duplication. However we must preserve all substantive info; we can split. Let's extract: Location: Irving, TX - Hybrid, 2 days onsite (Tuesday & Wednesday) Duration: 6 months with possible extension Compensation: $100/hr Work Requirements: US Citizen, GC Holders or Authorized to Work in the U.S. Role Overview: We are seeking a Senior AI Engineer who can build, architect, and deploy production-ready AI agents using open-source LLMs. This is a hands-on engineering and architecture role focused on taking AI solutions beyond POCs and into production. Key Responsibilities (list): - Build and deploy AI agents using open-source LLMs. - Develop multi-agent architectures, including an agent aggregator that delegates tasks to specialized AI agents. - Architect the AI platform so additional agents and capabilities can be easily added in the future. - Use Python, LangChain, and LangGraph to develop agentic AI solutions. - Integrate agents with MCP servers, APIs, and AI tools to execute business functions. - Establish AI governance and identity controls, defining what AI agents are permitted to access and perform. - Build and leverage vector databases and RAG to support agent decision-making and action authorization. - Understand how to host and operationalize AI agents and vector databases in a production environment. - Design and build an actual production product, not simply a proof of concept. - Work at an architecture level while remaining highly hands-on with development. Must-Have Qualifications: - 6+ years of software development experience. - 1+ year of hands-on AI experience. - Strong experience with Python, LangChain, and LangGraph. - Experience building and deploying AI agents into production. - Understanding of RAG, vector databases, and LLM-based applications. - Experience designing scalable multi-agent architectures. Preferred / Nice to Have: - CIAM / Customer Identity & Access Management experience. - Experience with AI identity and governance. - Experience working with MCP servers and API/tool integrations. - U.S. educational background. Ideal Candidate Profile: The ideal candidate is a hands-on AI engineer with architect-level thinking. They should have experience taking an AI agent from development through production, understand how agents interact with tools/APIs, and be capable of designing a scalable multi-agent platform rather than building a one-off POC. Benefits: Our benefits package includes: Comprehensive medical benefits, Competitive pay, 401(k) retirement plan…and much more! Now map to headings: - About the role: Role Overview paragraph. - Responsibilities: list of Key Responsibilities. - Requirements: Work Requirements (US Citizen etc.) plus maybe Duration? Duration is not a requirement but could be placed under Schedule? Actually schedule is about onsite days. Duration is separate; we could put Duration under About the role as extra sentence? But we must preserve all info. Could add a short paragraph after Role Overview: "Location: Irving, TX - Hybrid, 2 days onsite (Tuesday & Wednesday). Duration: 6 months with possible extension." That fits under About the role. - Qualifications: Preferred/Nice to Have list. - Skills: Must-Have Qualifications? Or maybe Skills: technical skills (Python, LangChain, LangGraph, etc). But Must-Have includes those. Could treat Must-Have as Qualifications (mandatory) and Preferred as Skills? But we already have Qualifications heading for Preferred. Let's decide: Option: Requirements = Mandatory qualifications (Must-Have). Qualifications = Preferred/Nice to Have. Skills = maybe we can list specific technical skills extracted from Must-Have (Python, LangChain, LangGraph, etc) but that duplicates. Better to avoid duplication: we can put Must-Have under Requirements, Preferred under Qualifications, and maybe we don't need Skills section if no distinct skill list beyond those. However the instruction says we can include sections only when posting has real specific content. If we don't have distinct content for Skills, we omit it. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: Role Overview + Location + Duration. - Responsibilities: Key Responsibilities list. - Requirements: Must-Have Qualifications list. - Qualifications: Preferred/Nice to Have list. - Benefits: Benefits package list. - Pay: Compensation. - Schedule: Hybrid, 2 days onsite (Tuesday & Wednesday). (Location already included in About the role; but schedule is separate; we can still include schedule with onsite days.) We must not repeat location in both About the role and Schedule? It's okay but maybe we should keep location only in About the role and schedule only the onsite days. However location includes hybrid detail; schedule could just be "2 days onsite (Tuesday & Wednesday)". We'll keep location in About the role. Now we need to format HTML: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not include / or markdown fences. We'll output something like:

  About the role

  We are seeking a Senior AI Engineer who can build, architect, and deploy production-ready AI agents using open-source LLMs. This is a hands-on engineering and architecture role focused on taking AI solutions beyond POCs and into production. Location: Irving, TX - Hybrid. Duration: 6 months with possible extension.

  Responsibilities

  • Build and deploy AI agents using open-source LLMs.
  • Develop multi-agent architectures, including an agent aggregator that delegates tasks to specialized AI agents.
  • Architect the AI platform so additional agents and capabilities can be easily added in the future.
  • Use Python, LangChain, and LangGraph to develop agentic AI solutions.
  • Integrate agents with MCP servers, APIs, and AI tools to execute business functions.
  • Establish AI governance and identity controls, defining what AI agents are permitted to access and perform.
  • Build and leverage vector databases and RAG to support agent decision-making and action authorization.
  • Understand how to host and operationalize AI agents and vector databases in a production environment.
  • Design and build an actual production product, not simply a proof of concept.
  • Work at an architecture level while remaining highly hands-on with development.

  Requirements

  • 6+ years of software development experience.
  • 1+ year of hands-on AI experience.
  • Strong experience with Python, LangChain, and LangGraph.
  • Experience building and deploying AI agents into production.
  • Understanding of RAG, vector databases, and LLM-based applications.
  • Experience designing scalable multi-agent architectures.

  Qualifications

  • CIAM / Customer Identity & Access Management experience.
  • Experience with AI identity and governance.
  • Experience working with MCP servers and API/tool integrations.
  • U.S. educational background.

  Benefits

  • Comprehensive medical benefits
  • Competitive pay
  • 401(k) retirement plan
  • and much more!

  Pay

  $100/hr

  Schedule

  2 days onsite (Tuesday & Wednesday)

  Check for any boilerplate removed: we removed EEO statements, privacy policy, accommodation contact, About INSPYR Solutions company description, etc. Good. We preserved all substantive info: role overview, responsibilities, must-have, preferred, benefits, pay, schedule, location, duration, work requirements (US Citizen etc.) Wait we omitted Work Requirements (US Citizen, GC Holders or Authorized to Work in the U.S.). That is important. We need to include that somewhere. Could be under Requirements as well