Skip to content
Tutorials Center
My learning

Topics

Lesson 64 of 77 ยท Behavioral and Soft Skills

Resume, Portfolio and Take-Home Projects

Write developer resume bullets that get interviews, choose portfolio projects that impress, and handle take-home assignments with a clear strategy.

Before anyone asks you a question, they read a page. A recruiter often spends less than a minute on a resume, and an engineer skimming a portfolio decides within a few clicks whether the work is worth a closer look. Interview skills do not help if you never get the interview, so this lesson covers the documents and projects that get you there, plus the take-home assignment that sometimes stands between you and the on-site loop.

Everything here is advice rather than code, because no runtime is needed to improve a resume. Use it as a checklist when you edit your own.

What should a developer resume look like?

Keep it to one page if you have under about ten years of experience, two at most otherwise. Use a plain single-column layout, a standard font and normal section names (Experience, Projects, Skills, Education). Many companies run resumes through software that extracts text, and fancy columns, icons and skill-level bars can scramble it or add nothing.

A resume in order

Header Name, email, city, GitHub, LinkedIn.
Experience Newest first, three to five bullets each.
Projects Two or three, with links.
Skills Honest list, grouped by type.

Education goes first only if you are a recent graduate.

1 / 2

List only skills you could discuss for five minutes. Interviewers love to pick one item from your skills list and ask about it; "Kubernetes" on a resume is an invitation to be asked how a pod is scheduled.

How do you write strong bullet points?

A bullet should say what you did, how, and what changed. The pattern is action verb + what + how/scale + result. Compare:

Weak Strong
Responsible for the search feature Built product search on Elasticsearch handling 40k queries a day; cut median response time from 900 ms to 180 ms
Worked on bug fixes Fixed 35 production defects in the billing service, reducing support tickets about invoices by roughly a third
Helped with testing Added integration tests for the payment flow, raising coverage from 40% to 78% and catching two regressions before release

Rules of thumb:

  • Start with a strong verb (built, designed, reduced, migrated, led), not "responsible for".
  • Include a number when you honestly have one: users, requests, time saved, money, team size. If you do not have an exact figure, an honest estimate with "about" is fine. Never invent numbers; interviewers will ask how you measured them.
  • Show impact, not duties. "Wrote unit tests" is a duty; "caught regressions before release" is an impact.
  • Say what you did. If the work was a team effort, describe your slice of it.
  • Put the most relevant bullets first for the job you are applying to, and tailor a few words to the posting. Copying keywords you cannot back up is a trap.

Be ready to explain every line. A resume is the agenda for your interview, and the questions will come from it.

What projects impress employers?

Quality beats quantity. Two projects you can discuss in depth are better than ten tutorial clones. Strong projects share traits:

  • They solve a real problem, even a small one: a tool you actually use, a scraper for a hobby, a bot for a community.
  • They are finished enough to try. A live link or a short demo recording matters, and so does a README that explains what it is, how to run it and what you learned.
  • They show engineering, not just features: tests, a sensible structure, error handling, a deployment, a short note on trade-offs you made.
  • They match the role. For a back-end job, an API with authentication, a database and a rate limiter says more than a pretty landing page. For front-end roles, accessibility, performance and responsive design matter.
  • You wrote them. Following a video tutorial step by step shows persistence, but it does not show design thinking. Extend it with your own feature and say so.

Contributions to open-source projects count too, even small ones: documentation fixes, a reproduced bug report or a merged pull request show that you can work in someone else's codebase.

Your repository as a portfolio

Reviewers do open GitHub. Pin your best repositories, give each a clear README with a screenshot, setup steps and a short "design decisions" section, and delete or archive abandoned experiments. Commit messages that explain why and a visible history of tests passing in CI tell a story that a flashy theme cannot.

How do you handle a take-home assignment?

Take-homes range from a two-hour exercise to a weekend project. Treat them as a sample of how you work, not a trick question. A reliable approach:

  1. Read the brief twice. List the requirements, the stated constraints (language, time limit) and what is unclear. Note the evaluation criteria if they are given.
  2. Ask clarifying questions by email if something is truly ambiguous; otherwise write down your assumptions in the README. Both show good judgment.
  3. Scope to the time limit. If they say "about three hours", do not spend fifteen. A smaller, polished solution beats a sprawling one, and overshooting can signal that you will struggle with boundaries.
  4. Get a correct core working first, then add tests, then polish. Commit as you go with clear messages.
  5. Write a short README: how to run it, how to run the tests, what you assumed, what you would do with more time, and any trade-offs.
  6. Test the edges: empty input, invalid input, large input, duplicates. Reviewers check them.
  7. Run it from a clean checkout before submitting, as a reviewer would. A solution that does not start is the most common avoidable failure.

Pitfalls to avoid: over-engineering with frameworks the task does not need, leaving debug output and commented-out code, ignoring error handling, copying solutions you cannot explain and skipping tests. Expect a follow-up conversation where you walk through your code and are asked to extend it live, so you must understand every line you submit.

It is also reasonable to ask how the take-home will be evaluated and whether it is paid or time-boxed. Companies that ask for 10 or more unpaid hours are signaling something about how they value candidates' time, and you may decline politely.

A resume review checklist

Before sending anything, read it as a stranger would:

  • Does the first third of the page show your best, most relevant work?
  • Does every bullet have a verb and, where honest, a number?
  • Are links live and pointing to something worth seeing?
  • Is it free of typos? Read it aloud, and have a friend read it too.
  • Could you speak about every line for two minutes?
  • Is the file name sensible (jane-doe-resume.pdf) and the format PDF unless asked otherwise?

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which resume bullet is strongest?

    It starts with an action, explains how, and states a measurable result. The others describe duties without impact.
  2. 2. You have 12 hours of free time, but the take-home says 'about three hours'. What is the best approach?

    A focused, tested, well-explained solution at the stated scope shows judgment. Overshooting can look like poor boundaries, and the README shows you know what is missing.
  3. 3. Why is listing every technology you have ever touched in your skills section risky?

    Anything on your resume is fair game for questions. List what you could discuss comfortably for several minutes.
  4. 4. Which portfolio project is likely to impress most?

    A real problem, a finished and demonstrable result, and visible engineering practice make a project easy to evaluate and discuss.

Summary

  • Keep the resume to one clean page, in plain layout, with honest, discussable skills.
  • Write bullets as action, how and measurable result; never invent numbers.
  • Choose two or three real projects with demos, tests and a README that explains trade-offs.
  • For take-homes, clarify, respect the time limit, get a correct core first, test edges and document assumptions.
  • Be ready to explain every line of everything you submit.

Next: Salary Negotiation and Evaluating Offers.