Implementation Engineer (Remote)
Tealium · United States · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Who We Are", "What We Are Looking For", "YOUR DAY TO DAY", "What You Bring To Tealium", "Wage Transparency", "Benefits", "Compensation Range", "WHY YOU WANT TO WORK HERE". We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings if they match content? The instruction: "use
.
What You Bring To Tealium: list of qualifications/experience/skills.
Wage Transparency: includes statement about pay range and benefits.
Benefits: detailed list.
Compensation Range: "$85,000 - $110,000 Base + Bonus"
WHY YOU WANT TO WORK HERE: culture/benefits description.
We need to avoid duplication: Benefits and WHY YOU WANT TO WORK HERE overlap (volunteer hours, etc). We'll combine into Benefits section maybe.
We must not include "Wage Transparency" heading; we can incorporate into Benefits and Pay.
We need to output:
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings if they match content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if appropriate, but we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we map content to those standard headings. However we must include a section ONLY when posting has real, specific content for it. So we need to decide which sections apply.
We have content: "Who We Are" could be "About the role"? Actually "About the role" is more about the job. "Who We Are" is company overview. Could be considered "About the role"? Not exactly. But we could treat "Who We Are" as "About the role"? Might be okay. However instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map:
- About the role: maybe combine "Who We Are" and "What We Are Looking For"? Actually "What We Are Looking For" describes the role. Could be "About the role". We'll put a brief paragraph summarizing role.
- Responsibilities: from "YOUR DAY TO DAY" bullet points.
- Requirements/Qualifications/Skills: from "What You Bring To Tealium". Could split into Requirements (experience), Qualifications (education?), Skills (technical). But we can combine into one section maybe "Requirements". However instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also "Why you want to work here" could be part of Benefits? But it's more culture. Could be a separate section "Why you want to work here" but not in list. However instruction says use those example headings; but not strictly limited? It says use for section headings (e.g. About the role...). Likely they want us to use those headings where applicable. We could add a section "Why you want to work here" as a heading but not in the list; but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those.
Thus we need sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? Could split Requirements into Requirements and Skills. But we can combine.
We must not include headings with filler text. Ensure we have substantive content.
We must remove boilerplate: navigation, legal, EEO, etc. At end there is EEO statement; we must remove.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Who We Are: paragraph about Tealium.
What We Are Looking For: description of Implementation Engineer role.
YOUR DAY TO DAY: list of responsibilities (bulleted sentences). We'll convert each sentence to
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we map content to those standard headings. However we must include a section ONLY when posting has real, specific content for it. So we need to decide which sections apply.
We have content: "Who We Are" could be "About the role"? Actually "About the role" is more about the job. "Who We Are" is company overview. Could be considered "About the role"? Not exactly. But we could treat "Who We Are" as "About the role"? Might be okay. However instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map:
- About the role: maybe combine "Who We Are" and "What We Are Looking For"? Actually "What We Are Looking For" describes the role. Could be "About the role". We'll put a brief paragraph summarizing role.
- Responsibilities: from "YOUR DAY TO DAY" bullet points.
- Requirements/Qualifications/Skills: from "What You Bring To Tealium". Could split into Requirements (experience), Qualifications (education?), Skills (technical). But we can combine into one section maybe "Requirements". However instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also "Why you want to work here" could be part of Benefits? But it's more culture. Could be a separate section "Why you want to work here" but not in list. However instruction says use those example headings; but not strictly limited? It says use for section headings (e.g. About the role...). Likely they want us to use those headings where applicable. We could add a section "Why you want to work here" as a heading but not in the list; but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those.
Thus we need sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? Could split Requirements into Requirements and Skills. But we can combine.
We must not include headings with filler text. Ensure we have substantive content.
We must remove boilerplate: navigation, legal, EEO, etc. At end there is EEO statement; we must remove.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Who We Are: paragraph about Tealium.
What We Are Looking For: description of Implementation Engineer role.
YOUR DAY TO DAY: list of responsibilities (bulleted sentences). We'll convert each sentence to
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. So we should map content to those. Thus we need sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? Could split Requirements into Requirements and Skills. But we can combine. We must not include headings with filler text. Ensure we have substantive content. We must remove boilerplate: navigation, legal, EEO, etc. At end there is EEO statement; we must remove. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Who We Are: paragraph about Tealium. What We Are Looking For: description of Implementation Engineer role. YOUR DAY TO DAY: list of responsibilities (bulleted sentences). We'll convert each sentence to
About the role
... (combined Who We Are + What We Are Looking For)
Responsibilities
- ... ...
Requirements
... (experience, skills, etc)
Benefits
- ... ...
Pay
Compensation range: $85,000 - $110,000 base + bonus (actual offer may vary based on job-related knowledge, skills, and experience).
We should also include note about bonus and stock options, etc. Let's extract details. From Benefits paragraph: "In addition to a competitive base salary, this position is eligible for a robust benefits package that includes the following: Employees are eligible to receive an annual bonus and stock options. Employees and their families are eligible for medical, dental, vision, life, and disability insurance. Employees have the option to enroll in our 401k plan and are eligible to receive contributions for company matching. Employees are eligible for flexible paid time-off and extended paid parental leave. We offer 11 paid holidays annually with an additional Healium Be-Well break for most employees. We offer 15 hours of paid work time for volunteer activities and programs. Our sick leave accrual is the following for our employees: Exempt CA employees (not including San Francisco) including NY : accrue 40 hours each year. Unused sick leave carries over into the next year. Employees cannot exceed 80 hours in a given year. Exempt Non - CA employees (not including NY) including SF: Accrue 1 hour every 30 hours worked. Cannot exceed 180 hours in the calendar year. Non-Exempt: accrue 1 hour every 30 hours worked. Unused carries over to the next year. Not to exceed 108 hours in a calendar year. An overview of our benefits and perks can be found on our careers page, https://tealium.com/careers/. Additional details regarding the benefits package will be provided during your interview process." Also WHY YOU WANT TO WORK HERE includes many culture items: Tealium WOWs, Mosaic, Tealium Cares (volunteer), Tealium Connects (remote-first), Tealium Ownership (equity grants), Tealium Time (PTO), Healium (wellness), Tealium LIFT (learning), Health and Related Benefits Programs. We can incorporate those into Benefits section as bullet points. We must not invent info; just restate. Now Responsibilities: list from "YOUR DAY TO DAY". Let's extract each sentence: - Proactively support customer adoption, expansion, and technical success across proof of value, implementation, and forward-deployed engagements. - Collaborate with customers, account teams, and partners to design and implement end-to-end solutions that connect data collection, enrichment, activation, and measurement to clear business and AI-driven outcomes - Lead discovery and solutioning sessions to clarify goals, validate feasibility, assess customer architectures and implementation maturity, and identify technical risks, adoption blockers, optimization opportunities, and new use cases. - Serve as a trusted technical advisor to customer stakeholders, translating complex technical concepts across data, marketing, IT, and emerging AI-focused use cases in a clear and actionable way - Leverage AI tools and modern workflows (including code assistants, automation, and analytics copilots) to accelerate implementation delivery, improve solution quality, and surface insights more efficiently - Use SQL, data analysis, visualization, and AI-assisted analytics to validate data quality, identify patterns, and generate scalable, customer-ready insights and recommendations - Troubleshoot complex technical issues across JavaScript tags, APIs, SDKs, integrations, and data pipelines, using both traditional debugging methods and AI-assisted diagnostic approaches to accelerate resolution - Support proof of value and expansion opportunities by identifying technical requirements, validating solution fit, documenting key decisions and next steps, and applying deep expertise in Tealium’s solutions across customer engagements. - Identify, evaluate, and implement AI-enabled and modern tooling opportunities to improve implementation efficiency, reduce manual effort, accelerate time-to-value, and optimize delivery outcomes at scale. - Act as a bridge between technical execution and business outcomes, ensuring every implementation is tied to measurable customer value and long-term success Now Requirements: from "What You Bring To Tealium". Let's extract bullet-like sentences (they are separated by periods). We'll combine into a paragraph or list? Since we need- for any list of duties/requirements/benefits. So we should make a list for requirements. List items: - Experience working with Tealium products and solutions is strongly preferred. - 3+ years of experience in client-facing technical roles such as implementation, solutions consulting, technical support, or customer-facing engineering within a SaaS, digital technology, martech, or data environment. - Strong experience in troubleshooting and resolving technical issues related to tagging, APIs, SDKs, integrations, data discrepancies, and front-end implementations in complex customer environments - Deep familiarity with digital marketing technologies, tag management, customer data platforms, digital analytics, and data/AI-driven workflows across web, mobile, and connected applications - Demonstrated ability to leverage AI-powered tools and modern workflows (e.g., code assistants, analytics copilots, automation tools) to accelerate debugging, improve solution quality, and increase delivery efficiency - Strong written and verbal communication skills in English are required; Spanish language proficiency is a plus. - Proficiency with SQL and data analysis to validate implementations, assess data quality, identify issues, and generate actionable customer insights and recommendations - Expert in JavaScript, HTML, CSS, Python, JS frameworks, and experience in mobile frameworks or other coding languages. - Strong written and verbal communication skills, with the ability to clearly explain technical concepts to both technical and non-technical stakeholders. - Ability to lead customer-facing discussions, manage expectations, navigate escalated issues, and collaborate effectively across internal teams, partners, and customers. - Demonstrated ownership mentality with the ability to independently manage customer expectations, drive issue resolution, and execute without heavy reliance on program or project management support. - Data-driven mindset with the ability to make decisions grounded in analysis, measurement, and customer impact - Continuous learner with a strong interest in emerging technologies, especially AI-enabled tooling and modern implementation practice. - Ability and willingness to travel approximately 20% to support customer engagements, onsite meetings, and other business needs. Note there is duplication of communication skills; we can keep one. Now About the role: combine Who We Are and What We Are Looking For. Who We Are paragraph: "Tealium is the trusted leader in real-time Customer Data Platforms (CDP), helping organizations unify their customer data to deliver more personalized, privacy-conscious experiences. As the demand for connected, intelligent customer engagement grows, Tealium’s leadership in CDP is translating directly into leadership in enabling enterprise AI strategies. By providing clean, consented, and actionable data, Tealium empowers its customers to accelerate the adoption of AI and machine learning, fueling smarter personalization, predictive insights, and business outcomes at scale. More than 800 leading global brands trust Tealium to power their customer data strategies and deliver real-time, personalized experiences at scale. Team Tealium has team members present in nearly 20 countries worldwide, serving customers across more than 30 countries. We win together with respect and appreciation for the talents required of all positions and the people who contribute to each of these. We are intentional about our WOWs (Ways of Work)