Senior AI Growth Enginer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to include sections only when posting has real specific content. We have content about role summary, responsibilities, desired traits (skills/qualities), physical demands, compensation (pay). No explicit benefits or schedule. So we can have sections: About the role (maybe using the "About MISUMI Americas" and role summary). Responsibilities (list of duties). Requirements/Qualifications/Skills (desired traits). Pay (compensation range). Possibly Physical Demands could be part of Requirements? But we have a specific heading for Physical Demands not in list; but we can either omit or include as a separate section? The instruction says use headings from list; we should not create other headings. So we need to map content to those headings. Physical Demands could be placed under Requirements or maybe omitted? But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could put under a Requirements
and include physical demands as a paragraph. Or we could create a Skills
for desired traits, and Requirements
for physical demands. But we need to decide.
We have sections: About the role (intro + role summary). Responsibilities (list). Requirements (physical demands). Skills (desired traits). Pay (compensation). Benefits? none. Schedule? none.
We must not include headings with filler text. So we will output:
About the role
... (combined About MISUMI Americas and role summary)
Responsibilities
- ... each bullet
Requirements
Physical demands: ... (the paragraph)
Skills
- ... each desired trait bullet
Pay
The compensation range for this position is $180,000 - $215,000 USD based on experience
We must not include boilerplate like EEO, navigation, etc. Also remove duplicated lines. Ensure we preserve all substantive info. Now extract content. About MISUMI Americas paragraph: "MISUMI Americas, a division of MISUMI Group, is a leading provider of standard, configurable, and custom manufacturing solutions. By integrating a vast catalog of components with a world-class digital manufacturing platform, MISUMI Americas empowers engineers and procurement teams to accelerate innovation across the entire product lifecycle. With operations in the San Francisco Bay Area and Chicago, the company serves as a vital partner for the most innovative companies in the Americas." Role Summary: "Objective / Purpose of the Position The Senior AI Growth Engineer builds the systems that power customer acquisition at MISUMI Americas. This is a builder role: the person who designs and ships the automated, AI-driven acquisition infrastructure — audience models, enrichment pipelines, personalization logic, and multi-touch campaign automation — that the demand generation function runs on." Combine into one paragraph maybe two sentences. Responsibilities bullet list: Under "Areas of Responsibility: Essential Functions" we have several paragraphs each starting with a bold heading? Let's extract: - Acquisition Systems & Automation: Design, build, and maintain automated acquisition systems — including AI-driven outbound (e.g. AI SDR workflows), enrichment pipelines, lead routing, and lifecycle automation. Build personalization logic for inbound and outbound programs, driven by audience segments, behavioral signals, and lifecycle stage, and operate it at scale. Instrument and integrate the acquisition stack — CDP, marketing automation, CRM, and experimentation tooling — so data and triggers flow reliably across systems. - Segment & Audience Intelligence: Mine quantitative and qualitative data to identify high-propensity customer segments, and build the models that score and prioritize acquisition targets. Leverage AI and automation to enrich audience profiles, including data append, third-party signal aggregation, and web scraping where appropriate. - Campaign Architecture & Experimentation: In partnership with the Director of Demand Generation and Director of Lifecycle Marketing, translate pipeline goals into automated campaign workflows spanning acquisition, onboarding, and account graduation. Build the experimentation infrastructure that lets the team test messaging, offers, and channel mix, and turn winning pilots into evergreen, automated motions. Build and maintain reporting dashboards that surface funnel performance, segment health, and campaign attribution for stakeholders. - Cross-Functional Collaboration: Partner with the Director of Demand Generation and Director of Lifecycle marketing — building the platforms that the demand generation function operates. Partner with the data and analytics team to access, clean, and model the data required for segmentation and measurement. Collaborate with marketing operations, product marketing, and sales to align systems to messaging, territory, and outbound priorities. We need each asunder Requirements. Compensation: "The compensation range for this position is $180,000 - $215,000 USD based on experience" We'll put under Pay. Now ensure no duplicate lines. Also remove "We’re actively seeking teammates who: Bring diverse perspectives and experience to our culture and company. Excel at being part of a strong, empathetic team.Thrive in an environment emphasizing respect, honesty, collaboration, and growth.Have an ‘always learning’ mindset that celebrates learning, not just wins. Help us continue to build a world-class organization that values the contributions of all of our teammates". This is also substantive? It's about culture; maybe could be considered part of About the role or Skills? But it's not under a heading; it's generic culture statement. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include it somewhere. Could be placed under About the role as additional paragraph. It's not boilerplate; it's about company culture. So we should include it. Thus after About the role paragraph, add another paragraph with that culture statement. Now check for any other boilerplate: "We encourage applications from members of underrepresented groups, including but not limited to women, members of the LGBTQ community, people of color, people with disabilities, and veterans." This is EEO boilerplate, should be removed. Also "Physical Demands" heading we are not using as heading; we put content under Requirements. Now produce HTML. Let's craft.
About the role
MISUMI Americas, a division of MISUMI Group, is a leading provider of standard, configurable, and custom manufacturing solutions. By integrating a vast catalog of components with a world-class digital manufacturing platform, MISUMI Americas empowers engineers and procurement teams to accelerate innovation across the entire product lifecycle. With operations in the San Francisco Bay Area and Chicago, the company serves as a vital partner for the most innovative companies in the Americas.
The Senior AI Growth Engineer builds the systems that power customer acquisition at MISUMI Americas. This is a builder role: the person who designs and ships the automated, AI-driven acquisition infrastructure — audience models, enrichment pipelines, personalization logic, and multi-touch campaign automation — that the demand generation function runs on.
We’re actively seeking teammates who: Bring diverse perspectives and experience to our culture and company. Excel at being part of a strong, empathetic team. Thrive in an environment emphasizing respect, honesty, collaboration, and growth. Have an ‘always learning’ mindset that celebrates learning, not just wins. Help us continue to build a world-class organization that values the contributions of all of our teammates.
Responsibilities
- Acquisition Systems & Automation: Design, build, and maintain automated acquisition systems — including AI-driven outbound (e.g. AI SDR workflows), enrichment pipelines, lead routing, and lifecycle automation. Build personalization logic for inbound and outbound programs, driven by audience segments, behavioral signals, and lifecycle stage, and operate it at scale. Instrument and integrate the acquisition stack — CDP, marketing automation, CRM, and experimentation tooling — so data and triggers flow reliably across systems.
- Segment & Audience Intelligence: Mine quantitative and qualitative data to identify high-propensity customer segments, and build the models that score and prioritize acquisition targets. Leverage AI and automation to enrich audience profiles, including data append, third-party signal aggregation, and web scraping where appropriate.
- Campaign Architecture & Experimentation: In partnership with the Director of Demand Generation and Director of Lifecycle Marketing, translate pipeline goals into automated campaign workflows spanning acquisition, onboarding, and account graduation. Build the experimentation infrastructure that lets the team test messaging, offers, and channel mix, and turn winning pilots into evergreen, automated motions. Build and maintain reporting dashboards that surface funnel performance, segment health, and campaign attribution for stakeholders.
- Cross-Functional Collaboration: Partner with the Director of Demand Generation and Director of Lifecycle marketing — building the platforms that the demand generation function operates. Partner with the data and analytics team to access, clean, and model the data required for segmentation and measurement. Collaborate with marketing operations, product marketing, and sales to align systems to messaging, territory, and outbound priorities.
Requirements
The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee routinely is required to sit; walk; talk and hear; use hands to keyboard, fingers, handle, and feel; stoop, kneel, crouch, twist, crawl, reach, and stretch.
Skills
- Systems thinker with a builder’s bias — defaults to automating a problem rather than executing it manually.
- Intellectually curious and analytically rigorous, comfortable in ambiguous, data-rich environments.
- Entrepreneurial, with a bias toward testing, iteration, and measurable outcomes.
- Excellent communicator, able to translate technical systems into narratives that both technical and non-technical stakeholders can act on.
- Thrives in a fast-paced, high-growth environment.
Pay
The compensation range for this position is