have been developing software program and codes for 4 years since graduation. Many have labelled this as a software developer instead of as a software engineer.
Wondering if On the market survey would a graduate degree would hold a stronger lead over a software developer or would the solving of technical questions at the interviewing stage hold a stronger stance.
what are the main sources of conflicts among developers on the usage of open source code or microsoft source code although both meet the means of development and software functionality at the end of the project deliveries.
Another point to note is that the interview is not a one way street. When possible, look for a new job while you still have one. This way you are not in a desperate situtation.
With that said, there are times when you should cut your losses, and end the interview yourself.
On one occasion, I had a technical interview for 3 hours. It was one of those situations where you were treated badly. The interviewer was an hour and a half late for the interview. I sat near the reception desk, waiting patiently. The receptionist went out to lunch, and returned stunned to still see me there. Finally, the interviewer greeted me.
It took him another half hour to assemble a team for the interview. Nothing was planned. (that showed me a lot about the situation there)
Two hours after my scheduled interview, a team of developers fired questions at me for 3 straight hours. I answered every one of them. As the interview progressed, I realized they were using a new tool but using an obsolete paradigm. I was losing interest in this position as time went on.
At the end of the interview, I knew I could definitely help the team, but really didnt want to be in this situation. I was stunned to be told that they also have a computerized quiz that needed to be taken for the position. They said the quiz would take 1-2 hours.
I said "Thank you for your time, but I don't think this would be a good fit." I didn't end it earlier because I didn't want to act in an unprofessional manner.
Don't settle for a situation that will not make you happy.
You make an excellent point here! In terms of a two way street, you should also spend time interviewing your interviewers. You need to make sure that the position and the company are the right match for your career goals. If there are continuous issues being thrown up during the interview - poor organization, people are rude or late, the problems they are solving aren't interesting etc - then you need to make the decision not to work at that particular company. Too many folks have been burned by jumping into a situation with a "top employer" only to be disillusioned a few weeks or months later by the culture and work environment.
Hi, I must say I know exactly how you felt. I once had an interview which due to an excellent organisation took 5h-6h to finish... I felt like I was there the whole day...
I would really advice anyone who has a choose in this matter to leave immediately after you notice that there is an extreme lack of organisation because for me that is certainly not a workable environment.
Also regarding the quiz, I must say I like this approach but what is even better is if they start off with a quiz which proceeds to an interview. I once was invited to complete a java programming test before having a first contact with a company. That was a great approach and by passing the test they eliminated the need of their developers wasting time by asking you questions for ~3h.