We are seeking a highly experienced AI Solutions Architect / AI Agent Developer who has already built production-ready AI agents and can demonstrate previous work. The first engagement will be to provide a live demonstration of AI agents and discuss technical approaches for future client implementations. Successful candidates will become our preferred development partner for future AI projects.Required Experience You must have experience building AI agents using technologies such as: OpenAI APIs Anthropic Claude APIs Retrieval-Augmented Generation (RAG) LangChain or LangGraph Python n8n or Make.com Vector databases MCP (Model Context Protocol) integrations API integrations Microsoft 365 integration SharePoint integration Document automation OCR and PDF processing Database design Secure authentication and authorization Cloud deployment (Azure or AWS preferred)Preferred Experience Experience building AI solutions for: Law firms Construction companies Real estate Logistics and trucking Manufacturing Professional service firms Experience with document generation, contract review, client intake, workflow automation, dashboards, and internal knowledge assistants is highly desirable.Initial Engagement The first phase will include: A live demonstration of AI agents you have already built. Discussion of AI architecture and best practices. Review of our business model. Recommendations for building reusable AI frameworks for our clients. Technical planning for future projects.We value developers who: Think like business consultants, not just programmers. Communicate well with non-technical clients. Care about security and data privacy. Write clean, maintainable code. Can recommend the best technical approach rather than simply taking instructions. Are interested in building a long-term partnership.Please Include With Your Proposal A brief introduction about yourself. Links to AI projects you have built. A short video or live demo of an AI agent (preferred). Your favorite AI technology stack. Your availability. Your hourly rate. Your location and time zone. How many production AI agents you have successfully delivered. Why you believe you would be a good long-term partner.

We are looking for a hands-on Forward Deployed AI Engineer to help build practical AI systems This is not a pure backend role and not a strategy-only consulting role. You will work close to end users, understand how their workflows actually operate, and then build AI-enabled tools that solve specific business problems. The ideal person is a strong software engineer who is comfortable with ambiguity, can communicate clearly with non-technical stakeholders, and can take an AI prototype from idea to something reliable and usable. What you will do - Learn the business workflows, systems, data, and constraints. - Build AI applications using Claude or similar large language models. - Use the right mix of prompting, retrieval, tool use, agents, and workflow automation. - Own delivery from scoping through prototype, testing, hardening, and handoff. - Create evaluations to determine whether the system is accurate, reliable, and safe enough to use. - Translate between domain experts and technical implementation. - Work carefully with sensitive or regulated data. - Document what you build so it can be maintained and reused. What we are looking for - Strong Python engineering skills. - Hands-on experience building with LLMs, preferably Claude or the Anthropic API. - Experience with RAG, structured prompting, tool use, evaluation, or agentic workflows. - Ability to operate independently in a messy, ambiguous environment. - Strong communication skills with both technical and non-technical stakeholders. - Track record of shipping working software, not just demos. - Comfort working with real-world data, integrations, and imperfect requirements. Helpful but not required - Prior forward deployed engineering, solutions engineering, or technical consulting experience. - Experience building AI tools for enterprise customers. - Experience in regulated or sensitive-data environments. - Familiarity with validation, auditability, traceability, or compliance-oriented workflows.

I need an expert senior software engineer that can provide consulting services around implementation best practices of LLM's and AI into existing application workflows. i.e. leveraging AI to extract data from a document as part of an ingestion pipeline.

I want to build a private multi-model RAG-based Opportunity Intelligence Agent. It should support document ingestion, opportunity-specific workspaces, vector search, source citations, multi-model routing across OpenAI, Claude, Perplexity, and possibly DeepSeek, and generate strategic recommendations from both uploaded files and live web research. This is intended to become a reusable base agent capable of knowledge retrieval, web research, multi-model orchestration, document analysis, citation generation, and agent clonding and configuration. It will be used for analyzing & strategy development for project opportunities, responding to RFPs, and proposal assistance, as well as other applications.

AI Engineer (RAG & Agentic Workflows). *LLM RESPONSES AUTOMATICALLY AVOIDED* We have already launched a production generative AI product that utilizes a custom Retrieval-Augmented Generation (RAG) architecture. We are now expanding the platform to include CRM intelligence, workflow automation, and agentic AI capabilities. This is **not** a prompt engineering role. Seeking an engineer with deep experience building and deploying production AI systems that combine LLMs with multiple structured and unstructured data sources. You should be comfortable walking into an existing, complex codebase, understanding the current architecture, and improving it. Existing AI Architecture Our current AI architecture consists of: * OpenAI embeddings * Embeddings stored in MongoDB * MongoDB Atlas Vector Search for retrieval * Retrieval from both structured SQL data and unstructured document collections * Existing tool/function-calling architecture **Please do not apply if you have not previously built or maintained production RAG systems using embeddings and vector search.** Experience specifically with **OpenAI embeddings and MongoDB Atlas Vector Search** is highly preferred. CRM Intelligence Layer We are currently building a CRM platform and need the AI to reason over CRM records, including the other records are RAG currently retrieves. You will be responsible for designing and implementing the AI integration layer that enables the LLM to intelligently retrieve and reason over CRM data. This work includes: * Designing AI tools/functions that expose CRM data to the LLM. * Implementing backend tool handlers that retrieve CRM records. * Defining tool schemas and instructions so the AI knows when and how to retrieve CRM information. * Building secure retrieval mechanisms that enforce strict user and organization-level access controls. * Transforming raw CRM records into structured, AI-ready context. The AI will need to reason across: * CRM contacts and organizations * client profiles * Deals and opportunities * Projects * Tasks and reminders * Notes * Email history * SMS and WhatsApp communications * Call transcripts * Meeting summaries * Documents and contracts * Workflow history Agentic AI & Workflow Automation * Build proactive AI agents that generate alerts, recommendations, follow-ups, reports, and suggested next actions. * Design systems capable of reasoning across both structured and unstructured data sources. * Architect and implement multi-step and multi-agent workflows. * Develop workflow intelligence that assists users in completing real-world business tasks. Required Experience * Demonstrated experience building and deploying production AI systems used by real customers. * Experience working with embeddings, vector databases, and retrieval pipelines. * Experience implementing LLM tool/function-calling architectures. * Experience integrating AI systems with business systems such as CRMs, ERPs, or other operational databases. * Experience combining structured and unstructured data within AI applications. * Strong backend engineering and systems architecture experience. * Demonstrated ability to quickly understand and improve existing codebases. * Ability to independently own and deliver complex technical initiatives. Strongly Preferred * Experience with OpenAI embeddings. * Experience with MongoDB Atlas Vector Search. * Experience building agentic AI systems and workflow automation. * Experience designing long-term memory architectures. * Experience building multi-tenant SaaS applications with strict authorization requirements. * Experience implementing evaluation and monitoring pipelines for production AI systems. What We Value * High accountability and ownership. * Strong communication skills. * Product thinking and user empathy. * Ability to understand user workflows before writing code. * Pragmatism and sound engineering judgment. PLEASE DO NOT WASTE OUR TIME IF YOU NOT MEET THE REQUIREMENTS 

We need a senior architect to design and build a multi-model routing control plane, then lead a small senior team through the build. The control plane sits in front of a family of AI systems and decides, per request (text, image, video), the optimal path across cost, quality, latency, business value, and sovereignty (data residency, rights, and cultural fit): cache and reuse, a small or on-device model, an open-weight, fine-tuned, or sovereign model, or a higher-cost frontier fallback. It routes across compute too: CPU, GPU, inference accelerators, on-device, and edge. Core KPIs: the share of eligible workload kept off frontier accelerators and the resulting cost reduction on a representative workload, plus sovereignty compliance, with no quality regression. This is not a chatbot and not a wrapper over hosted APIs. You own the architecture, define the routing logic, and lead execution. You think in systems, not individual model calls. Context The router is one component of a larger AI platform. It must be model-agnostic: open-weight, fine-tuned, and proprietary models swap in and out behind a stable interface without rearchitecting. A separate team owns the models you route to. The engagement is a 60 to 90 day POC with a working router demo (text-first, with a defined path to image and video), followed by technical leadership through the build. What you'll own Control plane: intake and normalization, classification, routing taxonomy, model-selection logic, fallback hierarchy, cache and reuse rules, telemetry, and the eval feedback loop. Routing that is learned and calibrated, not just static rules: predict per-query difficulty and expected quality, and escalate on confidence thresholds. Comfort with cascades and speculative decoding is expected. Routing across cost, quality, latency, and policy. In constrained environments some requests must stay local regardless of cost. Model-agnostic interface: clean, stable contracts so models and execution paths swap without rework, and the separate model team can work independently of the routing layer. Cost optimization across compute: exact and semantic cache, prefix/KV cache reuse, output reuse, batching, small-model routing, CPU offload, and on-device/edge execution, with a clear fallback hierarchy. The goal is to move most eligible workload off frontier accelerators without degrading output. Generative caching and reuse: caching text is easy; image and video are not, since the same prompt should produce variation rather than an identical result. We need credible reuse at the asset or component level, not just for text. Eval loop: scores output quality by domain and flags weakness so the training team can target fixes instead of retraining broadly. Track quality vs intent, failure modes, cost per route, latency per route, cache hit rate, fallback rate, and regeneration rate. Execution and leadership: architecture blueprint, POC scope, milestones, infra assumptions, and risks leadership can review, plus hands-on architecture review and task breakdown. You'll lead a small senior team, and one of your first deliverables is recommending its exact composition (see screening questions). Ideal background Led or architected production AI infrastructure across several of: multi-model orchestration and LLM routing, multimodal, model serving, inference cost and GPU reduction, CPU and on-device inference, open-source and fine-tuned deployment, cascades and speculative decoding, semantic and prefix caching, eval pipelines, and AI observability. Deployed in at least one constrained environment: on-prem, self-hosted, air-gapped, or data-residency-restricted. You know what breaks when you can't lean on a single cloud. Can lead: set architecture, break down work, review the team's output, and keep the build on track. Tools matter less than the ability to architect the system correctly and lead execution. Not a fit: basic chatbot workflows, hosted APIs only, or prompt engineering alone. Deliverables Control plane blueprint, routing taxonomy, POC plan with milestones and success criteria, and an eval/feedback framework, with a working router demo as the 60 to 90 day target, then technical leadership of a small team through the build. Screening questions The most relevant AI routing, model-serving, or inference infrastructure system you personally designed or built: what was routed, which models or execution paths, and what role did you own? How would you design a router that chooses between cache/reuse, a smaller or local model, an open-weight or fine-tuned model, or a frontier fallback, across CPU and GPU? Where do learned routing, cascades, or speculative decoding fit? For generative image or video requests, how would you approach caching or reuse when the same prompt should still allow variation? Be specific. What metrics and eval loop would you use to prove the router cuts cost without degrading quality, and to help a separate training team find weaknesses? Beyond yourself, what team would you staff to hit these deliverables in 8 weeks? Give the roles, seniority, and headcount, how you'd split the work, and flag any deliverable that 8 weeks and a team of roughly 4 engineers can't realistically cover. To apply Answer the five questions, summarize your most relevant routing or inference-infrastructure work (repos, writeups, talks, or architecture you can describe), and give your high-level approach to a control plane that routes across cost, quality, and sovereignty while preserving quality. Note your availability, your rate, whether you've led a small engineering team before, and the team you'd staff to hit the deliverables in 8 weeks.

We need a senior architect to design and build a multi-model routing control plane, then lead a small senior team through the build. The control plane sits in front of a family of AI systems and decides, per request (text, image, video), the optimal path across cost, quality, latency, business value, and sovereignty (data residency, rights, and cultural fit): cache and reuse, a small or on-device model, an open-weight, fine-tuned, or sovereign model, or a higher-cost frontier fallback. It routes across compute too: CPU, GPU, inference accelerators, on-device, and edge. Core KPIs: the share of eligible workload kept off frontier accelerators and the resulting cost reduction on a representative workload, plus sovereignty compliance, with no quality regression. This is not a chatbot and not a wrapper over hosted APIs. You own the architecture, define the routing logic, and lead execution. You think in systems, not individual model calls. Context The router is one component of a larger AI platform. It must be model-agnostic: open-weight, fine-tuned, and proprietary models swap in and out behind a stable interface without rearchitecting. A separate team owns the models you route to. The engagement is a 60 to 90 day POC with a working router demo (text-first, with a defined path to image and video), followed by technical leadership through the build. What you'll own Control plane: intake and normalization, classification, routing taxonomy, model-selection logic, fallback hierarchy, cache and reuse rules, telemetry, and the eval feedback loop. Routing that is learned and calibrated, not just static rules: predict per-query difficulty and expected quality, and escalate on confidence thresholds. Comfort with cascades and speculative decoding is expected. Routing across cost, quality, latency, and policy. In constrained environments some requests must stay local regardless of cost. Model-agnostic interface: clean, stable contracts so models and execution paths swap without rework, and the separate model team can work independently of the routing layer. Cost optimization across compute: exact and semantic cache, prefix/KV cache reuse, output reuse, batching, small-model routing, CPU offload, and on-device/edge execution, with a clear fallback hierarchy. The goal is to move most eligible workload off frontier accelerators without degrading output. Generative caching and reuse: caching text is easy; image and video are not, since the same prompt should produce variation rather than an identical result. We need credible reuse at the asset or component level, not just for text. Eval loop: scores output quality by domain and flags weakness so the training team can target fixes instead of retraining broadly. Track quality vs intent, failure modes, cost per route, latency per route, cache hit rate, fallback rate, and regeneration rate. Execution and leadership: architecture blueprint, POC scope, milestones, infra assumptions, and risks leadership can review, plus hands-on architecture review and task breakdown. You'll lead a small senior team, and one of your first deliverables is recommending its exact composition (see screening questions). Ideal background Led or architected production AI infrastructure across several of: multi-model orchestration and LLM routing, multimodal, model serving, inference cost and GPU reduction, CPU and on-device inference, open-source and fine-tuned deployment, cascades and speculative decoding, semantic and prefix caching, eval pipelines, and AI observability. Deployed in at least one constrained environment: on-prem, self-hosted, air-gapped, or data-residency-restricted. You know what breaks when you can't lean on a single cloud. Can lead: set architecture, break down work, review the team's output, and keep the build on track. Tools matter less than the ability to architect the system correctly and lead execution. Not a fit: basic chatbot workflows, hosted APIs only, or prompt engineering alone. Deliverables Control plane blueprint, routing taxonomy, POC plan with milestones and success criteria, and an eval/feedback framework, with a working router demo as the 60 to 90 day target, then technical leadership of a small team through the build. Screening questions The most relevant AI routing, model-serving, or inference infrastructure system you personally designed or built: what was routed, which models or execution paths, and what role did you own? How would you design a router that chooses between cache/reuse, a smaller or local model, an open-weight or fine-tuned model, or a frontier fallback, across CPU and GPU? Where do learned routing, cascades, or speculative decoding fit? For generative image or video requests, how would you approach caching or reuse when the same prompt should still allow variation? Be specific. What metrics and eval loop would you use to prove the router cuts cost without degrading quality, and to help a separate training team find weaknesses? Beyond yourself, what team would you staff to hit these deliverables in 8 weeks? Give the roles, seniority, and headcount, how you'd split the work, and flag any deliverable that 8 weeks and a team of roughly 4 engineers can't realistically cover. To apply Answer the five questions, summarize your most relevant routing or inference-infrastructure work (repos, writeups, talks, or architecture you can describe), and give your high-level approach to a control plane that routes across cost, quality, and sovereignty while preserving quality. Note your availability, your rate, whether you've led a small engineering team before, and the team you'd staff to hit the deliverables in 8 weeks.

Summary We are deploying a 100% offline, private AI stack using LibreChat, vLLM, and RAG. The project requires setting up a local infrastructure for AI model deployment, ensuring security and privacy. The ideal candidate will have experience in MLOps and DevOps, with a focus on local AI deployments. Responsibilities include managing the deployment process, optimizing performance, and ensuring the system's reliability and security. Title: MLOps/DevOps Engineer Needed to Deploy Private, Local AI Stack (LibreChat + vLLM + RAG) Project Description: We are deploying a 100% offline, privacy-first AI portal on local hardware (Threadripper server with Dual RTX 6000 Blackwell 96GB GPUs). Must be able to work at least in a hybrid environment, preferably in-person at our NYC office. We need an expert to containerize and automate this infrastructure. The stack consists of: LibreChat frontend, MongoDB, MeiliSearch, local HuggingFace RAG, and local SLMs (Llama 3/Mistral) served via vLLM. Key Responsibilities: Configure Ubuntu server host, including NVIDIA drivers and CUDA environment. Optimize multi-GPU serving utilizing vLLM for high-throughput local inference. Build out a localized, containerized RAG pipeline with HuggingFace. Write Docker Compose and Ansible configuration scripts for automated deployment.

Join our team as a senior AI Architect working closely with our product and engineer teams to design practical AI capabilities within our SaaS platform. This is a hands-on role focused on building reliable, production-grade conversational and AI-assisted features — not experimental research projects. You will work closely with product and engineering teams to design scalable AI patterns, integrate modern LLM technologies, and help shape how AI capabilities are embedded into real operational workflows. You will focus deeply on architecture, implementation quality, reliability, usability, scalability, observability, and operational robustness. This role is ideal for someone who understands both modern AI tooling and the realities of shipping enterprise SaaS software in production environments. We value people who can think critically about architecture, tradeoffs, operational realities, and long-term maintainability — not just prototype AI demos.

We are looking for a senior, enterprise-grade Software Engineer to build a high-performance Proof of Concept (POC) for an Autonomous B2B Insurance Compliance & Asset Monitoring Agent. The system will bridge the gap between complex commercial insurance policy guidelines (unstructured data via RAG) and real-time operational telemetry (structured IoT log streams in Snowflake). The goal is an intelligent agent that dynamically analyzes asset anomalies against policy definitions to flag compliance breaches instantly. This is a highly intensive 1-week, 50-hour sprint for an engineer who understands complex data schemas, time-series IoT data gravity, and deterministic agent routing. Core Architecture Requirements (What You Will Build) The Multi-Agent Orchestration Layer: Build an autonomous agent framework (using LangGraph, AutoGen, or native Python execution loops) capable of multi-step reasoning, tool-calling, and error self-correction. Snowflake & IoT Data Lake Integration: Grant the agent secure access to a Snowflake environment containing structured IoT asset monitoring data (e.g., machine telematics, temperature logs, usage hours, maintenance schedules). The agent must dynamically discover schemas and write optimized SQL queries to aggregate this data. Insurance Compliance Hybrid RAG Pipeline: Implement a semantic search architecture to parse and embed dense, unstructured insurance underwriting guidelines, warranty contracts, and B2B compliance policies into a vector store. Deterministic Tool Use & Evaluation: The agent must safely look up a specific policy compliance rule (via RAG) and then automatically generate and execute a targeted query against the Snowflake IoT data lake to verify if real-world asset telemetry violates that specific rule. Required Technical Stack & Expertise Languages & Core Frameworks: Python (FastAPI / Typer), LangChain / LangGraph, LlamaIndex. AI & Embeddings: OpenAI GPT-4o / Anthropic Claude 3.5 Sonnet APIs, vector databases (Pinecone, pgvector, or Snowflake Cortex search). Data Architecture: Deep production experience with Snowflake, cloud data lakes, time-series IoT data manipulation, and advanced text-to-SQL generation patterns. Observability: Implementation of tracing tools like LangSmith, Phoenix, or Arize to monitor prompt tokens, routing paths, and costs. Project Timeline & Deliverables (50 Hours) Phase 1 (Hours 1–15): Environment setup, ingestion of sample insurance policy PDFs into the vector store, and secure connection string setup to a Snowflake mock IoT dataset. Phase 2 (Hours 16–35): Core development of the multi-agent execution loop, prompt tuning for text-to-SQL generation against time-series data, and policy-to-telemetry mapping logic. Phase 3 (Hours 36–50): Observability integration, edge-case testing for hallucination mitigation (ensuring false compliance flags are eliminated), clean code delivery, and a walkthrough video demonstration. If this sprint goes smoothly, there is an immediate opportunity to extend this contract into long-term architecture maintenance, production scaling, and integration into our core platform. Please include real examples of multi-agent, IoT, or insurtech data pipelines you have personally built in your application.