Workflow Automation Development - PHP/MySQL & Claude Code Specialist

Cliente Freelancer · Remoto · Remoto · freelance · mid · 10–4000 USD

Publicada el 2026-07-31

Descripción de la oferta

Position: Senior PHP/MySQL Engineer (Claude Code Specialist) - Workflow Automation Platform, Long Term We are a U.S. professional services firm building an internal workflow automation platform to replace a licensed third-party system. This is a long-term engagement, six months or more, for one senior engineer. WHAT EXISTS We have a design skeleton, not a finished system: - A draft MySQL 8 schema (definition/runtime separation, RBAC, audit tables) - A prototype workflow engine validated against a real workflow definition - An importer that normalizes an existing workflow export of ~290 activities and ~5,000 tasks - Skeleton auth, audit logging, and cron scaffolding This has not been run in a live environment and is not a vetted production architecture. We expect you to review it critically and tell us where it is wrong before you build on it. Candidates who accept it uncritically are not what we are looking for. THE STACK - PHP 8.1+, zero third party dependencies (PDO, openssl, password_* only; no Composer, no framework) - MySQL 8 on AWS (Linux) - Server rendered PHP with light vanilla JS. No SPA framework. - Must work across Chrome, Safari, Firefox, and Edge - Cron driven background processing THE CORE PROBLEM A configurable workflow engine. A workflow is a template of approximately 290 activities, each gated by conditions: data comparisons, checklist selections, and task predecessors. The engine evaluates each case's data and instantiates only the activities whose triggers fire. The engine is domain agnostic, so additional workflows are data rather than code. Work routes to queues with load balanced distribution across approximately 20+ users. The system handles deadline ticklers, confirmable dates, and hold and close behavior. AI ARCHITECTURE A two-tier design. You must be comfortable with both: - Local tier: a dedicated Mac server running Ollama, handling high volume, routine, and privacy sensitive work including document assembly from templates, field extraction, classification, and summarization. Zero marginal cost, and data does not leave our infrastructure. - Cloud tier: the Anthropic Claude API for work requiring higher level reasoning. You will build a routing and abstraction layer that selects the tier based on task type and data sensitivity, so either tier can be replaced without touching calling code. Every AI generated document must pass a human approval gate before finalization. This requirement is not negotiable. REPORTING The platform exchanges data in both directions with a third-party financial model maintained outside the system. Egress: stable star schema views over the transactional tables, exposed through a least privilege read only account. Ingress: a validated import path for external financial data, staged into dedicated tables, with schema validation, rejection handling, and a load log. Each data element has a single system of record and neither side overwrites the other's authoritative data. You build the interface and the contract. You do not build dashboards and will not work in the BI tool itself. CLAUDE CODE REQUIREMENT We work in Claude Code. We are not hiring a general PHP developer who occasionally uses AI tooling. We need someone who works this way daily: who writes and maintains CLAUDE.md files, plans before executing, uses subagents and MCP servers, and can keep a large codebase coherent across long sessions. Claude Code proficiency will be tested in a paid trial task before any long-term commitment. DELIVERABLES (milestone based, fixed price per milestone) 1. Seed loader: import the normalized workflow definition into the schema 2. UI: queue worklists, case view, task completion with checklist capture 3. Engine completion: predecessor sequencing, confirmable dates, tickler logic 4. Workload distribution across queues 5. Charge and time model: flat fee and hourly capture, time entries, milestone billing events 6. Data interface: star schema views for BI egress (read only), and a validated ingress path for external financial data 7. AI tier: local Ollama integration, Claude API tier, and routing layer 8. Document generation with mandatory human approval gate REQUIREMENTS - 7+ years production PHP, strong MySQL schema and query skills - Demonstrable Claude Code proficiency (see screening questions) - Comfortable working without frameworks and without Composer - Experience designing reporting views or star schemas for BI consumers - Experience with systems carrying audit and compliance requirements - Minimum four hours of daily overlap with U.S. Eastern time - Signed NDA before any code or documentation is shared - Synthetic test data only. No production data access at any point. SCREENING QUESTIONS (answer all; generic applications will not be reviewed) 1. Paste a CLAUDE.md file you have written for a real project. Explain two decisions in it. 2. Describe a refactor spanning ten or more files that you did in Claude Code. How did you plan it, and how did you verify the result? 3. Have you built or configured an MCP server? Which one, and for what purpose? 4. Describe a time Claude Code produced code you rejected. How did you catch it? 5. Why would we forbid Composer on this project? Give us your honest assessment, including whether you disagree. 6. Have you deployed a local LLM (Ollama or similar) in a production path? Describe the setup. TO APPLY Begin your response with the word "SEQUENCE" to confirm you have read this posting. Applications opening with a generic pitch will be declined.

Skills

Fuente original: freelancer

Análisis JobHunter