What Questions Should a PHP Developer Ask?

Why are we building this website?

It's important to understand why a website is being built. This will help you determine whether it's necessary, how it will be used, and who will use it. These questions can also help you define some of the key features of the site and its goals. The answers to these questions are a great way to start fleshing out an overarching vision for what this product is supposed to do, who it needs to serve, and how they'll use it.

• Why are we building this website?

• Who is our target audience?

• What are some key features of this site that users should know about?

What is the current code base like?

It's important to know how large a code base you are going to be working with, but also what kind of quality it has. Is the code well-tested? How often is it tested? What kind of testing does your team use: unit tests, functional tests, or both?

What about the coding style? Is there any documentation for the codebase? Are there standards in place that you need to adhere to when making changes (or is this team more "just do it" style)?

How will the database work?

• What type of database will be used?

• How will it be accessed?

• How will it be structured?

• What is the expected performance of the database, and how does it compare to other databases in use by your company or other companies?

• What is the expected performance of the application, and how does it compare to other applications that use this same database or similar ones (if available)?

• What is the expected performance of your website as a whole, including all pages that work with this particular app (if applicable)?

Who is going to be managing the backend?

You should also ask who will be managing the backend. If you’re working with an agency, they may have a dedicated team of developers who manage the servers and databases. But if you’re working with a small business, they may not have a dedicated server administrator or web developer on staff. That means that any questions about security vulnerabilities and performance issues will fall squarely on your shoulders as a PHP developer.

So, who is going to be managing the backend?

What resources are available?

What resources are available?

What is the budget? What are the deadlines? What is the timeline and scope of this project?

You may also want to ask: What is the expected outcome of this project? Or, what are its goals or purposes?

What are your expectations of me and my work?

The first question that you should ask a client is “What are your expectations of me and my work?” You need to know what their focus is: the developer, the product, or even something else entirely. It's important to understand what they expect from you because it'll give you an idea of how much stake they have in this project (and whether or not they're willing to sacrifice it).

In addition to understanding their expectations for yourself as a developer and where they see themselves fitting into the overall process, it will also help define how long they think things should take. This can be especially helpful if there are other factors like budget constraints or timelines attached with supporting this project.

What is this web application supposed to accomplish?

The first questions you should ask any prospective employer are about the application and how it will be used.

The more information you can get about the specifics of a project before starting on it, the better. You'll need to know:

• What are its main features?

• How will it be used? (How many people will use it at once? Do multiple users need access to different parts of the system or will they all use similar functions?)

• Who are its main users? Are they experienced web developers, or casual users who don't know anything about programming languages or servers but just want a website that works well on their browser?

• What are its goals/purposes/aims/objectives?

What has been done to date, and what needs to be completed?

You should ask the interviewer:

• What has been done to date, and what needs to be completed?

This question can help you understand a lot about your potential new employer. You'll learn how much time has already been invested in this project, which will let you know if it's a long term position or short term. If there is no documentation, it may indicate that there are communication problems between developers and management. In addition, you want to make sure that the current team is capable of completing their own tasks before jumping on board.

PHP developers should know exactly what they will be working with before they start a new project.

Before you start a new project, ask yourself some questions.

• What exactly am I going to be working with?

• What do I need to do?

• What will I be working with?