Fast verdict: “WordPress developer” covers different skills. Define whether the job is page building, theme work, plugin code, infrastructure or repair.
Classify the project
Document the current host, theme, plugins, PHP version, staging availability and critical integrations. Explain whether the engagement is a build, redesign, migration, speed project, cleanup or custom function.
Ask for relevant proof
Request comparable sites and ask what the developer personally built. For technical work, discuss version control, staging, backups and rollback.
Protect production
- Use staging whenever practical
- Create a tested backup
- Give least privilege access
- Record licenses and ownership
- Define rollback and support
Structure the engagement
| Milestone | Evidence |
|---|---|
| Discovery | Scope, risks, dependencies |
| Staging | Review URL and test checklist |
| Launch | Backup and smoke tests |
| Handoff | Credentials and documentation |
Red flags
Avoid direct production edits without backup, unexplained plugin sprawl, nulled software and vague ownership of premium licenses.