What the website needs to support
A company website needs to support content and conversion while staying dependable. Growth experiments compete for time with modernization, security and reliability, including technical debt. I set priorities around what the team can deliver with the capacity available.
My role
As Website Manager at JumpCloud, I lead web engineering and conversion work. I set roadmaps and quarterly priorities, and coach engineers as they take on technical ownership. I work with Marketing and Product, as well as Engineering, Security, Data and Revenue Operations.
Coaching includes career planning and gradually delegating technical refinement and delivery. Engineers need ownership of the decisions around their work as well as the implementation.
Getting platform changes out
I delivered Pardot-to-Marketo integration and Vue modernization, coordinating owners around consent requirements and testing before release. Those changes affect the people publishing content and running campaigns, as well as the people maintaining the site.
Reusable components support ongoing delivery. The roadmap also includes observability and recurring maintenance, with event-collection audits alongside new capabilities.
Work still being evaluated
I built PageInsights to examine aggregate page behavior, including section exposure and friction around calls to action and forms. Collection is disabled by default. Permissions and retention controls bound what it can collect and store. Installation and authenticated health checks passed in isolated WordPress/MariaDB. Staging and live use remain unverified.
First-party experimentation is a build-versus-buy evaluation and technical spike. It covers assignment and measurement, consent, caching and performance. JumpCloud AI search has a business case and working prototype. Both are separate from delivered platform changes, and the search prototype is separate from the House of Destiny beta.
Discuss the work
Tell me what your team needs to build, or where the work is getting stuck.