← Live feed

Laravel & Flutter Developer for AI Integration

Budget: $15.0 - $30.0 HOURLY / PART_TIME ⭐ 0.00 (0) Poland

laravel-framework

Preferred qualifications

  • Talent type: Independent
  • Experience: Expert
  • English: Conversational
Full-stack developer (Laravel + Flutter) for a live fintech product, AI-first workflow ABOUT THE PROJECT The product is flight cancellation insurance. A user buys a policy in a mobile app, pays by card, and gets paid out if the flight is cancelled. The product is live: five services, smart contracts on Polygon mainnet, apps in both stores. We are now moving to a fiat-first model: Stripe for payments, blockchain kept only as a registry of policies and payouts. I need one developer who owns the product technically from here on: new features, bug fixes, integrations, releases. Tasks are end-to-end, from the database and API down to the screen in the app. STACK Backend (your main area): PHP 8.1, Laravel 10, Octane, MySQL, Firebase Auth, JWT. Modular structure (Handler / Service / Repository), PHPUnit, PHPStan. Mobile: Flutter, Dart 3, provider, go_router, Firebase (auth, push, dynamic links). Redesign in progress, dependencies need an upgrade. Insurance Engine: Go 1.22, Gin, go-ethereum, Google Cloud KMS. Internal service, all wallet and blockchain logic lives here. Oracle: Laravel 11, Filament 3. Flight status data from several providers. Contracts: Solidity 0.8.28, Hardhat, OpenZeppelin 5. Already in mainnet, rarely touched. Infra: Docker, Google Cloud Run. Every repository has a CLAUDE.md with conventions, architecture docs and a plan. You will not be guessing how things are built. WHAT YOU WILL WORK ON FIRST - Stripe payments (Payment Sheet, Apple Pay, Google Pay). - A registry-only contract and moving the Engine to it. - Flight status oracle from multiple data sources. - Payouts (bank transfer from the admin panel, USDC) and KYC at payout time. - Loyalty program, QA, Telegram alerts. After that: regular product work. Features, bugs, dependency upgrades, store releases. HOW WE WORK This is the most important part of the post, so read it carefully. All code in this project is written with Claude Code. Each repository has its own CLAUDE.md, agents and skills are configured. I am looking for someone who already works this way every day: you give the agent a task, review what it produced, fix the prompt or the instructions when needed, and ship. You do not type code line by line. If you have not used Claude Code or a comparable agentic tool in real production work, this job is not a fit. I expect two things at the same time, and I will not trade one for the other: - Fast. A medium feature ships in a day or two, not a week. - Done well. Tests on new logic, linters green, existing conventions followed, nothing left "to clean up later". It touches money, so sums, statuses, permissions and idempotency are checked, not assumed. Tasks are given as outcomes, not step-by-step instructions. You split the work across services yourself, pick the order, and ask only when a decision is truly mine to make. After each task I want a short report: what was done, what was tested, what was not done and why. MUST HAVE - Strong production Laravel: modular architecture, repositories, queues, migrations, PHPUnit. - Flutter: screens, navigation, state, REST integration, push, localization, iOS and Android builds, store releases. - Daily use of Claude Code (or Cursor / Codex in agent mode) for real production work, not just autocomplete. - End-to-end ownership of a task, from DB to screen. - Clean, readable code and the habit of following an existing codebase style. - Care with money and secrets. NICE TO HAVE - Go: the Engine is in Go, you will read and modify it. - Web3 basics: EVM, transactions, nonce, gas, contract roles, EIP-712 signatures. Enough to read Solidity and Hardhat tests and run a local node. - Stripe or other payment integrations. - Google Cloud: Cloud Run, KMS, Secret Manager. - Russian and Ukrainian. Project documentation, CLAUDE.md files and many code comments are currently in Russian; they can be translated to English for the right candidate. Some client-facing documents are in Polish. TERMS Hourly or per milestone, we can discuss. Starting at 20 hours per week with a path to full-time. Long-term if it works out. To show you actually read this post, start your proposal with the word "Cancun". Proposals that do not start with it will not be read.
Open job

AI proposal draft

Generate a short cover letter to copy into the offer. Says you are interested and ready to work.

Sign in to generate an AI proposal draft.

Log in