Technical Architect - ML

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Quantiphi (company description) but not "About the role". There's a "Job Summary". Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings based on content. We have: - About Quantiphi (company overview) maybe not needed as heading? Could be "About the role"? Actually "About the role" would be job summary. We have "Job Summary:" paragraph. So we can put that under

About the role

with

containing the job summary. - Responsibilities: there is a "Roles & Responsibilities" section with bullet points (some with sub-bullets). We'll output

• for each duty. Need to preserve all substantive info. The bullet list includes many items, some with sub-bullets indicated by ○. We can treat each top-level bullet as
• and sub-bullets as nested
  • . We'll need to capture them. - Experience Required Skills & Qualifications: This seems to combine experience, skills, qualifications. We can split into Requirements, Qualifications, Skills maybe. But we should not create thin sections. The posting has "Experience Required Skills & Qualifications:" then a paragraph: "6-8 years of hands on experience..." then "Technical Skills - Must Have:" list, then "Technical Skills - Good To Have" list. We could create sections: Requirements (experience), Qualifications (maybe same), Skills (must have and good to have). But we need to avoid duplication. Perhaps combine into one section "Requirements" covering experience and skills. However instruction: prefer few substantive sections over many thin ones. So we could have: - About the role (job summary) - Responsibilities - Requirements (includes experience, must-have skills, good-to-have skills) Optionally Benefits, Pay, Schedule: none present, so omit. We must not include boilerplate like cookie/navigation etc. The text includes some fluff like "If you like wild growth..." that's not boilerplate but could be considered a closing statement; we could include it maybe under About the role? It's not part of job summary but could be included as a paragraph after responsibilities? It's more like a cultural note. Might be considered boilerplate? It's not standard legal; it's a cultural statement. Could keep as part of About the role? Might be okay. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given. Let's extract sections. Job Summary paragraph: "We are seeking an experienced Architect Machine Learning Engineer to architect, build, and deploy production-grade agentic AI systems and multi-agent workflows from the ground up. The ideal candidate will have deep expertise in designing autonomous AI systems that can collaborate, reason, and execute complex tasks with minimal human intervention. You will be responsible for creating scalable, robust agentic workflows using cutting-edge frameworks like CrewAI/Langraph, while ensuring enterprise-grade deployment on major cloud platforms." That's the Job Summary. Now Responsibilities: Under "Roles & Responsibilities" there is a list: - Architect & Build Agentic Systems: Design and develop end-to-end multi-agent systems from scratch. You will create the foundational agent harnesses, define communication protocols, and build orchestration layers using frameworks like CrewAI, Langgraph, and AutoGen. Architectural decisions to ensure: ○ Hierarchical and collaborative multi-agent structures with well-defined agent roles, responsibilities, and communication protocols ○ Dynamic task decomposition, sophisticated tool integration, planning mechanisms (ReAct), and self-correction loops ○ Develop state management systems and memory mechanisms for persistent agent interactions - Engineer Advanced Agent Capabilities: Develop custom agent-tools and define specialized agent-skills that empower agents to perform complex, domain-specific tasks. - Pioneer Context Engineering: Implement advanced context engineering and memory systems to ensure agents maintain state, learn from interactions, and make informed decisions in dynamic environments. - Deploy Production-Grade Solutions: Own the deployment, scaling, and maintenance of robust, low-latency agentic systems on major cloud platforms (GCP, AWS, or Azure). You will implement best-in-class MLOps practices for monitoring, continuous integration/continuous deployment (CI/CD), and system reliability. - Integrate and Optimize LLMs: Integrate LLMs to serve as the core reasoning engines for autonomous agents. You will apply advanced techniques like RAG and PEFT to optimize performance. - Create and maintain comprehensive tool libraries for agents including API integrations, database queries, and external service connections - Design and implement RAG systems using vector databases (Pinecone, Weaviate, ChromaDB) - Develop custom tools and plugins that enable agents to interact with various enterprise systems and APIs - Ensure tool reliability, error handling, and seamless integration within agentic workflows - Implement comprehensive monitoring and tracing systems for agent behavior, performance, cost optimization, and latency analysis - Design novel evaluation frameworks to assess multi-step agentic task success, reliability, and accuracy - Utilize advanced observability tools (LangSmith, Arize AI, or custom solutions) to trace agent decision making processes - Establish metrics and KPIs for measuring agentic system performance in production environments We need to preserve each bullet as
  • . Some have sub-bullets indicated by ○. We'll nest those. Now Experience Required Skills & Qualifications: Paragraph: "6-8 years of hands on experience in machine learning and AI engineering with proven track record of taking ML systems to production" Then "Demonstrated expertise in building multi-agent systems and agentic workflows, preferably with Langraph/CrewAI" Then "Technical Skills - Must Have:" list: - Programming & ML: Expert-level Python proficiency with ML frameworks (TensorFlow, PyTorch, Transformers). Experience with FastAPI, async programming, and microservices architecture - Data & Vector Systems: Hands-on experience with vector databases (Pinecone, Weaviate, ChromaDB) and building scalable RAG systems - Monitoring & Observability: Experience with LLM application monitoring tools (LangSmith, Weights & Biases, custom telemetry solutions) - Proven ability to architect and implement complex AI systems from scratch in production environments - Cloud Platform Expertise: Production-level experience with at least one major cloud platform (AWS, GCP, or Azure), including: ○ Compute services (EC2, GCE, Azure VMs) ○ Serverless functions (Lambda, Cloud Functions, Azure Functions) ○ Container orchestration (EKS, GKE, AKS) ○ Managed AI/ML services (SageMaker, Vertex AI, Azure ML) - Production & DevOps: Strong skills in Infrastructure as Code (Terraform, CloudFormation), CI/CD pipelines (GitHub Actions, Jenkins), and containerization (Docker, Kubernetes) Then "Technical Skills - Good To Have" list (many items). We'll include them as sub-items under a Good To Have list. We need to decide sections: Could have Requirements (experience) and Skills (must have/good to have). But we could combine into one "Requirements" section that includes experience and skills. However the instruction says use headings like Requirements, Qualifications, Skills. We could create: -

    Requirements

    containing experience paragraph and demonstrated expertise. -

    Skills

    containing Must Have and Good To Have lists. But we might also have Qualifications separate? Not needed. We must not create empty sections. So we will output:

    About the role

    Job Summary paragraph

    Responsibilities

    ...

    Requirements

    6-8 years of hands on experience...

    Demonstrated expertise in building multi-agent systems...

    Skills

    Must Have

    maybe? But instruction only mentions h3 for section headings. Could we use

    inside? It didn't forbid other headings, but said use

    for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot use other heading levels for sub-sections. Safer to keep within

    sections only. Could embed Must Have and Good To Have as or

    headings. We'll just use

    Must Have:

    then

    ... Then similarly for Good To Have. We must not repeat job title as heading. Already not. We must not include Job ID etc. Not present. We must remove boilerplate: The text includes "While technology is the heart of our business..." that's fluff but maybe considered company overview. It's not part of job posting specifics? It's generic. Might be considered boilerplate? It's about company culture. Could be considered part of About Quantiphi. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company overview is not exactly boilerplate but could be considered generic marketing. However it's substantive about Quantiphi. Might be considered part of "About the role"? Not exactly. The instruction says "Prefer a few substantive sections over many thin ones." Could we include a section "About Quantiphi"? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings like About Quantiphi. So we should incorporate that info maybe into About the role? But About the role is supposed to be job summary. However we could extend About the role paragraph to include company overview? Might be okay but risk of misrepresenting. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add other headings if needed, but they gave examples. Safer to stick to those. The company overview could be placed under About the role as a preamble? Might be okay. But we must preserve ALL substantive information. If we omit the company overview, we lose info. So we need to include it somewhere. Could put it in a

    before the About the role heading? But then no heading. The instruction says output ONLY the HTML fragment; we can have

    elements without heading. That's fine. So we can have a leading

    with the company overview paragraphs, then

    About the role

    etc. Thus we will output:

    While technology is the heart of our business, a global and diverse culture is the heart of our success. ... (the whole initial paragraph up to "Be part of a trailblazing team...") Actually that includes multiple paragraphs. We'll include all that before the role specifics. Let's copy the initial fluff up to "Be part of a trailblazing team that’s shaping the future of AI, ML, and cloud innovation. Your next big opportunity starts here! For more details, visit: Website or LinkedIn Page." That's the company overview. Then we have "Role Architect Machine Learning Engineer Experience: 8–12 Years Location: New Jersey (Onsite)" This includes role title, experience, location. We should not repeat job title as heading, but we can include this metadata in a short

    or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a

    with that line. Then "Job Summary:" we will put under About the role. Thus final structure:

    While technology is the heart of our business, a global and diverse culture is the heart of our success. We love