Software Engineer

Summary

Ardenus is hiring software engineers across the stack. We're a small, fast-moving team building the structured-knowledge layer that modern enterprises run on — ontology, data pipelines, AI applications, infrastructure, and the product surfaces that sit on top. Most of our roles are specialized, but a lot of good engineers don't slot cleanly into one box, and we'd rather meet you than miss you.

This is the general track. If you write good software and want to do meaningful work, apply here and we'll route you to the team that fits. We hire for judgment, taste, and the ability to ship — not a specific résumé shape.

Description

Build production features across the Ardenus platform — backend services, data pipelines, frontend surfaces, internal tooling, or infrastructure, depending on where you fit.

Work directly with the people whose decisions you're affecting. Small team, short feedback loops, no committee design.

Own what you ship end-to-end, from the first sketch through deployment and the on-call rotation that follows.

Pick up the parts of the stack you haven't worked in before. We'll back you while you learn.

Help us decide what gets built. Engineering input shapes the roadmap here, not the other way around.

Minimum Qualifications

• You should:
• Have shipped real software that other people use — at a job, in school, as a side project, or in open source. We care that it exists and that you can talk through it.
• Be fluent in at least one mainstream programming language (Python, TypeScript/JavaScript, Go, Rust, Java, or similar).
• Read code carefully, write code that other people can read, and debug your way out of things that don't work the first time.
• Communicate clearly in writing. Most of our work is asynchronous.
• Be excited about the problem space — data, AI, infrastructure, or product surfaces sitting on top of all three.

Preferred Qualifications

• You can:
• Point to something you've built that you're proud of — a repo, a project, a feature, a write-up, a talk.
• Demonstrate experience in any of the areas we work in: knowledge graphs, LLM applications, data pipelines, cloud infrastructure, frontend systems, or developer tools.
• Show that you've worked across the stack at some point, even if you've since specialized.
• Speak to a moment where you took something that wasn't working and made it work — a flaky pipeline, a slow query, a broken deploy, a confusing UI.
• Bring a perspective we don't already have on the team. We hire for range.