We are looking for an experienced AI Voice Developer to build AI receptionists for service-based businesses. This will be an ongoing relationship, not just a one-time project. If you do great work, we expect to send multiple clients every month. Responsibilities Build an AI receptionist that can: Answer inbound phone calls 24/7 Hold natural conversations using an LLM Answer business FAQs Book appointments into the client's booking software/CRM Transfer calls to the business owner when appropriate Send SMS confirmations and follow-up messages Respond to incoming customer text messages Integrate with APIs when needed (BookingKoala, GoHighLevel, HubSpot, Calendly, etc.) Test and optimize the AI before delivery Requirements Experience with Vapi, Retell AI, Bland AI, or similar voice AI platforms Experience integrating CRMs and booking systems through APIs Strong understanding of prompt engineering for voice agents Ability to troubleshoot and improve call quality Excellent communication Ability to deliver projects within 3–7 days To Apply Please answer the following: Which voice AI platforms have you built on? How many AI receptionists have you built? Have you integrated booking software or CRMs before? Have you worked with BookingKoala? Please send 2–3 demo phone numbers or videos of AI receptionists you've built. What is your flat-rate price per AI receptionist? What do you charge monthly for ongoing support? We are looking for a long-term white-label partner who can fulfill projects as we bring in new clients.

Overview Transit & Flow is a fast-scaling Columbus home services company (plumbing, HVAC, drain, sewer, water heater, sump pump) building a premium, AI-powered operation. We are wiring together a set of best-in-class platforms into one self-functioning system that captures, books, reschedules, reminds, invoices, and follows up with customers automatically across phone, website chat, and Thumbtack. We need a senior integration specialist to stand this up cleanly, end to end, on a short-term contract. This is an execution role for someone who has built production voice-AI and automation systems before, not a learner. Detailed architecture blueprints will be provided to the hired contractor under NDA. What you will build A connected stack with no manual re-entry between systems: • Bland AI voice agents (several agents: inbound scheduler, after-hours and emergency handling, Thumbtack lead agent, and an outbound reminders and follow-up agent) • A website chat agent running the same booking logic in text • Thumbtack Live Connect bridged to a Bland agent via API and webhook, plus the Thumbtack lead feed into our automation bus • Quo.com as the telephony and SMS layer (call forwarding to Bland, SMS send via API, one consistent business number) • GoHighLevel CRM integration (contact sync, pipelines, nurture) • Make.com as the orchestration layer (scenarios for booking, rescheduling, reminders, estimates, invoicing, lead intake, error handling) • Scheduling, rescheduling, cancellation, and automated appointment reminders against our field service management platform (currently Jobber, migrating to OctopusPro, so platform-flexible API work is required) • Email automation including emailing and resending invoices and receipts on request Core responsibilities • Configure Bland pathways, custom tools, and webhooks that read and write to our systems mid-call (check availability, book, reschedule, cancel) • Build robust Make.com scenarios with idempotency, retries, error handling, and alerting • Integrate REST APIs and webhooks across Bland, Quo, GoHighLevel, Thumbtack, the FSM, and email • Bridge Thumbtack Live Connect to a dedicated Bland number so leads are answered live • Implement automated SMS and voice reminders with confirm and reschedule handling • Document everything and deliver a clean handoff so the system is maintainable and scalable Must-have skills • Proven production experience with a voice-AI platform: Bland strongly preferred, or Vapi, Retell, or Synthflow with transferable skill • Advanced Make.com (or n8n) including webhooks, data stores, error handling, and routing • Strong REST API and webhook integration skills, JSON, authentication, signing • GoHighLevel API experience • Telephony and SMS concepts: call forwarding, SIP or number routing, A2P • Ability to design for scale and reliability, not just a demo that works once Nice to have • Quo.com or comparable VoIP platform experience • Thumbtack pro tooling or lead-response automation experience • Home services or field service management background • OctopusPro, Jobber, or similar FSM API experience Engagement • Short-term contract, estimated 3 to 5 weeks • Milestone-based fixed price preferred, hourly considered for the right expert • Async daily updates, a few live working sessions per week • NDA and scoped system access required; you will not receive owner credentials How to apply Do not send a generic proposal. Answer these in your application: 1. Link or describe a voice-AI agent you built that booked or scheduled against a live external API mid-call. What platform, what API, what was the hardest part? 2. How do you make Make.com or n8n scenarios idempotent and resilient to duplicate webhooks and failed calls? 3. In two or three sentences, how would you bridge Thumbtack Live Connect to a voice AI agent so the agent answers the lead live? 4. Your proposed milestone breakdown and realistic timeline for the scope above. 5. How you handle client credentials and secrets securely. Strong applications that show real systems thinking move to a short paid test task before the full award.

I need a advanced agentic system built with persistent memory and up to 6 agents that work together. I am building a franchised coffee shop business. there is so much data that can be pulled together and harvested from customer spending habits and also what is the highest grossing items that sell , vs the most profitable hours of the day. All that data needs to be meshed with the actual Quickbooks data and financials. All that then needs to be balanced with real world site selection for new coffee shop locations. Here is what I need: Agent 1. Pulls information Directly from clover POS automatically. Agent 2. takes Agent's 1 information and cross references with Margin Data from Quickbooks. Recommends New drinks that are both on trend AND High Margin. Agent 3 is the financial Agent. It works directly with Quickbooks. It monitors cash flow and alerts when labor percentage exceeds parameters. It also stress tests expansion and " what if" scenarios. Agent 4. the site selection agent. agent 4 monitors LoopNet, Costar, and parcel data for commercial land available. It cross references traffic count and demographics, it checks competitor coffee presence etc. Agent 5 is the capital strategist. when agent 4 finds a location, it consults with agent 3 which is connected to Quickbooks , it models out loan scenarios, cash flow impact. and helps run " what if " scenarios that it gets asked. Agent 6 is the main Orchestrator that runs everything that I would communicate soley with through Whatsapp. It connects all the agents and pulls data collectively and makes them all work together and stress tests ideas that one agent might find.

I am working through a design agency on an application for their end client. I think the agency will need you to contract with them directly, but I will manage the project for them. I have scoped out the project already, and our plan is to internally perform a design phase with the client to produce a prototype with Lovable. There may be minor changes to scope after that design phase. The purpose of the app is to create bespoke wedding gown concept images for potential customers of an online wedding dress store. I have provided the details below and attached as a PDF 1. Customer opens an AI dress/gown design experience from a link in their separate e-commerce site. - This can be presented in its own page, we don't want a chat window to be present on any other page - This will be a chat-based interface built into the content area of the page, instead of a popup - The design must be elegant, and match the theme of the e-commerce site - The top navbar and footer don't need to be exactly recreated in this subdomain site, but should look similar enough to create a seamless experience - There will be no integration with the e-commerce site, we need to keep these web apps completely separate 2. The customer must sign up for an account and purchase one credit to begin the AI session - We will need to set up the subdomain site with its own payment processing system and login system - The payment integrations are Stripe to facilitate credit card and Apple pay, and a basic Paypal integration 3. The customers should be able to use a magic link to sign into their accounts, instead of having to remember a password - The account should automatically remember the browser to reduce friction for future access to the app 4. When an AI session begins, we will ask the customer a series of questions programmatically to prime the AI agent so that it can deliver better results - The questions will need to use conditional logic, such that the first question which determines one of 3 main conditional tracks: What type of gown are you looking for? Wedding Gown, Evening Gown, Cocktail Dress - If Wedding Gown is selected, the AI should suggest for the customer to take go to a bridal store and pictures of themselves in different dresses they like and upload the pictures, and describe what they do and don’t like about each dress. It can ask this in the freeform chat, since it may make the most sense to let them fill out the entire questionnaire to stay engaged, and we should reduce the costs of development for the questionnaire by omitting any unnecessary UI that the freeform chat can provide. - It may be best to always just prompt for them to upload the inspirational image at the beginning of the freeform chat so we can omit unnecessary programmatic UI, but in the case of the Wedding Gown it will specifically ask the customer to peform the above task. - We may have other specific questions to add to the questionnaire depending on what conditional track the customer chooses, though only the 3 main branches of conditional logic based on dress type will be required. - Examples of general questions it will need to ask are as follows: -- silhouette -- neckline -- sleeves -- fabric -- embellishments -- color -- train -- length -- closure -- lining -- structure -- inspiration -- event type -- I didn’t get the exact list of questions yet from my client that we should ask in the initial questionnaire. Let me know if you will need this information to accurately provide a price for the development of this application 5. We should not display a concept image after the programmatic questionnaire, the customer will be taken directly into the freeform chat from the questionnaire. - The AI agent may start with an overview of the selected choices from the questionnaire, then can generate concept images at its discretion. 6. The AI should guide the customer through a freeform conversation - The conversation should begin with the AI asking the customer to subjectively describe their dream dress 7. The AI should also make a suggestion near the beginning of the conversation for the customer to upload at least one inspirational photo, but photo upload is optional - If the customer uploads an initial inspiration image, the AI agent should not attempt to figure out body type, measurements, or any other information that we can gather programmatically. - It should treat the inspirational image the same way it would treat any image the customer uploads during the freeform chat, to reduce the cost of development as much as possible. 8. Customer can proceed with a freeform conversation description - The customer should have the option to type in a chat and to upload images - The purpose of the conversation is for the customer to describe the desired dress or gown in an open-ended way 9. AI generates one or more concept images based on the conversation, as soon as it can once it has enough information - The AI model we select should be very good at generating these types of images, this is probably the most important quality the AI model needs to have - The concept images should have the same quality as the final image 10. It is acceptable to generate the gown on a mannequin or a real human model, however the dress must be photorealistic, not a sketch or cartoonish rendering. 11. The concept images that the AI generates and the final image should portray the body type and skin color which the customer specifies - It is very important for us to render the image of the garment on the correct body type - ex. Hourglass, pear-shaped, thin, plus sized, etc. -- Specific body measurements do not need to be factored into the rendering of the body type, it just generally needs to be able to render the garment on different body types. - It is also very important for us to render the garment on a human model or mannequin which has the same or similar skin color as the customer inquiring -- This is important for the customer to judge the garment color and fabric type that will look best on them -- This is also important to make the app inclusive for people of all racial backgrounds who might use the app -- It may be best not to display the face, or if human models are used, to use pictures of models with different racial backgrounds, to avoid bizarre mismatches between facial characteristics and skin tone - The AI agent should ideally prioritize pictures of garments from our client’s website to use as inspiration when it generates renderings in the freeform conversation, along with the customer’s description of what they want. However this is not a hard requirement, so it could be eliminated from the requirements if it greatly increases devlopment effort. - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to build the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application. 12. AI asks whether the generated concept is generally what the customer wants - Customer can revise the concept conversationally 13. AI can regenerate or refine images after customer feedback 14. The tone of the conversation the AI has with the customer is important. - We will want it to speak like a friendly expert seamstress. - This requirement will be somewhat subjective and so we will need to budget time for our client to request revisions to this tone based on their review of the system. 16. We ideally want the agent (both chat and image generation) to have deep expertise about fabrics and these types of garments in general, so it can guide the user through prompts, and render the chosen fabrics correctly - I think freeform chat will be necessary for the customer to explain which fabrics should be used where on the garment, instead of gathering this informaton in the programmatic questionnaire - The customer will likely revise the fabric selections after they see the initial renderings of the garment - We would like to avoid the costs of training an AI for this, so ideally we should use commercially available AI models which have been trained for this purpose, instead of having to train our own model. Prompting the AI with this information might be a cost-effective way to teach it this expertise 17. There will be certain restrictions on what types of colors or fabrics can be used in the dress designs - So, the agent should know these restrictions when it has the freeform conversation with the customer. - For example, the store owner will not be able to produce dresses with neon colors, tie dye colors, etc. - Our client will articulate a list of restrictions for us before we begin the project. 18. AI should never display links to other websites, or suggest for the customer to navigate to other websites 19. This AI might not need to be trained specifically for this industry, but we should at least use prompting to direct it to gather this kind of information, and to give it some background about what each of these things mean, so it can describe them to the customer. We basically need to make it as knowledgable as possble while keeping costs low. 20. The AI system the system should remember their active conversation - Since the customer will be required to have an account to use the AI system we can use that to automatically save the AI conversation - The saved conversation should preserve all the information that the customer input since the beginning of the AI session - A customer can only have one active AI session at a time - The customer cannot resume an AI session that has been completed - We don't need to provide a way for the customer to see the details of completed AI sessions 21. AI should have a fallback/human-help option if the customer gets stuck or the AI fails. - The fallback should collect enough information for an admin to follow up manually, so it should present a form in order to ensure that all the necessary information gets collected - A message should be displayed above the form, or somewhere on the page, to inform the customer that the entire conversation will be sent along with the form submission, so they know that they do not have to type all the details of the AI conversation - The app must present a button outside of the chat prompts after 3 - 5 chat messages have been sent, so the customer knows they have the option to terminate the AI conversation and manually ask for help. - That button would display the form - We don't want to display the button before any conversation has happened because we don't want customers to skip the chat altogether. -- One of the business goals of this app is to allow custom inquiries without overwhelming the support staff - Site admins must have the ability to adjust how many messages the button will display after, so they can control this threshold after they observe the results of real conversations - After the button initially displays, it should remain present in the view so the customer can easily access it at any point in the conversation 22. The freeform chat must be limited to something like 50 to 75 messages, in order to avoid excessive charges from the 3rd party AI services - This threshold should be adjustable from an admin portal - If this threshold is reached during the conversation, then we should force the customer to use the fallback form from requirement #21 to submit their inquiry 23. Customer can submit the completed design inquiry when satisfied. - During the submission process, the chat must ask for the following information, and present the following pre-written messages. This doesn't actually need to be executed by the AI model, but it can just be programmatically presented to the customer: - Ask for customer contact info, including name, email, and phone number. - Ask for requested event/date, while making clear the date is not guaranteed. - Ask for seamstress-relevant measurements, including bust, waist, hips, hollow-to-hem, shoulder width, bust point, underbust, waist-to-floor, arm length, bicep, wrist, back width, torso length, height, shoe height, and preferred fit. -- I still have to refine this list with the client, I am not sure if it needs to ask for all these things, or if there are some different things that I haven't listed here which it needs to ask for -- When it asks for this information it should display links under each measurement type to articles which describe how to produce each of the measurements. We can hardcode these links or allow the admin to specify each, they don't need to be generated by AI. - Prewritten disclaimer text should display. 24. The final submission should notify a list of email addresses set by a site admin. 25. The final submission will completely consume the credit used to purchase this AI session - The AI conversation cannot be resumed after the final submission - Another credit must be purchased to start a new AI conversation - New AI conversations will not have any memory of the previous conversations, any new AI conversations will start from a clean slate 26. Admins must have the ability to manually reset a credit, or assign a credit for free and cancel a current session, so the customer can start a new AI conversation. - This doesn't need to be very user friendly for the admin. If a session is reset this way, no knowledge of the previous conversation needs to be preserved. 27. Admins should be able to review partial, or completed conversations within a list in the admin portal - Each line item should display a status indicator to show if the conversation has been submitted yet, if an admin has began the review process, or if the item has been handled: Ex. In Progress, Submitted, In Review, Awaiting Payment, Handling, Ready To Ship, Closed - Admin should be able to see the answers to the programmatic questionnaire - Admin should be able to review the full conversation history - Admin should be able to review all uploaded photos/files - Admin should be able to review all AI-generated images, and the final one should be clear to them - Admin should be able to see the collected technical design details and measurements 28. Pricing of the garment remains manual and is handled by after review, the AI should not give any quote or present any pricing even if asked by the customer. 29. If the customer asks for pricing, the AI should display a prewritten script like this: "Pricing will be determined by the store owner after this conversation has been reviewed." 30. Invoices and payment will be handled manually through native WooCommerce custom order/invoice functionality which is already present in the e-commerce site, the AI system doesn't need to handle this at all. I mentioned this above on the requirements, but I want to reiterate since it is important and a hard requirement for how the development milestones must be structured: - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to do the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application As an optional add-on to the scope of this project, can you give a separate estimate to enhance the AI such that it understands which kinds of modifications will increase or decrease the cost of producing the gown, so it can guide the customer in case they are asking for very expensive things. - It shouldn’t give any specific price numbers, but should give the customer guidance if additions or alterations will significantly increase or decrease the cost of production. - This will be to prevent the customer from being surprised when the store owner manually follows up with them with the price of the garment they designed. This client did agree to adhere to a strict schedule to provide feedback after each round of development, given that we complete each round of development on the schedule we agreed to. - However, this client has deviated from agreed schedules multiple times in the past on other projects I did with them, so you should factor that into your timeline and cost estimations - We cannot increase the development cost mid-way through the project, however we can adjust the development timeline if the client deviates from the schedule In your proposal, please also include a quote or estimate for the cost of hosting and ongoing maintenance after the app has launched - Our client can pay for the hosting directly - We will need at least ongoing updates to patch security vulnerabilities and ensure uptime of the app and all its features which will be defined by the scope of this project - We don't need a 100% 24/7 uptime SLA, but basically just keeping everything up to date so it stays stable, and we'd need someone to respond to outages within 24 hours - Outage response can consist of simple rollbacks, if necessary, as long as all the chat session info is at least provided to the client as a CSV or similar, along with all graphic assets from any conversations, so they don't lose any data from an outage - I would set the expectation with my client that we would treat any future support or enhancement requests to be additionally charged for on an as-needed basis

We are looking for a highly capable AI consultant with a strong technical background in software development, AI-assisted workflows, and research. The ideal candidate is someone who understands modern AI tools, can quickly evaluate information for accuracy, and can help accelerate development, documentation, and decision-making across a variety of projects. * Utilize AI tools such as Claude, ChatGPT, and other leading platforms to support research, analysis, and development * Verify information, identify reliable sources, and distinguish between speculation and fact * Assist with software development, debugging, and technical problem-solving * Build scripts, automations, prototypes, and internal tools as needed * Help organize complex information and knowledge systems, including work within Obsidian * Translate ideas and concepts into actionable plans, technical documentation, and working solutions * Collaborate on a wide range of technical, operational, and strategic projects Qualifications * Strong software development experience * Proficiency with modern programming languages such as Python, JavaScript/TypeScript, or similar * Extensive experience using AI tools, including Claude, ChatGPT, Cursor, and related technologies * Ability to critically evaluate information and conduct high-quality research * Strong understanding of AI concepts, terminology, and emerging technologies * Excellent written and verbal communication skills * Comfortable working independently and navigating ambiguity

We're building an internal operations platform to automate utility account management for a large real estate portfolio. Today, much of this work is manual. Information about utility accounts exists across multiple systems, and employees spend significant time identifying missing bills, reconciling account data, researching exceptions, and coordinating follow-up work. We're building a system that automates these processes by synchronizing data between our operational system and accounting system, applying business rules to identify exceptions, and presenting actionable work queues and dashboards for our operations team. Examples include: Utility accounts that exist in one system but not another Missing or delayed utility bills Accounts requiring setup or closure based on occupancy changes Autopay and e-bill tracking Operational exceptions that require human review Dashboards, work queues, assignments, notes, and status tracking Our internal product manager owns the business requirements and workflows. Your role is to work closely with them to design and implement the technical solution, not to perform business process discovery. What You'll Do Design and use AI to build the application's backend and frontend. Design a clean, maintainable application architecture. Use AI to build dashboards and workflows that allow operations teams to efficiently manage exceptions. Translate product requirements into production-ready software. Leverage AI development tools (Codex, Claude Code, Cursor, or similar) as a core part of your workflow to accelerate development. Review, validate, and refine AI-generated code to ensure quality and maintainability. What We're Looking For We're looking for an experienced software engineer with strong software engineering fundamentals who embraces AI-assisted development. You should understand how modern software applications are architected, designed, built, and deployed, and be comfortable making sound technical decisions while moving quickly. Experience in many of the following areas is preferred: Full-stack application development Application architecture and system design APIs and system integrations SQL databases and data modeling Authentication and security Cloud-hosted applications Testing and debugging Source control and collaborative development We care much more about engineering judgment, speed of execution, and the ability to effectively leverage AI than expertise in any particular language or framework. Nice to Have Experience building internal business applications or operations platforms Experience working with accounting, ERP, or workflow systems Experience building dashboards and operational tooling To Apply Please include: A brief summary of your experience building business applications. The AI development tools you use regularly (Codex, Claude Code, Cursor, Windsurf, etc.) and how they fit into your workflow. Examples of projects where AI significantly accelerated your development process. Your availability over the next 2–3 months and your expected hourly rate.

We're hiring 2 experienced developers to build AIOS deployments for our growing client base. FluentOS is a 9-person team that builds AIOS (AI operating systems) that connect a business's existing platforms together and run AI agents on top of them. We're onboarding 6–7 new client projects every week and need two more builders who can take a project and deliver it. The industries we work in: We deploy across a wide range of professional and service businesses, so you'll get variety: - Financial services & wealth advisory - Tax & accounting firms - Dental and medical practices - Home services & roofing - Property management Each client runs on a different stack — CRMs, comms tools, scheduling, payment systems, document and data sources — and our job is to unify those into one system and build agents that operate across them (lead response, follow-up, reporting, document workflows, estimating, intake, and more). What you'd be building: - AIOS deployments end to end — integrating client platforms via their APIs - AI agents that read/write across those connected systems - Reliable, production-grade automations that real businesses depend on daily What we're looking for: - Proven delivery experience — you've shipped projects clients actually use, not just personal experiments - Strong coding background (Python and/or TypeScript); comfortable with API integrations and agent frameworks - Experience with LLM/agent development (Anthropic/Claude, tool use, multi-step agents) is a big plus - Fast, organized, and communicative — we move quickly and build as a team, not in isolation - Able to work closely with Ray, our lead developer, who'll get you ramped into live projects The setup: - 1099 contract, paid per project — not salaried - Steady, scalable volume (6–7 new projects/week) means consistent work for builders who deliver - Strong potential for ongoing, long-term collaboration as we scale To apply: Tell us briefly about a real project you've built and delivered — ideally something involving API integrations, automation, or AI agents. Include links to work or repos if you have them. Please start your reply with the word "FLUENT" so we know you read this. We'll be scheduling interviews shortly.

Are you an experienced web developer who loves building applications, enjoys mentoring, and is excited about leveraging AI to code faster? I am looking for a sharp, collaborative technical partner to work with me live over Zoom to build out various web applications. A core part of our workflow will involve utilizing Claude (and other AI tools) to brainstorm, scaffold, and accelerate our development process. Instead of working in isolation, you will be partnering with me in real-time to solve problems, review code, architect solutions, and push projects across the finish line. What You’ll Do Live Pair Programming: Join scheduled Zoom calls to actively write, debug, and review code together. AI Collaboration: Work alongside me to prompt, refine, and implement code generated by Claude to speed up the development lifecycle. Web Application Development: Help build, test, and deploy functional, clean web applications from scratch or improve existing codebases. Architectural Guidance: Offer advice on best practices, database design, and framework selection based on project needs. What I’m Looking For Strong Technical Foundations: Proficiency in modern web development frameworks and languages (e.g., JavaScript/TypeScript, React, Node.js, Python, or similar modern stacks). AI-Fluent: You don't just know how to code; you know how to use AI tools like Claude efficiently to debug, generate ideas, and optimize workflows. Excellent Communication & Patience: Since we will be working live on Zoom, you must be a clear communicator who enjoys explaining technical concepts and brainstorming out loud. Problem Solver: A knack for breaking down complex feature requests into manageable, step-by-step development tasks.

Need an experienced developer to integrate an AI-powered feature into an existing application. Small scope, fast turnaround

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.