Your code, inside a hospital — not a backlog.
Eclypse engineers don't ship features into a queue. They sit inside a government agency, a hospital pharmacy, or a pharma sponsor's own environment and carry one real workflow from bottleneck to signed-off output. We're looking for people who want that — whether you've done it for a decade or you're trying to find out if it's for you.
Forward-deployed, not back-office.
Forward-deployed engineers at Eclypse own a workflow end to end: the domain, the deployment, the evidence, and the expert on the other side of the desk. There's no hand-off to a separate "customer success" team — you stay accountable for what you build until your team has fully handed the wheel over to theirs.
Weeks inside the environment
Time spent inside customer environments — a government cloud tenancy, a hospital's pharmacy floor — not in a sprint-planning tool.
One engineer, one workflow
You carry a workflow from bottleneck to signed-off output. No hand-off to a separate delivery team partway through.
Engineering with teeth
Air-gapped runtimes, GDPR, PDPA, MLR review. The constraint is the interesting part, not the obstacle.
Nothing you build is thrown away
What you build becomes a module every future deployment stands on — including the next one you're handed.
An internship here means a real work package, not a project that gets thrown away in September.
We don't scope down a toy version of the work for interns. You'd sit next to a forward-deployed engineer on one bounded piece of an actual deployment — a specific module, a specific agent, a specific extraction step — with your name on something that ships into a real environment, not a repo nobody opens again.
Work one bounded slice of a real work package — the same registry of modules a full-time engineer builds from, not a separate "intern track."
Directly with the forward-deployed engineer who owns the deployment, not a rotating buddy system.
A finished CV of healthcare or regulatory experience. Curiosity about the domain and comfort saying "I don't know that yet" go further here.
Regardless of where you are in your career.
- You'd rather own a real constraint than be handed a clean spec.
- You're comfortable being the only engineer in the room and the only non-clinician, non-regulator in the next one.
- You'll learn a domain — pharmacovigilance, HEOR, hospital procurement — as deep as you'll learn the code.
- You want to see what you built still running a year later, not sunset in the next re-org.
There's no standing job board — here's why.
We hire around specific work packages as we win them, not against a running list of open requisitions — so there's rarely a listing sitting here that matches you exactly. Write to us directly instead: tell us what you'd want to work on, where your background overlaps with what's on this page, and whether you're looking for a role or an internship. We read every one ourselves.
Write to us
ECLYPSE
AI
Our proprietary AI orchestration platform for healthcare: one engine, a registry of reusable task modules and domain agents, and a governed knowledge base — deployed inside your walls and run by your team.