Engineering Manager, Platform (Privy)

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who we are About Privy", "About The Team", "What you’ll do", "Who you are", "In-office expectations", "Pay and benefits". Also maybe "About Privy" etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The headings we can use must be from that list. We need to map content to appropriate headings. We have content: "Who we are About Privy" (mission, description). Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "What you’ll do" which is responsibilities. "Who you are" is qualifications/requirements. "In-office expectations" maybe schedule? Not exactly schedule but location expectations. Could be "Schedule"? Not really. "Pay and benefits" maps to Pay and Benefits sections. We also have "About Privy" and "About The Team" maybe could be "About the role"? But we should not repeat job title as heading. We can have sections: About the role (maybe combine Who we are About Privy and About The Team). Responsibilities (What you’ll do). Requirements (Who you are). Benefits (Pay and benefits). Possibly Schedule (In-office expectations). However schedule heading expects schedule details like remote/hybrid etc. The posting has in-office expectations: "Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users." That's schedule-ish. So we can put that under Schedule. We must not include headings with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Not present. We need to output only HTML fragment, no /. Use

for each section heading, then content in

or

• as appropriate. We need to preserve all substantive information. So we need to include details from each section. Let's extract content: Who we are About Privy: - Mission: make privacy and user ownership the default online. - Build simple, flexible APIs and tools for developers to build new products on crypto rails. - Privy owns abstractions and infrastructure layer above wallets, integrating across chains, third-party providers, and Stripe products like Treasury and Link. - Solve hard technical problems while leveraging Stripe's distribution to reach customers like Ramp, Klarna, Deel, Kraken, Hyperliquid, and Fomo — powering experiences for both mainstream users and crypto natives. About The Team: - Engineering at Privy distinguished by: - High urgency: Shipping very small iterations, very fast, to learn very quickly. - Product taste: Customers are developers; to build effective products requires technical knowledge - you will often be "the PM". - Security mindset: Great portion of product is trust; while dedicated security team, every engineer brings security to designs from start. - In practice, use boring technology like Node, React, and AWS so we can focus engineering energy on pushing boundaries of Privy's core product, e.g., through hardware enclaves, multi-region low latency APIs, and blockchain abstractions accessible to mainstream developers. What you’ll do (Responsibilities): - Lead Privy’s Wallet Platform team, a product-minded platform group building primitives and developer-facing surfaces behind Privy’s wallet product that helps users transact >$18B monthly. - Team works on deep wallet infrastructure like AWS Nitro Enclaves, to developer APIs, webhooks, and secure transaction submission. - Balance new capabilities with targeted reliability and scale work, setting technical direction while keeping team close to developer and customer experience. - Hands-on, TLM-shaped engineering management role. - Grow a small team, stay close to architecture and execution, help Privy make sound platform investments as product scales. - Set technical direction for platform capabilities that underpin Privy’s wallet product. - Drive four nines uptime and own reliability, performance, usability, and evolution of Privy’s wallet system. - Work directly with Product, Security, and other engineering teams to define durable interfaces and turn platform needs into clear roadmaps. - Build and ship systems in weeks that will last years. - Stay close to work by reviewing pull requests and design documents, helping scope technical initiatives, and stepping into complex technical problems. - Build a team culture that values technical rigor, ownership, urgency, and thoughtful operational practice. - Be a thoughtful people leader shaping careers, coaching your team and those around you, and learning from others invested in your success. Who you are (Requirements/Qualifications): - Strong ownership and care deeply about business impact. - Performance-oriented mindset and high bar for quality and excellence. - Deep backend or platform experience and can independently evaluate architecture, systems tradeoffs, and technical feedback. - Understand that a platform is a product. Can connect decisions about interfaces, reliability, performance, and migrations to developer, customer, and business outcomes. - Can set technical direction for a platform that must serve multiple product needs, while maintaining clear boundaries and a durable architecture. - Experience leading and developing engineers, and understand that strong management requires active practice. - Stay close to architecture and execution, including design reviews, code review, and complex technical decisions. - Comfortable working through ambiguity and balancing long-term platform foundations with immediate product needs. - Experience with wallet, custody, signing, crypto infrastructure, or consequential platform decision-making is a plus. In-office expectations (Schedule): - Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users. - This expectation may vary depending on role, team and location. - Example: Stripes in Stripe Delivery Center roles in Mexico City, Mexico; Bengaluru, India; and Dublin, Ireland work 100% from the office. - Some teams have greater in-office attendance requirements, to appropriately support users and workflows, which the hiring manager will discuss. - This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility when possible. Pay and benefits (Pay and Benefits): - Annual US base salary range for this role is $236,000 - $354,000. - For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. - This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. - Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process. - Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends. - At Stripe, we're looking for people with passion, grit, and integrity. You're encouraged to apply even if your experience doesn't precisely match the job description. Your skills and passion will stand out—and set you apart—especially if your career has taken some extraordinary twists and turns. - At Stripe, we welcome diverse perspectives and people who think rigorously and aren't afraid to challenge assumptions. Join us. Apply now. We need to remove application instructions? The last sentences about applying now maybe considered application instructions. The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove "Join us. Apply now." and maybe "You're encouraged to apply even if your experience doesn't precisely match the job description." That's application instructions. Also "At Stripe, we're looking for people with passion, grit, and integrity." That's maybe not application instruction but could be considered fluff. However it's part of benefits section? It's more like company culture. Might be okay to keep? The instruction says remove application instructions. The sentences about applying are definitely application instructions. Also "Join us. Apply now." is definitely application instruction. The earlier sentence "You're encouraged to apply even if your experience doesn't precisely match the job description." is also application instruction. We should remove those. Also "At Stripe, we welcome diverse perspectives and people who think rigorously and aren't afraid to challenge assumptions." That's not application instruction but could be considered EEO? It's about diversity, maybe considered EEO boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that line as well. Thus we need to keep only substantive content: pay, benefits, etc. The benefits list we can keep. Now we need to format. We'll have sections:

  About the role

  (maybe combine Who we are About Privy and About The Team). Could also split into two sections: About the company and About the team but headings limited to given list. We could use "About the role" for company/team description. Or we could have "About the role" and "Responsibilities", "Requirements", "Benefits", "Pay", "Schedule". But we must not create sections without real content. We have content for all. We need to decide which headings to use: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we have Requirements covering qualifications. We'll use Requirements. We need to ensure we don't repeat job title as heading. Not an issue. Now we need to output HTML fragment. We'll produce:

  About the role

  ... content ...

  But we have two paragraphs: mission/description and team attributes. Could combine into one

  with multiple sentences, or separate

  elements. Use

  for prose. We'll need to embed lists for bullet points. For team attributes we have bullet list; we can use

  • . Similarly for responsibilities we have many bullet-like sentences; we can use
    • . For requirements also bullet list. For benefits we have list. For schedule we have prose. For pay we have prose. Let's extract and format. About the role content: Mission: make privacy and user ownership the default online. Build simple, flexible APIs and tools for developers that make it easy to build new products on crypto rails. Privy owns the abstractions and infrastructure layer above wallets, integrating across chains, third-party providers, and Stripe products like Treasury and Link. We get to solve hard technical problems while leveraging Stripe's distribution to reach customers like Ramp, Klarna, Deel, Kraken, Hyperliquid, and Fomo — powering experiences for both mainstream users and crypto natives. Engineering at Privy is distinguished by: - High urgency: Shipping very small iterations, very fast, to learn very quickly. - Product taste: Our customers are developers, and to build effective products for them requires technical knowledge - you will often be "the PM". - Security mindset: A great portion of our product is trust. While we have a dedicated security team, every engineer brings security to their designs from the start. In practice, we use boring technology like Node, React, and AWS so we can focus our engineering energy entirely on pushing the boundaries of Privy's core product, e.g. through hardware enclaves, multi-region low latency APIs, and blockchain abstractions that are accessible to mainstream developers. We'll put that in

      for first paragraph, then

      • for the three bullet points. Responsibilities (What you’ll do): - Lead Privy’s Wallet Platform team, a product-minded platform group building the primitives and developer-facing surfaces behind Privy’s wallet product that helps our users transact more than $18B monthly. - The team works on everything ranging from deep wallet infrastructure like AWS Nitro Enclaves, to developer APIs, webhooks, and secure transaction submission. - You’ll balance new capabilities with targeted reliability and