Employers read for outcomes, not syllabi. Studied database systems describes what the university did. Designed and normalized a database for a mock logistics firm, then cut query times by rewriting the slowest joins describes what you did. Every semester produces raw material like this: capstones, labs, group projects, essays with defensible research, society roles, part-time work.
Do the translation while the details are fresh. For each significant piece of work, write down what the task was, what you personally contributed, which tools or methods you used, and what the result was. Keep the honest version: numbers you can defend in an interview and scope you actually owned. An hour of this at the end of each semester beats a panicked final-year reconstruction.
Where work can be shown, show it. A public code repository, a design portfolio, a writing sample, or a recorded presentation converts a claim into an artifact, and artifacts are what set early-career applications apart when everyone's work history is thin.