Laravel Developer for Periodic Code Review & Technical Audit

I am developing a new web application called Happenstance, a social matching discovery platform currently being built as a Laravel application. Much of the development work is being completed with the assistance of OpenAI Codex. I am not a software developer myself, so I am looking for an experienced Laravel developer to act as an independent technical reviewer throughout the development process. The goal is not to replace the current development workflow or rebuild the application. I want an experienced human developer to periodically review the codebase and make sure the application is being built using sound engineering practices and that we are not introducing architectural, security, performance, or maintainability problems that could become difficult or expensive to correct later. Technology Stack The application currently uses: • Laravel • PHP • Blade • PostgreSQL • JavaScript • Vite • Git / GitHub The project includes user registration and authentication, provider profiles, administrative moderation, notifications, search and filtering, image uploads and processing, verification workflows, and other application-specific functionality. What I Need I am looking for a senior developer who can periodically review the GitHub repository as the project develops. Your role would primarily be to evaluate the quality of the implementation rather than write new product features. Areas I would like reviewed include: • Overall application architecture • Laravel best practices • Database schema and migrations • Eloquent models and relationships • Controllers, services, actions, and business logic • Authentication and authorization • Security vulnerabilities • Input validation • File and image upload security • Data privacy and access controls • Admin functionality • Background jobs and notifications • Error handling • Query efficiency and database performance • Front-end/backend separation where relevant • Automated tests and test coverage • Dependency management • Code organization and maintainability • Deployment-related risks • Technical debt • Potential scaling problems • Anything that appears unnecessarily complicated, fragile, or likely to cause future problems I am particularly interested in identifying situations where code may appear to work correctly today but is being implemented in a way that could create problems as the application grows. How the Review Would Work This would be an ongoing but relatively lightweight engagement. At various milestones, I would provide you with access to the current GitHub repository and ask you to review the changes that have been made since the previous review. I would expect each review to include: 1. ••Critical issues•• Security vulnerabilities, data-loss risks, authorization problems, serious architectural issues, or anything that should be corrected immediately. 2. ••Important improvements•• Code that works but should be redesigned or refactored before additional functionality is built on top of it. 3. ••Technical debt•• Issues that are acceptable for an MVP but should be documented and addressed later. 4. ••Minor improvements•• Code quality, organization, conventions, or maintainability suggestions that are useful but not urgent. 5. ••Overall assessment•• A short explanation of whether you believe the project remains technically healthy and whether there are any areas I should be particularly concerned about. Where possible, I would like findings to reference the relevant files, classes, migrations, or lines of code so that I can give the recommendations back to Codex to implement. You would not necessarily be expected to make the changes yourself. Important Part of the Role I am specifically looking for someone willing to question the implementation rather than simply confirm that the application works. For example, I want you to identify things such as: • A feature that works but has been implemented using the wrong abstraction • Business logic being placed in the wrong part of the application • Database decisions that could become limiting later • Authorization checks that are incomplete • Tests that give a false sense of security • Overengineering • Underengineering • Laravel functionality being recreated unnecessarily • AI-generated code that is technically valid but unnecessarily complex • Security assumptions that should not be trusted • Architecture that will make future development harder The purpose of the review is to provide an independent engineering perspective. All B00sted proposals will be ignored as it's a waste of connnects and also I want to see who is actually reading this job description. Also all agency proposals will be ignored. Ideal Candidate You should have strong professional experience with: • Laravel • Modern PHP • PostgreSQL or relational database design • Application security • Git and GitHub • Automated testing • Production web applications Experience reviewing or inheriting existing Laravel applications would be particularly valuable. Experience with AI-assisted software development is also useful. I am interested in someone who understands both the strengths and weaknesses of AI-generated code and knows what deserves additional human scrutiny. Communication You must be able to explain technical problems clearly to a non-developer. I do not need lengthy academic explanations. I need practical guidance such as: • What is wrong • Why it matters • How serious it is • What should be changed • Whether it needs to be fixed now or can wait I am comfortable discussing technical concepts, but I need someone who can translate engineering decisions into understandable risks and recommendations. Engagement I envision this initially as a paid code audit followed by periodic reviews as development progresses. This could potentially become a long-term relationship where you review the project at major development milestones. When applying, please include: • Your Laravel experience • Examples of applications or codebases you have reviewed or maintained • Your experience with application security • Whether you have worked with AI-generated or AI-assisted code • Your preferred approach to conducting a code review • Your hourly rate or proposed price for an initial repository audit