Obtenez une réponse de cet employeur
Votre CV et votre lettre de motivation, adaptés exactement à ce que l’employeur recherche.
Saifuro LLC is seeking a product engineer / full-stack Web3 developer to join early and shape the product. You will own the architecture, testing, deployment, and monitoring as the team scales, while engaging directly with customer teams to identify needs and ship rapid fixes for onboarding and usage.
You will build on-chain features for USDC settlement and escrow traceability, and create dashboards spanning the database to the user interface to show agent spend and decision history.
Saifuro checks payments that AI agents try to make. An agent asks to spend, we compare the request with a mandate a human approved earlier, and the answer comes back signed so the receiving side can verify it. There's escrow on Base and Solana for trades between agents, and settlement is in USDC, onchain. We never hold customer funds. The docs are public at docs.saifuro.com, and the people who use them are developers building agents and the teams selling APIs to those agents.
You'd be one of our first engineers, and you'd lead the product customers log into: the console where a finance team watches its agents spend, the policy editor, the approvals, the sandbox. Founding means you shape what we build as well as how, and you have a say in who joins next. Call it product engineer, full-stack developer or Web3 developer if you prefer.
You've shipped TypeScript on both sides, a React front end and a Node back end, in a product people paid for.
You've built against an EVM chain or Solana, with viem, ethers or something like them.
You live in one of the countries we can hire in.
Beyond these requirements, we'll support you in learning whatever else the role demands. If your experience is relevant but your title differs, we would still like to hear from you. Work outside a job counts too: open source, hackathons and your own projects.
It helps, but isn't required, if you've built dashboards for payments or fintech, if you've worked with Postgres and event streams, if you know Go, if you've built with an agent framework or MCP, or if you've been one of the first engineers somewhere before.
Hours are flexible. The one thing we ask is to be online from 14:00 to 17:00 UTC, when the team overlaps for calls and quick questions. That's a window, not the working day. The rest of your hours are yours to arrange. A mainnet incident doesn't keep office hours. If that window is the middle of your night, say so and we'll work something out.
You can combine this with a job at another company, as long as the two don't conflict.