Growth Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. The posting includes: - Location US remote - Employment Type Full time - Department Engineering - OverviewApplication About Pika (some weird formatting) - About Pika description - About The Role (repeated multiple times) - What You’ll Do (list of bullet-like sentences) - What We’re Looking For (list) - Nice to Have (list) - Our Stack (list) - What We Offer (list) - Also repeated sections. We need to produce sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content accordingly. We have: - About the role: description of role (overview). Could be "About The Role" section. - Responsibilities: "What You’ll Do" list. - Requirements: "What We’re Looking For" (core requirements). Could be "Requirements". - Qualifications: maybe "Nice to Have" could be "Qualifications" or "Nice to Have". But we only have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put "Nice to Have" under "Qualifications" or "Skills". The instruction: "Prefer a few substantive sections over many thin ones." So we might combine. We have "Our Stack" which could be under "Skills" (technologies). Or we could have a "Skills" section for required proficiencies. We have "What We Offer" which includes benefits: Competitive salary, equity, health benefits, stipends, retreats, culture. So we can make a Benefits section. Pay: The posting says "Competitive salary in the AI industry". That's specific enough? It says competitive salary, not a number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive salary in the AI industry". That's a statement about pay, albeit vague. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include Pay with that statement. However, they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they have separate headings for Benefits and Pay. Could we put salary info under Benefits? The instruction says we should not create Pay section unless posting actually states them. It does state competitive salary, so we could include Pay. But we could also incorporate salary into Benefits section as part of compensation. However, they said "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits into one Benefits section? But they gave separate headings; we could still include both if we have content. However, we have no schedule info (no mention of schedule). So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe Nice to Have), Skills (Our Stack), Benefits (What We Offer), Pay (Competitive salary). Could also combine Pay and Benefits. But we need to avoid filler. Ensure each heading has substantive content. Let's extract content: About the role: The repeated block: "We are seeking a Growth Engineer to accelerate the adoption and expansion of Pika’s creative AI platform. As a Growth Engineer, you will use your technical expertise to identify, build, and optimize features, systems, and experiments that drive user acquisition, activation, engagement, and retention. You’ll collaborate closely with product, design, marketing, and data teams to unlock rapid, measurable growth across the product. You will combine hands-on engineering with a deep analytical mindset, iterating quickly on growth initiatives and leveraging both code and data to uncover opportunities. Your work will directly impact millions of creators and help us shape the future of AI-powered media tools." We should include that once. Responsibilities: "What You’ll Do" list items: - Design, develop, and launch growth features and experiments across the Pika platform - Implement scalable A/B tests and personalization strategies to optimize user acquisition and retention - Analyze data to discover new growth levers and track the effectiveness of growth strategies - Work closely with product, marketing, and data teams to prioritize and execute high-impact growth initiatives - Rapidly prototype and ship new product surfaces, onboarding flows, and engagement loops - Optimize performance, reliability, and user experience for features targeting key growth metrics - Contribute to product virality, referral, and sharing capabilities to expand reach - Advocate for a data-driven, experimentation-focused engineering culture We can put each as

• . Requirements: "What We’re Looking For" list: - 4+ years of software engineering experience, ideally on product or growth teams - Proven record of building and optimizing user-facing features, preferably in consumer or SaaS products - Experience with experimentation frameworks, A/B testing, and data analysis - Strong problem-solving and analytical skills, with ability to translate insights into scalable solutions - Proficiency with modern web or backend technologies (Python, Go, Node.js, TypeScript, or similar) - Familiarity with growth tools and analytics platforms (Amplitude, Segment, Google Analytics, etc.) - Excellent communication skills and ability to collaborate with cross-functional teams - Self-motivated, curious, and comfortable operating in a fast-paced, high-growth environment Qualifications: "Nice to Have" list: - Experience in generative AI, creative tools, or social platforms - Background in high-growth startups or rapid experimentation roles - Open source, hackathon, or growth hacking experience Skills: "Our Stack": Python, Go, Node.js, Postgres, Redis, Docker, Kubernetes, AWS/GCP We could list as
• . Benefits: "What We Offer": - Competitive salary in the AI industry - Substantial equity in a fast-growing startup defining the future of AI and creativity - Comprehensive health benefits, monthly stipends, and company retreats - Collaborative, high-growth culture—everyone contributes to growth and success We could separate salary into Pay section, but we can also include all under Benefits. However, we have a Pay heading possible. Let's decide: Since they said "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin if we split salary out. Better to combine into Benefits section, and not create Pay section. But we need to check instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could create Pay section with that line. But then Benefits section would have equity, health benefits, stipends, retreats, culture. That's still substantive. So we could have both Pay and Benefits. However, they said prefer few sections over many thin ones. Having Pay (one line) and Benefits (four lines) maybe okay. But we could also incorporate salary into Benefits as first bullet. That would reduce sections. I'd lean to combine into Benefits to keep fewer sections. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating a Pay section with just one line if we can incorporate it elsewhere. So we will not create Pay section. We'll have Benefits section with all four bullets. Schedule: No info, so omit. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to use

  for each section heading. Use

  • for any list of duties/requirements/benefits, and

    for prose. Thus:

    About the role

    We are seeking a Growth Engineer to accelerate the adoption and expansion of Pika’s creative AI platform. As a Growth Engineer, you will use your technical expertise to identify, build, and optimize features, systems, and experiments that drive user acquisition, activation, engagement, and retention. You’ll collaborate closely with product, design, marketing, and data teams to unlock rapid, measurable growth across the product. You will combine hands-on engineering with a deep analytical mindset, iterating quickly on growth initiatives and leveraging both code and data to uncover opportunities. Your work will directly impact millions of creators and help us shape the future of AI-powered media tools.

    Responsibilities

    • Design, develop, and launch growth features and experiments across the Pika platform
    • Implement scalable A/B tests and personalization strategies to optimize user acquisition and retention
    • Analyze data to discover new growth levers and track the effectiveness of growth strategies
    • Work closely with product, marketing, and data teams to prioritize and execute high-impact growth initiatives
    • Rapidly prototype and ship new product surfaces, onboarding flows, and engagement loops
    • Optimize performance, reliability, and user experience for features targeting key growth metrics
    • Contribute to product virality, referral, and sharing capabilities to expand reach
    • Advocate for a data-driven, experimentation-focused engineering culture

    Requirements

    • 4+ years of software engineering experience, ideally on product or growth teams
    • Proven record of building and optimizing user-facing features, preferably in consumer or SaaS products
    • Experience with experimentation frameworks, A/B testing, and data analysis
    • Strong problem-solving and analytical skills, with ability to translate insights into scalable solutions
    • Proficiency with modern web or backend technologies (Python, Go, Node.js, TypeScript, or similar)
    • Familiarity with growth tools and analytics platforms (Amplitude, Segment, Google Analytics, etc.)
    • Excellent communication skills and ability to collaborate with cross-functional teams
    • Self-motivated, curious, and comfortable operating in a fast-paced, high-growth environment

    Qualifications

    • Experience in generative AI, creative tools, or social platforms
    • Background in high-growth startups or rapid experimentation roles
    • Open source, hackathon, or growth hacking experience

    Skills

    • Python
    • Go
    • Node.js
    • Postgres
    • Redis
    • Docker
    • Kubernetes
    • AWS/GCP

    Benefits

    • Competitive salary in the AI industry
    • Substantial equity in a fast-growing startup defining the future of AI and creativity
    • Comprehensive health benefits, monthly stipends, and company retreats
    • Collaborative, high-growth culture—everyone contributes to growth and success
    Check for any duplicated content: We removed repeated sections. Ensure we