Senior Backend Code Auditor (PHP / BD Architecture) – Spec Enforcement Role We are looking for a senior backend engineer to audit and enforce strict specification compliance inside a Brilliant Directories (BD) environment. This is not a development role. This is a backend architecture and code audit role focused on preventing shortcuts, hardcoding, and technical debt during milestone implementation. Context We are building a data-driven platform where: Backend database fields must match a predefined spreadsheet spec 1:1 No hardcoded HTML values are allowed All containers must be dynamic and API-ready Visual implementation must not bypass backend structure No autonomous sequencing decisions are allowed The development spec is explicit and detailed. Your role is to ensure it is followed exactly. Your Responsibility For each milestone delivered by the BD developer, you will: Review backend field creation in BD Form Manager Verify database variable naming matches spec exactly Detect hardcoded values inside Custom HTML blocks Check that all rendered values use BD dynamic placeholders (e.g. %%%variable_name%%%) Validate conditional logic (hide-if-empty, etc.) Identify any architectural shortcuts that create future technical debt Deliver structured findings in clear written form You do not implement features. You do not redesign architecture. You do not reinterpret specifications. You audit and enforce. Important We are not looking for: Someone who wants to “improve” the architecture Someone who rethinks specs Someone who introduces their own sequencing logic Someone who prefers creative autonomy over disciplined execution We are looking for: A senior engineer who respects defined architecture Someone who follows spec 100% Someone who flags deviations clearly and objectively Someone comfortable working inside legacy PHP systems Required Skills Strong PHP backend knowledge MySQL database structure understanding Experience reviewing legacy systems Ability to detect hardcoded logic inside templates Architecture and technical debt awareness Brilliant Directories experience is a plus, but not required if backend fundamentals are strong. Engagement Structure Small project 1–3 months 5–8 hours per week Milestone-based audits To Apply Please answer: Have you ever rejected a developer’s implementation because it deviated from spec? Briefly explain. How do you detect hidden technical debt inside template-based PHP systems? Do you prefer enforcing defined architecture, or designing your own? We are not looking for the cheapest option. We are looking for discipline and structural thinking. If you read this carefully and feel aligned with this approach, apply. If you prefer creative autonomy over strict spec enforcement, this is not the right role.