Member Avatar for LevyDee

When creating a resume for a programming job, you want to include some source you have written right? I am updating my resume and have added 4 pages of source, is that to much? THanks

  • 3 Contributors
  • 2 Replies
  • 112 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by VernonDozier

Dani AI

Generated

— There are better ways to show your skills than pasting four pages of raw source into a resume. Both and touched on presentation and HR handling; below are concrete, recruiter-friendly steps that complement that discussion and make your work easy to review.

Pick 2–3 representative artifacts rather than a page dump: one clean, single-file example (under ~200 lines) that shows style and problem solving; one small project repo with a clear README.md, build/test commands and a few automated tests; and one one-page annotated excerpt that explains the problem, your approach, and a measurable outcome (performance, memory, complexity, bug reduction, etc.). Add a one-page reviewer guide that points to the exact files and line ranges to inspect and states what you personally authored.

Sanitize anything non-public: remove company names, credentials, proprietary data and exact customer logic. If subject to NDA, recreate a minimal reproducible example that illustrates the algorithm or pattern without leaking IP. Package artifacts so a non-technical screener can preview (single PDF summary) and a technical reviewer can dive deeper (repo with build instructions and sample input/output).

Practical checklist:

  • Keep examples small and focused; emphasize clarity and tests.
  • Include How to run commands and expected outputs.
  • Note your contribution (lines, modules, features) and dates.
  • Prefer a short portfolio summary PDF plus a linked repo for full code.
  • Get a peer to confirm buildability and confidentiality.

These steps get reviewers quickly to the signal in your code and avoid the common trap of overwhelming them with uncurated source.

Recommended Answers

All 2 Replies

Member Avatar for Fbody

I don't think I would actually make them part of my resume, but you will want to submit them as an enclosure or attachment. Just make sure you some how direct the Personnel Manager's attention to the attachment/enclosure. This would generally be accomplished in your resume's cover letter.

Generally, the amount of code you submit would be indicated in an employer's solicitation for applicants.

Edited by Fbody because: n/a
Member Avatar for VernonDozier

I'd say don't include it unless they ask for it. They may have a very specific format of how they want it. Follow that format to the letter if it's provided. Otherwise, if they ask for a resume and a cover letter, just give them that. An attachment might not be the end of the world, but it may also get lost in the shuffle, particularly if it's an unsolicited resume to the HR department.

It doesn't hurt to add a line like:

Please see for examples of my code.

to your cover letter. But putting actual code samples in the actual resume would be a definite mistake.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.