Full Time
open for negotiations
40
Jun 19, 2026
Location: Remote (Philippines-based)
Duration: 6-month OJT (potential full-time conversion)
Hours: 40 hours/week
Stipend: TBD (open for discussion based on experience)
Updated: June 2026
THE ROLE
You'll be building the actual software that runs our ventures — and learning how real software gets shipped in a
live, fast-moving business environment.
We don't have time for slow sprints. We have more ideas than hands. Dashboards our clients demand. Internal
tools our teams stitch together in spreadsheets. Client-facing portals that need to exist. Snap & Prospect
automation pipelines. And someone needs to make them real.
That someone is you — but we'll teach you how.
What you'll actually do:
• Build real, shipped tools — not homework projects. CRM enrichment scripts, onboarding workflows,
recruiter dashboards, automation glue between Gmail/Sheets/Telegram/Slack. You'll see your code running in
production within weeks, not months.
• Learn by doing — We'll pair you with our team on live builds. You'll see what good code looks like (and what
bad code looks like). You'll learn when an AI is being helpful vs. when it's confidently wrong. You'll ship messy
v1s and iterate based on real feedback.
• Own the full loop — Spec (usually from a Slack message or voice note), build, deploy, iterate. We give
direction; you ship.
• Treat AI as a co-builder, not a crutch — Claude Code, Cursor, Windsurf — these are your tools. You'll learn
to work with AI, not just at AI.
• Move fast — When someone says "what if we…", you'll prototype something demo-able in a day or two, not
request a Gantt chart
WHO WE'RE LOOKING FOR
You don't need 5 years of experience. You need the right foundation and mindset.
Must-have:
? Technically capable — You've built something that ran. A side project. A class assignment you actually
finished. A startup idea you coded. It doesn't need to be polished; it needs to be real.
? AI-native — You think in AI. You use Claude, ChatGPT, or Cursor daily. You can articulate your actual
workflow (not "I sometimes use Copilot"). You're comfortable asking an LLM for code and know how to spot
when it's lying.
? Systems thinking — Either you're a CS/IT student or recent grad who understands databases, APIs, and
deployment, OR you're a business/entrepreneurship student who's built a venture or prototype and understands
how systems need to work to solve real problems.
? Hunger to ship — You get frustrated by endless meetings. You want to see your work in the world. You're
willing to learn in public.
? Communication — Half our briefs come as voice notes. You're okay with ambiguity and can ask clarifying
questions without needing a 30-page spec.
Nice to have:
? You've built something with Claude Code or Cursor and can talk about what worked/didn't
? You're comfortable with: Next.js, React Native, FastAPI, Node, Supabase, Vercel
? You've touched:
? You understand business tools: CRMs (HubSpot, Pipedrive), recruiting ops, or SME workflows
? You're based in the Philippines and understand SEA or Australian SME operations
THE OJT ADVANTAGE
This isn't a typical internship. You're not making coffee or organizing files.
? You'll ship real code to real users within your first month
? You'll learn modern development the way it's actually done in 2026 — with AI as a first-class teammate
? You'll work across the full stack — no "frontend only" silos; you'll touch API design, database schemas,
deployment, customer feedback loops
? You'll build a portfolio of deployed projects you can show future employers
? You'll earn a stipend (negotiable) + potential full-time offer at the end if it's a good fit
? You'll be paid for your time — not exploited as free labor
HOW TO APPLY
Send us:
1. A short note (200 words max) on:
• The most interesting thing you've built (could be a hackathon project, class assignment, side project, startup
idea)
• What it does
• What tools you used (especially if you used AI)
• What you'd do differently if you built it again
2. Show your work:
• GitHub links (even half-finished projects)
• Deployed apps or links to live projects
• Screenshots, demo videos, or Loom walkthroughs
• If you built something with Claude Code or Cursor, please include it
3. Optional but encouraged (60–90 minutes):
Pick one and build it using Claude Code, Cursor, or your favorite AI-native tool. Don't polish it. Send us the
messy version + a 2-minute Loom walkthrough explaining what you built and what you'd change.
Option A: A CSV-to-personalized
Option B: A
Option C: A mini dashboard that pulls from a public API (weather, crypto prices, GitHub repos, whatever) and
displays something useful
Send your code + Loom to: