What is the minimum...
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
WOW! I hate lengthy posts. I'll read it tomorrow... ;P
Maxwell Chen
-
WOW! I hate lengthy posts. I'll read it tomorrow... ;P
Maxwell Chen
I do to unless I know there is someone out there on the other end that wants a meaningful answer and in this case there is. :rose:
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
I do to unless I know there is someone out there on the other end that wants a meaningful answer and in this case there is. :rose:
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
There are some CPians who run their own companies, or who are top managers. Let's wait for their answers. :)
Maxwell Chen
-
There are some CPians who run their own companies, or who are top managers. Let's wait for their answers. :)
Maxwell Chen
:-D I'm self-employed and have been for 2+ years. I've been nothing but profitable since my inception and I'm debt free. I don't have employees but I have a rich network of contacts that I use on a regular basis to delegate work to that I'm to busy to personally handle. Having said this (which may sound like boasting, I don't want it to) like you I'm interested in hearing from those people as well. There are indeed some people here who have backgrounds steeped in a broad but deep set of experiences. Which is exactly why I posted my reply in the lounge instead of emailing the guy back directly. There are so many here who have so much more wisdom than I do. Why not get some insight from everyone rather than the narrow and limited view of just one? That's what I think anyway...:rose:
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
:-D I'm self-employed and have been for 2+ years. I've been nothing but profitable since my inception and I'm debt free. I don't have employees but I have a rich network of contacts that I use on a regular basis to delegate work to that I'm to busy to personally handle. Having said this (which may sound like boasting, I don't want it to) like you I'm interested in hearing from those people as well. There are indeed some people here who have backgrounds steeped in a broad but deep set of experiences. Which is exactly why I posted my reply in the lounge instead of emailing the guy back directly. There are so many here who have so much more wisdom than I do. Why not get some insight from everyone rather than the narrow and limited view of just one? That's what I think anyway...:rose:
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
I'm just feeling like a worm in your mind. :-D
Maxwell Chen
-
I'm just feeling like a worm in your mind. :-D
Maxwell Chen
Oh heck! Not at all. It's CP takes time to get to know all 2 million of us I mean at any given time there could be 5,000 to 20,000 of us here...:-D
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
I have read your answer and will refer to it based on my experience from 2 different situations. 1. Someone who's been out there recently looking for a job in web development and going through *some* job interviews. 2. Someone who's job was interviewing and evaluating a lot of candidates for different jobs in the field of medicine and teaching (worked with psychologists/professional consultants and performed all kinds of tests). What you said is true, but only in some cases. It depends on the company size and who performs the interview. In a small company it might just be the boss himself who usually doesn't understand the technical aspect of the work, and will rely more on your resume and official qualifications - he has no other way to evaluate you. He will ask mostly simple "technical" questions based on your experience ("did you work with this or that technology?"). In a bigger company it might be the head of the team/department you're applying to or someone from human resources - often, a combination of the two. The first will actually test you or ask strict professional questions, and the second will evaluate your work/social habbits and personality. Each of these people will look for different things in the interview. I think that the more qualified the person who interviews you, the better the chances you have getting past the official resume/diplomas. Usually, if the company you applied to is really professional - inviting you for an interview means your experience is enough to get the job (if you didn't lie on your resume). Then they'll test you other skills. Isaac Sasson "I hate it. Java sucks. And Java's generics suck harder. And in general, Java just sucks." - David Stone, The Lounge (May 1st 2006)
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
If you have to ask you need more experience :) Seriously, every place I have worked and/or interviewed was unique. There is just no way to know what positions might exist that you would fit without jumping into the market. Of course that statement could be complete garbage. :doh:
"What classes are you using ? You shouldn't call stuff if you have no idea what it does" Christian Graus in the C# forum led mike
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
It's all about getting a job done , and not BS'ing about your capacity (note: NOT capability) to finish it.
-
Oh heck! Not at all. It's CP takes time to get to know all 2 million of us I mean at any given time there could be 5,000 to 20,000 of us here...:-D
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
>> I'm just feeling like a worm in your mind. Oh it's the diffrence between your culture and mine. I'm not sure how to express it correctly in English. In my culture, when we say:
Person A is just like a roundworm in Person B's mind ("stomach" in Chinese word actually).it implies:The Person A can correctly surmise what Person B thinks.How do you English speakers express this concept? :-D
Maxwell Chen
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
...wordcount? :~ 1000!!!!! (I copyed it into word and ran word count, minus signitures its 1092 words) :eek: William Penington
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
Where do you get time to write such lengthy posts? ;P What's your typing Speed? Talking about typing speed, I think that would make a good post... What's your typing speed...... :laugh::laugh::laugh: --- With best regards, A Manchester United Fan The Genius of a true fool is that he can mess up a foolproof plan!
-
...wordcount? :~ 1000!!!!! (I copyed it into word and ran word count, minus signitures its 1092 words) :eek: William Penington
I think he and Marc Clifton runs a conspiracy :rolleyes:
-
Okay, someone who is a member here has emailed me asking what I think the minimum level of experience is that they should have before they go job hunting again. I've been stumped by this question for over a week now. I have finally realized that the answer to this question is so subjective that one answer won't be enough. Everyone's answer is going to be based up on their background, education, experience and philosophy on hiring. So I'm going to open this thread with my own answer. My answer will not be wrong, it will not be right and it's not open for discussion. If your answer is different from mine that's what I want so just post it. You don't have to change my opinion you just need to provide feedback for the person who will read it and it will thereby enrich their own information base and it may help them to land their next job of choice. Here goes... {ANSWER: From my perspective.} The minimum experience you should have before going to interview for your next programming job goes like this. There is no minimum it seems to me like every job I've ever interviewed for I didn't have all the experience they wanted (but I still got the job). Every person I've ever interviewed and recommended for hire didn't have all the experience to fill the position but they still got hired. So if I were to take these statements and expand them into an answer I'd say something like this. If you have all the experience a job requires you may not get it. You may not get it for several factors. You might be able to justify asking more money than the company intended to pay. The company may have wanted someone teachable that they could shape and mould. Whatever the reason having the round peg for a round hole requirements is very difficult to accomplish and it may not get you the job. In your situation you simply won't be that round peg anyway so let's move past that and talk about what attributes might in fact get you the next job you go looking for in software development. 1. The ability to answer technical questions is important. Having the accurate answer not nearly so. Even if you don't have the right answer explain you don't. Then say but if I were to approach that problem right now here's how I would go about solving it. Go into the steps you would take in discovering an answer. Why do I say this? Writing software is easy for problems you understand and have an answer for. You need a function that sums 5 parameters that's easy you can code that in no time. You need to write a virtual, memory resident database that refreshe
Hi Codefrog, The jobs I see on the Internet are almost all from recruiting agencies, and for those who started programming as a hobby, it will be hard to get an invitation for an interview. This because job agencies want some proof of your skills (education or job experience). I think the best advice to those who want a job as a programmer is to say that they should go back to school and get the proper education. When you have the right education or certification things will be much easier i think, even without much experience. :) With friendly greetings, Eric Goedhart Skype: eric-goedhart Deep in the fundamental heart of mind and Universe there is a reason. -Slartibartfast -- modified at 11:43 Saturday 6th May, 2006
-
Where do you get time to write such lengthy posts? ;P What's your typing Speed? Talking about typing speed, I think that would make a good post... What's your typing speed...... :laugh::laugh::laugh: --- With best regards, A Manchester United Fan The Genius of a true fool is that he can mess up a foolproof plan!
Over 100 WPM.:-O
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
>> I'm just feeling like a worm in your mind. Oh it's the diffrence between your culture and mine. I'm not sure how to express it correctly in English. In my culture, when we say:
Person A is just like a roundworm in Person B's mind ("stomach" in Chinese word actually).it implies:The Person A can correctly surmise what Person B thinks.How do you English speakers express this concept? :-D
Maxwell Chen
We call it 'getting into someone's head'. The image is similar.
Software Zen:
delete this; -
We call it 'getting into someone's head'. The image is similar.
Software Zen:
delete this; -
WOW! I hate lengthy posts. I'll read it tomorrow... ;P
Maxwell Chen
Maxwell Chen wrote:
WOW! I hate lengthy posts. I'll read it tomorrow...
WOW! will it be shorter then? ;P _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Over 100 WPM.:-O
The enemy's gate is down.:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog. The act of using CPhog alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
code-frog wrote:
Over 100 WPM.
Don't believe him folks!! he two-finger typed it over the last month... ;P _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)