Summary I’m looking for an experienced automation engineer to upgrade my AI assistant workflow from manual Chrome relay browsing to a robust, persistent browser automation system. Current state: I have a setup of 1 main clawdbot, controlling and directing 2-3 small bots in a VPS, with tailscale security. Main Bot can browse with a chrome relay/attached tab, but this is too manual. Goal: Main bot assistant should execute web tasks directly (search, compare, form-fill, booking flow) with approval gates before payment. Scope of Work 1. Build a persistent browser worker using Playwright + Chromium 2. Implement session/profile persistence (secure login state management) 3. Create task pipeline: - open target site - search and compare options - fill forms - pause at final confirmation/payment for human approval 4. Add OTP/manual checkpoint handling 5. Add retry/recovery logic for dynamic pages 6. Add audit trail (logs + screenshots per major step) 7. Add policy/guardrails: - budget limits - preferred vendors/airlines - time-window constraints 8. Prefer API-first fallback where available (use API instead of UI automation when possible) Technical Requirements (Must Have) - Familiar with Clawdbot setup in VPS with Tailscale surcurity - Strong Playwright experience (Node.js or Python) - Browser automation in production-like environments - Handling anti-bot friction and dynamic selectors responsibly - Secure credential/session handling - Experience with queue/worker architecture and error recovery - Clear logging and observability Nice to Have - Experience integrating with AI agents/LLM workflows - Experience with booking/travel/ecommerce flows - Docker deployment and server hardening - API integration experience (travel/commerce providers) Deliverables - Working automation service deployable on my server - Configurable task templates (starting with travel booking flow) - Approval-gate step before final submission/payment - Full documentation: - setup - runbook - troubleshooting - security notes - Handover session (recorded or live) Acceptance Criteria - No manual Chrome relay attach needed - Assistant can complete end-to-end browser workflow up to payment confirmation - Stable performance across repeated runs - Errors are logged clearly with screenshots - Easy for non-engineer owner to trigger workflows Security & Privacy - Do not hardcode credentials - Use encrypted secrets/environment variables - Least-privilege design - No external sharing of data/session artifacts