Looking for an experienced AI developer to help build an AI agent using Claude. Requirements: Experience building AI agents and autonomous workflows Strong experience with Claude and Anthropic models Ability to integrate external data sources and APIs Experience deploying production-ready AI solutions Please include: Examples of similar AI agent projects you've built Your experience with Claude Your recommended tech stack Estimated timeline and cost Looking to start immediately.

Engagement Overview I am the CEO and principal attorney of a small law practice specializing in campaign finance, lobbying regulation, FARA, nonprofit law, and government ethics. My five-person team — a junior partner, two associates, and an executive assistant — recently integrated into a larger firm. I am looking for an experienced Claude/AI automation builder for a phased engagement to design, build, and deploy a suite of interconnected agents and automations. This brief covers three phases. Phase I (Inbox Triage) is the highest immediate priority and the natural starting point. Phases II and III follow sequentially. Strong candidates will be evaluated on Phase I but should demonstrate familiarity with the full roadmap. This is a paid engagement. Scope, timeline, and rate are open to discussion. Technology Stack Email: Gmail (personal Pro account — not firm infrastructure) AI: Claude (Anthropic) via MCP or API Task and project management: Notion (existing workspace; routing tables, matter tracking, and timesheet structure already in place) Calendar: Google Calendar Internal chat: Google Chat Document storage: Google Drive (primary); local hard drives on iMac and MacBook Pro (secondary) Matter management / DMS: iManage (larger firm system — integration via dedicated ingestion email address) Voice notes: Plaud (AI note-taker) Signing platform: TBD — candidates should ask during scoping Out of scope: Signal and iMessage — encrypted platforms with no API access; manual forwarding convention only Confidentiality Requirements This is a law practice. Attorney-client privilege and work product protection apply to all client communications and matter-related documents. These are not compliance checkboxes — they are professional obligations with real consequences. The successful candidate must: • Execute a non-disclosure agreement prior to engagement • Demonstrate genuine understanding of why data handling matters in a legal context — not just technically, but professionally • Never use client names, email content, routing data, or document content for training, testing, or demonstration purposes • Work exclusively within the client's authenticated accounts — no third-party data stores outside the approved stack • Design systems that minimize data exposure — process and route, do not store unnecessarily Generic proposals that do not address confidentiality specifically will not be considered.   Phase I — Inbox Triage Agent Real-time classification and routing of inbound Gmail, with a daily digest to the executive assistant. Objective The principal attorney's Gmail inbox receives high volumes of email across clients, matters, and categories of widely varying priority. The goal is an agent that processes every inbound message, classifies it, routes it to the correct person automatically, and ensures nothing drops — without overloading the executive assistant with triage work she should not be doing. Two-Stage Routing Logic Stage 1 — Sender Classification Every inbound email is classified against a tiered contact list maintained in a Notion database: MVC: Most Valuable Clients — 5 to 10 contacts. Highest priority. HVP: High Value People — 10 to 20 contacts. Some overlap with MVCs. Principal attorney, unless task-type rule applies All other clients: Roster managed in Notion with assigned attorney(s). Assigned attorney(s) per Notion client record Catch-All: Anyone not in the contact table — prospects, opposing counsel, vendors, bar association, etc. Generate executive assistant daily digest Stage 2 — Task-Type Classification (MVCs only) For MVC contacts, a second classification layer routes based on the nature of the request. Rules are client-specific. Examples: • Scheduling requests → Executive assistant • Contracts and approvals → Designated associate(s) per client record • Strategic and substantive legal matters → Principal attorney Task-type rules are defined per MVC client and must be configurable without developer involvement. Routing Table — Notion All contact and routing data lives in an existing Notion database. The agent reads from it at runtime. Required fields: • Contact name and/or email domain • Tier (MVC / HVP / Standard / Catch-All) • Assigned attorney(s) for Standard clients • Task-type override rules for MVCs The executive assistant must be able to add, edit, and re-tier contacts without touching code. This is a hard requirement. Routing Output Candidates should propose their recommended approach from among the following, based on current Gmail MCP capabilities: • Apply Gmail label and/or forward to assigned attorney's address • Create a pre-addressed draft for principal attorney review before sending • Log routing decision to Notion with email link and recommended assignee Please address this question directly in your proposal — it is a key evaluation criterion. Daily Executive Assistant Digest Once per day at a configurable time, the agent generates a digest delivered to a designated Notion page covering all catch-all emails from the prior 24 hours. Each entry includes: sender, subject, timestamp, and a one-line AI summary of the email's apparent purpose.   Phase II — 5 AM Daily Brief A structured morning brief delivered to Notion each day before 5 AM, aggregating schedule, tasks, workflow status, news, and forward-looking context. Objective The principal attorney starts each day across multiple locations and needs a single, consolidated view of what matters — professional and personal — without opening email. The brief is delivered to a dedicated Notion page and covers the sections below in the following order. Section 1 — Daily Schedule Full calendar for the day pulled from Google Calendar. All events, calls, and commitments in chronological order. Section 2 — Open Projects and Undone Tasks Two sub-sections: (a) MVC high-value work — open projects and incomplete tasks for Most Valuable Clients, filtered to substantive legal work only; and (b) Personal — all open personal projects and tasks without exception. Personal items are comprehensive by design: if it is not surfaced here, it will be forgotten. Source: Notion task and project database. Section 3 — Blocking What is the principal attorney specifically holding up? Items where others in the firm are waiting for a review, decision, approval, or action. Source: Notion matter and task records where assignee or status indicates the ball is in the principal attorney's court. Note to builder: this section requires careful logic design. The agent must infer from status fields and assignee data what is genuinely waiting on the principal attorney versus what is simply unresolved. Work with client during onboarding to define the exact field logic. Section 4 — News Digest Industry News Curated digest of overnight developments in: campaign finance law and FEC activity, election administration, lobbying regulation (federal and state), nonprofit political activity, and government ethics. Format: short summary of each item with a link to the full article. Aim for signal, not volume — 5 to 10 items maximum. US Political News 5 to 10 headlines with links covering: presidential politics, US Senate and House elections, and major gubernatorial races. Stories people are actually talking about, not wire service filler. Section 5 — Firm Workflow Matter-level status summary pulled from Notion, organized by client tier and activity: Status Definition Closed Completed yesterday Moving Action taken yesterday Paused No action yesterday Stuck No action in five or more days Client groupings: MVCs (non-high-value work), Standard clients (all work), and any other open matters. Section 6 — One Month Look Ahead Rolling 30-day forward view pulled from Google Calendar covering: regulatory filing dates and compliance deadlines, matter-level deadlines, client birthdays, holidays, and planned vacations or travel. Anything that requires preparation or awareness in the next 30 days. Section 7 — Personal Financial Summary (If Feasible) Summary of personal financial position pulled from Monarch Money, if an API or MCP connector is available. Candidates should investigate Monarch's API access and address feasibility in their proposal. If not currently feasible, this section is omitted without affecting the rest of the brief. Delivery Notion only — not email. A dedicated page refreshed each morning before 5 AM. Previous day's brief should be archived, not overwritten.   Phase III — Night Maintenance Three nightly agents that run after close of business: timesheet creation, document filing preparation, and Plaud note routing. All outputs are delivered to Notion for principal attorney review. Part 1 — Timesheet Creation Objective Each evening, the agent reviews the day's activity across three sources and populates a timesheet in an existing Notion template for the principal attorney's review and finalization. Sources • Google Calendar — all events and calls attended • Gmail sent items — emails sent that day, grouped by client/matter where inferable • Google Chat — internal messages sent, grouped by thread/matter where inferable Note to builder: Google Chat API access will need to be confirmed alongside Gmail and Calendar MCPs. Confirm availability and any OAuth scope requirements in your proposal. Output: Populated Notion timesheet using existing template structure. Principal attorney reviews each morning, adjusts entries as needed, and finalizes. The agent does not finalize — it drafts. Part 2 — Document Filing Objective Each evening, the agent surfaces documents created or edited that day for the principal attorney's review. The attorney flags finals, and the agent forwards them to the firm's iManage ingestion email address for filing. Sources • Google Drive — documents created or modified that day • Local hard drives — iMac and MacBook Pro Note to builder: local hard drive access requires a locally-running component (daemon, Claude Code instance, or folder-watching script) on each machine. Please address your proposed approach to this in your proposal. Alternative approach for consideration: a designated 'Ready to File' folder on each machine that syncs to Google Drive. The attorney drags filing-ready documents into this folder throughout the day; the agent watches the folder and processes from there. Simpler architecture, device-agnostic, and builds a consistent filing habit. Candidates should evaluate and recommend. Output: A Notion page listing all documents surfaced for that day, with document name, location, and last-modified time. Principal attorney marks finals. Agent forwards marked documents to the iManage ingestion email address. iManage filing is handled by firm IT from that point — no direct iManage API integration required. Part 3 — Plaud Note Routing and Archiving Objective: The principal attorney uses a Plaud AI note-taker on calls and meetings. Each evening, the agent pulls new Plaud summaries, routes them to the appropriate team members, archives a copy to Notion tagged to the relevant client matter, and deletes the underlying audio and transcript from Plaud's platform and the local device. Prerequisite — Plaud API Plaud API or webhook access is a prerequisite for this part. Candidates must investigate and confirm availability before scoping. If Plaud does not currently support programmatic access, this part will require a manual export step as a workaround — please address both scenarios in your proposal. Routing Logic: Similar in structure to Phase I inbox triage routing (MVC/HVP/Standard tiers with task-type overrides) but with distinct rules to be defined with the client during onboarding. Do not assume inbox triage rules apply directly. Archiving: One copy of each Plaud summary is saved to Notion as a note, tagged to the relevant client matter. Tagging logic to be defined during onboarding. Deletion: After successful routing and archiving, the agent deletes: (a) the audio and transcript from Plaud's platform via API, and (b) any local copies on the principal attorney's devices. Local deletion requires the same locally-running component described in Part 2. Candidates may propose a unified local agent that handles both Part 2 and Part 3 local operations.   What I'm Looking For Strong candidates will have: • Demonstrated experience building Claude-based automations or agents — not general AI experience • Hands-on experience with Gmail MCP, Google Calendar MCP, and Notion MCP (or equivalent API integrations) • Ability to build systems that non-technical users can maintain — editability and simplicity are as important as technical sophistication • Comfort with phased delivery — Phase I first, Phases II and III following sequentially based on performance • Experience with professional services clients (legal, financial, consulting) is a meaningful plus • Willingness to execute an NDA and work within a legally sensitive environment What to Include in Your Proposal Please address the following specifically. Proposals that do not engage with these questions will not be considered. • Your proposed technical architecture for Phase I — how you would connect Gmail, Claude, and Notion • Your answer to the Gmail MCP routing output question in Phase I (labeling vs. drafts vs. Notion logging) — what is actually supported and what do you recommend • Your assessment of Plaud API availability and your proposed approach for Phase III Part 3 • Your assessment of Monarch Money API feasibility for the Phase II financial summary section • Your proposed approach to local hard drive access for Phase III Parts 2 and 3 — daemon, sync folder, or other • A comparable project you have delivered — describe the client type, the stack, and what made it work • Your estimated timeline and rate for Phase I, and a rough order-of-magnitude estimate for Phases II and III • Confirmation that you are willing to execute an NDA prior to engagement I am looking for someone who has read this brief carefully and has a specific, informed point of view on how to build it. This is phase one of a longer automation roadmap and the right candidate will be a long-term partner, not a one-time contractor.

Build Private AI Chat Tool Using Anthropic Claude API — Law Firm Budget: $1,500–$3,000 fixed price Description: I'm a managing attorney at a small law firm in New York. I need a private, secure web application that gives my 4-person team access to Claude AI for document summarization and legal drafting — using the Anthropic API with Zero Data Retention so no client data is stored externally. What I need built: Browser-based chat interface (works like claude.ai but private) Per-user login (4 users) PDF upload — user uploads a document, selects a task (summarize medical records, extract key facts, etc.), Claude returns structured output Conversation history saved to our own encrypted database, tagged by case number Admin view where I can see all conversations across all users Hosted on a private server with HTTPS/SSL No data logged or stored outside our own database Clean, simple UI — non-technical staff must be able to use it Tech requirements: Anthropic Messages API (claude-sonnet-4-6) Zero Data Retention configured on the API account PostgreSQL or similar database for history Per-user authentication (JWT or similar) PDF text extraction before sending to API Encrypted database at rest You must have: Prior experience with the Anthropic Claude API specifically Experience building secure web apps with user auth and databases Portfolio or examples of similar builds Please answer this in your proposal: have you configured Zero Data Retention on the Anthropic API before? This is a fixed-price project. I own all code upon final payment.

We are building an AI-powered hospitality assistant for full-service restaurants. The product helps guests find the right dishes, increases average check size automatically, and reduces pressure on staff during peak hours — all with zero hardware required. What we need: • Mobile-first web app — opens in the browser, no download required • AI conversation layer using OpenAI GPT-4o or Anthropic Claude API • Owner dashboard for menu management, daily priorities, and live order notifications • Multi-tenant architecture — each restaurant’s data is fully isolated • Real-time notifications between guest interface and staff • Multilingual support: English, Spanish, Arabic • Milestone-based payments with a functional demo at each stage • Full IP transfer on project completion Required: • Live web apps in your portfolio that are currently active • Hands-on experience with OpenAI or Anthropic APIs — name the project • Multi-tenant SaaS experience • Willingness to sign NDA and work-for-hire agreement before project start

About the Role Assembly Software is a B2B SaaS company serving law firm customers and is actively expanding its internal AI capabilities. We are seeking a highly skilled AI contractor to serve as our embedded AI program lead — someone who can own and advance the design, implementation, and governance of AI tooling across the entire organization. This is a hands-on, strategic role. You will work directly with IT leadership and cross-functional teams to assess our current AI landscape, close gaps, and build a mature, secure, and operationally excellent AI program. We are a heavy Anthropic/Claude shop. Strong familiarity with Claude, the Anthropic API, and the Model Context Protocol (MCP) ecosystem is a significant advantage for this role. Core Responsibilities • Audit existing AI tool usage and identify overlaps, gaps, and shadow IT • Design and implement a company-wide AI governance framework • Lead MCP server setup, integration, and lifecycle management • Configure and manage Claude Teams/Enterprise deployments • Build and maintain an internal AI Skill Library for staff use • Define AI security policies and data access controls • Evaluate and recommend new AI tools and vendors • Establish prompt engineering standards and best practices • Connect AI tooling to internal business systems (Salesforce, M365, Asana, and others) • Support AI integrations with sensitive data sources including our data warehouse and CRM • Produce documentation, SOPs, and executive-ready reporting • Train internal staff and stakeholders on AI capabilities and safe usage Required Qualifications • Hands-on AI implementation experience in enterprise environments • Deep familiarity with large language model platforms, particularly Anthropic Claude and OpenAI • Proven experience building and managing MCP (Model Context Protocol) servers and integrations • Strong understanding of AI security — data exposure risks, access scoping, governance controls, and audit logging • Experience integrating AI tooling with business systems such as Salesforce, Microsoft 365, or similar platforms • Ability to author clear governance documentation, security policies, and executive-facing deliverables • Comfortable operating independently with minimal oversight while maintaining strong stakeholder communication Preferred Qualifications • Hands-on experience with the Anthropic Claude API, including system prompt design, tool use, and agentic workflows • Background in B2B SaaS, legal technology, or other regulated industries • Familiarity with SOC 2 compliance requirements as they relate to AI tooling and data access • Prior experience standing up internal AI assistants or Copilot-style tooling connected to live business data • Knowledge of data warehousing and secure query patterns for LLM-to-database integrations • Familiarity with CI/CD workflows and lightweight DevOps for deploying AI services

I need a developer to build an AI visibility audit tool for destination marketing. The core logic is already defined and I have a full spec. I need someone who can build it clean and ship it. What the tool does: it queries ChatGPT, Gemini, Claude and Perplexity with a fixed set of real traveler questions, captures whether a destination shows up and where its competitors land, scores the result, and drafts a short report. Roughly 15+ questions, each run a few times per platform, with web search enabled. What I need built: The query engine across all three platforms, running on my own API keys Integration with my existing scorecard backend A gated flow: a personal emailed link that runs once per user, results delivered by email A saved-run database I can log into and review, so every run is stored from day one Built to be re-run on a schedule later (this becomes an ongoing monitoring product) Two non-negotiables: It runs entirely on my API accounts and keys. Billing and ownership sit with me. I own all code and IP outright. This is a defined, finish-and-ship project, not open-ended. I'll share the full spec with candidates who look like a fit. US-based candidates only. Skills LLM / OpenAI API, Gemini API, Perplexity API, API integration, Python (or your stack — tell me), backend development, database design, prompt engineering If interested, please respond with the following answers to be taken seriously: Describe a tool you've built that calls LLM APIs in production. What did it do and what was your specific role? How would you handle the fact that AI answers vary run to run? How do you make a score that holds up to scrutiny? What's your approach to keeping per-query API costs controlled at volume? Rough estimate on timeline and cost for a project scoped like this.

Rebuild a travel agency SaaS platform from a working no-code prototype to Next.js + Supabase. Features include Notion-style CRM, AI proposal builder (Claude API), client portal, commission tracking, Stripe billing, and Duffel flights API. Row-level security required. Fixed price project. Full working prototype provided as reference.

Description We are a US-based software company that already runs AI coding agents in daily engineering work. We are looking for a senior agentic development expert to help us push further. This is a specialist engagement, not an entry-level or generalist AI role. We want someone who has done this for real teams shipping production code and can go deep quickly. The engagement starts with a focused review of how we use agents today and where they can safely take on more, followed by a practical plan we can act on. Specifics are shared under NDA once we shortlist. You are a strong fit if you: - Have designed and rolled out agentic development workflows for a production engineering team, with results you can point to - Know Claude Code at an expert level: harness setup, context management, custom skills and slash commands, subagents, hooks, and MCP - Have integrated agents into an existing codebase and CI, including automated review and guardrails - Can advise on running agents securely around proprietary code and secrets - Can assess a team's current setup and turn it into concrete, sequenced steps This is probably not the right fit if: - Your experience is mostly personal projects, tutorials, or casual use of AI chat tools - You have used AI coding tools but have not set up team-level workflows or guardrails - You are a generalist looking to branch into AI Nice to have: - Python backend and web application experience - Experience with automated, agent-driven code review and test workflows Engagement: - Remote, expert-level rate - Short initial engagement with potential to extend - Some availability for scheduled, recorded calls - NDA required before we share specifics To apply (proposals without these will not be considered): - A specific example of an agentic development setup you built for a team, what you designed, and the outcome - The AI coding agents you have worked with and the depth of that work - Links to anything that shows your work (skills or agent configs, writeups, repos, demos), if you can share them

Role Overview You are the Executive AI Enablement Lead at AIVC, the person whose job is to make the executives at AIVC’s client businesses true power users of Claude, Cowork, and code- and agent-driven workflows. AIVC partners with operator businesses to drive AI-led EBITDA growth, and part of that work is bringing each company’s most senior leaders up the AI curve. You’re the person who personally designs and runs that path on every engagement: assessing where a given client executive is today; curating the right materials, videos, and course content; running 1:1 coaching; building executive playbooks; and acting as their daily operator-in-the-loop until the new workflows stick. The first concrete instance is already lined up, a named client managing partner has explicitly asked for the fastest path to becoming a power user of Claude, Cowork, and Claude Code / Skills. From there you scale: same treatment to additional client executives across the portfolio, then a documented set of executive-grade playbooks and patterns that compound across every future engagement. You are bias-toward-results – a win is the client executive’s calendar-week looking different, not a beautifully written rubric nobody uses. What You’ll Own (Outcomes) • Within 30 days of pairing with the first client managing partner, they have a working daily routine in Claude, Cowork, and Code/Skills that’s already replacing or improving how they handle at least three recurring tasks • Within the first quarter of the engagement, the client executive is a true power user — running multi-step workflows, custom Skills/Projects, and agent-assisted tasks without needing coaching scaffolding for the basics • A documented set of executive playbooks (research, writing, analysis, synthesis, workflow automation, agent-assisted tasks) that compound across every client engagement, not one-offs • A curated, current library of learning materials, videos, example workflows, and Claude-native patterns — including a clear point of view on which external courses, tutors, or expert resources are worth plugging in • Observable change in how client executive cohorts use AI: from reactive chat to repeatable, structured, outcome-oriented workflows • A foundation of training assets and patterns that scales beyond executive coaching into broader client teams in year two • A reputation among AIVC’s clients as the trusted go-to for “how do I do this better in Claude” — measured by inbound demand and engagement expansion What You’ll Do (Responsibilities) • In the first weeks: build the first client managing partner’s tailored upskilling plan — assess current usage, identify the highest-leverage workflows for their day-to-day, curate the right mix of materials / videos / course content, and recommend any tutor or expert-guided support to fold in • Provide 1:1 coaching for client executives — managing partners, founders, C-suite leaders — on Claude, Cowork, and code- and agent-based workflows • Design tailored training plans per executive that go beyond basic onboarding into advanced usage, with explicit progression from chat → workflows → agents • Curate the best external materials (videos, courses, blog posts, example projects) and rewrap them into client-ready, AIVC-flavored learning paths • Teach practical, high-leverage use cases live: research, writing, analysis, synthesis, workflow automation, and agent-assisted tasks • Help client executives move from general chat usage into repeatable workflows — Claude Projects, Skills, scheduled Cowork tasks, MCP integrations, custom agents • Serve as a real-time tutor and expert resource for client executives — over Slack, in meetings, on-site, and in async written feedback • Run office hours, workshops, and informal Q&A sessions inside client teams to keep adoption sticky between coaching sessions What We’re Looking For (Required) • Deep hands-on expertise with Claude across every surface (Claude.ai, Claude Projects, Claude Code, Claude Skills, Claude API) — and an active habit of pushing the edges of each • Strong working fluency with Claude Cowork specifically, including scheduled tasks, connected apps / MCPs, and the broader workflow surface • Strong capability with code-enabled AI workflows: you can write Python and/or TypeScript, build agents, configure MCP integrations, and ship a working internal automation end-to-end without needing an engineer • Demonstrated ability to teach non-technical but highly demanding users — you’ve made executives, founders, or senior operators meaningfully better at something complicated, not just trained engineers • Strong workflow design instinct — you can translate messy business questions into clean prompts, workflows, and systems • Polished, discreet, and effective in high-touch client executive settings — high EQ, low ego, comfortable representing AIVC inside senior client environments and around senior decision-makers • Strong bias toward practical results over theoretical AI knowledge — the metric is the client executive’s behavior change, not the elegance of the explanation • Excellent written and verbal communication; you can write a playbook a client executive will actually read and use • Comfort with significant travel to client sites and embedded, on-site engagement work • 5+ years of professional experience across some mix of: applied AI / ML, technical training and enablement, developer relations, solutions engineering, executive coaching, management consulting, or chief of staff / senior operator roles to executives Helpful If You Have (Preferred) • Prior experience coaching or supporting C-level executives, founders, or managing partners as a client-facing professional — executive coach, principal solutions engineer to executive customers, chief of staff to a CXO, or partner-level consultant • Background that combines technical depth with people skills — developer relations, solutions engineering, technical training, or learning & development at a frontier AI or developer-tools company • Direct experience building executive-facing training programs or curricula that demonstrably moved adoption inside other organizations • Hands-on familiarity with the Anthropic product surface specifically: Claude Projects, Claude Skills, Claude Code, MCP server development, Claude API • Track record of getting non-technical users to genuinely adopt a technical tool — i.e., users who chose to keep using it after the training ended • Background in management consulting, professional services, executive coaching, or learning & development — especially in environments where the customer was a senior external client • An active personal portfolio of AI work (workflows, automations, blog posts, talks, open-source contributions) you can point to • Comfort building light tooling (a Notion playbook system, a Claude Skills catalog, a small dashboard) without needing engineering support • Familiarity with AIVC’s model — operator business engagements, EBITDA-led measurement, and the broader compounding intelligence layer — or eagerness to come up the curve quickly

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.