Jobs · Business Development · New York

Sales Assistant (Hybrid)

Penguin Random House · New York, NY · 1 wk ago
Business Development$55k/yrFull-time
The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it properly. First, I need to identify the sections: - Company Description (but this is boilerplate about the company, not specific to the role) - Job Description (this has the role overview) - Specific responsibilities (list of duties) - Qualifications (list of requirements) - Additional Information (contains hybrid schedule, salary, benefits, application deadline, EEO, etc.) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists - Use

    for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no html/body, no markdown code fences Let me parse the content: The posting has: 1. Company Description - generic company info, not role-specific. Could be folded into a brief paragraph or omitted? The rule says "Preserve ALL substantive information" but also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered boilerplate? But it's part of the posting. However, the rule says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Company description is not minor metadata. But it's generic. I think I should include it as a brief paragraph under "About the role" or "Company Description" heading? The allowed headings include "About the role". I could have an "About the role" section that includes the job description paragraph and maybe company description. 2. Job Description paragraph: "Penguin Random House is looking for an analytically minded Assistant to join the Online and Digital Sales team..." This is the role overview. 3. Specific responsibilities: bullet list. 4. Qualifications: bullet list. 5. Additional Information: contains hybrid schedule (1 day/week), salary ($55,000), benefits list, application deadline, EEO statements (boilerplate), GDPR disclosures (boilerplate), etc. I need to create sections only for real content. The posting clearly states: - Responsibilities (specific list) - Qualifications (specific list) - Schedule: hybrid, 1 day/week in office - Pay: $55,000 yearly - Benefits: listed (Medical, Dental, Vision, etc.) So I should have sections: About the role (or Job Description), Responsibilities, Qualifications, Schedule, Pay, Benefits. But note: "Prefer a few substantive sections over many thin ones." Could combine Schedule and Pay into one? But they are distinct. The rules list separate headings for Pay, Schedule, Benefits. I'll include them if they have real content. Also, the Additional Information includes application deadline and instructions (resume and cover letter). That's application instructions, which should be removed per "Remove ... application instructions". So drop that. EEO and GDPR disclosures are boilerplate, remove. Now, structure:

    About the role

    Penguin Random House is looking for an analytically minded Assistant to join the Online and Digital Sales team. This position reports to the Online and Digital Sales Director, supporting the sales managers responsible for selling Random House Adult titles to multiple online accounts including Amazon, Apple, Audible, Kobo, and Spotify. The Assistant will distribute sales reports corporately, track/analyze data, help the team prepare for various meetings, and act as a liaison between the sales managers, sales directors, and the publishers. They will be tasked with reading frontlist titles, asked to share their opinions on them, and sit in on both divisional book launch, strategy, and marketing meetings across many pre-eminent publishing divisions. A creative and strategic marketing instinct will be important when managing backlist merchandising packages across all book categories at Amazon and other online accounts. If you are a reader interested in book publishing and the evolving, fast-paced world of online/digital sales, this will be the perfect position for you! This NYC-based role is a hybrid position with in-office responsibilities for a minimum of one day a week in the office. We will consider candidates who can work from a commutable distance to our offices at 1745 Broadway, which includes the tri-state area (NJ, CT, & PA). The salary for this role is $55,000.

    But the salary and hybrid info are also in Additional Information. I'll keep them in About the role? Or separate sections. The rule says include Pay and Schedule sections if posting actually states them. The posting states salary in Job Description and again in Additional Information. It states hybrid schedule in Job Description and Additional Information. So I should create separate Pay and Schedule sections. But the About the role section already includes that info. To avoid duplication, I could keep the overview in About the role without salary/schedule details, and then have separate Pay and Schedule sections. However, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I must include all details. I can include the salary and schedule in both places? Better to have them in dedicated sections and maybe mention briefly in About the role. Let me read the Job Description paragraph again: it includes "This NYC-based role is a hybrid position with in-office responsibilities for a minimum of one day a week in the office. We will consider candidates who can work from a commutable distance to our offices at 1745 Broadway, which includes the tri-state area (NJ, CT, & PA). The salary for this role is $55,000." So that's part of the job description. I'll keep that in About the role, and also have separate Schedule and Pay sections for clarity? But that would duplicate. The rule says "never emit a heading followed by filler/placeholder text". If I create a Schedule section, I need to put the schedule details there. I could move the schedule details from About the role to Schedule section. But the About the role paragraph would then be missing that info. I think it's okay to have the schedule and pay in their own sections and not repeat in About the role. However, the job description paragraph is a cohesive block. I could keep the paragraph as is, and then have Schedule and Pay sections that repeat the info? That would be duplication. The rule doesn't forbid duplication, but it's not ideal. I'll include the schedule and pay details in the dedicated sections, and in About the role I'll keep the paragraph but maybe remove the salary and schedule sentences? But that would be summarizing away detail. The rule says "do NOT invent or summarize away detail." So I must preserve all details. I could keep the paragraph intact and also have separate sections with the same info. That preserves all details. But the user might not want duplication. However, the instruction is to reformat into clean semantic HTML. Typically, you'd have an overview and then separate sections for specifics. I'll keep the overview paragraph as is, and then have Responsibilities, Qualifications, Schedule, Pay, Benefits sections. The Schedule and Pay sections will contain the specific details (maybe more detailed from Additional Information). The Additional Information also says "The salary or salary range for this position is $55,000." and "This is a hybrid position, requiring approximately 1 day per week at our 1745 Broadway location." So I'll use those. Benefits: listed in Additional Information: "Full-time employees are eligible for our comprehensive benefits program. Our range of benefits include, but are not limited to, Medical/Prescription drug insurance, Dental, Vision, Health Care/Dependent Care Flexible Spending Account, Health Savings Account, Pre-Tax and Roth 401(k), Short and Long-Term Disability Insurance, Life/AD&D Insurance, Commuter Benefits, Student Loan Repayment Program, Educational Assistance & generous paid time off." That's substantive. Now, Qualifications section: the posting has "Qualifications Please apply if you meet the following minimum requirements:" then a bullet list. I'll use that. Responsibilities: "Specific responsibilities include:" then bullet list. Now, Company Description: It's a long paragraph about the company. Should I include it? The rule says "Preserve ALL substantive information". It is substantive about the company. But it's not about the role. Could be included in an "About the company" section? But the allowed headings don't include "About the company". The allowed headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the role" is there. I could include company description as a paragraph before the role description? But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid company description. However, the user might expect only role-related sections. The example headings include "About the role". I think I'll include a brief company description as a paragraph under "About the role" or maybe as a separate

    before sections? But the output should be HTML fragment with sections. I'll include a

    About the role

    and then a

    that includes the company description? That would be mixing. Better to have a separate

    Company Description

    ? Not in allowed list. The rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But it says "use

    for section headings (e.g. ...)". It doesn't forbid other headings. However, "Prefer a few substantive sections over many thin ones." Company description is thin? It's a long paragraph. But it's generic. I think I'll omit the company description because it's boilerplate about the company, not specific to the job. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered marketing boilerplate. But it's part of the posting. I'll include it as a paragraph under "About the role" maybe. Let me decide: I'll create an "About the role" section that includes the job description paragraph (which already describes the role). The company description is separate. I'll include it as a separate paragraph before the sections? But the output must be only HTML fragment. I could do:

    About the role

    Penguin Random House is the leading adult and children's publishing house in North America, the United Kingdom and many other regions around the world. In publishing the best books in every genre and subject for all ages, we are committed to quality, excellence in execution, and innovation throughout the entire publishing process: editorial, design, marketing, publicity, sales, production, and distribution. Our vibrant and diverse international community of nearly 300 publishing brands and imprints include Ballantine Bantam Dell, Berkley, Clarkson Potter, Crown, DK, Doubleday, Dutton, Grosset & Dunlap, Little Golden Books, Knopf, Modern Library, Pantheon, Penguin Books, Penguin Press, Penguin Random House Audio, Penguin Young Readers, Portfolio, Puffin, Putnam, Random House, Random House Children's Books, Riverhead, Ten Speed Press, Viking, and Vintage, among others.

    Penguin Random House is looking for an analytically minded Assistant to join the Online and Digital Sales team. This position reports to the Online and Digital Sales Director, supporting the sales managers responsible

Similar jobs

Sales Assistant

Robert HalfBaton Rouge, LA· 1 mo ago
Business Developmentapply on roberthalf.com

Sales Assistant

Compass Business Solutions, Inc.Markham, IL· 1 mo ago
Business Development$23–$25/hr

Sales Assistant

Ocean Drive MarketingCoral Gables, FL· 1 mo ago
Customer Serviceapply on gmail.com

Sales Assistant

DunelmGreenford, OH· 2 mo ago
Salesapply on dunelmcareers.com