We’re hiring a Fullstack Engineer to join our startup and incubator. If you’re a real engineer who’s embraced AI as a force multiplier — not a crutch — keep reading. The Role We’re building multiple products across our incubator, and our founding engineer needs to start handing things off. That’s where you come in. You’ll own features and tasks end-to-end. We’ll give you context, point you in a direction, and trust you to ship it. Around 40–60% of your day‑to‑day will involve AI‑assisted development — but the kind where a real engineer is behind the wheel, not just copy‑pasting outputs and hoping for the best. The rest of the time, you’ll be reading existing codebases, understanding production systems, working with databases, and making thoughtful changes to architectures that are already in place. When the AI breaks (and it will), you need to know how to debug and solve problems on your own. $36,000 - $72,000 (Based on experience) What You’ll Do Take ownership of features and projects from kickoff through deployment — without needing to be walked through every step Work within existing production codebases, understanding how things are built and why before making changes Use AI tools daily and effectively as part of your engineering workflow Work with databases and make architectural modifications to existing systems Make smart product‑level decisions when they come up — we’re a startup, not a place where every pixel gets approved by committee Communicate clearly and proactively, especially when you’re blocked Ship across multiple projects as we build and incubate new products What We’re Looking For A trained engineer first. You were writing and shipping code before AI tools existed. You understand fundamentals — data structures, system design basics, debugging, reading other people’s code. AI makes you faster, not functional. Fullstack proficiency. Comfortable across the stack. You don’t need to be a specialist in everything, but nothing should feel foreign. Database experience. You’ve worked with databases in production — querying, modeling, migrations. Not just tutorials. Architectural awareness. You can look at how a system is built, understand the reasoning, and make modifications confidently. We’re not asking you to architect from scratch — but you need to navigate and extend what’s already there. Autonomy and ownership. You take a task, figure out the path, and deliver. You ask good questions when you’re genuinely stuck, not because you need your hand held. AI‑native workflow. You actively use AI in your engineering work and understand both its strengths and its limits. Strong English communication. Our team operates primarily in English. You’ll be receiving tasks and collaborating with leadership who may not speak Spanish, so you need to be comfortable communicating clearly in English — written and verbal. This Role Is Not a Fit If We want to be upfront so we don’t waste your time or ours: You learned to code primarily through AI tools. We need someone who was building and shipping software before ChatGPT, Copilot, or any LLM‑based tooling existed. If AI is how you learned — rather than how you accelerated — this isn’t the right role. You need detailed specs and step‑by‑step guidance for every task. We’ll give you context and direction, but you’re expected to figure out the path forward. This is a startup — not everything is documented. You’re looking for heavy mentorship or a structured learning environment. We’re happy to answer questions and unblock you, but we’re not in a position to teach fundamentals. You should already have them. You’re not comfortable making decisions on your own. If you freeze when there’s no clear “right answer” or need approval on every small choice, you’ll struggle here. Your English isn’t strong enough to hold a real‑time technical conversation. We need you to communicate clearly with team members who don’t speak Spanish — written and verbal, without friction. Location This role is remote for candidates based in Argentina or Colombia . Spanish is the day‑to‑day language with part of the team, but English fluency is required. Why This Role You’ll have real ownership from day one. We’re not hiring you to execute a Jira board — we’re hiring you to help us build. You’ll work across multiple products, have direct input on how things get built, and operate with the kind of autonomy that only exists at early‑stage companies. If you’re tired of being micromanaged and want to actually own your work, let’s talk. To Apply We’re not looking at resumes first — we’re looking at how you communicate and think. To be considered, please apply at the link: Applications without a Loom video will not be reviewed. We know that’s an extra step — that’s the point. We want people who are willing to put in the effort. #J-18808-Ljbffr