We've raised a total of $10.5M to bring automation to healthcare.
Read more
Engineering culture

How we build at Keragon.

We’re engineers who love owning things end-to-end. From the design doc to production. We ship fast with an AI-first workflow, secure defaults and a strong DevOps culture with a human always in the loop.

TypeScript
React · Node.js
Full CI/CD
Continuous shipping
AI-first
Claude Code · Auto-review
End-to-end QA
Engineers own quality
Our Stack

TypeScript, end-to-end.

We use TypeScript across the board - React on the frontend, Node.js on the backend. We work in a monorepo and we're fully cloud-native.

That said, we don't hire for a specific language or technology. Whether your background is Python, Java, C#, Go, or something else entirely, we don't mind. We're looking for strong engineers. The language is just a tool.

TypeScriptReactNode.jsMonorepoCloud-nativeHIPAA compliant
How We Build

Small teams. Full ownership.

No one hands out tasks here. You pick up a project and own it - the spec, the design, the build, the ship. You're not executing someone else's plan. You're making the plan.

  • * Small cross-functional vertical teams, each responsible for a slice of the product. Every team includes engineering, growth, and design - everything needed to operate independently.
  • * Each team uses a Team Alignment Map (TAM) to stay focused on what delivers the most business value, with clear ownership and dependencies tracked openly.
  • * We follow agile principles - ship frequently, adapt quickly, keep feedback loops tight - but without the ceremony. No story points, no forced sprint planning, no rituals for the sake of rituals.
  • * Each team runs weekly syncs to stay aligned. Every Friday, the whole company comes together for a town hall with demos, metrics, and KPIs - all shared openly.
How do we decide what to work on? Each team uses a Team Alignment Map (TAM) - a structured framework to stay focused on what delivers the most business value, with clear ownership and visible dependencies across teams.
AI-First Engineering

AI is embedded in how we build, every day.

We're an automation company - so we hold ourselves to the same standard we set for our customers. AI isn't a side experiment here. It's how we work.

  • * We plan and write code with tools like Claude Code, and every PR runs through AI code reviewers automatically.
  • * But we own what we release. Every piece of code is reviewed by the author and a teammate to make sure it's right and complies with our engineering guidelines. No exceptions.
  • * The result: incredible speed and quality. AI writes the code, we make sure it ships right.
  • * AI literacy is a company-wide expectation. Onboarding includes tooling sessions, and we share best practices and what's working across teams, regularly.
Human in the loop, always. AI reviewers help us move fast and catch issues early - but human judgment is the final call before anything reaches production. Safety is non-negotiable.
Quality & Shipping

Full CI/CD. Everyone ships.

DevOps isn't a team at Keragon. It's a culture. Everyone owns their releases, monitors their services, and takes responsibility for what they ship.

  • * Full CI/CD. Any engineer can release at any time, as long as your tests pass and your code has been reviewed by a human teammate.
  • * End-to-end QA. Engineers own quality across the board: unit tests, integration tests, E2E tests. Not because we're cutting corners - but because the people who build the software are the best people to make sure it works.
  • * Everyone monitors production. You ship it, you watch it. This creates accountability and engineers who deeply understand what they're building.
  • * AI reviewers help catch issues fast, but human judgment is always the final call before anything reaches production.
A Typical Day

Plan. Build. Ship. Repeat.

No one assigns you tickets. You and your team decide what's next. Here's what a day looks like in practice.

01 — Plan

Design first

Write a design doc, think through edge cases, run it by teammates for feedback. Good design saves bad debugging.

02 — Build

Build with AI

Write code with Claude Code or other tools. Review what they produce, iterate fast. AI is your pair programmer - you're the one with judgment.

03 — Ship

Own the release

Open a PR, AI review runs automatically, a teammate reviews, tests pass, deploy. No handoffs. No waiting. Done.

Who We Hire

We hire senior engineers.

Not because of a title or years of experience - but because of how you work. Here's what that looks like in practice.

You figure things out

Given a problem, you'll find the solution without waiting for someone to break it down into subtasks. Ambiguity doesn't stop you - it's where you start.

You own your work end-to-end

From understanding the problem, to designing the approach, to shipping it in production and supporting it after. No hand-offs.

You're excited about AI

You don't just use it - you think about how to use it better. You're curious about what's possible and you push the limits regularly.

You care about quality

Not because someone told you to write tests. Because you take pride in what you ship and you don't want to be paged at 3am either.

Language doesn't matter

We work in TypeScript, but if your background is Python, Java, C#, or anything else - that's fine. We hire engineers, not language specialists.

Full-stack mindset

You'll touch frontend, backend, and increasingly AI and agent work. You don't need to be an expert in all of it - but you're comfortable crossing boundaries.

500+ healthcare companies trust Keragon to build HIPAA-compliant automations in a secure way