An application made for this job — a tailored resume and cover letter that speak straight to the posting.
NikoHealth is building a next-generation DME/HME platform and seeks an experienced Platform/DevOps Engineer to own CI/CD, developer experience, and release automation. You will modernize deployments across Windows Server/IIS and AWS, working with Terraform and Octopus Deploy, while collaborating with senior engineers and the CTO.
As one of the first two engineering hires in the US, you will shape the platform, drive automation, and scale the fleet.
NikoHealth is a rapidly growing SaaS company transforming how Durable Medical Equipment (DME) and Home Medical Equipment (HME) providers operate. Our innovative, all-in-one platform streamlines business operations, empowering providers to work smarter and more efficiently.
This is a newly created role, and one of the first two engineering hires NikoHealth will made in the United States. You'll report directly to the CTO and own how our software gets released and run while working closely with other senior engineers.
We operate dozens of .NET services deployed per-customer on Windows Server and IIS in AWS, managed with Terraform and Octopus Deploy. Across hundreds of provider tenants that's thousands of running application instances. Today a change waits for the next release train, and the train then takes weeks to reach the whole fleet, so end-to-end a given feature takes months. Improving our deployment and development experience is the first job. After that there are dozens of areas of platform investment needed to support how fast we're scaling.
This is brownfield and we're honest about it. Some of this estate is well-built and some of it grew. We're not asking you to rewrite it, because hundreds of providers bill claims through it every day. We're asking you to make it measurable, make it safe to change, then change it. If you've built a career inheriting other people's systems and making them boring, you'll like it here.
We work with AI agents, seriously. The team works agentically and so will you. What matters is what you do after the agent produces something: tests, linters, project instructions, a loop you can run again. If your answer to a bad result is a longer prompt, we're probably not a fit. This is also why developer experience sits in this role rather than somewhere else: an agent is only as good as the feedback loop it runs in, and ours needs work.
Most application development is done by a long-standing engineering partner. You'd own the pipeline, the infrastructure, and the environments, and over time the standards their code meets before it ships while working closely with our off-shore development team.
Two people isn't a platform team, it's the start of one. Until it's three, coverage is shared between you, the CTO, and our head of engineering. Everyone here is remote, and we'd like your hours to overlap the US East Coast.
This is the start of the engineering team, not the end of it. We're hiring more engineers through 2027. The people who join first get the widest scope, the most say in how the team gets built, and first choice about what they own as it grows.
This is a remote role, but candidates must be based in the U.S.