Senior Customer Engineer - LATAM

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections if posting has real specific content. We have content for About the role (the paragraph after "About The Role"). Responsibilities list (bullet points). Requirements: we have "We're Looking For Someone Who Has ..." includes many bullet-like items. We need to parse them into list items. Also Skills maybe separate? The posting includes "Fluency in business and conversational Spanish and English." etc. Could treat as Requirements. Could also have Skills section for technical skills like SQL, dbt, Python, etc. But we can combine into Requirements. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have About the role content. Responsibilities content. Requirements/Qualifications content: the "We're Looking For Someone Who Has ..." list. Benefits content: "Benefits And Perks" list. Pay: not specified (no salary). So we should NOT include Pay section because no specific content. Schedule: not specified. So omit Pay and Schedule. We also have "About Mixpanel" and "About The Customer Engineering Team" but those are likely boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Mixpanel" and "About The Customer Engineering Team" might be considered company overview, not required. But they might be considered part of the posting; but the instruction says to preserve ALL substantive information; do NOT invent or summarize away detail. However earlier they said: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect only those headings. The "About Mixpanel" and "About The Customer Engineering Team" are not among those headings, so we should not output them as headings. Could we embed that content under a generic

without heading? The instruction: "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." It doesn't forbid other paragraphs without heading. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should only use those headings for sections. But we could still have

paragraphs without heading for other content like company overview. However they also said "Prefer a few substantive sections over many thin ones." Might be okay to include a brief intro paragraph before sections. But the instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output something like:

About Mixpanel ...

About The Customer Engineering Team ...

About the role

...

Responsibilities

...

Requirements

...

Benefits

...

We must not include Pay or Schedule. Now we need to extract the content. Let's parse the posting. First paragraph: "About Mixpanel Mixpanel is the leading product intelligence and analytics platform, trusted by more than 29,000 companies to help understand how people use the products they build. By combining powerful analytics with AI that knows your business, Mixpanel helps teams see what’s working, diagnose what’s not, and decide what to build next. Learn more at mixpanel.com." Second: "About The Customer Engineering Team Mixpanel's Customer Engineering teams are analytics consultants who embed themselves within our enterprise customer teams to drive business outcomes. We work with prospects and customers throughout the customer journey to understand what drives value, and serve as the technical counterpart to our Sales organisation to deliver on that value. You will partner closely with Account Executives, Customer Value Architects, Product, Engineering, and Support to successfully roll out self-serve analytics within our customers' organisations, help manage change, execute on technical projects and services that delight our customers, and ultimately drive ROI on the customer's Mixpanel investment." Third: "About The Role Our Customer Engineers are inquisitive, nimble, and able to clearly articulate the technical benefits and requirements of Mixpanel to developers and product managers, while also communicating the business value of our product to senior executives. In your first month, you'll become a Mixpanel expert—both in features and functionality as well as implementation. You'll shadow customer calls and demos with current Customer Engineers and Account Executives while learning to articulate our value proposition, and be trained on Mixpanel's internal systems and tools. Within your first three months, you'll be directly involved in deal cycles with Account Executives. You'll lead the technical qualification for customer use cases and deliver customised demos for prospects and existing customers, working directly with leadership at the prospect's organisation to understand business challenges that can be solved through an analytics platform. You'll also work with the prospect's business and technical teams to scope and execute proof-of-concept projects to establish Mixpanel's value—including consulting on data ingestion methods, overall architecture, success criteria, and rollout strategies for analytics tools across an organisation." Then Responsibilities list (bullet points). Let's extract each bullet: - Serve as a trusted technical advisor for prospects, providing strategic consultation on data architecture, governance, instrumentation, and business outcomes - Communicate and consult effectively at all levels of the customer's organisation to earn trust and influence buying decisions - Bridge the technical-business gap—working with senior stakeholders to define success for proofs-of-concept and ensuring successful execution and outcomes - Leverage your Mixpanel expertise and technical/consultative skills to impart best practices throughout proof-of-concept projects - Partner with Account Executives to drive revenue growth, serving as the key technical contact for customers - Partner with post-sales teams to ensure that pre-sales value propositions translate into tangible post-sales results - Develop relationships and uncover the needs of key technical stakeholders within your assigned book of business - Be the "Voice of the Prospect" by collecting feedback from potential Mixpanel customers and sharing it with the Product team Now "We're Looking For Someone Who Has" list. Let's extract each item: - Fluency in business and conversational Spanish and English. - The ability to communicate with stakeholders at all levels—from discussing APIs with developers to organisational efficiency with CIOs. - A demonstrated track record of qualifying and selling technical solutions to executive stakeholders - 6+ years of experience in a Software-as-a-Service Sales Engineering or related role - Experience in data querying, modelling, and transformation using tools such as SQL, dbt, Python, Business Intelligence platforms, or Product Analytics tools - Familiarity with databases and cloud data warehouses (e.g., Google Cloud, Amazon Redshift, Microsoft Azure, Snowflake, Databricks) - A successful record of experience in sales engineering, consulting, or technical project management - Excellent written, analytical, communication, and presentation skills - Strong process and project delivery discipline - Proficiency with AI tools such as Claude, Claude Code, Gemini - The ability to travel as needed Then "Bonus Points For" list: - Experience with value engineering frameworks: translating customer pain into quantified business outcomes, building ROI calculators, and leading executive-level value conversations tied to measurable KPIs - Exposure to product-led growth (PLG) environments and sales-assisted conversion motions - Background in high-growth SaaS environments (Series B–E or beyond) Now Benefits And Perks list: - Comprehensive Medical, Vision, and Dental Care - Mental Wellness Benefit - Generous Vacation Policy & Additional Company Holidays - Enhanced Parental Leave - Volunteer Time Off - Additional US Benefits: Pre-Tax Benefits including 401(K), Wellness Benefit, Holiday Break - please note that benefits and perks for contract positions will vary* We should keep the note? It's part of benefits. It's not boilerplate; it's a note. We'll include as a list item maybe. Now we need to decide sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits. Could we separate Skills from Requirements? The list includes both experience and skills. Could create Requirements for experience and qualifications, Skills for technical skills. But we have limited time; we can put all under Requirements. Or we could have Requirements for experience and qualifications, Skills for technical skills (SQL, dbt, Python, etc.) and maybe AI tools. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into Requirements. Thus we will have:

About the role

...

Responsibilities

...

Requirements

...

Benefits

...

We should not include Pay or Schedule. Now we need to ensure we preserve all substantive information. The About Mixpanel and About The Customer Engineering Team paragraphs: Should we include them? They are substantive but not under a heading. We could include them as

before the sections. That would preserve them. The instruction didn't forbid extra paragraphs. It only said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings or paragraphs. It said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies if we have a section heading, we should use

. It doesn't forbid other content. So we can include a brief intro

with those paragraphs. But we need to avoid duplication: The About Mixpanel and About The Customer Engineering Team are not duplicated elsewhere. We'll include them. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc. We must remove that. Also the "Why choose Mixpanel?" paragraph and culture values etc. That might be considered boilerplate? It's not exactly legal but could be considered company marketing. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Why choose Mixpanel?" and culture values might be considered substantive? However they are not under the prescribed headings. Could we include them as a

before sections? That would preserve them. But the instruction also says "Prefer a few substantive sections over many thin ones." Including many paragraphs may be thin. However they are substantive. But maybe they consider them as boilerplate? Not sure. The EEO statement is definitely boilerplate to remove. The "Why choose Mixpanel?" and culture values might be considered marketing fluff but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove marketing fluff. So we should keep them. Thus we will include after the initial company overview paragraphs maybe a paragraph about "Why choose Mixpanel?" and culture values. But we need to avoid duplication: The "About Mixpanel" already mentions 29,000 customers etc. The "Why choose Mixpanel?" repeats some of that. Might be duplication. The instruction says remove duplicated lines. So we should avoid duplicating same info. The "Why choose Mixpanel?" includes: "We’re a leader in analytics with over 29,000 customers and $277M invested from prominent investors: like Andreessen-Horowitz, Sequoia, YC, and, most recently, Bain Capital. Mixpanel’s pioneering event-based data analytics platform