Go to any job posting sites and it's easy to find a lot of job postings, I like to keep my personal / professional real life separate from my online activities - so I am not posting anything that points back at who I am.
I am not everyone's baby sitter to tell them what they need to know. I reply to everyone I interviewed, even when they don't succeed.
You have no evidence to back up "few and far between" - like I said, just google dev job in Toronto, or go to LinkedIn and search - there are TONS of postings.
and no, we are by no mean desperate to hire. I would rather not make hire than making desperate hiring decisions, I am not hiring just any code monkey off the street.
Like I said - you are competing against new grad with 2+ years of experience. The onus is on you to be competitive.flafson wrote: ↑Not trying to be dramatic, just the reality. Employers 95% of the time don't want to give any kind of chance without 1-2 years experience in the specific job they want to hire for. For new grads (like myself) it becomes very difficult to find someone who will be willing to take a chance on me. I have experience doing IT but nothing programming related and so far nobody is willing to give me a chance for entry level positions. Seems (to me at least) that the only positions that someone will hire me are for intern jobs.
Things are actually a lot more open these days, you have a lot more avenues to showcase your skills - app store are wide open, anybody can have a website, you can volunteer on non-profit projects (I did that)
it is much better when you have an experience, it's as simple as that. It's not a claim, it's a fact.
Do you even know how we screen? What made you say my screening criteria discard talents?
I just mentioned to you I only had ~15 applicants to the position ... where are all these people who are qualified but looking for job that you kept mentioning?
Again - while you, Mark77, come up with this random assertions and numbers - there are people like myself who are actually going through it and experiencing it in real life.
Where did I ever say I tested Java syntax over the phone?
This is what I said for reference:
People make mistakes writing code on the white board, I don't care about the small details.
But if you don't even know what are primitive variables, or what an object is, there's an issue. (just an example, not my actual questions)
And to be honest, the job description clearly mention Java as our programming language, if you spend 5-10 minutes googling "Java interview questions", you can ace phone interviews easily. There's only so much you can ask on the phone.
glut? 15 applicants are "glut" ? ... lol.
It's simple ...
if your resume don't get response, your resume is not good enough
if your interview didn't get through, means your resume is good enough to get employer interested, but your interview skills are lacking (or your technical skills are lacking)
What I am looking for may not be what the next employer looking for ... so there's no point for me to tell them specific things that they don't have that made me not screen them, they could very well have other skills that are not applicable to my position but another employer will be looking for.
When the job posting is clearly about web/mobile software development, and you only have hardware experience - you are not a fit, it's dead simple.