I'm sharing my recent interview experience for the job description:
- Strong understanding of Object Oriented Programming
- Solid development experience in PHP, Laravel, Rest API, GIT
- Strong troubleshooting skills and Good experience of using source control systems.: TFS, GIT
- A natural communicator who can explain technical concepts in clear, plain English (both written and verbal)
- Should be able to explain at least one of his/her development assignments with reasoning; as to how it was designed, what approach were used and why?
So, here is how it went
explain me in brief about this xyz project you did
what's a persist cookie
how a php session works and why we use it?
suppose if we disable cookies in our browser, are we able to login?
explain the entire process of session implementation in your php project
Did you implement caching in your laravel project, how it works
What are facades
what's an abstract class
Difference between abstract class and interface
why do we use interface
Can you explain me the request lifecycle in laravel
what's polymorphism
explain method overloading and overriding with an example and their differences
what's ajax and explain synchronous and asynchronous requests
can we send a synchronous request in ajax
what's indexing in SQL
how indexing affects the select, insert and update queries
what's git stashing and how it works?
can we use multiple env files in a laravel project?
how does queue works in laravel and how do we implement it on server
To conclude, when you work full time on frameworks like Laravel. Your base skills kind of fades off like manually managing a session since laravel does a lot of scaffolding for you, so you almost forget about these things as they are not automatically being taken care of. However, we have to keep in mind about internal workings to such concepts.
For the cure, I might create one project using vanilla PHP. As it will brush up those concepts.
Hope, these short snippets would be helpful to you folks. Bye for now :)
Top comments (1)
Hahah, I wonder if any OOP interview has ever concluded without at least a single question on explaining one of these: Abstraction, Encapsulation, Inheritance, Polymorphism xddd