Ardenus is a company focused on building the structured-knowledge layer for modern enterprises, and they are seeking software engineers to join their fast-moving team. The role involves building features on the Ardenus platform, learning on the job, and growing into a more skilled engineer with support from experienced colleagues.
Responsibilities:
- Build real features on the Ardenus platform — backend, frontend, data, tooling, or infrastructure — starting with the parts that match what you already know
- Learn the rest on the job. You'll be paired with experienced engineers who review your work, answer your questions, and help you level up fast
- Own pieces of the product end-to-end as you grow, from the first idea through shipping it and watching people use it
- Ask questions out loud. We'd rather you ask early than guess. There are no dumb questions on this team
- Grow into the engineer you want to become. We invest in people, not just hires
Requirements:
- Have built something with code — a project, a feature, a script, a website, a contribution — and be able to talk through how it works and why you made the choices you did. It does not have to be at a job
- Know at least one programming language well enough to be productive in it (Python, TypeScript/JavaScript, Go, Java, Rust, C#, or similar). One is plenty to start
- Be willing to learn the rest as you go. We care more about how fast you pick things up than what you already know
- Communicate clearly in writing. Most of our work is asynchronous, and good writing is how we stay aligned
- Be genuinely curious about the problem space — data, AI, infrastructure, or the product surfaces that sit on top of all three
- Point to anything you're proud of — a repo, a school project, a hackathon entry, a freelance build, an open-source pull request, or a write-up. Polish matters less than that it's real and it's yours
- Show that you've taught yourself something hard and stuck with it until it worked
- Demonstrate any exposure to the areas we work in: web apps, databases, APIs, cloud, AI/LLM tools, or developer tooling. Any one of these is a great start
- Speak to a time you were stuck, asked for help or dug into the docs, and came out the other side. That instinct matters more here than knowing everything up front
- Bring a background, perspective, or path into engineering that's different from the rest of the team. We hire for range, and we mean it