ABOUT THE PROJECTS. I run a curated marketplace on Shopify (The Ever Good) and I am building out an AI automation system to handle routine tasks in the business. I am AI-savvy and have built a Python agent myself, so I understand what I am asking for. I have the architecture planned and the business requirements semi-documented for each piece. I simply do not have the time to build everything I want to build, which is why I need a developer to work alongside me. The first project is a product review collection and import system. If it goes well, there is ongoing work building out additional agents over time, one at a time. This is a potential long-term engagement depending on how the first project goes. WHAT WE ARE BUILDING. The overall system is a set of AI agents that handle specific business tasks and route outputs to a simple dashboard where I can review, approve, and trigger actions before anything goes live. The dashboard is a Lovable build that gives me a single place to monitor agent status, review outputs, and approve or return anything that needs a human decision before it moves forward. Agents are planned across several areas of the business. We will build one at a time. I will walk you through the requirements for each before you start. Examples of agents here by business category (these could change): - MARKETPLACE & CATALOG. Product Reviews (first project), Catalog Enrichment and SEO, Pricing and Margin Monitor, New Product Auto-Pricer, Maker Stories, Maker Audit, Maker Analytics, Review Monitor. - CONTENT & SOCIAL. Content Generation, Cultural Moment Monitor, Social Publishing, Pinterest Curator, Instagram DM Automation, Image Production, Founder Content Amplifier. - MARKETING & ADS. Email Sequences, Paid Media Director, Ads Performance Monitor, LinkedIn Outreach. - SEO and Search. SEO and AI Search Visibility, Crawl Error and Redirects. - THE SCHOOL (Our Coaching Offerings). AI Readiness Assessment, Coaching Prep Tool, Workshop Launcher, Course Completion Monitor, Immersion Round Tracker. - FINANCE & OPS. Profit Police, Cash Flow Forecaster, Financial Health Monitor, System Health Monitor. - CUSTOMER SERVICE & GIFTING. Customer Service Drafts, Gift Inquiry and Proposals, Basket Assembler. OUR TECH STACK (Could Change). - AI AGENT BUILDING STACK. Claude Code, Claude API, Python, Make.com, Replit, Lovable, Google Sheets API, Baserow. - OTHER BUSINESS SYSTEMS. Shopify API, DropCommerce API, Matrixify, Typeform, Stripe API, Yotpo API, Klaviyo API, Instagram Business API, Later API, Pinterest API, ManyChat API, Bannerbear API, LinkedIn API, Google Analytics 4 API, Google Search Console API, DataForSEO API, QuickBooks Online API, Google Drive API. HOW WE WORK. - HOURLY. Collaborative and iterative engagement. - REQUIREMENTS. We review together before each build and refine as we go. - QA. I handle testing and QA on my end. - DOCUMENTATION. All work is documented throughout with decision logs and handoff notes so full ownership and control remains with me at every stage. - IP. All intellectual property and work product belongs to me entirely. - CLAUDE. You are expected to maintain your own Claude environment at a level that supports serious development work with no usage limitations. - ACCESS. All business systems and APIs provided with scoped credentials as needed. - DEPLOYMENT. Production deployment is handled collaboratively. - COMMITMENT. Looking for someone who can help maintain and evolve these tools over time while I retain full control and understanding of everything we build. WHAT I AM LOOKING FOR. - CLAUDE. Must use Claude as your central AI LLM. Experience. Working experience with the Claude API and the tools in the building stack above, or a demonstrated ability to learn new tools quickly. - COMMUNICATION.Clear communicator who works independently and does not need to be managed through a task, but is promptly responsive to me. - MINDSET. Building with AI tools as a regular part of your work. TO APPLY. Please share a brief description of one or two AI agents you have built, what they did, and what tools you used. Include a note on your familiarity with the tools listed above and your hourly rate.

I need a web developer that can be trusted with my idea. I have built a website with Claude AI and need a developer to finish the following items and take it to the next level. The tasks involve completing the website, ensuring it is user-friendly, and optimizing for performance. The ideal candidate should have experience in web development and AI integration.

Type: Hourly, ongoing (part-time to full-time, room to grow) Stack you'll work in: Notion, Slack, HubSpot, Google Workspace/Gmail, Claude + other LLM APIs, Zapier/Make/n8n About us We're a fast-moving sports and fan-engagement startup. We're small, we ship quickly, and we want AI woven into how the whole company operates, not as a side experiment, but as the default way we work. You'd be the person who makes that real. What you'll do Map our current workflows across sales, marketing, ops, and content, then find the highest-leverage places to automate. Build automations and agent workflows that connect our tools (Notion, Slack, HubSpot, Gmail/Google Workspace) using platforms like Zapier, Make, or n8n plus LLM APIs. Design and ship AI agents for real jobs: lead routing and CRM enrichment, content drafting, customer/fan response triage, internal knowledge search, reporting digests. Stand up the connective tissue (prompts, integrations, guardrails, and monitoring) so automations are reliable, not brittle demos. Train and enable our team: build SOPs, run working sessions, and create lightweight docs so non-technical people actually adopt what you build. Help set our AI strategy and roadmap as we scale. You're a strong fit if you Have shipped real automations and AI agent workflows in production (not just prototypes). Are fluent with Zapier / Make / n8n and at least one major LLM API (Anthropic/Claude, OpenAI). Know your way around HubSpot, Notion, Slack, and Google Workspace integrations and APIs. Can write clean prompts and think in systems: edge cases, error handling, human-in-the-loop checkpoints. Can explain technical work to non-technical people and get them to adopt it. Communicate proactively and move fast without breaking trust on things that touch customers or revenue. Nice to have Experience taking a small company "AI-native" end to end. Background in sports and/or blockchain. Comfort with light scripting (Python/JS) when no-code hits its limits. How to apply In your proposal, please: Describe one AI agent or automation you built, the tools involved, and the measurable result. Tell us how you'd approach training a non-technical team to actually use what you build. This part matters as much as the build. Share your hourly rate and weekly availability. Proposals that skip these will be passed over. We're looking to start with a small paid task and grow the engagement from there.

We're seeking an experienced developer or agency to create a premium, modern website for a subscription-based platform. The project involves integrating AI technologies with Next.js to enhance user experience. The ideal candidate will have a strong background in web development and a keen eye for design.

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.

Custom iPad Client Closeout, Feedback & Review Automation Platform Developer Project Overview We are a high-end residential design-build firm seeking a developer to create a custom iPad-based client closeout platform. The system will be used during final project walkthroughs to conduct a structured satisfaction survey, capture referrals and testimonials, generate personalized AI-powered review content, and guide homeowners through the Google Review submission process. Our goal is to create a seamless, professional experience that increases client engagement, captures valuable feedback, improves our online reputation, and strengthens long-term client relationships. This project will be used by our team in homeowners' residences during project closeout meetings and should be designed to be simple, intuitive, and completed in just a few minutes. Desired Workflow 1. Team member conducts an in-person closeout survey with the homeowner. 2. Responses are entered into the iPad application. 3. The system evaluates client satisfaction and identifies highly satisfied clients. 4. AI generates a personalized review draft based on the client's actual responses. 5. The client reviews and edits the review if desired. 6. The client enters or confirms their Google account information. 7. The system directs the client to our Google Review page and facilitates the review submission process. 8. Survey results, testimonials, referral opportunities, and review data are stored in a database and/or Google Sheets. Survey Questions The application should allow us to customize and modify survey questions over time. Initial questions may include: Overall Satisfaction * How satisfied are you with your overall experience? * Did the completed project meet or exceed your expectations? * Would you hire us again for future projects? Communication * Were we responsive to your questions and concerns? * Did you feel informed throughout the process? Design & Construction Experience * Were you satisfied with the design process? * Were you satisfied with the quality of workmanship? * Did our team effectively solve challenges that arose during the project? Referrals & Advocacy * Would you recommend us to friends or family? * Would you be willing to provide a referral? * Would you be willing to participate in a future case study or testimonial? Marketing Permissions * May we use photos of your project in our marketing materials? * May we use portions of your testimonial or review in our marketing materials? AI Review Generation Based on survey responses, the application should generate a natural, authentic review draft. Example: "Working with Marvista Design + Build was a wonderful experience. Their team was responsive, professional, and highly organized throughout the entire process. We especially appreciated their communication, attention to detail, and commitment to quality. The finished project exceeded our expectations, and we would gladly recommend them to anyone considering a remodeling project." The generated reviews should vary in language and structure so they feel authentic and personalized. Additional Features Testimonial Capture * Collect written testimonials * Optional voice-to-text testimonial entry * Store testimonials in a searchable database Referral Capture * Identify clients willing to refer others * Capture referral contact information * Track referral opportunities Net Promoter Score (NPS) * Include NPS scoring * Flag dissatisfied clients for internal follow-up * Prevent unhappy clients from being directed toward public review requests Reporting Dashboard * Review completion statistics * NPS tracking * Referral tracking * Testimonial tracking * Historical reporting Data Storage Preferred integrations include: * Google Sheets * Google Workspace * Airtable * Cloud database solutions We are open to recommendations. Technical Requirements We are open to the developer's recommendation regarding architecture and technology stack. Potential solutions include: * Native iPad application * React Native * Flutter * Progressive Web Application (PWA) * OpenAI API integration * Google Workspace integration * Airtable integration The solution should be easy to maintain and scalable for future enhancements. Future Vision This is intended to become Phase 1 of a broader client experience platform that may eventually include: * Automated review campaigns * Referral management * Client for Life program tracking * Testimonial library management * CRM integration * Marketing automation We are looking for a developer who can help us think strategically about the long-term roadmap, not simply build the initial application. Ideal Freelancer We are looking for someone who: * Has experience building custom business applications * Has experience with AI integrations * Has experience with survey platforms and workflow automation * Understands user experience and interface design * Can recommend the best technical approach * Can build scalable solutions that can evolve over time When Applying, Please Include 1. Examples of similar applications you have built. 2. Experience with AI-generated content and OpenAI integrations. 3. Experience with Google Workspace, Airtable, or CRM integrations. 4. Your recommended technical approach for this project. 5. Estimated timeline and budget range. 6. Any suggestions for improving the workflow described above. We are less concerned with a specific technology stack and more interested in finding the right development partner who can help us create an exceptional client experience.

AI SYSTEMS ENGINEER Agentic AI, Multi-Agent Systems & Secure AI Workflows (U.S.) Remote • United States We're building production AI systems designed for enterprise environments. We're looking for exceptional AI systems engineers who enjoy solving difficult systems problems – not just writing code. Our work sits at the intersection of agentic AI, software architecture, enterprise systems, governance, security, and operational intelligence. We design AI systems that improve how organizations operate while meeting the standards required for production deployment. We value engineers who think in systems, challenge assumptions, and care deeply about building technology that is reliable, understandable, secure, and useful. If you're motivated by difficult engineering problems, thoughtful architecture, and building production AI systems for enterprise organizations, we'd like to hear from you. WHAT YOU'LL HELP BUILD Examples of the types of systems we design include: - Multi-agent AI systems - Enterprise AI assistants - Secure AI workflows - Enterprise workflow automation - AI-powered knowledge systems - Human-in-the-loop decision support - Document intelligence - Retrieval-Augmented Generation (RAG) - AI memory and retrieval systems - AI evaluation and testing frameworks - Secure enterprise AI platforms - AI governance capabilities - Operational intelligence platforms TECHNICAL EXPERIENCE WE VALUE We're interested in engineers with experience in some combination of: - Python - AI Agent Development - LangGraph - LangChain - Large Language Models - API Development - Vector Databases - Software Architecture - Enterprise Systems Integration - Information Security Experience with OpenAI, Anthropic, Model Context Protocol (MCP), cloud infrastructure, workflow orchestration, observability, distributed systems, or regulated technology environments is also valuable. We do not expect expertise in every technology. We care far more about engineering judgment, systems thinking, demonstrated execution, and continuous learning than checking every technology box. THE PROBLEMS WE ENJOY SOLVING The engineers who thrive here enjoy questions like: - How should multiple AI agents coordinate work? - How should humans remain in control of important decisions? - How should production AI systems scale safely? - How should memory be designed for enterprise AI? - How should AI systems balance operational performance with governance, security, and reliability? - How should AI systems create measurable business value? If those questions excite you, you'll probably enjoy working with us. WHAT MAKES SOMEONE SUCCESSFUL HERE We're looking for engineers who: - Think in systems rather than individual features. - Care deeply about production quality. - Enjoy solving ambiguous technical problems. - Communicate complex ideas clearly. - Balance speed with sound engineering judgment. - Build practical solutions rather than chasing hype. - Continuously learn, experiment, and improve. We're significantly more interested in systems you've built than technologies you've used. Please provide specific examples that demonstrate your role, engineering decisions, and measurable outcomes. We recognize that many engineers use AI as part of their workflow. You're welcome to do the same. However, your application should accurately reflect your own experience, judgment, and technical thinking. We respect the confidentiality of your current and former employers, clients, and partners. Please do not include proprietary or confidential information in your application. Describe your work at a level that demonstrates your engineering approach without disclosing protected information. PROFESSIONAL STANDARDS We value integrity, sound engineering judgment, and respect for intellectual property. Please do not include confidential, proprietary, export-controlled, or other non-public information belonging to your current or former employers, clients, or partners in your application or work samples. We're interested in your engineering approach, architectural thinking, and problem-solving methodology – not protected information belonging to others. If you share code, architecture diagrams, technical documentation, or project examples, please ensure you have the legal right to do so and identify any material open-source or third-party technologies where appropriate. By submitting application materials, you represent that you have the legal right to share them and that doing so does not violate any confidentiality, intellectual property, employment, consulting, or other contractual obligations. Any engagement, if offered, will be subject to a separate written agreement covering confidentiality, intellectual property ownership, compensation, and other applicable terms. Submission of an application or participation in the evaluation process does not create any employment, independent contractor, partnership, joint venture, agency, fiduciary, or other business relationship with 26ers AI, nor does it obligate either party to enter into any future engagement. 26ers AI reserves the right to evaluate applications, discontinue discussions, modify the hiring process, or decline to pursue any engagement at its discretion. Nothing in this posting should be construed as an offer of employment or an offer to contract.

We need to have a AI developer who is readily available on slack to fix any errors that may arise from our app and to do monthly check and updates. we want this to be long term and to be a partnership. Occasionally we may have a new project to work on as well.

We’re looking for an experienced engineer or trainer to help deliver hands-on AI coding training for engineering teams. The focus is on moving engineers beyond basic Copilot/autocomplete usage into agentic workflows with tools like Claude Code, Codex, GitHub Copilot, and related tooling. Scope: Run practical workshops for engineers Teach Claude Code, Codex, and Copilot workflows Cover task scoping, prompting, reviewing diffs, and code validation Help create assets like CLAUDE.md, agents.md, slash commands, or workflow templates Advise on best practices, cost awareness, security, and team adoption Ideal candidate: Strong software engineering background Hands-on experience with Claude Code, Codex, or similar tools Experience training engineering teams Clear communicator with practical examples Please apply with relevant examples of AI coding workflows, trainings, or engineering teams you’ve supported.

Developer Scope of Work Project Overview & Engagement Terms Domexa Labs for MyCondoCompliance (mycondocompliance.com). MyCondoCompliance is an enterprise and consumer-facing web platform built to aggregate, OCR, analyze, and report on condominium association compliance data throughout Florida (starting with Miami-Dade County). 1. Key Engagement Expectations: Dedicated Weekly Support: We require reliable, continuous development capacity week-over-week to support platform growth, new features, maintenance, and internal system updates. Flexible Monthly Hours: Hours will flex on a month-to-month basis depending on business priorities, product release cycles, and current backlogs. Minimum 2-3 hours/week, not to exceed 15hrs/week. Rapid Turnaround & Steady Communication: We operate in a fast-paced environment. Quick turnarounds on hotfixes, active updates on tasks, and daily/structured communication are critical. Language Requirement: Excellent, professional verbal and written English is a strict requirement for technical syncs, documentation, and coordination. 2. Technical Infrastructure & DevOps Architecture The MVP is complete, live, and deployed. You will inherit the following technical ecosystem: Infrastructure Stack: - Code Repository: Managed via GitHub. - Front-end Hosting: Deployed and managed on Netlify. - CI/CD: Automatically triggers deployment to production on master branch updates, and to staging/dev on dev branch updates. - Back-end Hosting & Infrastructure: Managed on Digital Ocean inside a Kubernetes environment. - DNS Administration: Managed on Digital Ocean. - Third-Party API Integrations: - Mapbox: Powers map-based search and property discovery. - Mailgun: Handles transactional email delivery. - Chatbase: Integrated for natural language querying and chat functionality. - TipTap: Rich text editor powering board notes and internal editing. 3. Scope Evolution & Core Pipelines As our incoming developer, you will be expected to maintain, debug, and expand upon the core features built during our initial execution phases. A. Data Pipelines & OCR Ingestion Engine - Website Scraper/ETL: Continuous ingestion pipelines that pull structured condo data and metadata from county public registers. - Normalization Engine: Ingestion pipeline that categorizes incoming unstructured documents into strict schemas - OCR & Vectorization: All ingested documents are automatically processed via an OCR layer, and the resulting plaintext is indexed into a vector database for semantic search and Retrieval-Augmented Generation (RAG). B. Autonomous AI Processing Agents We run specialized Python/Node microservices to process aggregated document metadata: - Granular Extraction: AI agents systematically query vector databases to extract critical datapoints - Audit Trails & Provenance: Each extracted datapoint must carry verification properties—linking back directly to the document source, specific page/snippet, and extraction timestamp. C. Portal Tiering & Client Features - Consumer Interface: Detailed property pages, dynamic scoring components, PDF report compilation and downloads. - Enterprise Interface: Multi-tenant web app allowing real estate, financial, and legal clients to access deep search, structured list filtering (e.g., filtering condos by unit counts, reserve posture, specific clauses such as "Kauffman language", and termination criteria), and batch export controls. - Admin Dashboard: Tracks user engagement metrics, domain lookups, purchase histories, and mailing list extractions.