Head of Growth Engineering, Delivery Manager - DTC Startup

About Us

HarZa Group is a fast-growing operator of direct-to-consumer brands in health and wellness. Our flagship brand, Rejuvacare, serves more than 400,000 customers with products targeting chronic pain and mobility, including RejuvaKnee, FootRenew, RejuvaFlow and OzemPatch. We ship primarily to the United States and run a membership program that powers recurring revenue. The company has scaled 12x in a single year to nearly 150 people across more than 15 countries. We are remote-first, async-first, and hold a high standard of accountability across everything we do.

The Role

We are a direct-to-consumer business where technology is a direct function of marketing. Our marketing team can develop a campaign idea and write the copy for it in a single day, but that idea only starts producing revenue once it has become a live, accurate and fully functioning landing page, checkout or funnel. The speed of our production function therefore sets the speed of the entire business.

We are hiring a Head of Web Production to build and own the operating system through which marketing requirements become live digital experiences. Your responsibility is not to manage tasks, chase deadlines or add project management meetings. It is to redesign how the work gets done. You will examine every stage of production, remove unnecessary handoffs, improve requirements, manage dependencies, install effective quality controls, and decide where AI, automation, page builders, reusable components or traditional development should be used.

For every requirement you should be asking whether this genuinely needs a developer, whether it can be built from an existing component or template, whether an AI-enabled page builder can complete most of it, whether the marketing team can safely complete it without engineering, whether the requirement can be eliminated or standardized, whether the quality check can be automated, and why it is taking as long as it is. Your job is to protect the business objective while continuously challenging the method used to achieve it.

To be explicit about scope, this is not a cloud infrastructure or site reliability role. This is web production and development operations for a high-volume direct response marketing business.

What You Will Own

The Production Operating System

Map and redesign the workflow from marketing request to production launch, identifying bottlenecks, unnecessary handoffs, waiting time and duplicated work, and establishing clear ownership at every stage. Define what information must exist before work can begin, create work-in-progress limits and prioritization rules, and build separate production lanes for urgent changes, standard pages, experiments and complex technical projects so that urgent work stops destroying the predictability of planned work. Create clear escalation paths for blockers and for requirements that change mid-build.

Requirements and Task Definition

Build standardized briefs for landing pages, checkouts, funnels, upsells and technical changes, and establish a Definition of Ready for every category of work so that incomplete or ambiguous requests never enter development. Ensure every requirement carries complete copy, design direction, references, responsive behaviour, tracking requirements and acceptance criteria, and translate marketing intent into specifications that developers and page builders can execute without repeated clarification. Create a controlled process for requirements that change after development has begun.

AI-First Production

Audit the full production process for opportunities to use AI and automation, evaluate AI coding tools, AI page builders, no-code platforms, reusable components and template-based systems, and determine the right balance between developers, page builders, designers and AI-enabled operators. Build workflows where AI converts approved briefs, copy and designs into high-quality first drafts, install guardrails that allow non-developers to build safely without damaging performance, tracking or brand standards, and reduce repetitive development through reusable sections and approved design systems. Measure the actual impact of AI on cycle time, cost, quality and throughput rather than assuming it.

Dependencies and Capacity

Create visibility over the workload and capacity of development, design and other shared resources, identify dependencies before work enters production, and sequence work based on when copy, graphics, video, development and approvals will realistically be available. Prevent developers from being assigned work that cannot be completed because a dependency is missing, build a capacity planning system that lets marketing understand what can actually be delivered and when, and surface constraints early enough for the business to reprioritize or find an alternative. Reduce reliance on informal messages and on individual managers holding critical information in their heads.

Quality Built Into the Process

Move quality control upstream instead of relying on final-stage inspection. Introduce developer self-QC before any task is submitted, create standardized QC checklists by page and funnel type, define acceptance criteria before development begins, and establish an independent final QC process that does not depend entirely on one person. Implement automated testing wherever practical, including visual regression, broken links, responsive layouts, tracking, checkout functionality, browser compatibility and page performance. Categorize defects, track root causes, and ensure repeated defects change the underlying system, checklist, component or training rather than being corrected one at a time.

Team Structure and Capability

Lead the existing production team and raise its operating standard. Determine which work should be completed by developers and which should be completed by AI-enabled production specialists, and make sure capability is matched to the work. Coach the team on estimation, task clarification, self-QC and AI-assisted workflows, set clear performance expectations for speed, predictability and quality, and build enough documentation and shared visibility that the function does not depend on any single person holding critical context.

The Measurement System

Build and maintain reporting on request-to-launch cycle time, active production time versus waiting time, throughput by work category, on-time delivery, clarification interactions after assignment, first-pass QC rate, average revision rounds, escaped defect rate, rework hours, blocker age, the share of work completed through reusable components or AI-assisted workflows, cost per page or funnel, and marketing launch delays caused by technology or creative dependencies. These metrics exist to improve the system, not to generate reporting.

How Success Will Be Measured

Your first thirty days are about establishing a baseline. We do not currently measure cycle time, waiting time, clarification loops, rework or escaped defects, so your first task is to map the current state from request to launch and put real numbers against it, then produce a prioritized roadmap for improving the system. We would rather agree ambitious targets against real data than hand you numbers invented before anyone measured anything.

By sixty days we expect a standardized intake and requirements process, clear Definitions of Ready and Done, service-level expectations by category of work, visibility over development and creative capacity, dependency planning across copy, design, video, development, tracking and approvals, piloted AI-assisted and template-driven workflows, and a live operating dashboard covering speed, quality and throughput.

By ninety days we expect the function to be trending strongly toward a materially shorter median request-to-launch cycle time, the large majority of work delivered by the committed date, the large majority of work passing final QC without another development round, a sharp reduction in issues identified after approval by the CEO or the media buyer, full visibility over active work, dependencies, blockers and capacity, standard page types produced without bespoke development, and higher throughput without a corresponding increase in headcount. Exact targets will be finalized against your baseline.

Significant experience improving the operations of a web development, digital production or growth technology team, with a proven record of reducing delivery time, increasing throughput or improving first-pass quality. Experience in an environment where development speed directly affects revenue. A strong working understanding of landing pages, ecommerce funnels, checkouts, upsells, testing and conversion-focused web production.

Enough technical depth to challenge estimates, architecture choices and development approaches, including a working understanding of HTML, CSS, JavaScript, APIs, analytics, tracking, page builders and modern web development workflows. Experience implementing AI tools or automation inside a real production environment rather than as a pilot or a talking point. Experience designing intake processes, acceptance criteria, capacity planning and quality control systems, and a strong grasp of dependencies and constraint management.

The ability to communicate effectively with marketers, copywriters, designers, media buyers and developers, and the confidence to challenge senior stakeholders when a requirement is unclear, unnecessarily complicated or being solved in the wrong way. Strong analytical ability, comfort making decisions from operational data, and a bias toward simplification, standardization and measurable results.

Experience with direct response ecommerce, high-volume web production, Shopify, Checkout Champ, Figma, landing page builders, CRO testing and marketing analytics is highly advantageous. Formal qualifications are not required where there is strong evidence of relevant outcomes. You must be able to overlap consistently with our collaboration window of 8:00am to 12:00pm EST.

This Role Is Not

This is not a traditional cloud-infrastructure DevOps role, a Jira administration role, a project coordinator position, or a role focused on running agile ceremonies. It is not a role for someone who accepts every requirement without questioning it, whose first answer to any constraint is additional headcount, who can describe AI tools but has never embedded them into an operational workflow, or who wants engineering leadership disconnected from marketing and revenue.

What We Offer

A fully remote senior position with genuine ownership of a function that directly determines how fast the business can move. We offer paid time off, a monthly wellness stipend, medical insurance support, a company-funded computer allowance after a tenure milestone, a birthday gift card, an in-country meetup allowance, and participation in company-funded leadership offsites. You will have direct access to the founders, a high-volume testing environment, and the mandate to build the system rather than inherit someone else's process.