Sr. Solutions Architect (Pre Sales)

We need to output HTML fragment with sections only when there is real specific content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: company description? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description at top is maybe considered boilerplate? It's not exactly legal but it's generic description; but it's substantive? It describes Nielsen's mission. Might be considered company description; but we need to preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive about Nielsen. Should we include it? The instruction says "Prefer a few substantive sections over many thin ones." We can include an "About the role" section maybe containing the job description details. The company description could be placed maybe as a paragraph before sections? But they said use

for section headings (e.g. About the role, Responsibilities...). They didn't forbid other headings, but they said use

for section headings (list). Likely they expect sections like About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have content: Job Description (the paragraph about Nielsen looking for experienced consultative sales professional...). That's suitable for About the role. Responsibilities: there is a big block starting with "Own and grow a book of strategic accounts..." etc. That's responsibilities. Qualifications: there is a block "Qualifications 10–15 years..." etc. That's qualifications. Skills: maybe we can extract skills from qualifications? But we have a separate Skills section maybe we can include if there is explicit skills list. The posting includes "Strong consultative selling skills; able to open a credible conversation..." etc. That's more like qualifications/skills. Could treat as Skills. Benefits: there is "Additional Information Enabling your best to power a better media future. Holistic Rewards: We are committed to an inclusive benefits package..." That includes benefits description. So we can create Benefits section. Pay: there is "Compensation Transparency: The posted base salary range is a reasonable estimate..." That's pay info. So we can include Pay. Schedule: not mentioned. So we should not include Schedule. We must not include sections with filler like "commensurate with experience". The pay section includes actual content: base salary range estimate, factors, bonuses etc. That's substantive. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

...

Responsibilities

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

...

Pay

...

We need to preserve all substantive information; do not invent or summarize away detail. So we need to copy the text exactly? Probably we can paraphrase but must preserve meaning. Safer to copy the relevant sentences as is, maybe split into list items. We need to ensure we don't include boilerplate like "Enabling your best to power a better media future." That's part of Additional Information but it's also part of benefits? It's okay. We need to remove duplicated lines, scam-warning etc. So we must cut the scam warning paragraph at end. Also remove EEO etc. There's a line: "Nielsen makes hiring decisions without regard to disability status, protected veteran status, or membership in any other protected class." That's EEO boilerplate; must remove. Also remove "Please be aware that job-seekers may be at risk..." etc. That's scam warning; remove. Also remove "Depending on the role, additional benefits may include a company-provided vehicle and/or discretionary incentive/bonus eligibility." That's benefits; keep. Also "Compensation Transparency: The posted base salary range is a reasonable estimate that may be adjusted based on the final work location of the selected employee. Individual pay within the range is determined by factors such as experience, training, geography, certifications, and business needs. Beyond base salary, this role may be eligible for bonuses, equity, or other incentives." Keep as pay. Now we need to extract About the role: The paragraph after Job Description: "Nielsen is looking for an experienced, consultative sales professional to drive sales of Nielsen Bi-Directional (NRLD Enrichment). Bi-Directional lets clients securely combine their own first-party data with Nielsen Respondent Level Data (NRLD) inside a privacy-safe, clean-room environment, then generate predictive audience scores across their full customer database — without raw data ever leaving the room. This is a strategic, high-visibility product sold primarily as an expansion into accounts Nielsen already serves. Success depends less on cold prospecting and more on relationship depth, communication skills, technical fluency, and the ability to translate a client's business question into a Bi-Directional use case. The strongest candidates can open a credible conversation with a buyer before they know exactly which use case will land, then guide a multi-stakeholder enterprise cycle from discovery through a proof-of-concept to a signed, renewable engagement. This role is ideal for a seasoned professional with a strong blend of advanced research expertise, extensive client-facing experience, a proven track record in sales, and a passion for driving strategic growth." Also there is "What You'll Sell Bi-Directional is not an off-the-shelf data feed..." That's also part of role description. Should we include that in About the role? Probably yes. Thus About the role includes both paragraphs. Now Responsibilities: list of bullet points after "Responsibilities". We need to capture each sentence as list item. Let's extract: - Own and grow a book of strategic accounts, selling Bi-Directional primarily as an expansion into existing Nielsen relationships rather than net-new logos. - Consult with clients to identify solutions and align the product to a specific, quantified business need — translating a vague "we want better measurement" into a concrete use case (churn-risk scoring, streaming-nomad conversion, sponsorship lift, cross-platform migration, content valuation). - Lead discovery that surfaces the client's real economic question and sizes the value at risk, then frame Bi-Directional as the mechanism that closes that specific gap. - Quantify ROI before the client signs, using a value-at-risk framing (addressable audience gap × LTV or CPM) grounded in the client's own numbers. - Scope and shepherd proof-of-concept engagements, agreeing a success metric in writing before any build, and converting proven results into signed, renewable commercial agreements. - Navigate multi-stakeholder enterprise cycles, mapping and engaging the technical, commercial, financial, and privacy/governance stakeholders — surfacing the governance stakeholder early, since privacy clearance is the most common silent deal-killer. - Explain the Compute-to-Data clean-room architecture credibly to both business and technical/legal audiences: raw PII never leaves the room; only mathematical scores do. - Defend the deal against the status quo (in-house 1P data, DIY clean rooms) and against competitors (e.g. VideoAmp, iSpot), using a discovery-first, methodology-based approach rather than feature claims. - Position sports and other strategic-wedge accounts for their downstream pull-through value, not just their standalone revenue. - Interpret internal and external business issues and recommend best practices; solve complex problems by taking a broad perspective to identify innovative solutions. - Work independently, with guidance only in the most complex situations; may lead functional teams or projects. - Recognized for deep expertise in a specific discipline or function, solving complex problems and guiding project teams or functional processes. - For employees outside India and the United States: willingness to serve as a local internal subsidiary director to represent the entity in-country, with full support from corporate teams, in governance matters. Now Qualifications: list after "Qualifications". Let's extract each bullet: - 10–15 years in a consultative sales, pre-sales, or solutions-consulting capacity, with recognized expertise in data clean rooms, identity resolution, and privacy-safe data matching and analytics. - Proven track record selling data, identity, measurement, or analytics solutions into media, streaming, advertising, or agency accounts. - Familiarity with technologies like Snowflake clean rooms, Amazon Web Services infrastructure, Structured Query Language, identity resolution, and platforms like Live Ramp - Proven experience commercializing sophisticated identity and data enrichment solutions; specific familiarity with Respondent Level Data (RLD), first-party data integrations, and bi-directional audience expansion methodologies is highly advantageous. - Strong consultative selling skills; able to open a credible conversation with a buyer before knowing exactly which use case will land, and to translate a business question into a technical use case. - Comfort explaining technical concepts — data clean rooms, identity resolution, privacy-safe matching, predictive scoring at scale — to both business and technical stakeholders. - Experience navigating multi-stakeholder enterprise sales cycles, including engaging privacy/legal/governance stakeholders as a precondition to closing. - Familiarity with the media measurement and ad-tech landscape (linear, streaming, digital, audio) is strongly preferred, including awareness of the competitive set and how to differentiate on methodology. - Communicates complex concepts; anticipates potential objections and influences others to adopt a different point of view. - Leads others to solve complex problems; uses analytical thinking, tools, and judgement to identify innovative solutions. - Requires depth and/or breadth of expertise in their own specialized area and general knowledge of related areas. - Impacts the achievement of customer, operational, project, or service objectives; work is guided by department objectives. - Bachelor's degree or equivalent experience; advanced degree or specialized certifications strongly preferred. Now Skills: Could be overlapping with qualifications but we can create a Skills section pulling out skill-related statements: maybe "Strong consultative selling skills; able to open a credible conversation..." etc. But we already have those in qualifications. To avoid duplication, maybe we don't need a separate Skills section if content is thin. However the instruction says prefer few substantive sections over many thin ones. We could omit Skills if it's not distinct. But we have skill statements in qualifications; we could keep them there. However we need to decide: Should we create Skills section? The posting includes "Strong consultative selling skills; able to open a credible conversation..." etc. That's skill. But we already have it in qualifications list. If we create Skills, we would duplicate. Better to not create Skills unless there is explicit separate skills list. There isn't. So we omit Skills. Benefits: from Additional Information: "Holistic Rewards: We are committed to an inclusive benefits package that supports our employees and their families. This includes comprehensive health and wellness plans, a 401(k) with a Nielsen company match, and a generous paid time off policy. Depending on the role, additional benefits may include a company-provided vehicle and/or discretionary incentive/bonus eligibility." We should keep that as Benefits. Pay: from Compensation Transparency paragraph. Now we need to ensure we don't include any boilerplate like "Enabling your best to power a better media future." That's part of Additional Information but it's also maybe part of benefits? It's a tagline; we could include it in Benefits paragraph as it's part of the same block. It's not boilerplate; it's part of the description. We'll keep. Now produce HTML. We need to wrap each section in

heading then content. For lists, use

• items. For prose, use

  . Let's craft. About the role: combine the two paragraphs into maybe two

  elements or one. We'll do two

  for readability. Responsibilities:

  with each bullet as
  • . Qualifications: similarly. Benefits:

    with the benefits text. Pay