H2LooP.ai is building next-generation sovereign coding models and context platforms for system engineers across embedded systems, robotics, UAV, avionics, automotive, consumer electronics, and industrial IoT.

Our core team comes from Google, Toshiba, Cisco, Bosch, Philips, and NXP.

You will work on Hydron — our AI coding agent for hardware engineers. Same category as Claude Code and Codex, different problem: Hydron talks to real boards over serial, grounds itself in datasheets and reference manuals, and generates code that has to survive MISRA review and run on a microcontroller with 64KB of RAM. It ships as a CLI and a VS Code extension, and it runs inside air-gapped defense and automotive networks where no cloud API is reachable. You will work directly with the engineer who leads it.
 

What you'll own

Features and bug fixes across Hydron

• Ship real features end-to-end across both surfaces — the CLI agent runtime and the VS Code extension — from first commit to merged PR

• Work the bug backlog: reproduce the failure, write the test that catches it, fix the cause rather than the symptom, and verify the fix holds

• Hold the bar on your own work: tests pass, types check, and you can explain why the change is correct before you ask anyone to review it

Bringing the frontier into Hydron

• Track what Claude Code, Codex, Cursor, and the rest of the field are shipping, and form a view on what actually matters versus what is a demo

• Adapt the good ideas into Hydron rather than copying them: a pattern designed for web development usually needs rethinking before it works for someone debugging an I2C driver

• Argue for what we should build next, with reasoning grounded in having used these tools seriously yourself

• This is why heavy hands-on use of coding agents is a hard requirement below, not a nice-to-have. You cannot judge what is worth taking from a tool you do not use every day.

UX and DX

• Improve how Hydron feels to use: TUI interactions, output density, error messages that tell the user what to do next, first-run and onboarding flows

• Improve how Hydron feels to build: the test and typecheck loop, the internal tooling, and the friction that slows every engineer on the team down a little every day

• Turn the fixes into something that stays fixed: a script, a test, or a documented workflow rather than a one-off patch
   

Required experience

• Demonstrated engineering strength. Something substantial you have built that you can defend line by line — a real project, significant open-source contributions, a hard systems problem you solved. We care about what you can build and reason about, not where you studied or how long you have been doing it.

• Real TypeScript / JavaScript experience. Hydron is TypeScript end to end. You should be comfortable reading and changing a large codebase you did not write, without needing every file explained to you first.

• Heavy hands-on use of coding agents. You use Claude Code, Codex, Cursor, or similar as a daily driver, and you have opinions about them — what they get wrong, where they waste your time, what you have worked around. This is a core qualification for the role, not a checkbox.

• You find your own work. Given a rough problem instead of a specification, you investigate, decide what to do, and come back with something working plus a clear account of the tradeoffs you made.
   

Strong-to-have

• UI work in a component framework — the TUI and the extension webview are both SolidJS, and React experience transfers directly

• You have built something agentic yourself: tool calling, an agent loop, an MCP server, a scripted multi-step task that actually ran

• Taste in developer tooling: a CLI you built for yourself, an editor setup you have tuned, dotfiles you actually maintain

• Comfort in the terminal and with git as a tool rather than three memorized commands

• Contributions to an open-source project where you had to work inside someone else's conventions.
   

How the internship runs

Anywhere between 3 and 6 months. If you are still in college, we prefer 6 — it is long enough to own something substantial rather than just get oriented. If you have already graduated, 3 to 4 months is the norm, which gives both sides enough time to assess fit and performance before a full-time offer.

1. Weeks 1–2: Get Hydron running locally on both surfaces, then land your first merged PR from the bug backlog. Small, real, and in production — not a sandbox exercise.

2. Weeks 3–8: Own a scoped feature end-to-end: design, implementation across CLI and extension, tests, review, merge. Alongside it, work bugs and UX fixes so you see the whole codebase rather than one corner of it.

3. Beyond: Bring us something we were not planning to build. By this point you will know both Hydron and the wider agent landscape well enough to have a real opinion about what is missing — the expectation is that you make the case for it and then build it.
    

Compensation & logistics

• Competitive stipend

• In-person, Bangalore office

• Small team — direct access to founders and the engineers building the product
   

No cover letter needed. A degree, college tier, and prior internships are not filters here.