Projects and coursework

Choose two to four projects that relate to the job, give each a clear title, context and dates, and describe what you did and what resulted in one to three bullets. A good projects section can do the work of an experience section for students.

Format:
"Title | Context (course, competition or personal) | Dates

• What you built, researched or produced, and the tools used.
• Your role, if it was a team.
• The result: grade, users, findings, award or feedback."

Example:
"Campus Parking Finder App | Mobile Development module | Sep – Dec 2025

• Built an Android app in Kotlin showing free parking spaces from a shared spreadsheet.
• Worked in a team of three; designed the database and wrote the search feature.
• Tested with 25 students; demonstrated to the class and received the top project grade."

Put the most relevant project first, and link to code, a portfolio or a demo if you have one. Leave out small exercises and projects that add nothing new.

Choose the projects that are most relevant to the job, most substantial, and easiest to explain with a clear result. Quality and relevance matter more than quantity.

Ask for each project:

• Does it use skills or tools mentioned in the job advert?
• Did I play a clear, significant role?
• Is there an outcome I can describe: a working product, a finding, a grade, an award?
• Can I talk about it confidently in an interview?

Your final-year or capstone project usually belongs on the list. Change your selection for different types of job, as different projects suit different roles.

Two to four projects is usually right for a one-page student resume. That is enough to show range without crowding out education and experience.

If projects are your main evidence, such as for software, data or design roles, three or four well-described projects can work. If you have strong internships, one or two key projects may be enough.

Each project should add something new: a different skill, tool or type of result. If two projects show the same thing, keep the stronger one.

Mention the team size, then focus your bullets on the parts you personally did. Readers want to know your contribution, not just the team's result.

Example:
"Retail Demand Forecasting | Business Analytics capstone | Jan – May 2025

• Team of four; I owned data cleaning and the forecasting model.
• Built a time-series model in Python that predicted weekly sales for 20 products.
• Presented findings to a panel; project graded A."

Use accurate verbs: "led", "designed" and "built" for your own work, and "contributed to" or "supported" for shared work. Be ready to explain your part in detail at interview.

If the team divided work by area, say which area was yours: research, design, coding, analysis, writing or presenting. If you also coordinated the team, add a separate bullet for that. Avoid writing "we" in bullets, and do not list the team's total output as if it were yours alone. A clear, modest description of a real contribution is more convincing than a claim to have done everything.

Yes, but describe only what you actually did, even if it was a smaller part. Claiming the whole project could backfire in an interview.

Example: "Contributed the competitor analysis section to a team marketing plan; created charts used in the final presentation."

If your part was very small and the project is not relevant, you may prefer to leave it out and include a project where your contribution was larger. Honesty about your role builds trust.

Give the project title, the course or programme, dates and any industry partner, then describe the problem, your approach, your role and the outcome. A capstone is often the best example of what a graduate can do, so it deserves space.

Example:
"Capstone: Energy Use Reduction for a University Building | BSc Mechanical Engineering | Sep 2024 – May 2025

• Team of five, sponsored by the university's facilities department.
• Measured air-conditioning energy use over eight weeks and modelled three improvement options.
• Recommended controls changes estimated to reduce cooling energy; findings presented to the facilities manager."

Tips:

• Lead with the problem in plain language.
• Name methods and tools that match the job.
• Make your personal role clear.
• Include any award, grade or adoption by the partner.

If the capstone is your strongest evidence, place the projects section above other experience.

Yes. Taking part in a hackathon shows you can build something under time pressure and work in a team, which employers value, especially in technology.

Example:
"FinTech Hackathon, Dubai | Mar 2025 (48 hours)

• Built a prototype budgeting chatbot with a team of four; I developed the backend API in Python.
• Pitched the prototype to a judging panel of industry mentors."

Describe what you built and your role. If you reached a final round or received a special mention, include it. You do not need to say you did not win.

Include the result in the title line or the first bullet, along with the event name, date and what you built. Prizes are strong evidence, so make them easy to see.

Example:
"Winner, Smart City Hackathon | Abu Dhabi | Nov 2025

• Developed a traffic-reporting web app with a team of three; I designed the map interface in JavaScript."

If the event had many teams, you can mention it only if you know the number from the organisers. You can also list the prize in an "Awards" section, but describe the project under projects.

List it as a project or achievement with the event, your team role, what you analysed and recommended, and the result.

Example:
"Regional Business Case Competition | Feb 2025

• Analysed a logistics company's expansion options with a team of four; built the financial projections.
• Recommended entry into one market; placed second of 16 university teams."

Case competitions show analysis, teamwork and presentation, which are valued in consulting, finance and management roles. Put the placing in the title if it was strong.

Usually no. Short assignments, worksheets and routine lab exercises are expected parts of a course and rarely stand out. Include only work that was substantial, independent or produced something notable.

A useful test: did it take several weeks, involve real decisions, or produce something you could show? If yes, it may be a project. If it was a two-day exercise everyone did, leave it out or mention the skill in your modules line instead.

Put the most relevant project first, whether it is academic or personal. Employers care about what you did, not where it came from.

You can use one "Projects" section and label each entry: "(Final-year project)", "(Personal project)" or "(Hackathon)". This keeps everything in one place and lets you order by relevance.

Personal projects can be especially persuasive because they show initiative. If one of yours is closer to the job than your coursework, lead with it.

Use a short, descriptive title that says what the project does or is about. Avoid internal code names or vague titles.

Better titles:

• "Inventory Tracker for a Local Pharmacy"
• "Sentiment Analysis of Hotel Reviews"
• "Marketing Plan for a New Café Brand"

Less useful titles:

• "Project X"
• "Group Assignment 3"

If your project had an official name, you can add a description after it: "SmartPark: parking availability app". The reader should understand the project from the title alone.

Add a link where there is something good to see, such as code, a live site, a demo video or a report. Do not add links to empty, unfinished or messy pages.

Tips:

• Use short links and make sure they work.
• Write the link as text, since some systems may not keep clickable links.
• Make the linked page explain the project quickly, for example a README with a summary and screenshots.

If you have several projects in one place, you can give one link to your GitHub profile or portfolio in the header instead of a link per project.

Tidy your best repositories so a visitor can understand them in a minute. An employer may only glance at it, so first impressions matter.

Checklist:

• Pin your two to four best projects.
• Add a clear README to each: what it does, how to run it, technologies used and a screenshot.
• Remove or make private any broken, copied or embarrassing repositories.
• Use meaningful commit messages going forward.
• Add a short profile description and a professional photo or avatar.

Do not upload coursework if your university forbids sharing solutions, and never upload company code from an internship.

Not always, but a simple portfolio can help for roles where samples of work matter, such as marketing, communications, writing, design or research. For many business roles, a strong resume is enough.

If you create one, keep it simple:

• Three to five pieces, such as a marketing plan, an article, a presentation or a research summary.
• A one-line description of each and your role.
• A shared folder or simple website that opens easily.

Remove confidential material or anything you worked on for an employer without permission.

Yes, if you learned something useful and can describe what you did. Not every project succeeds, and employers know that.

Focus on your actions and what you found:
"Solar-Powered Phone Charger | Engineering Design module | 2025

• Designed and built a prototype; output was below target in testing.
• Identified panel angle and battery losses as causes and documented improvements in the final report."

This shows honesty, testing and problem-solving. Be ready to talk about what you would do differently.

Only if you added meaningful work of your own, and describe it honestly. A copy of a tutorial project is common and does not show much.

Make it yours by:

• Adding new features or a different design.
• Using it to solve a real problem for you or someone else.
• Explaining what you changed and why.

Example: "Extended a tutorial to-do app with user accounts and reminders; deployed it for my study group."

If you only followed the steps, mention the skill you practised in your skills section instead.

Mention it if AI tools were a meaningful part of the work, and be clear about your own role. Honesty matters, and knowing how to use AI tools well can itself be a useful skill.

Examples:

• "Used an AI coding assistant to draft test cases, then reviewed and corrected them."
• "Built a chatbot on top of a commercial AI service; designed prompts and evaluated responses with 20 users."

Do not present AI-generated work as entirely your own. Be ready to explain how the project works without the tool's help.

Coursework means the modules or courses you studied; projects are specific pieces of work you produced. On a resume, coursework is usually a single line of module names, while projects get their own entries with bullets.

• Coursework: "Relevant modules: Thermodynamics, Fluid Mechanics, CAD Design".
• Project: "Heat Exchanger Design | Thermodynamics module | 2025", followed by bullets on what you designed and found.

Use coursework to show knowledge areas and projects to show what you can do. A strong project from a module is usually more persuasive than the module name alone.

Yes, if it was a substantial investigation with your own design, analysis or results, rather than a routine practical. Describe it like a small research project.

Example:
"Effect of Temperature on Enzyme Activity | Biochemistry lab project | 2025

• Designed and ran experiments at five temperatures with three repeats each.
• Analysed results in Excel and wrote a report graded A."

For lab-based jobs, name techniques and equipment you used, such as spectrophotometry or PCR, if you used them independently.

Describe the business idea briefly, your role, the research and analysis you did, and the outcome, such as a grade, competition result or real launch.

Example:
"Business Plan: Healthy Vending Machines for Schools | Entrepreneurship module | 2025

• Researched demand by surveying 90 students and parents.
• Built a three-year financial forecast and break-even analysis in Excel.
• Pitched to a panel of local business owners; plan rated highest in class."

Highlight the skills relevant to your target job, such as market research, financial modelling or presenting.

Name the brand or client (real or fictional), what you researched, what you recommended, and how it was received.

Example:
"Digital Marketing Plan for a Local Bakery | Marketing Communications module | 2025

• Audited the bakery's social media and identified gaps in posting and audience targeting.
• Proposed a three-month content calendar and a small paid ads test.
• Owner adopted the content calendar; project awarded a distinction."

If the plan was used by a real business, say so. Add a link to the plan or presentation in your portfolio if you have permission.

Yes, if it relates to the job or shows strong research and writing skills. Present it as a project with a short description.

Example:
"Research Paper: Remote Work and Employee Wellbeing in the UAE | Organisational Behaviour module | 2025

• Reviewed 25 academic sources and analysed survey data from 60 employees.
• Graded A; selected as an example paper for future students."

If it was published or presented at a conference, put it under "Publications" or "Presentations" instead.

Give each studio project a title, brief, and your design approach, and link to a portfolio with drawings and images. For design roles, the portfolio is often as important as the resume.

Example:
"Community Library Design | Year 3 Design Studio | 2025

• Designed a two-storey library for a site in Sharjah, focused on natural shading and courtyards.
• Produced plans, sections and 3D renders in Revit and Lumion."

Choose the projects that best match the employer's work. Keep descriptions short and let the portfolio show the detail.

State the question, the data, the tools and methods, and the main finding. Data roles want to see your process and your ability to explain results.

Example:
"Dubai Metro Ridership Analysis | Personal project | 2025

• Cleaned and analysed open data on monthly ridership using Python (pandas) and SQL.
• Built a Power BI dashboard showing trends by line and station.
• Found that weekend ridership grew faster than weekday ridership; published a short write-up on my blog."

Link to the code or dashboard if you can.