Engineering Manager, Data Warehouse and Integrations
maybe under About the role? Actually "About The Role & Team" is a heading. We'll treat that as About the role. We need to include About the role content: description of team, what they own, recent work, lead a team of ~10 engineers, reporting to Head of Data Platform, stack, etc. Then Responsibilities: bullet list. Then Skills And Experience: bullet list (maybe separate Required and Nice to have). We'll combine into Requirements section? The instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Skills And Experience. Could map to Skills or Requirements. Probably use "Skills" heading for required skills, and maybe "Qualifications" for nice-to-have? But we should only include sections when posting has real specific content. We have both required and nice-to-have. Could combine into Skills (required) and maybe Qualifications (nice-to-have). But we need to avoid filler. Let's decide: Use "Skills" for required skills (2+ years leading engineers, 6+ years building backend, etc). Use "Qualifications" for nice-to-have (Snowflake, Temporal, advertising integrations). Or we could just have one "Skills" section containing both required and nice-to-have, but better to separate. Benefits: The posting lists many benefits: medical/dental/vision, 401k match, flexible time off, stipends, parental benefits, mental health, ESPP, etc. Also mentions competitive pay and benefits packages. So we should include Benefits section with bullet list. Pay: The posting includes salary ranges for various locations: Colorado, New York City, San Francisco Bay Area, California outside SFBA, Washington state. Also mentions eligibility for equity, benefits, other forms of compensation. So we have Pay info. Should we create a Pay section? Yes, because posting states them. We'll include Pay section with bullet list of ranges per location. Schedule: Not mentioned. No info about work hours, remote, etc. So we should not include Schedule heading. We must not include boilerplate like EEO, scam warning, etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "Amplitude is the leading AI analytics platform..." maybe that's company overview; but it's not under a heading. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive. However, we are to output only HTML fragment; we can include a
with that overview before headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other content outside headings. We can include a leading paragraph summarizing the company description. But we must not repeat job title as heading (the page already shows it). There's no job title given explicitly; but we can ignore. Thus structure:
Amplitude is the leading AI analytics platform, helping over 4,700 customers—including Atlassian, Burger King, NBCUniversal, and Square—build better products and digital experiences. With powerful AI Agents embedded across our platform, teams can analyze, test, and optimize user experiences faster than ever. Ranked #1 across multiple categories in G2’s Winter 2026 Report, Amplitude is the best-in-class solution for product, data, and marketing teams. Learn more at amplitude.com. As an organization, we deliver for our customers by living our values. We operate from a place of humility, take ownership of problems and successes, approach challenges with a growth mindset, and put our customers at the center of everything we do. Amplitude’s Commitment to Diversity Equity & Inclusion (DEI): Amplitude believes that diversity enables the creation of better products, improves the ability to solve complex problems, and drives more powerful solutions. We strive to create an environment of inclusion—one focused on psychological safety, empathy, and human connection—that will allow employees of all backgrounds to thrive.
ThenAbout the role
with content: The Data Warehouse and Integrations team owns how that data gets in and out — importing behavioral and customer data from cloud data warehouses like Snowflake, Databricks, and BigQuery, from cloud object storage like S3 and Azure Blob Storage, and pushing enriched event data back out to warehouses, object storage, streaming destinations, and downstream advertising and marketing platforms. That means batch and streaming pipelines moving billions of events a day, connections that have to keep working across dozens of customer-controlled systems, credentials and configuration that have to stay correct and secure, and latency and reliability targets that customers build their own pipelines on top of. Recent work includes launching new warehouse export destinations, migrating our import pipelines onto a durable workflow engine, building low-latency streaming export, and supporting cross-region and cross-cloud customer storage. You'll lead a team of around 10 engineers building this, reporting to our Head of Data Platform, and you'll be the person accountable for the roadmap, the reliability, and the growth of the people on it. The stack is Java, Temporal, Kafka, Kubernetes, Terraform, DynamoDB, S3, and Snowflake, running on AWS and GCP. ThenResponsibilities
with- items: Set the direction and roadmap for data import and export, with clear priorities and tradeoffs you can explain to engineers, PMs, and customers; Lead, coach, and grow a team of around 10 engineers — hiring, career development, feedback, and performance; Partner with your tech leads on architecture across ingestion, transformation, and delivery, without becoming the bottleneck for every decision; Own reliability, SLOs, and cost efficiency for pipelines customers depend on daily; Expand the set of destinations and sources we support, and make each new integration cheaper to build than the last; Work directly with Product, Design, and other Data Platform teams to ship end-to-end; Get involved personally in significant customer onboardings and escalations.
Then
Skills
(required) with bullet list: 2+ years leading engineers, as a manager or as a tech lead; 6+ years building backend, data, or infrastructure systems; Experience with data integration or pipeline work — ETL/ELT, data warehouses, streaming, or batch processing at scale; Comfortable with modern cloud infrastructure (Kubernetes, Kafka, S3 or equivalent object storage, Terraform); A track record of improving reliability, latency, or cost for systems in production; Clear communication with engineers and non-engineers alike, especially when something has gone wrong. ThenQualifications
(nice-to-have) bullet list: Experience with Snowflake, Databricks, BigQuery, or similar warehouses — as a builder or a heavy user; Experience with durable workflow engines such as Temporal; Experience with advertising or marketing platform integrations. ThenBenefits
bullet list: Excellent medical, dental and vision insurance coverages, with 100% employer-paid premiums for employee Medical, Dental, Vision on select plans; 401(k) retirement plan with an employer match of up to 1% of your eligible pay each pay period up to $2,000 annually; Flexible time off, paid holidays, and more; Generous stipends to spend on what matters most to you, whether that’s wellness (monthly), commuter transit/parking (monthly), learning and development (quarterly), new hire home office equipment, and much more; Excellent parental benefits including: 12 weeks of Paid Parental Leave, Carrot Fertility Benefits/Adoption/Surrogacy support, Back-up Child Care support; Mental health and wellness benefits including no cost employee access to Modern Health coaching & therapy sessions; Employee Stock Purchase Program (ESPP); Mentorship programs, management training, and wellness initiatives; Charitable giving grant and paid volunteer time off. We could also include "competitive pay and benefits packages" but that's covered. ThenPay
bullet list: Colorado range: $227,000 - $341,000 total target cash (inclusive of bonus or commission); New York City salary range: $254,000 - $381,000 total target cash (inclusive of bonus or commission); Salary range: $254,000 - $381,000 total target cash (inclusive of bonus or commission) for San Francisco Bay Area of California; California salary range: $227,000 - $341,000 total target cash (inclusive of bonus or commission) for California outside of the San Francisco Bay Area; Washington salary range: $227,000 - $341,000 total target cash (inclusive of bonus or commission) for Washington state; Eligible for equity, benefits and other forms of compensation. We should not include the Washington only unlimited PTO etc because that's benefits already covered; but we could add to Benefits if not duplicate. However the Washington only specifics: unlimited PTO, 10 to 13 holidays annually, medical dental and vision PPO and CDHP plans, company sponsored 401(k) retirement plan. Some of these are already covered in benefits (flexible time off, 401k match). Might be redundant but we can include as part of Benefits if we want to preserve all substantive info. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in the source. But we should avoid boilerplate duplication. The Washington only specifics are not boilerplate; they are location-specific benefits. We could add them to Benefits as extra bullets. But we already have flexible time off, paid holidays, etc. The Washington only specifics add unlimited PTO, 10 to 13 holidays annually (will vary), medical dental and vision PPO and CDHP plans, company sponsored 401(k) retirement plan. Since we already have generic 401(k) match, we could add note about Washington: unlimited PTO, 10-13 holidays, medical/dental/vision PPO/CDHP plans, company sponsored 401(k) retirement plan. Might be okay. We'll include them as separate bullet under Benefits. Now ensure we removed all boilerplate: EEO, scam warning, etc. Also removed "Other Fun Facts About Amplitude" maybe not needed as it's not under a heading but could be considered substantive? It's more fun facts; but we already have company overview. Might be okay to omit as it's not under a heading and could be considered extra but not required. The instruction says preserve ALL substantive information; but we can argue that fun facts are substantive. However they are not under a heading; but we could include them as a paragraph after company overview. However they include statements like "Our customers love us! They've said we're the #1 product analytics solution for 23 quarters in a row on G2." etc. That's substantive. Might be worth including. But we already have similar statement about ranked #1 across multiple categories in G2’s Winter 2026 Report. The fun facts add extra detail. To be safe, we could include a paragraph after the company overview that includes those fun facts. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a paragraph for fun facts is okay. But we must not include navigation/legal/EEO etc. The fun facts are not boilerplate. Let's include a short paragraph