Team Idea
Joining an unfamiliar codebase is slow for a reason people rarely name: the code tells you what it does, never why. That reasoning lives in commit history, pull requests and the conversations around them.
We are building an onboarding copilot that uses IBM Bob 2.0's full-repository context to get a new engineer productive fast: map how the system is structured, trace a feature end to end, and answer "why is this like this" with the decision behind it rather than a paraphrase of the code.
The part we care about most: it is permission-aware. Context is stamped with who may see it, so a contractor onboarding onto one module does not get answers drawn from material they should never have read.
Background: 12 years backend, including owning a module inside a 6,900-commit platform I did not write, and 1,500+ commits to PeeringDB as an outside contributor.
Building solo but glad of company: frontend or design especially. UTC+7, flexible hours.
Team Members
Samsul Hadi
samsulhadi
Senior Software Engineer
