Timeline for As a job seeker, is it worth applying for jobs where they ask me to do some code in my own time, as opposed to conventional interviews?
Current License: CC BY-SA 3.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2016 at 16:38 | history | tweeted | twitter.com/StackWorkplace/status/734423263800102917 | ||
| May 7, 2016 at 16:23 | answer | added | eee | timeline score: 0 | |
| Dec 19, 2014 at 15:49 | comment | added | Dunk | @James:So the coding project did work for you. However, there is quite a lot to be said for 'cultural fit'. It isn't all about your technical skills. If your personality/style is going to cause friction on the team or your preferred methods don't match the company methods and there's an inkling that this could be an issue then it is better for all that you weren't hired. Low morale can kill a project just as much as low skill. | |
| Dec 17, 2014 at 17:47 | comment | added | James Adam | @Dunk, I've actually been told after an 'interview project': "Great job! You're hired! Oh, wait, the boss wants us to do an interview, don't worry it's just a formality." After the in-person interview, though, I was told I wasn't a 'cultural fit'. | |
| Jul 18, 2014 at 20:18 | comment | added | Eric J Fisher | @occulus in the US if people talk about people failing interviews outside the company they work for that edges dangerously close to defamation. (not that it doesn't happen, but if the person found out could be VERY costly to the offending party) | |
| Jul 18, 2014 at 12:13 | comment | added | occulus | "Fail fast with many short interviews" -- that approach might not be great for your self-esteem. You might also get a reputation in the industry for the guy who fails loads of interviews. | |
| Jul 18, 2014 at 4:05 | answer | added | Jakub | timeline score: -1 | |
| Jul 18, 2014 at 3:08 | review | Close votes | |||
| Jul 21, 2014 at 19:58 | |||||
| S Jul 18, 2014 at 2:42 | history | suggested | starsplusplus | CC BY-SA 3.0 |
made it clearer that the question is about what to do as a job seeker, not an interviewer, since I think some of the answers missed the point
|
| Jul 18, 2014 at 2:40 | review | Suggested edits | |||
| S Jul 18, 2014 at 2:42 | |||||
| Jul 18, 2014 at 2:29 | answer | added | starsplusplus | timeline score: 0 | |
| Jul 17, 2014 at 23:10 | answer | added | It'sPete | timeline score: 0 | |
| Jul 17, 2014 at 21:56 | comment | added | Dunk | I've only had 1 "coding project" interview. If you do it well then the interview can end up being just a formality, which happened to me. They already had an offer prepared before I even arrived at the interview. So if you are confident in your skills and are sure that they will reflect well then by all means the "coding project" interview is worth your effort. If you aren't too sure your work reflects well or aren't going to put in the effort to ensure it does then don't do it. You'll be judged by what you submit and if it isn't a fine example of your work then don't do it. | |
| Jul 17, 2014 at 14:33 | answer | added | Clair | timeline score: 12 | |
| Jul 17, 2014 at 14:23 | comment | added | Eric J Fisher | Coding projects are a decent enough way to interview for places offering a decent salary. You do need to be careful and do your homework though. There has been a recent trend it my area where people are having potential hires do actual work for the office (small several days to a week project) as part of their technical interview with no pay, and no intention of actually hiring. (IE a con for free labor) people are successfully taking these people to court, but it's still a growing trend, so just be aware and use your best judgment before investing your time. | |
| Jul 17, 2014 at 14:02 | answer | added | Stephan Branczyk | timeline score: 1 | |
| Jul 17, 2014 at 13:53 | answer | added | gnasher729 | timeline score: 7 | |
| Jul 17, 2014 at 13:53 | comment | added | raptortech97 | I don't know how many of these opportunities you expect to get offers from, but it seems obvious to me that it's worth it to spend a few days or a week on a project if it improves your quality of life at work or your salary by even just a bit. Of course, if financial difficulties mean you need to get a job immediately, that might be a different story. | |
| Jul 17, 2014 at 13:41 | answer | added | RetiredAssistant | timeline score: 3 | |
| Jul 17, 2014 at 13:10 | comment | added | Evgeny Goldin | My experience showed me companies practicing good test exercises tend to eventually have significantly more skilled software developers than companies practicing personal interviews only. The reason is simple - lot's of so-so developers can pass a personal interview but will fail in a simple test exercise or wouldn't even bother doing one. Which could be one of the goals, I assume - filter out those not willing to bother, not enjoying some extra coding. I always enjoyed having these test exercises and always learned a lot during the process, never questioned "should I" if exercise was good. | |
| Jul 17, 2014 at 12:37 | comment | added | Andrew Walters | I assume you'd be getting paid for a coding project at your standard rates? | |
| Jul 17, 2014 at 12:29 | answer | added | Tony | timeline score: 0 | |
| Jul 17, 2014 at 11:58 | comment | added | Shiraaz.M | @VietnhiPhuvan Not necessarily. In my country, I have experienced a couple of times where more highly compensated positions are met with less difficult interviews. Insurance and telecoms industries in my country have these qualities. | |
| Jul 17, 2014 at 11:57 | answer | added | Vietnhi Phuvan | timeline score: 1 | |
| Jul 17, 2014 at 11:48 | comment | added | Vietnhi Phuvan | What makes you think that coding projects and panel interviews are mutually exclusive? My best guess is that the more high;y compensated the position and the more senior the position, the more thorough the vetting is going to be. | |
| Jul 17, 2014 at 11:41 | answer | added | Joe Strazzere | timeline score: 6 | |
| Jul 17, 2014 at 11:29 | history | asked | Shiraaz.M | CC BY-SA 3.0 |