spec vs. samples?

  • Started
  • Last post
  • 27 Responses
  • ETM0

    That's BS. That could be anything from a day to a week or more work depending on numerous factors.
    Labour laws vary, but in any job around here, when you sign an employment contract there is almost always a 90 day probation period where you can be evaluated. No benefits, can be released without warning etc.

    They can have you do that 'project' as your first week's work. They see no promise, they can show you the door. Making you do anything that big for free is a con and I would be suspect of any place requiring this is you have a solid portfolio and references.

    I've seen interviews where they may take 15 mins of your time to solve a problem, ask you to do something in software or even write some code by hand. Fair enough, but that above is cray, IMO.

  • ETM0

    If you tell them to beat it, maybe you can consider letting us know what place this is... assuming if wouldn't harm you.

  • MrAbominable0

    i see the sense of what you guys are writing. my desperation is clouding my judgement A LOT. another version of me would tell me to run too. just wanted to make sure i wasn't overreacting.

    you're giving me good ideas about how to respond to this though.

    • do you need a contract?e-pill
    • you helped me with paperwork a long time ago. for which, i've been eternally grateful. thanks again btw!!!!MrAbominable
  • bulletfactory0

    For developers, we give them a code test which our engineers then evaluate and decide if we want to move forward. Is the code semantic? succinct? will it work? etc.

    For designers, I usually examine their portfolio, have them talk through their processes, discuss timelines, etc. One time I did have a designer lay out a webpage; however, I provided all images and content, and explained that I'd never use their work. I just wanted to see how fast they ideated (which I'm not convinced really showed me anything in the end - I wouldn't handle it that way again... I guess I was young when hiring my first team).

    In NYC, all jobs are "at will" meaning you can be fired or leave at any time, for any reason, without notice. The fact they are asking for so much work, being so specific and want this so fast raises a shit-ton of red flags.

    run.

  • MrAbominable0

    i didn't say upstream but it is for a job in NYC.

    the sample of their product co-branded with a big label screamed to me of their wanting to use it in a pitch; in opposition to just vetting me.

    thanks for shoring me up, all. i sent my nice "i don't do spec work" letter and doubled-down on the e-pill front with coming around and telling him that he could hire me in a couple of different ways to approach those interesting problems.

  • whatthefunk0

    I did this for a job once and the process was horrible - no direction, no copy, no campaign to go off of, no images, and no chance to discuss with the team. I made the designs and then they had the balls to ask for revisions while making comments that the designs "weren't what they were looking for". I responded by stating that I was no longer interested in the opportunity because if the team was this disorganized and bad at communicating a project like this I cannot imagine how difficult it would be to do it full time. I also reminded them that this test is a two way street, I got to see how they work and to be honest I'm glad that I did. It was for a 6 figure job and the company has since dissolved into the great void...

  • orrinward20

    With interviews for jobs that involve code I've usually had to do an example as part of the process. More than half the time it'd be directly for a part of their business. The times where I've been given a throwaway task I've actually felt like it's a waste of my time.

    The trouble with a portfolio is it doesn't show how you worked to a timeframe and whether you prioritise/organise well. I expect this is less of an issue with a long career in the industry but when I was jobhunting I was fresh out of Uni with only a year's placement under my belt. Everything in my folio outside of my placement work could have been awesome but taken me a year to produce.

    A 'code exam' helps show your efficiency and organisation skills. I usually enjoy them, unless I happen to be forced to work in some nonsense Visual Studio-esque application on a 'test machine' with 512MB RAM and an unresponsive keyboard.