Founding C++ Systems Engineer

Our mission is to make AI useful in the languages where being almost right is worthless. We start with C and C++, because that is where the cost of a wrong answer is highest and where every existing tool is weakest. The team is small, the org is flat, and we would rather settle an argument by looking at the codegen than by seniority. We like people who are stubborn about correctness and fast about everything else.

About the role

ByteAsk builds a coding agent that has to prove its work. It runs the code under a debugger, puts it through the sanitizers, profiles it, and keeps reworking the diff until the toolchain agrees the patch is right.

You will own the part of the system that decides whether a patch is actually correct. That means running the real tools a C++ engineer runs, reading what they return, and deciding what to do next. It is an open research problem dressed as a systems problem, and today nobody has solved it: agents resolve roughly 63% of real-world issues in Python and under 10% in C and C++. As one of the first engineers you will have far more scope than the same title anywhere else.

What you’ll do

• Cross-translation-unit reasoning, where every public agent scores close to zero
• Turning debugger, sanitizer and profiler output into a next move
• Tool selection, including knowing when the honest answer is "we don't know"
• Making the loop fast enough to live inside an edit cycle
• On-prem deployments
• Performance optimizations

You may be a fit if

• You have spent real years in C or C++ and know why the hard bugs are hard
• You have read sanitizer output at 2am and gone to the codegen to settle an argument
• You are comfortable owning an ambiguous problem with little guidance
• You are sceptical of AI writing C++, and want to find out exactly where it breaks
• You do not need an AI background. We would rather teach that half

$150K to $200K plus 0.5% to 2.0% equity.