Language allowed: PHP only. input: [1,3,0,1,0,5,8,20,5,3,0,4] output:[0,0,0,1,3,1,5,8,20,5,3,4]
Ingeniero De Software Php Interview Questions
4,367 ingeniero de software php interview questions shared by candidates
1. Simple PHP coding question to count no of occurrences of a particular word in para 2. Fundamental questions about PHP and CI 3. Question about MYSQL and joins 4. Question to create a service that can trigger at a scheduled time and send report to multiple email ids.
First part of the tech interview we discussed my implementation of a task from stage 2. Then I've been asked about general php dev like: * What will be you actions if your commit was declined by your colleague? * What have you used for tests? * What is Domain Driven Design? * What architectural patterns do you know?
What are some projects you're most proud of?
Hablar acerca de experiencias laborales
The questions were easy. All the questions related to db, php.
The technical interview panel was really rude. If someone gave you 48 hours of tasks with lots of (nice to have) and you still manage to submit them with all that is nice to have, then at least someone should acknowledge that they did it on time, but instead of that, they were rude. Everyone is learning here, no matter if you are a senior developer. Still, we're learning, and they are trying to prove to you that you did this, which can be done in that way. Of course, we took that as a task, not a final product ready for production, and even every developer uses their skills, which is different from your thinking, but instead of that, they criticize the fact that we didn't do it the way "the particular" person wanted; we're human beings, not robots, and we would do something that we thought was the right thing to do, and then they rejected it with lame reason. I am just trying to tell these people that if someone has experience of 8 to 10 years, it means they have been working all their life, which means they are ready to work, learn, and grow, so instead of giving tasks first, please have a technical round first so that we won't waste our time on 48 hours of tasks if you don't like the way the candidates are! Please don't waste someone's precious time and first have a technical round, because in that survey you will find out how the developer is! thanks
The technical questions primarily focused on Symfony and Domain-Driven Design implementations in PHP, with a particular emphasis on SOLID principles. Specifically, topics included: - Symfony: - Roles of Services, Containers, Kernel, and Entities - Exploration of other Bundles like API authentication and authorization - Doctrine related questions - Domain-Driven Architecture (in relation to implementation with Doctrine in Symfony): - Architectural concepts such as Layered Architecture, MVC, MVVC, Hexagonal (not microservice), and CQRS - Entities and associated considerations like validation - Aggregates, Factories, and Repositories (including Transaction management) - Modules and Value Objects, with potential deep dives into aspects like Side-Effect-Free behavior, Immutability, and Persisting Value Objects Importantly, there were no questions related to SQL, CI/CD, Orchestration tools, APIs, or microservices topics, rather just more than 1 hour focused on Symfony and Domain-Driven Design.
Meeting was canceled without notice.
Technical questions related to php mysql.
Viewing 2251 - 2260 interview questions