Interview questions about your own GitHub project
Paste a public repo. Penwell reads the README, the stack, and the commit history, then writes the questions you are likely to get and answers you can say out loud.
Free: 5 notebooks a month. No card. Public repos only.
What the questions look like
An example for a made-up task board app. Your questions come from your own repo.
Why did you use WebSockets for the live board updates?
I wanted two people on the same board to see changes straight away. Polling every few seconds felt slow, and it sent a lot of useless requests. I kept a simple fallback to polling for when the socket drops.
What was the hardest bug in this project?
Cards jumped back to their old column when two people dragged at once. I fixed it by giving every move a version number and ignoring older ones.
How it works
- 1
Paste the repo link
Any public GitHub repository, like github.com/you/your-project.
- 2
Say what you are aiming for
Add the role and your level if you want. It is optional, but answers get better.
- 3
Practise out loud
You get questions about your project, answers you can say, and a short story of how it was built.
What you get
- Questions about the choices in your project: stack, structure, trade-offs, bugs.
- Answers written to be spoken, not read, so they sound like a person.
- A short project story built from your commit history: what you built first, what changed, what you learned.
- The same notebook works with flashcards, so you can drill the questions before the interview.
Who it is for
- Freshers
- Your projects are most of your resume. Be ready for every question about them.
- Career switchers
- Turn a side project into proof you can build.
- Bootcamp graduates
- Explain your capstone without freezing on "why did you choose that?"
- Working developers
- Remember what you built two years ago before you talk about it.
What to expect
Penwell can only work from what is in the repo. A thin README and a few vague commits give general questions. It cannot know why you made a choice unless the repo or your notes say so, so treat the answers as a draft and put in your real reasons. Check every claim about your project before you say it in an interview.
Questions
How does it make questions from my repo?
Penwell reads the README, the tech stack, and the recent commits. It uses them to write the questions an interviewer is likely to ask about that project, and answers you can say out loud.
Does it work with private repos?
No. Public repositories only for now. If your project is private, paste the README or your own notes into Penwell instead.
Is it free?
You can try it free. Every account gets 5 notebooks a month, no card needed. Pro is $1.49 a month if you want unlimited.
Should I memorise the answers?
No. Read them, change them to match what you really did, and practise saying them in your own words. Interviewers can tell when an answer is recited.
What if my README is short or I have few commits?
The result gets more general. Add a few lines about your role, what was hard, and what you would change, and the questions get sharper.
Can I tell it the role and level I am applying for?
Yes. You can add the role, company, level, and what you are good at or nervous about. The more you give it, the less it has to guess.
Try it on the project you will talk about
Takes about a minute. No card.