Research Engineer

Job Description

We're a different kind of AI lab. Our research sits at the crossroads of database systems and interoperability, and it's shaped by real problems our enterprise partners bring to us.

\n

\n

We love work that's hard, meaningful and genuinely enjoyable at once. The best days here start with a tough problem, a whiteboard and a pile of code and experiments, and end with pizza boxes on the table and a solution finally cracked. We're builders at heart, drawn to problems nobody's solved yet and always looking past the immediate task toward what's next.

\n

\n

About the Role

\n

We're hiring a Founding Software Engineer to build products from the ground up and turn early stage research ideas into working systems. You'll contribute to product development, co-author papers submitted to leading scientific conferences and help drive our open-source efforts.

\n

\n

This is a true owner-operator position. You'll help shape a new type of applied AI research lab from its earliest days, with substantial equity upside to match the responsibility.

\n

\n

Who We're Looking For

\n

People who:

\n

\n
• Have an underway PhD or a PhD degree. We're a research lab, and every technical team member authors papers;
\n
• Have real builder experience, whether through hackathons, side projects or products shipped to real users (bonus points for scale);
\n
• Can't stop generating ideas. Ask them to build one feature and they'll come back with three more they think should exist too;
\n
• Want to work shoulder to shoulder with PhD researchers on new ideas in AI, ML and database systems;
\n
• Care about owning what they build from start to finish.
\n

\n

\n

Who We Are

\n

\n
• Moving fast: pre-seed funding closed, partnerships with leading universities in place and a major enterprise client signed, all within a few months;
\n
• Based out of two top-tier campuses;
\n
• Led by a technical founder with a PhD in computer science from a top program;
\n
• Committed to publishing at major scientific venues several times a year, with every technical team member credited as an author.
\n