Adobe Analytics & Measurement Consultant

We need to output HTML fragment with sections: About the role? The posting includes "The Role" description. Also "Your First 90 Days". Also "Why 5th Revolution The Work Other Firms Can't Offer". Also "Compensation & Engagement". Also "Benefits". Also "The Five Points". Also "Business Communication & Leadership", "Technical Breadth & Depth", "Strategic Thinking", "Drive to Learn & Grow, Together", "Relevant Experience". Also "Apply for This Role" but we should remove application instructions. Also "What To Expect", "Equal Opportunity" etc are boilerplate to remove. We must include sections only when posting has real specific content. So we need to extract content for each heading. We must not repeat job title as heading. Use

for section headings. We need to preserve all substantive info, not invent or summarize away detail. Use

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

  for prose. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to parse the posting and produce sections. Let's identify sections: - About the role? The posting has "The Role" paragraph: "Enterprises have no shortage...". That's prose. - Responsibilities? Could be the bullet list under "The Role"? Actually after "The Role" there is a paragraph describing responsibilities: "Build and validate. Implement Adobe Analytics and CJA ...", "Own the AA to CJA transition.", "Shape the framework.", "Turn data into decisions.", "Govern it." Those are bullet-like sentences each ending with period. Could treat as list. - Requirements/Qualifications/Skills: There's "Relevant Experience" section with bullet points: "2+ years hands-on Adobe Analytics with real CJA depth, or 5+ years in a closely related digital-analytics role", "At least one AA to CJA migration including the reconciliation; owning a full measurement framework lands you higher", "Adobe Certified Expert in Adobe Analytics or CJA a strong signal". Also there are skill sections: "Business Communication & Leadership", "Technical Breadth & Depth", "Strategic Thinking", "Drive to Learn & Grow, Together". Those could be considered skills/competencies. Could combine into a "Skills" section with subheadings? But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map. Probably best: About the role (The Role paragraph). Responsibilities (list of duties). Requirements (maybe combine relevant experience bullet points). Qualifications (maybe certifications). Skills (the four competency areas). Benefits (list: Paid sick leave, annual certification and professional-development budget, conference attendance and speaking opportunities, fully remote up to ~10% travel, latest tools, hardware, AI-enabled dev environments, small senior team, work directly with principal architect). Pay (compensation details: hourly $75-$135, salaried $110k-$190k, W-2 from day one, conversion details). Schedule (maybe mention remote, up to ~10% travel, hourly schedule agreed in advance, overtime). Also "Your First 90 Days" could be a section but not in allowed headings; maybe treat as part of Responsibilities or About the role? But we must not create headings not in list. So we need to fit content into allowed headings. Could put "Your First 90 Days" under Responsibilities as a list? Or maybe under About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It says "include a section ONLY when the posting has real, specific content for it". So we can use those headings only. So we need to map content to those. Thus we need to decide which sections to include. We have content for: - About the role: The Role paragraph. - Responsibilities: The bullet list of duties (Build and validate..., Own the AA..., Shape..., Turn data..., Govern it.) plus maybe the "Your First 90 Days" details (weeks 1-12). Could treat as responsibilities. - Requirements: The "Relevant Experience" bullet points. - Qualifications: Maybe the Adobe Certified Expert? But that's also a qualification. Could combine with Requirements. - Skills: The four competency areas (Business Communication & Leadership, Technical Breadth & Depth, Strategic Thinking, Drive to Learn & Grow, Together). Each has prose. - Benefits: List of benefits. - Pay: Compensation details. - Schedule: Remote, up to ~10% travel, hourly schedule agreed in advance, overtime. We must not include boilerplate like "Why 5th Revolution The Work Other Firms Can't Offer" etc. That's marketing fluff but maybe considered substantive? It's about culture; could be considered part of About the role? But it's not a standard heading; we could omit as it's not required headings. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit that fluff. Also "The Five Points" etc are also fluff; we can omit. Also "Apply for This Role", "What To Expect", "Equal Opportunity" etc are boilerplate to remove. Thus produce HTML with sections for each heading that has content. Let's extract precise content. About the role: The paragraph starting "Enterprises have no shortage of data collection and a serious shortage of numbers anyone trusts. This role runs the full width of that problem." Continue until "...and the governance that keeps it honest across an enterprise. Where you land is set by what you bring. We design as a team, and you own the measurement decisions your level carries." We need to keep that exactly. Responsibilities: List of duties: - Build and validate. Implement Adobe Analytics and CJA (report suites, connections, data views, derived fields) and QA with the AEP Debugger or ObservePoint until the numbers tie out. - Own the AA to CJA transition. Map metrics, dimensions, and events into CJA and reconcile until the business trusts the new number as much as the old. - Shape the framework. As you grow into it, own what gets measured and why, the data-view model, and the access design that lets people answer their own questions. - Turn data into decisions. Deliver the "so what": funnel, cohort, and attribution analysis, and the recommendation that follows from it. - Govern it. Set the naming, documentation, and QA standards, and teach client teams to keep them, so quality survives your handoff. Also "Your First 90 Days" details: Weeks 1-3, 4-8, 9-12. Could be included as responsibilities as well. Let's incorporate as sub-bullets maybe. Weeks 1-3: Inventory what exists. Report suites, the metrics leadership actually quotes, and every integration still pointed at a legacy API or authentication scheme. Adobe retires these on published dates, and they arrive faster than anyone plans for. Weeks 4-8: Stand up the CJA side. Connections, data views, and derived fields over data that is already flowing, then reconcile against Adobe Analytics until the differences are explainable rather than surprising. Weeks 9-12: Move the people, not just the data. Migrate projects and components, train the client's champion, and write the naming and QA standards down so quality survives your handoff. We can add these as list items under Responsibilities. Requirements: Relevant Experience bullet points: - 2+ years hands-on Adobe Analytics with real CJA depth, or 5+ years in a closely related digital-analytics role - At least one AA to CJA migration including the reconciliation; owning a full measurement framework lands you higher - Adobe Certified Expert in Adobe Analytics or CJA a strong signal Qualifications: maybe we could treat the Adobe Certified Expert as qualification, but it's already in requirements. Could leave Qualifications empty or omit. Better to omit Qualifications if no distinct content. Skills: The four competency areas with their prose. Let's extract each: Business Communication & Leadership: "You own the room and the outcome. You move fluidly between executive teams and delivery, framing everything in business value, and setting a direction cross-functional teams want to execute. Translate fluidly between executive and technical audiences Frame every decision in business value Lead cross-functional delivery teams" Technical Breadth & Depth: "Solid hands-on Adobe Analytics and Customer Journey Analytics, the implementation fluency to know *why* a number is wrong, and enough analytical skill to say what it means. Hands-on Adobe Analytics and CJA: report suites, connections, data views, derived fields, calculated metrics, Analysis Workspace The data foundation underneath: data layers, Adobe Tags, Web SDK and datastreams, mobile SDKs, and QA with the AEP Debugger or ObservePoint Analysis fundamentals: funnel, cohort, and attribution analysis, plus SQL for the questions Workspace cannot answer" Strategic Thinking: "You get from "we need a CDP" to the real business goals, a sequenced roadmap, and an ROI case that wins executive budget, sequencing for fastest measurable value, not activity. Turn vague asks into goals, roadmap, and an ROI case Scope, size against product licensing, and set realistic timelines Protect scope, schedule, and budget when reality pushes back" Drive to Learn & Grow, Together: "You never accept the status quo. You stay current because you are genuinely curious, and you level up the whole team by learning alongside your peers. Genuinely curious, always current Level up the whole team, not just yourself Best approach wins, regardless of title or tenure" Benefits: List: - Paid sick leave - Annual certification and professional-development budget - Conference attendance and speaking opportunities - Fully remote, up to ~10% travel - During the hourly phase your schedule is agreed in advance and all hours worked are recorded and paid, including overtime (maybe schedule) - Latest tools, hardware, and AI-enabled development environments - A small, senior team. You work directly with the principal architect on Fortune 100 accounts, not through layers of account management Pay: - During the initial hourly phase, this role pays $75 to $135 per hour. - On conversion to a salaried role, the base salary range is $110,000 to $190,000 per year. - W-2 from day one. - Hourly to start, converting to salaried. - You start hourly and overtime-eligible on a longer-term engagement, and convert to a salaried role from there. - We typically evaluate conversion within the first six to nine months. - Conversion depends on mutual fit and on business conditions, so we will not promise a date we cannot control, and we will tell you where you stand rather than leave you guessing. - Competitive rate; total compensation reflects skill and impact, not just years. - Annual certification and professional-development budget; conference attendance and speaking opportunities (already in benefits) - Fully remote, up to ~10% travel. (already) - Latest tools, hardware, and AI-enabled development environments (benefits) - A small, senior team. You work directly with the principal architect on Fortune 100 accounts, not through layers of account management (benefits) - Pay range. During the initial hourly phase, this role pays $75 to $135 per hour. On conversion to a salaried role, the base salary range is $110,000 to $190,000 per year. - Be plain about the arithmetic. The two are not a like-for-like comparison. Hourly, you are non-exempt: you are paid for every hour you work, overtime included, and you carry the variability. Salaried, you are paid whether or not you are on a billable engagement, and overtime no longer applies