Junior Full-stack Engineer

About the role

We are not looking for someone who already knows everything: we are looking for someone who learns fast, asks early, and is not satisfied with "it works on my machine".

You will start with scoped screens and endpoints that have clear acceptance criteria, and as you show judgement you will take on larger pieces. Your work gets reviewed and explained — that is the part that makes you grow.

It is a demanding first (or second) job: the product is real, the users are hospitals, and regulation is involved. In exchange, in one year you will know more about architecture and a complex domain than in three years building landing pages.

What you will do

• —Build screens in Next.js 14 with TypeScript, following the theming system and the patterns already established in the repository.
• —Create scoped NestJS endpoints with their input validation and role-based access control, on top of data models that already exist.
• —Replace placeholder data with real backend data: a good number of inherited screens still show simulated information and need to be wired up properly.
• —Write tests for what you build, and reproduce reported bugs until you find the cause (not the symptom).
• —Document what you learn in the repo: the next junior will thank you.

What we need from you

• —Solid JavaScript/TypeScript fundamentals: types, asynchrony, `async/await`, and understanding why `Promise.all` exists.
• —React with hooks: state, effects and component composition. Having built something end to end, even if personal or academic.
• —Working knowledge of SQL: writing a `JOIN`, understanding a foreign key, and knowing why an index matters.
• —Git: branches, commit messages a human can read, and resolving a conflict without panicking.
• —Something published we can look at: a GitHub repo, a deployed project, or a thesis with code. It counts for more than your GPA.
• —The ability to read someone else's code and to say "I did not understand this" without embarrassment. It is the skill we accelerate the most.
• —Fluent Spanish and full-time availability.

Nice to have (not required)

• +Having used a Node backend framework (NestJS, Express, Fastify) or an ORM such as Prisma or TypeORM.
• +Familiarity with Docker, even if only running `docker compose up`.
• +Having used Claude Code, Copilot or similar — and being able to tell us where it helped and where it led you into a dead end.
• +Genuine interest in healthcare: that kind of curiosity pays for itself here.

The stack you will work with

This role is NOT for

• ×Anyone who only wants to "make the front-end look nice" without touching data or servers: the role is full-stack from month one.
• ×Anyone who copies an answer from an AI model and ships it without understanding it. Asking is fine; pretending you understood is not.
• ×Anyone who needs a large team to hide in while learning: here everything you do is visible, for better and for worse.

How the process works

1. 1 · Apply
   The form on this page, with your GitHub or portfolio. No cover letter: we would rather read code.
2. 2 · Intro call (30 min)
   A short video call: what you have built, what interests you, how you work. We talk about terms and the salary band here, openly.
3. 3 · Paid take-home
   A scoped exercise on our real stack (3–5 hours). We pay for it: your time is worth something.
4. 4 · Technical review (60 min)
   We go through your decisions together. No whiteboard algorithms — we talk about your code.
5. 5 · Offer
   An answer within 5 business days of the review, yes or no.

What we offer

• —Salary in USD, paid monthly — we discuss the band on the first call, no games.
• —Fully remote within Colombia (optional hybrid in Medellín).
• —Budget for AI tooling (Claude, frontier models) — we use them, we pay for them.
• —Real product, real users, fast decisions: what you propose ships in days.
• —A crash course in Colombian healthcare: regulation, interoperability and electronic invoicing.