January 10, 201115 yr Hi all, Graduating this year and was looking to see if anyone had any advice for things such as essential skills and nice-to-know skills for PHP developer interviews. Also, I know we mainly use PHP for forms and database linkage and scraping etc. but what other uses should I be able to demonstrate. Appreciate any advice! Chris
January 10, 201115 yr 1 - Consider becoming Zend Certified - http://shop.zend.com/en/php-certification.html (it probably holds more weight than a degree) 2 - If I was hiring a PHP developer I'd expect them to know pretty much everything about the language, not just how to do a few things with it. I would also probably be looking for extra things like TDD, debugging/profiling knowledge, use of version control, experience with agile development methods. Edit: If it was a junior position, I wouldn't expect any of the above, probably just a good base understanding of computer science and some practical examples of things they've done with PHP. Edited January 10, 201115 yr by Jock
January 10, 201115 yr Author 1 - Consider becoming Zend Certified - http://shop.zend.com/en/php-certification.html (it probably holds more weight than a degree) 2 - If I was hiring a PHP developer I'd expect them to know pretty much everything about the language, not just how to do a few things with it. I would also probably be looking for extra things like TDD, debugging/profiling knowledge, use of version control, experience with agile development methods. Edit: If it was a junior position, I wouldn't expect any of the above, probably just a good base understanding of computer science and some practical examples of things they've done with PHP. Cheers Jock. Anything else to be able to demonstrate on top of forms, scraping and database linking?
January 10, 201115 yr 1 - Consider becoming Zend Certified - http://shop.zend.com/en/php-certification.html (it probably holds more weight than a degree) 2 - If I was hiring a PHP developer I'd expect them to know pretty much everything about the language, not just how to do a few things with it. I would also probably be looking for extra things like TDD, debugging/profiling knowledge, use of version control, experience with agile development methods. Edit: If it was a junior position, I wouldn't expect any of the above, probably just a good base understanding of computer science and some practical examples of things they've done with PHP. This is good advice
January 10, 201115 yr I'd consider sessions/security to be and important skill as well. Personally I'd think about writing a wee demo site that you can log into on your interview thats got some examples of your work on it, maybe throw in some AJAX and stuff. Half the nuggets that show up to developer jobs are just people who've used joomla and think they're a developer, so if you've got something you can demonstrate working that you made from scratch its going to impress them. My 2nd developer job I brought in a huge folder of class file print outs and the guy doing the interview took them to show the lead developer, they went into a room for like 15 mins then came out and offered me the job on the spot shame I quit after 6 weeks.
January 10, 201115 yr I agree with Jock (an increasingly frequent event...) although I'd remove the need for certain topics - bitwise operations for example. Personally, I'd be looking for someone with some good understanding of design patterns and associated implications (i.e. Dependency Injection, MVC), a competent degree of knowledge in *nix, good understanding of RDBMS - and a better understanding of how ORM features work in relation to Relational Theory (i.e. the implications of Active Record when using libs like Doctrine/Propel). More importantly than all of this - I'd want someone that ENJOYED coding! Plenty of devs out there that just do it for the cash...
January 10, 201115 yr Author Jock, can work sessions ok and will need to brush up on security outside of timeouts, MD5 and input sanitising. sunwukung, did a software architecture class so pretty clued up on design patterns. Will have to brush up on the rest of the stuff you mentioned. My *nix experience is pretty limited so I feel quite week in that area.
January 17, 201115 yr I use doctrine every day, but I wouldn't say its important to know unless the company was using it. However knowledge of what ORM's do, how they work, how you can benefit from them, etc would be very useful. Basically any Active Record Pattern knowledge would be beneficial IMO over someone who didn't know anything about it.
January 18, 201115 yr Just remember you are Developer first. PHP will be just one of many languages that you will probably ending up learning as time goes on (you probably have a bit of HTML, Javascript, CSS already), yes you will specialise, but that should be on top of being a general developer, not instead of. At a junior level I would put emphasis on learning skills (research (book, google, coworkers), team work, evaluation/experimentation of different ideas) and a general understanding (Im not talking experience or expertise, just ability to briefly explain most) of software (http://en.wikipedia.org/wiki/Software_engineering#Sub-disciplines) and web development (Clientside, serverside, database, graphic/web design, copyrighting, accessibility, usability) practices and principles and a bit of business understanding (project management, QA, support). Bonus points for examples using specific technologies asked for. Oh and finally I like to see a little bit of evidence of ability to communicate skills with non-technical colleges and clients. Cheers, Nick
January 18, 201115 yr How important would you say something like the doctrine ORM is - http://www.doctrine-project.org/projects/orm ? When going through some CodeIgniter stuff there is a huge tutorial that uses this. It's blowing me mind I wouldn't sweat it re:ORM - although Doctrine is arguably the best ORM for PHP. ORM is a bit of a coding minefield - and there are some strong feelings surrounding the concept of ORM. In general - an ORM is good for those instances when there is a general 1:1 mapping between a Domain Entity and a DB Table (i.e. User class : users table) - but can rapidly fall apart for anything more complex than a 2 or 3 table join. Moreover, ORM's can require a "de-normalised" DB structure to allow for OOP inheritance. There comes a point when the cost of using an ORM outweighs the benefits. There is an analagous concept - DBAL (Database Abstraction Layer) - that has perhaps more practical implications. Ultimately, a DBAL is an OOP wrapper for your most common DB routines (i.e. selectById, selectWhere). Personally, I prefer DBAL to ORM. I think it's a wierd tradeoff to corrupt your data structure and learn a code based non-optimal version of SQL when the whole chuffing thing is meant to hide all that away for you. DBAL just tidies away some of the more tedious details.
Create an account or sign in to comment