Engineering Manager - Consumer Product (Event)

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About The Team, Why This Role Matters, What You’ll Do, What Success Looks Like, What We’re Looking For, What We Offer, Salary Range (Pay), Location (Schedule? Actually location/hybrid). We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly. We must not repeat job title as heading. No Job ID. Remove boilerplate (EEO, etc). No navigation/legal. No application instructions. We need to include sections only when posting has real specific content. So we need sections: About the Team (maybe map to About the role?), Why This Role Matters (maybe Responsibilities?), What You’ll Do (Responsibilities), What Success Looks Like (maybe Qualifications? Actually it's outcomes), What We’re Looking For (Requirements/Qualifications/Skills), What We Offer (Benefits), Pay (Salary Range), Schedule (Hybrid location info). Also maybe About the role could be a brief intro? The intro paragraph about StubHub mission could be considered About the role? But we should not repeat job title. Could create an

About the role

with the introductory paragraphs about StubHub mission and the role description? However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. We need to decide mapping. We have content: - Intro: StubHub mission, hiring an Engineering Manager to lead team responsible for performer landing and event selection experiences... This is a technical and commercial leadership role... Location: Hybrid (3 days in office/2 days remote) – New York City, NY - About The Team: description. - Why This Role Matters: description. - What You’ll Do: list of responsibilities (bullet points). - What Success Looks Like: description of outcomes. - What We’re Looking For: list of qualifications/experience. - What We Offer: list of benefits and compensation description. - Salary Range: $300,000—$400,000 USD. - Location/Hybrid: schedule info. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown fences. We'll produce something like:

About the role

StubHub is on a mission to redefine the live event experience on a global scale....

But we need to ensure we don't duplicate content. Let's craft. We'll include: - About the role: combine the introductory paragraph(s) about StubHub mission and the role overview (first two paragraphs before About The Team). Possibly also include location? But location maybe goes to Schedule. - Responsibilities: What You’ll Do (list). Could also include Why This Role Matters? Might be considered responsibilities as well. But we can keep Why This Role Matters as a separate section? Not in the list of allowed headings but we could map to Responsibilities or maybe "About the role". The instruction says use those headings as examples, not strictly limited to those. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings if needed? It says use those for section headings (e.g.) meaning those are typical; we can use them. Probably best to stick to those. Thus we need to map content to those headings. Let's map: About the role: Intro + maybe Why This Role Matters? Actually Why This Role Matters explains impact; could be part of About the role. Responsibilities: What You’ll Do (list). Requirements: What We’re Looking For (list of experience/skills). Could also include Qualifications. Qualifications: maybe same as Requirements; but we can combine. Skills: maybe technical skills from What We’re Looking For (AI, experimentation, etc). Could be separate but we might avoid thin sections. Benefits: What We Offer (benefits list). Pay: Salary Range. Schedule: Location/Hybrid info. We should not create thin sections; prefer few substantive sections. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have Requirements and Skills separate if substantive. Let's decide sections: - About the role (intro + Why This Role Matters) - Responsibilities (What You’ll Do) - Requirements (What We’re Looking For) - Benefits (What We Offer) - Pay (Salary Range) - Schedule (Hybrid location) That's six sections, each substantive. We must not include filler like "commensurate with experience". Not present. Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail. We need to convert bullet lists to

• . We need to keep the exact wording? Should preserve all substantive information; we can copy sentences. Let's gather text. Intro paragraphs: "StubHub is on a mission to redefine the live event experience on a global scale. Whether someone is looking to attend their first event or their hundredth, we’re here to delight them all the way from the moment they start looking for a ticket until they step through the gate. The same goes for our sellers. From fans selling a single ticket to the promoters of a worldwide stadium tour, we want StubHub to be the safest, most convenient way to offer a ticket to the millions of fans who browse our platform around the world. StubHub is hiring an Engineering Manager to lead the team responsible for the performer landing and event selection experiences used by millions of fans across web and mobile. This is a technical and commercial leadership role for someone who can turn customer insight and data into measurable business results, move quickly through ambiguity, and build a high-performing engineering team. You’ll own the quality and execution of highly visible consumer experiences while raising the bar across product thinking, experimentation, technical judgment, and talent. Location: Hybrid (3 days in office/2 days remote) – New York City, NY" We'll keep that for About the role (maybe exclude location line, which goes to Schedule). So we can keep location line out. Now "About The Team" paragraph: "The Consumer Experience (CX) team is responsible for the end-to-end product experience for fans looking to discover, buy, and sell tickets to their favorite live events through our web and mobile platforms. It sits at the forefront of fulfilling StubHub’s mission to become the global destination for accessing live event experiences by crafting the product experience that millions of fans interact with every day. Within CX, the Events team owns the critical moment when a fan moves from exploring performers, teams, and tournaments to selecting the right event. This is where curiosity becomes purchase intent. The team combines customer insight, thoughtful design, resilient engineering, ranking and personalization, and rapid experimentation to make event selection fast, relevant, and trustworthy—ultimately helping more fans find and attend the live experiences they love." We could include this in About the role as well, but we already have intro. Might be okay to add to About the role. "Why This Role Matters" paragraph: "You’ll lead one of StubHub’s most visible and commercially important consumer surfaces, serving as a major entry point for paid search, organic discovery, and other high-intent traffic. The product and technical decisions your team makes directly influence conversion, engagement, retention, and Gross Merchandise Sales by determining how effectively fans move from discovery toward purchase. This is a high-visibility role with end-to-end ownership, close partnership across Product, Design, and Data, and a direct connection between engineering decisions and business performance." We can include that in About the role as well. Now "What You’ll Do" list: - Drive measurable commercial impact: Identify high-leverage customer problems, define clear success metrics, and connect engineering investments to improvements in conversion, engagement, retention, and GMS. - Lead through experimentation: Partner with Product, Design, and Data to form hypotheses, deliver focused experiments, evaluate results rigorously, and use what you learn to launch, revise, or stop investments. - Create clarity and execute quickly: Turn ambiguous customer and business problems into focused plans, make sound decisions with incomplete information, remove blockers, and ensure commitments are delivered with urgency and quality. - Raise the bar on talent density: Hire exceptional engineers, establish clear expectations, coach performance directly, develop senior technical leaders, and make timely, principled decisions when performance does not meet the bar. - Own technical quality: Remain deeply engaged in system-design and code-review discussions, challenge architectural decisions, and guide tradeoffs across scalability, reliability, performance, security, and long-term maintainability. - Apply AI thoughtfully: Identify practical opportunities to use AI in customer experiences and engineering workflows while establishing appropriate evaluation methods, quality thresholds, and safeguards. - Partner across the business: Work as a true counterpart to Product, Design, Data, Marketing, and other engineering teams—bringing customer, commercial, and technical judgment to roadmap decisions rather than simply executing predefined requirements. We need to keep each bullet as
• . Now "What Success Looks Like" paragraph: "Measurable improvements in customer and commercial outcomes, including conversion, engagement, relevance, performance, reliability, and GMS. A consistent experimentation cadence that produces clear decisions and demonstrable customer learning. Fast, predictable delivery of high-quality initiatives tied to company objectives, including in situations where requirements or dependencies are initially unclear. Stronger system health and engineering quality, reflected in areas such as latency, availability, incident reduction, maintainability, and development velocity. A high-performing team with clear expectations, strong accountability, active coaching, growing technical leadership, and continuously improving impact per engineer." We could treat this as part of About the role or maybe as a separate section like "Outcomes". But we don't have a heading for outcomes; we could incorporate into About the role or Responsibilities? It's more about success metrics. Could be part of About the role. But we already have About the role with intro; adding this may be okay. Now "What We’re Looking For" list: - 7+ years of software engineering experience, including technical ownership of production systems and business-critical customer experiences. - 3+ years of direct people leadership experience, with meaningful ownership of hiring, coaching, performance reviews, promotions, performance improvement, and difficult talent decisions. - Experience leading engineering for consumer-facing web or mobile products where success was measured through commercial or customer outcomes such as conversion, revenue, retention, or engagement. - Strong technical judgment and recent experience participating in code reviews, system-design reviews, and architectural decisions; regular coding is not required. - Demonstrated success using experimentation, customer evidence, and data to make product and engineering investment decisions. - Proven ability to work from first principles, create direction without a complete playbook, prioritize ruthlessly, and deliver under tight timelines. - Experience applying AI to customer products or engineering workflows, with an understanding of quality evaluation, guardrails, and measurable impact. - A track record of building high-performing teams, delivering candid feedback, developing senior engineers, and holding a consistently high performance bar. Now "What We Offer" list: - Accelerated Growth Environment: An environment designed for swift skill and knowledge enhancement, where you have the autonomy to lead experiments and tests on a massive scale. - Top Tier Compensation Package: Competitive base, equity, and upside that tracks with your impact. - Flexible Time Off: Enjoy unlimited Flex Time Off, giving you the flexibility to manage your schedule and take time to recharge as needed. - Comprehensive Benefits Package: Prioritize your well-being with a comprehensive benefits package, featuring 401k, and premium Health, Vision, and Dental Insurance options. - The anticipated gross base pay range is below for this role. Actual compensation will vary depending on factors such as a candidate’s qualifications, skills, experience, and competencies. Base annual salary is one component of StubHub’s total compensation and competitive benefits package, which includes equity, 401(k), paid time off, paid parental