Start with one finished project
A small working project provides clearer evidence than several broken links. Describe the problem, setup steps, key decisions and limitations in the README. GitHub profiles let you highlight relevant repositories and add a profile README.
- Test the demo and repository links in a signed-out browser.
- Never publish keys, passwords or real users' private data.
- For a team project, identify the parts you personally completed.
Show results and limitations
Error handling and empty states matter alongside the visual interface. Explain the main flow you tested, how to reproduce it and any remaining limitation. Do not claim performance gains or user numbers you have not measured.
Demonstrate remote collaboration
Clarify requirements before proposing a technical solution. Break the task into steps and explain why you did not choose an alternative approach. If you do not know something, explain how you would check it.
Ask about shared meeting hours, code review, task management and on-call requirements. Agree on the size, deadline and production-use terms of a test assignment in advance. Check your microphone, camera and screen sharing before the interview.
Your checklist
- The project runs using your instructions.
- The repository contains no secrets.
- Your own contribution and limitations are clear.
- You have clarified hours, communication and assignment scope.
Sources
External sources are provided for further reading. Examples are written by Işla; they are not real vacancies or promises of pay.