I'd start with asking "what do you need done?". Focus on the client rather than yourself. More than anything else potential clients and employers want to know that you understand their goals, are enthusiastic about helping them reach them, and will do what it takes to make it happen.

Once you know what they want, you will also be in a much better position to reassure the potential client that you can contribute to the project. If this is a coding project, you can write a targeted bit of code that shows you have the skills they are concerned about and can apply them to some small part of their problem. That is much easier than a demo website or CPAN module aimed at any-potential-customer-in-the-whole-wide-world.

You will also be in a much better position to decide if a code sample is even needed. For example, if you want a design or project management role on your next project, the client will most likely be far more concerned about how you scope a project. They will want to know whether or not you can identify the time and resources needed to complete it and make a cogent case to support your conclusions. If you are looking for a job as technical lead, explaining how you approach coding standards and a sample that illustrates you can practice what you preach may be more important than showing off the cool stuff you did on your last project. If the primary concern is algorithm development, your problem solving skills can be demonstrated in many ways.

Finally, these days development is often a team sport. The way you demonstrate your ability to communicate and work with others during the interview may be far more important to the hiring decision than any code sample you could leave behind, no matter how amazing.

Best, beth

In reply to Re: How do you show off your work to prospective clients? by ELISHEVA
in thread How do you show off your work to prospective clients? by punch_card_don

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.