EngineerPro↗ aiengineerprofessional.com

EngineerPro — three live fronts on one engine for software, AI, and data engineering.
A persona hub for software, AI, and data engineering — three live fronts on one engine, with Journeyman, the practice tool for new engineers, folded in.
Engineering is its own profession with its own canon, and the portfolio had accumulated a large engineering book and tool shelf sitting on a people-analytics site where it did not belong. Shedding it required a real destination first, not a redirect.
Three live fronts — aiengineerprofessional.com, dataengineerprofessional.com, softwareengineeringprofessional.com — serving guides off the shared control plane, with Journeyman (journeyman.softwareengineeringprofessional.com) as the embedded practice tool for new engineers.
- 01A profession-level peer, not a sub-brand. Engineering hangs off its own hub rather than under a management site, which is what let the analyst hub shed 118 engineering books cleanly.
- 02Content-first relocation. The books move only once the destination houses and renders them — the placement gate is mechanical (a product_home tag plus a foreign-home 404), not a matter of vigilance.
- 03A dual-home lens where the overlap is real. Roughly two dozen titles legitimately serve both engineering and people analytics and are kept on both shelves rather than forced to pick.
Three domains live and serving guides, and the least finished thing in the portfolio — carded because it is publicly live, not because it is done. Measured gaps: the property still declares itself planned while answering 200, its /guides index 404s while the detail routes work, and it over-serves guides homed elsewhere that a scoped front should refuse.
EngineerPro started as a placement problem — a large engineering shelf on the wrong site — and became an argument about structure: every profession the portfolio serves gets one canonical home, and the hub keeps only what is genuinely its own.