βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β
β C A R L O M I G U E L D Y Β· @carlomigueldy β
β β
β senior fullstack engineer / web3 / ai-native β
β β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
I take ambiguous product requirements and turn them into shipped production systems.
philippines Β· remote β 7+ yrs eng β 4+ yrs web3 β daily claude code & codex
I'm a senior fullstack engineer with deep Web3 experience and a daily AI-augmented engineering practice. I'm not just a frontend, backend, or smart contract engineer β I'm the one who owns the feature from a Figma frame and a half-written spec all the way to a green CI run and a production deploy.
const miguel = {
ownsEndToEnd: ['frontend', 'backend', 'smart contracts', 'tests', 'ci/cd', 'deploy'],
shipsWith: ['claude code', 'codex', 'mcp', 'sub-agents'],
bestAt: 'turning vague product requirements into production systems',
portfolio: 'https://carlomigueldy.dev',
status: 'open to joining a team Β· senior software / fullstack / web3 roles',
};π° Β Rumour β Web3 social trading on Hyperliquid β @AltLayer
Led frontend across the rumour-to-trade flow β owned the Farcaster Miniapp and LINE DappPortal shells end-to-end, the wallet-setup flow on Privy embedded wallets, the Tencent Chat messaging layer, and the perps trading UI on the Hyperliquid SDK. Ships as a PWA, Farcaster Miniapp, and LINE DappPortal Mini Dapp from a single React + Vite codebase.
π€ Β Autonome β no-code AI-agent deployment platform β @AltLayer
Owned the framework-discovery gallery, new-agent deployment flow, agent metadata editor, environment-variables dialog, and the Eliza framework UI integration inside the unified AltLayer Wizard frontend. Users pick a framework, configure persona and keys, and get a chat-ready agent in ~5 minutes.
π― Β Limitless Labs β prediction markets on Base β @Limitless Labs
Architected the NestJS / Fastify / PostgreSQL backend using domain-driven design and automated the full market lifecycle into an orchestration system that let operators create 10+ markets a day. Collapsed the manually-assembled market-creation flow into a single operator action behind an internal form, REST API, and Gnosis Safe SDK approval link.
π Β Atlantis World β Web3 social metaverse + $1M NFT sale β @Atlantis World
Promoted from blockchain engineer to lead blockchain engineer. Owned 11 of 16 DeFi/Web3 protocol integrations end-to-end (Yearn, 1inch, Balancer, Aave, Perpetual Protocol, Moola, Lens, Filecoin, Snapshot, NFT.Storage, POAP) and ran the live shift for the community NFT sale that raised ~$1M ETH.
languages typescript Β· javascript Β· python Β· go Β· solidity
frontend react Β· next.js Β· tailwind Β· shadcn Β· chakra Β· react hook form Β· zod
backend node.js Β· nest.js Β· fastify Β· hono Β· postgres Β· prisma Β· ddd
web3 foundry Β· hardhat Β· ethers Β· viem Β· wagmi Β· privy Β· gnosis safe Β· tenderly
ai / agentic mcp servers Β· tool & function calling Β· router orchestration Β·
human-in-the-loop approvals Β· claude code Β· codex Β· custom skills
testing playwright Β· synpress Β· vitest Β· hardhat Β· foundry Β· unit Β· smoke Β· ci
infra docker Β· kubernetes Β· gcp Β· aws Β· vercel Β· nginx Β· github actions
I use Claude Code, Codex, Multica AI and MCP-based workflows every day β not as autocomplete, but as a system. I design task breakdowns, tool boundaries, approval points, and reliability checks so agent-assisted work is something a senior engineer would actually ship. I've built custom Claude Code skill orchestrators with sub-agents (security audit pass over two production products, triaged into an epic, fixes shipped with cross-verification on a local stack).
The differentiator: I don't just use AI tools. I design the orchestration around them β tool surfaces, approval gates, test coverage β so the output is production-ready, not prototype-grade.
I'm actively looking to join a team β senior software, senior fullstack, senior frontend, or senior Web3 / blockchain engineer roles. Best fit: teams building in Web3, AI-native software, fintech, developer tools, marketplaces, or product-led SaaS.
The shape of the work I do best:
- a small team where one engineer can own a meaningful surface area
- ambiguous problems that need a working answer, not a perfect one
- a culture that respects both shipping speed and test coverage
If that sounds like your team β carlomigueldy.dev or carlomigueldy@gmail.com. I read everything.
built end-to-end Β· tested before shipped Β· shipped before perfected





