INDX Summer of Code 2026
Make this summer show up on your GitHub.
An AI-driven take on Google Summer of Code, for university and graduate students in Japan. Rolling start from August 2026: build software with a clear user story and real use cases, under review from full-time engineers, and publish it as open source.
You can start it as a side project alongside job hunting or research.
3weeks
Per project. Start date and length are negotiable.
¥2,000/hr
From ¥2,000 per hour, set by experience and skill.
100%
Every deliverable ships as open source.
Shift/Remote
Remote or on-site, your call. No fixed hours.
About
INDX Summer of Code is an internship built around AI coding tools. In three weeks you finish one piece of software and publish it as open source. Getting the AI to produce something that runs is not the finish line — the scope runs through review by full-time engineers until the code is readable by others, runnable by others, and fixable by you later.
Why join
01
We do not accept "the AI wrote it and it runs." Design, naming, error handling and tests get reviewed in a weekly session, with the reasoning spelled out.
02
Not "something impressive with AI" — something with a user story and use cases defined up front. Concrete specs are why three weeks is enough to finish.
03
Everything ships under an OSS license. After the program it is still your repository to improve — and one URL on your resume points at real code and real commits.
Team
Reviews are done by our full-time engineers. The three below set the engineering direction and the bar your code is held to.
01
Chief Executive Officer
伊藤 克哉
02
Chief Operating Officer
髙谷 謙介
03
Chief Technology Officer
オレリアン・クルゾ
Environment
No paying for cloud time or AI tooling out of your own pocket. We provide what the work needs; you decide how you work.
Use the INDX cloud environment, GPUs and managed services included. No personal server bills.
We provide accounts for the AI coding tools we use in production. No personal usage caps to worry about.
Fully remote works. On-site is welcome too, and you can switch mid-program.
No fixed working hours. Fit it around classes, research and job hunting.
One engineer is assigned per project, reachable on Slack whenever you are stuck.
README, license, sample data, demo video — we see the release through with you.
Focus areas
Themes come from these four areas — all of them work we actually do, which means someone in-house can review your code. Bringing your own theme is welcome too.
01
Collecting information scattered inside and outside the company, structuring it, and making it retrievable — treated as one continuous problem.
Concrete themes
Ingest several sources and stand up an internal knowledge base that answers with citations, in one command.
02
Raising small open-weight models to production quality, so data that cannot leave the building still gets processed.
Concrete themes
Drop in task samples and get a specialised model plus an accuracy-and-cost comparison table.
03
Handing judgement calls to an agent, so people spend their time framing the question and checking the conclusion.
Concrete themes
Hand it a CSV and one question, and get a cited report whose every step you can re-run.
04
Turning PDFs, forms, drawings and audio — none of it searchable or countable as it stands — into structured data.
Concrete themes
Index an entire pile of unstructured files and compare how often any term appears, year by year.
What you build
Every project has a clear user story and concrete use cases — and a stranger handed the repository can start it with one command by following the README. Meet both and it is done.
Program
The schedule is a guideline. Start date and daily rhythm bend to your calendar.
WEEK 0
Pick the theme, write the user story in one sentence, get your cloud environment and AI coding tools, create the repo.
WEEK 1
Drive the thinnest end-to-end use case with AI coding tools. Get consolidated feedback at the weekly review.
WEEK 2
Implement the rest. Design, error handling and tests get tightened through review — the steepest week technically.
WEEK 3
README, sample data, one-command start, demo. Add a license and publish it as open source.
AFTER
Keep improving it on your own. Send issues and PRs and we will keep reviewing.
Side project
Even with job hunting or another internship in motion, you can start this as a side project. Hours are shift-based, with nothing you have to attend at a fixed time. Weekends only or evenings only is fine.
And what you build gets published as open source. One URL on your resume lets an interviewer read the code and the commit history directly. Far faster than writing "I can use AI" — show what you finished and shipped with it.
Requirements
No professional experience required. We do assume you can read code yourself and understand roughly how AI coding tools work.
Required
Nice to have
Even if few of these apply, apply anyway if you have something you want to build. We start with a 30-minute chat.
Outline
Selection process
FAQ
Yes. Most people start as a side project, a few hours a week. Hours are shift-based and self-declared, and the start date is flexible. Three weeks is a guideline for focused work, not a deadline.
Yes. We look at what you have built — any size — and what you want to build next. We will help you set up your AI coding workflow after you join.
Yes. There are no fixed hours. Evenings only or weekends only is fine.
No. We provide INDX cloud infrastructure and AI coding tool accounts. A browser and an editor are enough to start.
It ships under an OSS license (MIT / Apache-2.0) and stays yours to improve and use afterwards. No customer data or confidential material goes into these projects.
Application form, a 30-minute casual chat, a conversation to align on the theme, then confirmation. We cover compensation details in the chat.
Apply
An engineer will reply within two business days. We start with a 30-minute casual chat to align on what you want to build and how.
Just want to talk first? That is welcome too.
contact@indx.jp