Founding Engineer - Special Projects

The Get-Sh*t-Done Engineer

Some of the most valuable people we've worked with don't fit neatly into a job description.

They can write code, debug hardware, figure out unfamiliar engineering problems, deal with customers, automate a workflow, and get something working before everyone else has finished discussing it.

We're looking for one of those people.

You'll work on whatever the most important problem at Aran is that week. Sometimes that means building an AI agent. Sometimes it means figuring out a difficult engineering constraint, prototyping a new tool, or getting a customer deliverable across the finish line.

You don't need to be the world's best specialist. You need to be exceptionally good at figuring things out and getting them done.

What you’ll achieve

• Take on high-priority engineering and software problems across the company, from concept to working solution.
• Build internal tools, AI agents, automations, and prototypes that eliminate repetitive engineering work.
• Work across civil, structural, mechanical, electrical, and software disciplines, learning whatever is necessary to solve the problem.
• Help turn messy, manual engineering workflows into scalable, automated systems.
• Jump into real customer projects, identify bottlenecks, and ship solutions without waiting for someone to define the process.
• Do the things that don't fit into anybody else's job description but absolutely need to happen.

Requirements

• You must
• Have an unusually strong track record of building things and figuring out hard problems independently.
• Be able to use AI coding tools to build functional software, regardless of your formal background.
• Learn unfamiliar technical subjects quickly and get productive without extensive guidance.
• Have excellent engineering intuition, resourcefulness, and judgment.
• Be relentlessly execution-oriented. When you encounter something you don't know, your first instinct is to figure it out.
• Care more about shipping working solutions than titles, processes, or organizational boundaries.
• You do not need to Have any particular degree or formal educational background.
• Specialize in one engineering discipline.
• Have worked in data centers, construction, or AEC.
• Have followed a conventional career path.
• If you've built companies, shipped hardware, written software, automated your own job, or accomplished something technically difficult that nobody asked you to do, we want to hear about it.