Martech/ Growth Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include headings for sections we have content. We can combine Requirements, Qualifications, Skills into one section maybe? The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Qualifications (combining Who You Are and What We're Looking For), Benefits, Schedule. Or we could have Requirements and Qualifications separate but that may be thin. Better to combine.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we should list each bullet as
- . For qualifications we can list bullet points. For benefits we list bullet points.
We need to use
for prose.
We must output only HTML fragment, no /, no markdown fences.
Let's extract content.
Company description: "Company Credit Genie is a mobile-first financial wellness platform designed to help individuals take control of their financial future. We leverage artificial intelligence to provide personalized insights and are building a financial ecosystem by offering tools and services that provide instant access to cash, and building credit. Our goal is to empower every customer to achieve long-term financial stability. Founded in 2019 by Ed Harycki, former Swift Capital Founder (acquired by PayPal in 2017). Backed by Khosla Ventures and led by industry pioneers from companies such as; PayPal, Square, and Cash App, we are well positioned to build the future of inclusive finance through cutting-edge technology and customer-centric solutions."
That's prose; we can put in a
maybe under a heading? The instruction says 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. There's no explicit heading for company overview; but we could include it as a
before sections. Since we need to preserve all substantive information, we should include that description. It could be placed as an introductory paragraph before any headings. That's fine.
Then About The Role heading: we have "About The Role" then paragraph: "We’re looking for a MarTech / Growth Engineer to sit at the intersection of Marketing, Engineering, Data, Product, and Operations. This is a hands-on engineering role focused on using technology to solve growth problems. You’ll own and evolve the technical infrastructure that powers customer acquisition, engagement, and retention across marketing data, attribution, lifecycle automation, experimentation, advertising platforms, and AI-powered workflows. You’ll be a hands-on builder, writing code, connecting APIs, designing data flows, automating workflows, implementing tracking, prototyping new capabilities, and shipping solutions directly. At the same time, you’ll need to understand the business problems behind the technology. You should be equally comfortable debugging an event payload, querying a funnel in SQL, implementing an API integration, and sitting with a marketer to figure out how to improve campaign performance. The goal is simple: make our growth organization dramatically more technical, automated, data-driven, and capable of moving faster."
We'll put that under
About the role
and then ... maybe multiple paragraphs but we can combine.
Then Responsibilities: "What You’ll Do" list bullet points. We'll create
Responsibilities
then with each bullet as - .
List items:
- Own the growth tech stack. Own and improve the platforms and infrastructure powering acquisition, attribution, lifecycle marketing, analytics, and experimentation.
- Build and own marketing data infrastructure. Design and maintain the pipelines that move customer data, identities, audiences, events, and conversions across our data and marketing ecosystem, ensuring data is accurate, reliable, and available where it’s needed.
- Automate growth operations. Apply strong engineering practices to eliminate manual workflows across marketing, reporting, campaign operations, QA, and experimentation.
- Build AI-native marketing capabilities. Embed AI into how Marketing operates, building agents and tools that can create, launch, optimize, and iterate on campaigns, not just analyze performance.
- Own attribution & measurement. Build and maintain conversion tracking across Meta, Google, TikTok, AppsFlyer, web, and mobile- including pixels, SDKs, server-side events, UTMs, and deep links.
- Enable lifecycle & experimentation. Build the data flows, triggers, audiences, and infrastructure that let teams launch sophisticated lifecycle programs and experiments quickly.
- Prototype growth ideas. Build landing pages, internal tools, scripts, automations, and lightweight product experiences to quickly test new opportunities.
- Turn data into action. Use analytics tools to diagnose funnels, measure experiments, identify opportunities, and improve growth performance.
- Explore emerging technology. Continuously test new AI, MarTech, advertising, and developer tools and bring the highest-leverage capabilities into our stack.
Now Qualifications/Requirements/Skills: combine "Who You Are" and "What We're Looking For" and maybe "Bonus Points". We'll create
Qualifications
then list bullet points.
From Who You Are:
- You’re a builder. You can write code, work with APIs, query data, debug integrations, and ship solutions independently.
- You understand growth. You’re comfortable with acquisition, conversion, retention, lifecycle marketing, experimentation, attribution, and marketing ROI.
- You’re comfortable across the stack. You don’t need to be the world's best mobile, backend, data, and web engineer simultaneously, but you can navigate unfamiliar systems and figure out how the pieces connect.
- You think in systems. You understand how advertising platforms, attribution, identity, event pipelines, warehouses, analytics, and lifecycle platforms fit together.
- You automate repetitive work. When you see a manual process, your instinct is to figure out how software can do it better.
- You move quickly. You know when something needs production-grade architecture and when a prototype is enough to validate an idea.
- You’re cross-functional. You can translate business problems into technical solutions and work effectively across Marketing, Product, Data, and Engineering.
From What We’re Looking For:
- 6+ years in growth engineering, MarTech engineering, data engineering, software engineering, or a similarly technical role.
- Strong TypeScript or Python and SQL skills.
- Experience building with APIs, webhooks, SDKs, and event-driven systems.
- Hands-on experience with several modern MarTech/data platforms such as Segment, Hightouch, Braze, Amplitude, AppsFlyer, Snowflake, GA4/GTM, Meta CAPI, Google Ads, or TikTok Events API.
- Understanding of event instrumentation, identity, attribution, conversion tracking, experimentation, and data quality.
- Experience using LLMs, agents, AI coding tools, or workflow automation to build real-world solutions.
- Ability to take ambiguous problems from idea → solution → implementation → measurement.
Bonus Points (we can include as bullet points under Qualifications as optional but still substantive):
- Experience working in a high-growth consumer business with significant paid acquisition spend.
- Experience in FinTech or another highly regulated industry.
- Experience with experimentation platforms, feature flags, or personalization systems.
- Experience building internal tools or data products for Marketing or Growth teams.
- Familiarity with privacy and consent requirements and how they affect advertising, analytics, and customer data infrastructure.
We'll include them as bullet points.
Now Benefits And Perks: we have a paragraph plus bullet list. We'll create Benefits
then maybe a intro then
list.
Intro paragraph: "Our goal is to provide a comprehensive offering of benefits and perks that promote better financial, mental, and physical wellness. We believe working alongside each other in person is the best way to build a great product and foster a strong company culture. Our expectation is that employees are in the office five days a week, allowing for optimal collaboration, inclusivity, and productivity. At the same time, we understand that life happens and recognize the importance of flexibility. We are committed to supporting our employees when circumstances arise that require remote work or adjusted schedules. Our goal is to ensure everyone can effectively balance personal and professional responsibilities while maintaining our collaborative and productive environment."
But schedule info is part of this paragraph; we might separate schedule into its own section. However the rule: include a section ONLY when posting has real, specific content for it. We have schedule info: expectation of in-office five days a week, flexibility for remote work or adjusted schedules. That's specific. So we could make a Schedule section with that info. Then Benefits section would focus on benefits list.
Thus we split: Benefits section: list of benefits.
Benefits list:
- 100% company-paid medical, dental, and vision coverage for you and your dependents on your first day of employment.
- Receive up to $100 per month in fitness reimbursement or enjoy a complimentary full membership to LifeTime Fitness or Equinox.
- 401(k) with a 3.5% match and immediate vesting
- Meal program available for both lunch and dinner
- Pre-tax benefits, including a $1,000 HSA match
- Life and accidental insurance
- Flexible PTO
- You will also have access to comprehensive medical, vision, and dental coverage, a 401(k) retirement plan with company match, short & long term disability insurance, life insurance, and flexible PTO along with many other benefits and perks.
Note some duplication; we can keep but maybe combine. We'll keep unique items.
Now Schedule section: Schedule
then with the schedule info: "Our expectation is that employees are in the office five days a week, allowing for optimal collaboration, inclusivity, and productivity. At the same time, we understand that life happens and recognize the importance of flexibility. We are committed to supporting our employees when circumstances arise that require remote work or adjusted schedules. Our goal is to ensure everyone can effectively balance personal and professional responsibilities while maintaining our collaborative and productive environment."
We should not include the earlier generic benefits paragraph that mentions schedule; we removed that.
Now we need to include the company description paragraph at top (no heading). Then About the role heading etc.
We must not include boilerplate like EEO, equal opportunity, accommodations, etc. Remove those.
Now ensure we don't repeat job title. Not present.
Now output HTML fragment.
Let's craft.
We'll start with a
for company description.
Then
About the role
...
Then Responsibilities
...
Then Qualifications
...
Then
for prose. We must output only HTML fragment, no /, no markdown fences. Let's extract content. Company description: "Company Credit Genie is a mobile-first financial wellness platform designed to help individuals take control of their financial future. We leverage artificial intelligence to provide personalized insights and are building a financial ecosystem by offering tools and services that provide instant access to cash, and building credit. Our goal is to empower every customer to achieve long-term financial stability. Founded in 2019 by Ed Harycki, former Swift Capital Founder (acquired by PayPal in 2017). Backed by Khosla Ventures and led by industry pioneers from companies such as; PayPal, Square, and Cash App, we are well positioned to build the future of inclusive finance through cutting-edge technology and customer-centric solutions." That's prose; we can put in a
maybe under a heading? The instruction says 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. There's no explicit heading for company overview; but we could include it as a
before sections. Since we need to preserve all substantive information, we should include that description. It could be placed as an introductory paragraph before any headings. That's fine. Then About The Role heading: we have "About The Role" then paragraph: "We’re looking for a MarTech / Growth Engineer to sit at the intersection of Marketing, Engineering, Data, Product, and Operations. This is a hands-on engineering role focused on using technology to solve growth problems. You’ll own and evolve the technical infrastructure that powers customer acquisition, engagement, and retention across marketing data, attribution, lifecycle automation, experimentation, advertising platforms, and AI-powered workflows. You’ll be a hands-on builder, writing code, connecting APIs, designing data flows, automating workflows, implementing tracking, prototyping new capabilities, and shipping solutions directly. At the same time, you’ll need to understand the business problems behind the technology. You should be equally comfortable debugging an event payload, querying a funnel in SQL, implementing an API integration, and sitting with a marketer to figure out how to improve campaign performance. The goal is simple: make our growth organization dramatically more technical, automated, data-driven, and capable of moving faster." We'll put that under
About the role
and then... maybe multiple paragraphs but we can combine. Then Responsibilities: "What You’ll Do" list bullet points. We'll create
Responsibilities
then- with each bullet as
- .
List items:
- Own the growth tech stack. Own and improve the platforms and infrastructure powering acquisition, attribution, lifecycle marketing, analytics, and experimentation.
- Build and own marketing data infrastructure. Design and maintain the pipelines that move customer data, identities, audiences, events, and conversions across our data and marketing ecosystem, ensuring data is accurate, reliable, and available where it’s needed.
- Automate growth operations. Apply strong engineering practices to eliminate manual workflows across marketing, reporting, campaign operations, QA, and experimentation.
- Build AI-native marketing capabilities. Embed AI into how Marketing operates, building agents and tools that can create, launch, optimize, and iterate on campaigns, not just analyze performance.
- Own attribution & measurement. Build and maintain conversion tracking across Meta, Google, TikTok, AppsFlyer, web, and mobile- including pixels, SDKs, server-side events, UTMs, and deep links.
- Enable lifecycle & experimentation. Build the data flows, triggers, audiences, and infrastructure that let teams launch sophisticated lifecycle programs and experiments quickly.
- Prototype growth ideas. Build landing pages, internal tools, scripts, automations, and lightweight product experiences to quickly test new opportunities.
- Turn data into action. Use analytics tools to diagnose funnels, measure experiments, identify opportunities, and improve growth performance.
- Explore emerging technology. Continuously test new AI, MarTech, advertising, and developer tools and bring the highest-leverage capabilities into our stack.
Now Qualifications/Requirements/Skills: combine "Who You Are" and "What We're Looking For" and maybe "Bonus Points". We'll create
Qualifications
then list bullet points. From Who You Are: - You’re a builder. You can write code, work with APIs, query data, debug integrations, and ship solutions independently. - You understand growth. You’re comfortable with acquisition, conversion, retention, lifecycle marketing, experimentation, attribution, and marketing ROI. - You’re comfortable across the stack. You don’t need to be the world's best mobile, backend, data, and web engineer simultaneously, but you can navigate unfamiliar systems and figure out how the pieces connect. - You think in systems. You understand how advertising platforms, attribution, identity, event pipelines, warehouses, analytics, and lifecycle platforms fit together. - You automate repetitive work. When you see a manual process, your instinct is to figure out how software can do it better. - You move quickly. You know when something needs production-grade architecture and when a prototype is enough to validate an idea. - You’re cross-functional. You can translate business problems into technical solutions and work effectively across Marketing, Product, Data, and Engineering. From What We’re Looking For: - 6+ years in growth engineering, MarTech engineering, data engineering, software engineering, or a similarly technical role. - Strong TypeScript or Python and SQL skills. - Experience building with APIs, webhooks, SDKs, and event-driven systems. - Hands-on experience with several modern MarTech/data platforms such as Segment, Hightouch, Braze, Amplitude, AppsFlyer, Snowflake, GA4/GTM, Meta CAPI, Google Ads, or TikTok Events API. - Understanding of event instrumentation, identity, attribution, conversion tracking, experimentation, and data quality. - Experience using LLMs, agents, AI coding tools, or workflow automation to build real-world solutions. - Ability to take ambiguous problems from idea → solution → implementation → measurement. Bonus Points (we can include as bullet points under Qualifications as optional but still substantive): - Experience working in a high-growth consumer business with significant paid acquisition spend. - Experience in FinTech or another highly regulated industry. - Experience with experimentation platforms, feature flags, or personalization systems. - Experience building internal tools or data products for Marketing or Growth teams. - Familiarity with privacy and consent requirements and how they affect advertising, analytics, and customer data infrastructure. We'll include them as bullet points. Now Benefits And Perks: we have a paragraph plus bullet list. We'll createBenefits
then maybe aintro then
- list.
Intro paragraph: "Our goal is to provide a comprehensive offering of benefits and perks that promote better financial, mental, and physical wellness. We believe working alongside each other in person is the best way to build a great product and foster a strong company culture. Our expectation is that employees are in the office five days a week, allowing for optimal collaboration, inclusivity, and productivity. At the same time, we understand that life happens and recognize the importance of flexibility. We are committed to supporting our employees when circumstances arise that require remote work or adjusted schedules. Our goal is to ensure everyone can effectively balance personal and professional responsibilities while maintaining our collaborative and productive environment."
But schedule info is part of this paragraph; we might separate schedule into its own section. However the rule: include a section ONLY when posting has real, specific content for it. We have schedule info: expectation of in-office five days a week, flexibility for remote work or adjusted schedules. That's specific. So we could make a Schedule section with that info. Then Benefits section would focus on benefits list.
Thus we split: Benefits section: list of benefits.
Benefits list:
- 100% company-paid medical, dental, and vision coverage for you and your dependents on your first day of employment.
- Receive up to $100 per month in fitness reimbursement or enjoy a complimentary full membership to LifeTime Fitness or Equinox.
- 401(k) with a 3.5% match and immediate vesting
- Meal program available for both lunch and dinner
- Pre-tax benefits, including a $1,000 HSA match
- Life and accidental insurance
- Flexible PTO
- You will also have access to comprehensive medical, vision, and dental coverage, a 401(k) retirement plan with company match, short & long term disability insurance, life insurance, and flexible PTO along with many other benefits and perks.
Note some duplication; we can keep but maybe combine. We'll keep unique items.
Now Schedule section:
Schedule
thenwith the schedule info: "Our expectation is that employees are in the office five days a week, allowing for optimal collaboration, inclusivity, and productivity. At the same time, we understand that life happens and recognize the importance of flexibility. We are committed to supporting our employees when circumstances arise that require remote work or adjusted schedules. Our goal is to ensure everyone can effectively balance personal and professional responsibilities while maintaining our collaborative and productive environment." We should not include the earlier generic benefits paragraph that mentions schedule; we removed that. Now we need to include the company description paragraph at top (no heading). Then About the role heading etc. We must not include boilerplate like EEO, equal opportunity, accommodations, etc. Remove those. Now ensure we don't repeat job title. Not present. Now output HTML fragment. Let's craft. We'll start with a
for company description. Then
About the role
...
ThenResponsibilities
- ...
Qualifications
- ...