Skip to content

Frequently Asked Questions (FAQ)

Here are answers to the most common questions about the KulKul Fellowship program, application process, and technical requirements.


Q: Do I need a letter of submission from my campus to join this fellowship?

Section titled β€œQ: Do I need a letter of submission from my campus to join this fellowship?”

No. You do not need a university cover letter to apply. Simply follow the 10-Step AI Challenge and submit your Pull Request to get started.

Q: Which majors or backgrounds can join this fellowship?

Section titled β€œQ: Which majors or backgrounds can join this fellowship?”

There are no major or university requirements. Anyone who is early in their software engineering journey can join. We welcome university students, self-taught developers, and career switchers alike.

We do not have a strict intake cap. If you complete the 10-step challenge, submit high-quality work, show solid git etiquette, and pass the final matching interview, you are welcome to join.

This is an intensive learning experience. We expect fellows to commit to at least 3 months of collaboration, with a minimum of 20 hours per week of active study, coding, and peer reviews.

This program is officially structured as a fellowship focused on peer-to-peer learning and community contribution, rather than a traditional corporate internship. However, because we facilitate the cohort with experienced engineering mentors, code reviews, and structured sandbox projects, it functions and provides the exact same hands-on value as a high-quality software engineering internship.

The initial version of the Kulkul Virtual Internship (previously hosted at open-source.kulkul.tech) has been officially sunsetted. The Kulkul Fellowship program replaces it entirely, offering a modernized, AI-first structure that builds upon the core principles of the original internship.


Q: Do my Pull Requests (PRs) need to be merged to be valid?

Section titled β€œQ: Do my Pull Requests (PRs) need to be merged to be valid?”

Yes. Your PRs must pass the review of our core crew and be merged to count towards your challenge completion, except for temporary steps where we specify otherwise.

The standard branch workflow is:

  1. Make sure you are on your main or master branch.
  2. Pull the latest upstream changes.
  3. Create a descriptive branch (e.g. feature/my-profile-page):
    Terminal window
    git checkout -b feature/your-branch-name
  4. Make your edits, commit your changes:
    Terminal window
    git commit -m "feat: your message"
  5. Push to your origin fork:
    Terminal window
    git push origin feature/your-branch-name
  6. Visit your fork on GitHub and click the green Compare & pull request button to submit it.