Using Weekly Projects for Job Applications

Every weekly assignment you submit inside the dashboard is a small, working piece of software. Most learners let these sit in a private repo until graduation. Treated correctly, each one becomes a public signal of skill that compounds week over week.

From Submission to Public Evidence

• Push the assignment to a public GitHub repo the same week you submit it, not in a batch at the end of the course.
• Write a two-line description: what the assignment required and what you built beyond the minimum.
• Tag the repo with the technologies it actually exercises (react, express, mongodb, openai-api) so it is searchable.
• Deploy anything with a UI, even a rough version — a live link outperforms a screenshot every time.

Weekly LinkedIn Posts, Not One Big Announcement

A single "I finished my bootcamp" post gets one moment of attention. A short post each week — what you built, one technical decision, one screenshot or short clip — builds a visible timeline that recruiters and future teammates can scroll through. It also gives you six or eight small pieces of writing to draw from instead of one, when you need to describe your experience in a cover letter or interview.

Building an Interview Answer Bank

After each weekly project, write down one debugging story and one design decision while the details are fresh. By the time you are interviewing, you will have a bank of specific, verifiable stories instead of trying to reconstruct them from memory under pressure. Pair this habit with the Interview Preparation practice questions in your dashboard to rehearse delivering these stories out loud.

Portfolio Deliverable

Audit your last three weekly submissions: confirm each has a public repo, a one-line description, and — where relevant — a deployed link. Then draft one LinkedIn post recapping the most technically interesting of the three.