Full-Stack Engineer (Mid-Level, 4–8 years)

Before you read further

We are a four-person seed-stage healthcare startup. We match patients to clinical trials at the point of care using structured intake data, and our platform is already running in production inside a major Korean university hospital. There is no layer of management between you and the outcome. That means two things:

1. You will own real systems that real hospital staff depend on, from your first month.
2. There is nowhere to hide. If you are looking for a place to coast on a salary while doing the minimum, this is the wrong posting. We say this plainly because it saves both of us time.

We are looking for one engineer who wants to build something that matters, is willing to be judged on results rather than hours, and treats "I said I would ship it Friday" as a promise.

What you will do

1. Build across the stack. Ship features end-to-end in our Next.js 15 / NestJS / Prisma / PostgreSQL codebase — API design, data model changes, frontend UI, tests, and the deployment that gets it into the customer's hands. You will not be handed tickets with the thinking already done.
2. Own your slice of the codebase. Take responsibility for defined modules of the platform: code quality, technical debt, documentation, and their behavior in production. When something breaks in your area, you are the first to know and the first to act.
3. Support customer deployments. Our product runs on-premise inside hospital networks (Linux, Docker, restricted or offline environments). You will help package installers, run deployments with our Lead Engineer, and troubleshoot directly with customer IT staff when needed.
4. Ship AI-driven features responsibly. We are turning our roadmap into concrete LLM-assisted features for a regulated environment. You will implement and integrate model-backed features under strict data-handling rules — patient data never leaves the customer's boundary or enters third-party AI APIs.
5. Communicate like an owner. Write down what you are doing, why, and when it will be done. Raise risks before they become delays. Give and receive direct code review. Run your own conversations with the Lead Engineer and, when relevant, with leadership and customers.

4–8 years of professional software development experience, with meaningful time in both backend and frontend work. TypeScript/Node.js and React experience is strongly preferred; you should be productive in our stack within weeks, not months.

Production ownership. You have kept at least one system running in production — you have been paged, you have debugged a live incident, you have written the fix and the post-mortem.

Relational database competence. You can design a schema, write and optimize SQL, and reason about migrations on live data (we use PostgreSQL with Prisma).

Deployment literacy. Comfortable with Git branching strategies, CI/CD (GitHub Actions), Docker, and Linux server basics. You do not need to have led releases, but you must be able to execute one safely.

Track record of finishing. You can point to work you drove to completion with limited supervision — you set the schedule, communicated it, and hit it. We will ask for specific examples and we will check them.

Direct, written-first communication. You document decisions, you say "I don't know" when you don't, and you disagree openly rather than quietly.

Working proficiency in both Korean and English (reading and writing technical material in English is essential; our codebase, documentation, and much of our internal communication is in English).

Experience deploying software into customer-controlled or on-premise environments (installers, environment constraints, offline/air-gapped systems).

Experience building or integrating LLM/AI features into a production product.

Experience in healthcare, regulated industries, or environments with strict data/compliance constraints (PIPA, HIPAA, or similar).

Exposure to a U.S. or international work culture (direct communication, ownership-driven, asynchronous by default).

Early-stage startup experience where you wore more than one hat.