I need an experienced Laravel engineer who can act as the project’s technical conscience while my core developers concentrate on implementation. Your main responsibility is to review every proposed change before it reaches production, ensuring it resolves 500 errors, Blade issues, and routing problems without introducing side-effects or deviating from our existing architecture. What I expect from you • Deeply inspect each pull request, confirm that the fix is minimal yet complete, and clearly explain why it works. • Monitor versioning and dependency drift to prevent future compatibility issues. • Identify risky patterns early, document them in plain English, and suggest lean, practical alternatives. • Coordinate with our PM and developers via Slack and GitHub to maintain a tight and constructive feedback loop. Acceptance criteria • Each reviewed ticket includes a concise approval note covering root cause, reasoning, and any residual risks. • No new 500 errors or routing regressions are introduced in the next release cycle. • All Blade updates remain consistent with our current component structure and naming conventions. Important constraints • This is strictly a review and validation role (no direct implementation unless explicitly approved) • No architecture changes • No refactoring unless justified and approved • No database changes • All recommendations must be explained before execution • Any out-of-scope issue must be reported, not fixed without approval I am not looking for someone to rewrite the application. The goal is to ensure each fix is stable, backward-compatible, and aligned with the current architecture. If your strength is validating solutions and safeguarding system stability, I’d like to hear from you.