Earlier quoted context omitted.
I've wondered about that myself. I wanted to stay, I liked it there. But it's like many relationships in life, if both parties don't want it, it won't pan out. Edit: I also had to take time off for studies and I suspect they really wanted all-hands-on-deck.
Darcy also goes to school although: "By day I attend the University of Western Australia"
Hiring Developers: You're Doing It Wrong
201–210 of 230 posts
Re: Hiring Developers: You're Doing It Wrong
#202Earlier quoted context omitted.
I've wondered about that myself. I wanted to stay, I liked it there. But it's like many relationships in life, if both parties don't want it, it won't pan out. Edit: I also had to take time off for studies and I suspect they really wanted all-hands-on-deck.
Darcy also goes to school although: "By day I attend the University of Western Australia"
Re: Hiring Developers: You're Doing It Wrong
#203Earlier quoted context omitted.
Wow here in Australia we get HUNDREDS of people lining up to interview for every job we advertise.
This is the same thing I've found, in Brisbane. People apply for jobs without skills, without hobbies involving development, without experience and without even looking at the website. I simply don't understand it... Are they hoping to get employed to twiddle their thumbs? Do they think they can pick it up on the fly?
Re: Hiring Developers: You're Doing It Wrong
#204Earlier quoted context omitted.
Again, I wonder what technology areas. Having looked, off and on, for C++ contract positions, I never see anything that high, in the SF area or elsewhere. Of course, my typical search involves Dice and Craigslist. Perhaps there's a better method of finding lucrative contracts.
As someone who has done this for 5+ years now (before that 10 years at various large / medium corps. and startups), I'd advise you that you won't find good opportunities via Dice and Craigslist. Nearly all of my contracts have come from references / networking (i.e. people I worked with once who hire me back as a consultant to build something / solve a problem). You're just looking in the wrong place.
I don't know, I don't really consider it "normal" or "market rate" if there isn't an open market for it.
I appreciate your wisdom, though, don't get me wrong. It just makes me question the typical advice espoused by people.
Re: Hiring Developers: You're Doing It Wrong
#205Earlier quoted context omitted.
That's kind of like asking why students choose to go to harder/more hostile universities.
You go to a challenging university because you want to take advantage of their knowledge, to the extent that you're willing to pay them for it. An employer wants to take advantage of your knowledge, to the extent that they're willing to pay you for it. The situations aren't comparable. I agree that three month contracts should be compensated at contractor wages rather than employee wages, unless the company is also p…
If you work at an excellent company, you can learn much, much more than you do at an average job, and you'll likely make connections with better people. Working with excellent people at a job has many of the same benefits as studying with many excellent people at a university. It's one of the biggest reasons to go to an elite school, and one of the biggest reasons to work at a very selective job.
If it's a great company, I think it's worth giving up some of those things for the chance to work there. If you can show them that you're much better than average, they'd be stupid not to bring you on full time. It's mainly risky if you don't think you can demonstrate that.
Re: Hiring Developers: You're Doing It Wrong
#206Re: Hiring Developers: You're Doing It Wrong
#207Re: Hiring Developers: You're Doing It Wrong
#208That way your work of looking into the code samples will be minimized. Even better, you'll get an idea of how well a coworker with a similar skillset can cope with that code. You can also judge how well people are at dealing with code from their coworkers and don't have to come up with examples yourself.
It does sound pretty good, no?
Re: Hiring Developers: You're Doing It Wrong
#209I have to disagree about the uselessness of a technical interview. I'm 100% with RethinkDB that any competent programmer should be able to figure out how to reverse a singly-linked list in some reasonable time. ( http://www.rethinkdb.com/blog/2010/06/will-the-real-programm... ). " Some were shooting their pre-canned answers at me with unreasonable speed." This should not be possible for all questions in a technical i…
I had the initial phone interview with RethinkDB and they were asking me questions about what is a B tree and how to use them to implement a filesystem/database, what is the pros and cons of structure A vs. structure B, etc.
I understand wanting the best of the best, people who have implemented filesystems before, etc., but I think it's pretty unrealistic to expect someone three years out of college who has not been working in the same area of specialization to just know this stuff off the top of his head.
Wouldn't it be much more realistic to basically give someone the Wikipedia entry for various data structures, tell them something about the data and workflows, and then ask which structure(s) they would use and why?
After that interview, I was sure I wasn't getting the job, but I wasn't very upset. They seemed to have unreasonably high expectations, and that's not exactly the most healthy work environment.
Re: Hiring Developers: You're Doing It Wrong
#210Few words about one startup-like company(based in Kiev, Ukraine) I have been working for 1 year as developer. It was focusing on .NET Enterprise apps. Their interview approach: - 1st day: tech-interview via phone(0.5-1hr); - 2nd day: (companies office) simple technical tests(choose-right-answer on paper), short technical interview(technology basics, fizz-buzz tasks, sql-tasks, usually join/group-by, having-based), coding-task on laptop(the most significant and essential(for evaluating developer) part of whole interviewing process write application for calculating bowling scores, Console app or GUI application - no matter, for candidates choice, time-bounds - for candidates choice; rules were provided and explained to each candidate + full access to internet resources + possibility to ask interviewer == real working environment); - 3rd day: final technical interview(patterns, OOP, code-design, etc.), general interview with CEO;
When I came to it, there were 3 devs(including me). The next(after me) developer were hired after ~60 interviewed fellows. Yeah, the total interview time is tend to be long and hard, as for candidate such as for company, BUT in such way were established the best TEAM I had honor to work in.
Thanks for attention:) Cheers Aleksey