Senior Analyst, Marketing Analytics
New Engen · Seattle, WA · 1 mo ago
Hybrid$95k–$105k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We need to parse the job posting.
First, there is a "WHY NEW ENGEN?" intro paragraph describing company. That could be "About the role"? Actually "About the role" is typical heading for description of role. The intro about company could be considered "About the role" or maybe "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for the description of the role and company context. The posting includes "What You'll Do" which is responsibilities. Then "What You Bring" which is requirements/qualifications/skills. Then "Location: Hybrid..." maybe schedule? Actually location is not schedule. There's "Perks & Benefits" which is benefits. Then "Salary Range:" which is pay. Then there is location/hybrid info maybe schedule? Not exactly schedule but could be schedule (Hybrid in Seattle or NYC 2x/week in office preferred; open to remote candidates based in Denver). That's schedule info (work arrangement). So we can put that under Schedule.
We must not repeat job title as heading. No job ID.
We must remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Important Notice About Job Openings" about fraudulent job postings. That's boilerplate/legal; we should remove. Also "Let’s Build What’s Next Together — If you’re passionate..." maybe considered marketing but it's substantive? It's a call to action; could be considered part of About the role? Might be okay to keep but it's not a list; it's prose. However it's near the end before the fraud notice. It's not boilerplate; it's a motivational closing. We could include it in About the role or maybe as a separate paragraph. But we should keep substantive info. It's not required to keep but we can keep.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections: responsibilities, requirements, qualifications, skills, benefits, pay, schedule.
We must not create sections with filler like "commensurate with experience". Not present.
We need to use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We need to parse the job posting.
First, there is a "WHY NEW ENGEN?" intro paragraph describing company. That could be "About the role"? Actually "About the role" is typical heading for description of role. The intro about company could be considered "About the role" or maybe "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for the description of the role and company context. The posting includes "What You'll Do" which is responsibilities. Then "What You Bring" which is requirements/qualifications/skills. Then "Location: Hybrid..." maybe schedule? Actually location is not schedule. There's "Perks & Benefits" which is benefits. Then "Salary Range:" which is pay. Then there is location/hybrid info maybe schedule? Not exactly schedule but could be schedule (Hybrid in Seattle or NYC 2x/week in office preferred; open to remote candidates based in Denver). That's schedule info (work arrangement). So we can put that under Schedule.
We must not repeat job title as heading. No job ID.
We must remove boilerplate: cookie/navigation/legal/EEO etc. At end there is "Important Notice About Job Openings" about fraudulent job postings. That's boilerplate/legal; we should remove. Also "Let’s Build What’s Next Together — If you’re passionate..." maybe considered marketing but it's substantive? It's a call to action; could be considered part of About the role? Might be okay to keep but it's not a list; it's prose. However it's near the end before the fraud notice. It's not boilerplate; it's a motivational closing. We could include it in About the role or maybe as a separate paragraph. But we should keep substantive info. It's not required to keep but we can keep.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections: responsibilities, requirements, qualifications, skills, benefits, pay, schedule.
We must not create sections with filler like "commensurate with experience". Not present.
We need to use for each section heading, then content:
for prose,
- for lists.
We need to decide what goes where.
Section "About the role": Could include the WHY NEW ENGEN? paragraph and maybe the "Let’s Build What’s Next Together" paragraph. Also maybe location? But location is schedule.
We'll put About the role: includes the WHY NEW ENGEN? paragraph and maybe the "Let’s Build What’s Next Together" paragraph (the call to action). We'll keep both as
. Section "Responsibilities": from "What You'll Do" bullet points. Those are a series of paragraphs each starting with bold? Actually they are sentences: "Support Measurement Strategy and Drive Day-to-Day Execution Key contributor..." etc. They are not bullet list but each is a separate paragraph with a bold heading? In the text they appear as lines with bold headings: "Support Measurement Strategy and Drive Day-to-Day Execution", "Design Testing Roadmaps and Methodologies", etc. We should treat each as a list item? The instruction: Use
- for any list of duties/requirements/benefits. So we should convert those into a list. Each duty is a separate item. We'll extract the duty description after the bold heading. Let's list them: - Support Measurement Strategy and Drive Day-to-Day Execution: Key contributor to the measurement strategy across your accounts, from defining the learning agenda to delivering actionable insights. - Design Testing Roadmaps and Methodologies: Develop clear, structured test roadmaps across channels and campaigns. Select and design the appropriate methodologies based on budget, data availability, and business context, including geo holdouts, incrementality testing, MMM, brand lift studies, forecasting, full-funnel user journey analysis, and other approaches. - Translate Data into Business Impact: Synthesize complex data into clear, compelling narratives for clients and internal stakeholders. Ensure results are not just reported but understood, connecting findings back to business objectives and recommending next steps. - Partner Cross-Functionally: Work closely with media strategists, BI and data teams, and client leads to align measurement strategies with broader campaign and business goals. Act as the bridge between business questions and analytical execution. - Build and Scale Measurement Frameworks: Contribute to the development of internal tools, frameworks, and playbooks that help scale measurement capabilities across teams. Bring structure and consistency to how measurement is applied across accounts. We'll make each as
- containing the full sentence(s). Section "Requirements": Could be from "What You Bring" which includes many items. Some are qualifications, some are skills. We need to decide which heading to use: Requirements, Qualifications, Skills. The posting includes both "5+ years in analytics, measurement, or a closely adjacent field" (requirement), "Hands-on design and/or execution experience with one or more of: ..." (qualification/experience), "Scripting ability in Python or R is preferred with a working knowledge of SQL" (skill), "Familiarity with Tableau and/or other BI tools" (skill), "Web analytics or full-funnel user journey experience is a plus" (skill/plus), "Understanding of e-commerce measurement frameworks and incrementality concepts" (knowledge), "Strong communicator and comfortable presenting to clients and working across media, strategy, and data teams" (skill), "Working knowledge of building and working with AI at an enterprise level is a plus" (skill), "Agency or consulting experience" (experience), "Deep familiarity with the paid media landscape (search, social, programmatic) and how measurement connects to media decisions and impacts on-site performance" (knowledge), "Builder mentality, with the curiosity to dig deep to uncover the “why” and not just the “what”" (attribute). Also location/hybrid info is schedule. We could split into Requirements (5+ years experience), Qualifications (hands-on experience with specific methodologies), Skills (scripting, BI tools, communication, AI, agency experience, paid media familiarity, builder mentality). But the instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Requirements" for the 5+ years and "Qualifications" for the hands-on experience, and "Skills" for the rest. But that may be many sections. However we need to include only when posting has real specific content. All those are real. We could have three sections: Requirements, Qualifications, Skills. That's okay. But we need to avoid thin sections: each should have substantive content. Each will have multiple items. Let's decide: - Requirements: "5+ years in analytics, measurement, or a closely adjacent field" - Qualifications: "Hands-on design and/or execution experience with one or more of: MMM, geo holdout testing, incrementality measurement, brand lift studies, forecasting, full-funnel user journey analysis" - Skills: list the rest: scripting ability in Python or R preferred with working knowledge of SQL; familiarity with Tableau and/or other BI tools; web analytics or full-funnel user journey experience is a plus; understanding of e-commerce measurement frameworks and incrementality concepts; strong communicator and comfortable presenting to clients and working across media, strategy, and data teams; working knowledge of building and working with AI at an enterprise level is a plus; agency or consulting experience; deep familiarity with the paid media landscape (search, social, programmatic) and how measurement connects to media decisions and impacts on-site performance; builder mentality, with the curiosity to dig deep to uncover the “why” and not just the “what”. We could also include location/hybrid info under Schedule. Benefits: from "Perks & Benefits" list. Pay: Salary Range: $95,000-$105,000 USD annual plus note about compensation determination. Schedule: Location/hybrid info: "Location: Hybrid in Seattle or New York City (2x/week in office) preferred; open to remote candidates based in Denver." Also maybe mention remote/hybrid work environment with flexible hours (that's also a benefit but could be schedule). Actually "Remote or hybrid work environment with flexible hours" is listed under Perks & Benefits. So schedule could be just location/hybrid preference. But we already have remote/hybrid as benefit. To avoid duplication, we could put location/hybrid under Schedule, and keep remote/hybrid work environment under Benefits? But the benefit list includes "Remote or hybrid work environment with flexible hours". That's a benefit. So we should keep that under Benefits. Then schedule could be just the location expectation? Actually schedule could be the "Hybrid in Seattle or New York City (2x/week in office) preferred; open to remote candidates based in Denver." That's schedule info (expected office days). We'll put that under Schedule. Now Benefits list: from "Perks & Benefits" bullet list: - Remote or hybrid work environment with flexible hours - Unlimited PTO + company holidays - Comprehensive medical, dental, vision, and disability coverage - Life & AD&D insurance - 401(k) with company match - Paid parental leave & family support - Pet care perks & insurance - Learning & career development programs - Commuter & transit benefits - Exclusive employee discounts We'll make each as
- .
Pay: Salary Range: $95,000-$105,000 USD annual. Also note: "Compensation for each opportunity is determined based on the applicable labor market, the scope and structure of the role or engagement, and the individual’s qualifications and experience." That's substantive; we should include as prose under Pay.
Now About the role: include the WHY NEW ENGEN? paragraph and maybe the "Let’s Build What’s Next Together" paragraph. Let's extract those.
WHY NEW ENGEN? paragraph: "WHY NEW ENGEN? At New Engen, we help brands grow—not just bigger, but smarter. We’re a digital marketing agency built to drive meaningful impact across the entire customer journey, blending media, creative, analytics, influencer, and retail strategies into performance-driven campaigns. Some clients partner with us through long-term agency relationships. Others tap into specialized solutions—like Donut Studios, our in-house creative studio for platform-native and short-form content, or Acorn Creator Suite, our influencer marketing solution built for retail impact. While each solution brings its own focus and flavor, they’re all part of how we deliver for our clients, together, as one team. We’re a collaborative group of strategists, creatives, analysts, and makers who are all in on helping brands—and each other—thrive. We work hard, stay humble, and build with purpose."
Then after responsibilities etc, near the end: "Let’s Build What’s Next Together — If you’re passionate about media and eager to make a meaningful impact with a team that’s all in, we’d love to hear from you." That's a call to action. We'll include as a paragraph.
We should not include the fraud notice.
Now produce HTML.
Structure:
About the role
WHY NEW ENGEN? At New Engen, we help brands grow—not just bigger, but smarter. ...
Let’s Build What’s Next Together — If you’re passionate about media and eager to make a meaningful impact with a team that’s all in, we’d love to hear from you.
Responsibilities
- Support Measurement Strategy and Drive Day-to-Day Execution: Key contributor to the measurement strategy across your accounts, from defining the learning agenda to delivering actionable insights.
- Design Testing Roadmaps and Methodologies: Develop clear, structured test roadmaps across channels and campaigns. Select and design the appropriate methodologies based on budget, data availability,