Hi, As a Web Developer what where the question asked in your interview? please share to us how was your interview, what clothes did you wear? How many mins/hours did it take? and anything that you could share regarding your interview. Thanks!
Well, I never appeared for an interview, but I have interviewed candidates on 4 or 5 occasions for their PHP-MySQL skills. Since I never appeared for an interview myself, I can't tell you about some things from a candidate's perspective, but I can tell what *I want*(technicals) from a developer. 1. I ask basic questions. 2. I don't pay attention to clothes until the candidate comes in torn, soiled and foul-smelling rags 3. I don't ask for how many years of experience he has.(I believe his coding will be a more reliable indicator) Once this is done, and if I feel that the guy is good enough, then we proceed to the coding test. Here, we give them an exercise to code. In the past, I have used the following exercises: 1. Simple address book for phone contacts. 2. A personal diary. 3. A minimal blog system. 4. Flexible pagination function or a class. 5. Regular expressions Many of the freshers tend to focus on the end-result alone, rather than focusing on the code quality too. In the code, I look at the following: 1. How the user inputs are being handled? 2. If a piece of input is going to affect DB transactions, its sufficiently sanitized? 3. Can the candidate identify sources of errors due or invalid input? If yes, does he write fail-safe code? 4. Does he know effectiveness of various functions? 6. Does he know about the PHP.ini file? 7. Does he comment the code enough so that when the next guy takes over, he doesn't go nuts! 8. New concepts such as OOP, modifying open source such as building plugins, etc! Many more minor details are there! The first round(viva-voce) taken usually 10-15 mins of no-non sense, to-the-point questions. If they survive, the round 2 takes somewhere 60 mins for the coding.[Ofcourse, here I don't go into others details such as images, CSS, etc. I expect a simple old fashioned HTML page.] And anyways, don't concentrate much on your looks and clothes, we are not interested in them if cannot code. You see, we want developers, not models I am accompanied by 1 or 2 people, and we mutually cover up areas left by one another.[Also, how well your interviewer is depends upon which organization you are applying. I have seem some micro-companies employing blindly ]
haha @rohan_shenoy wow, I really can't pass your test. Can you give me some tips where i could learn PHP? and where did you learn. I just have a little knowledge on PHP, just editing Joomla and wordpress Thanks for the tips!
Good questions When I interviewed for my past web development positions, the process was pretty much the same. They'd ask about my resume, just to clarify the skills I had, and they either requested a small portfolio, or just asked me to demo a few things I had done. Questions have ranged from PHP and Perl to system administration to networking. Most have been at a basic level. Some interviews didn't even ask questions, and instead relied on the demos of the stuff I had done. I have a theory that if you are being interviewed for any kind of programming job, the better your dress, the worse are your chances for getting hired. Jeans, tennis shoes, and a long sleeved buttoned shirt--but don't tuck it in! That will blow your chances.
i was once given a kind of 'golden rule' of interviews - do your homework. in particular, for younger dot-com-ish setups, dress codes may be surplus or just smart casual so appearing at an interview dressed up in a suit will place you in a very uneasy situation (vice versa also applies--if you are getting through some preliminary rounds with human resources / management in a corporate environment, you can't afford to look slacking either). visit their offcies /building the day before the interview or look outside and observe what your colleagues are like, it gives you a great insight on the kind of tone the interview and job will take later on. but remember - bottom line is, your coding skills is what matters with a very high relevance. you also need to be able to look at a tree but also see the forest - coding to the big picture. in the business sense, this can mean convincing the employer you can work: - fast - careful - to standards - well documented - using the right tools for the job - do not dwell, sometimes you need do enough to satisfy requirements / customers and move on to other tasks - work in a scalable way that won't cause problems in the future - ability to work alone... - ... and as a part of a team - have initiative and drive to excel you do that, and you are in. curveballs: questions like, what are your strengths and weaknesses... be prepared as they are meant to put you in a bit of a tight spot. in the context of progammers, a good answer for weaknesses (DO NOT BE PERFECT): can be a little impatient with people that are not technical at times (it is expected of most techies so that wont be a surprise--you are admitting it, which is a good, honest thing to do). obviously, do not do so if you are applying for a position that involves interfacing with your clients or as a project lead, etc. another 'negative' i have used in the past is "sometimes i tend to get carried away in my attempts to always produce structured and compliant code", which--really--is _also_ a _good_ thing perceived as 'great, just need to manage his priorities and time slightly carefully'. etc etc... anyway, good luck once again. remember - do not say yes to a job you have applied for just because they said yes - you also need to make sure you are joining the right company. make sure YOU can ask the right questions about who they are, what they do, how they stand financially and how they are growing, what your possible career and development paths may look like there, etc. they wont hold this against you (if with the right tone) - it shows an interest and displays desire to do a long term commitment.
they went and asked questions in related to my cv , sites by site what i did what experience i learned ... 100% cv related....
I've heard that for some really intensive job interviews they start asking algorithmic and problem solving questions. I think this is mostly to discover how the candidate solves problems. I'd assume that employers would want to know a lot about your previous experience (where you worked/studied, what you've learned).
If you are going for a job with a large corporate, I recommend that you show an understanding of DDA compliance and respect for the W3C.