Senior Lifecycle Marketer
Read AI · Seattle, WA · 1 mo ago
Hybrid$130k–$160k/yrFull-time
We need to output HTML fragment with sections: About Us? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those as examples. Probably okay to include About Us.
We need sections: Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Need), Benefits, Pay, maybe Skills? The posting includes "Why Read AI?" which is more about company culture/benefits. Could treat as Benefits or "Why Read AI?" as a section about company. But we need to avoid filler. The "Why Read AI?" includes Innovative, Massive Impact, Growth Opportunities, Leadership, Collaborative Culture. That's substantive. Could be a section "Why Read AI?" but not in list. Might be okay as a heading. However they said prefer a few substantive sections over many thin ones. Could combine "Why Read AI?" into Benefits or About Us. But we have separate Benefits: they mention low deductible health plans, flexible time away and family leave programs. Also equity. So we can have Benefits section.
Pay: they gave salary range $130,000- $160,000 plus equity and benefits. Also note about guideline. We'll include Pay section.
Schedule: not mentioned, so omit.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say 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. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." That's likely boilerplate (immigration). Also "Please note that the base pay shown is a guideline..." maybe keep? It's part of Pay section; we can keep but it's not boilerplate. However they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need sections: About Us? They didn't list About Us as a standard heading but we can include if content present. They gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include "About Us" maybe not needed. The posting includes "About Us" paragraph at top. Could treat as "About the role"? Actually "About Us" is company description. Could be "About the role"? Not exactly. But we could include a section with heading
About Us
and paragraph. The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those as examples. Probably okay to include About Us.
We need sections: Responsibilities (What You’ll Do), Requirements/Qualifications (What You’ll Need), Benefits, Pay, maybe Skills? The posting includes "Why Read AI?" which is more about company culture/benefits. Could treat as Benefits or "Why Read AI?" as a section about company. But we need to avoid filler. The "Why Read AI?" includes Innovative, Massive Impact, Growth Opportunities, Leadership, Collaborative Culture. That's substantive. Could be a section "Why Read AI?" but not in list. Might be okay as a heading. However they said prefer a few substantive sections over many thin ones. Could combine "Why Read AI?" into Benefits or About Us. But we have separate Benefits: they mention low deductible health plans, flexible time away and family leave programs. Also equity. So we can have Benefits section.
Pay: they gave salary range $130,000- $160,000 plus equity and benefits. Also note about guideline. We'll include Pay section.
Schedule: not mentioned, so omit.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we need to break into bullet points. The responsibilities are long paragraphs; we can extract bullet points for each major area: Foundation and infrastructure, Onboarding and activation, Engagement and habit formation, Monetization, renewal, and expansion, Experimentation and measurement, Quality and customer trust. Each bullet can contain the description.
For requirements: list items: 6+ years in lifecycle..., Hands-on with Sendgrid..., Measurable improvements..., Strong grasp..., Comfort defining..., Excellent writing..., Working knowledge..., Connecting self-serve usage... Also maybe "Experience with ...". We'll bullet.
Benefits: low deductible health plans, flexible time away and family leave programs, equity (mentioned). Also maybe "annual base salary ... plus equity and benefits" but that's Pay. Benefits: health plans, flexible time away, family leave.
We also have "Why Read AI?" content; could be a section "Why Read AI?" with bullet points: Innovative, Massive Impact, Growth Opportunities, Leadership, Collaborative Culture. Or we could incorporate into About Us. But we already have About Us paragraph. Might be better to have a section "Why Read AI?" as it's substantive.
We must not include boilerplate like "Applicants must be authorized..." etc. Also remove duplicated lines. Also remove "Please note that the base pay shown is a guideline..." maybe keep as part of Pay but it's not boilerplate; it's a note. Could keep as a
inside Pay.
We must not include application instructions. There's none explicit besides maybe "Please note that the base pay shown is a guideline". That's fine.
Now produce HTML fragment: start with maybe
About Us
...
then Responsibilities
... etc. Then Requirements
... etc. Then Benefits
... etc. Then Pay
...
. Then Why Read AI?
... etc.
Check for any duplicated content: The "About Us" paragraph appears at top; we will include that.
Now ensure we preserve all substantive information: The About Us paragraph includes details about Read AI, funding, mission. Keep that.
The Responsibilities: we need to capture all bullet points from "What You’ll Do". Let's parse:
Foundation and infrastructure
- Implement and operationalize the lifecycle platform, including moving priority journeys off of our legacy platform.
- Define the event, profile, account, plan, and usage data needed for segmentation and personalization, and partner with Engineering and Data on instrumentation, identity resolution, and measurement.
- Establish naming conventions, suppression rules, frequency policies, approval workflows, and QA standards.
- Build reusable components so routine experimentation doesn't require engineering.
- Ensure and improve upon our already high level of deliverability and engagement.
- Support localization and personalization at global scale.
Onboarding and activation
- Map the journey from account creation to calendar connection, first hosted meeting, first recap, repeat usage, and meaningful feature discovery — and reinforce value at the moment it becomes relevant.
- Build targeted programs for the specific drop-off points: registered but no calendar, connected but never hosted, received a recap but didn't return, used Read once and went quiet.
- Run coordinated in-product and out-of-product activation experiments with Product.
- Help users understand what Read does and what access it needs, without adding friction or educational homework that shrinks the number of users reaching value.
- Nudge users at the right time to enable discovery of features as well as upselling as the trial ends, or as new features are unlocked.
Engagement and habit formation
- Build behavioral journeys that drive repeat meetings and adoption of high-value capabilities.
- Base feature discovery on what a user has and hasn't experienced, not a generic product-news calendar.
- Coordinate email, in-product messaging, content, and webinars, personalized by role, workflow, and maturity — and give users reasons to return between launches.
Monetization, renewal, and expansion
- Connect demonstrated product value to relevant paid capabilities: free-to-paid, Pro-to-workspace, monthly-to-annual, workspace expansion.
- Build interventions for early churn risk, inactivity, downgrade intent, and upcoming renewal.
- Partner with CS on unmanaged and lightly managed customers.
- Identify power users who can become internal champions, and work with Sales and RevOps to surface product-qualified accounts — without pushing self-service customers into a human sales process they don't need.
Experimentation and measurement
- Maintain a prioritized experimentation roadmap with a clear hypothesis, audience, primary outcome, guardrails, and decision rule per test.
- Test across content, timing, trigger, channel, frequency, and offer.
- Measure incremental behavior and revenue change, not opens and clicks.
- Watch rates and gross outcomes so a better conversion rate doesn't hide fewer total activated or paying customers.
Quality and customer trust
- Own QA across audience selection, rendering, links, personalization, localization, tracking, and suppression.
- Maintain deliverability, consent, privacy, and preference management, and coordinate across teams to prevent over-messaging.
- Build feedback and survey programs that explain why users activate, disengage, convert, or churn.
Now Requirements: "What You’ll Need:" paragraph:
- 6+ years in lifecycle, CRM, retention, or growth marketing, for a high-volume SaaS (tens of millions to hundreds of millions of monthly sends), PLG, consumer, or prosumer product.
- Hands-on with Sendgrid, Customer.io, Iterable, Braze, HubSpot, Klaviyo, or comparable — including implementing or substantially rebuilding infrastructure, not only operating an established program.
- Measurable improvements in activation, retention, conversion, renewal, or expansion.
- Strong grasp of behavioral segmentation, triggered messaging, experimentation, and cohort analysis, plus the quantitative instincts to tell correlation from incremental impact.
- Comfort defining events, requirements, and measurement alongside engineers and data teams.
- Excellent writing, and experience coordinating email with in-product surfaces.
- Working knowledge of deliverability, consent, localization, and campaign QA.
- Connecting self-serve usage to workspace or enterprise adoption is strongly preferred.
Now Benefits: from "Why Read AI?" and also later: "We also offer low deductible health plans, as well as flexible time away and family leave programs." Also equity mentioned in Pay. So Benefits bullet list: low deductible health plans, flexible time away, family leave programs. Possibly also equity? But equity is part of Pay. We'll keep equity in Pay.
Pay: "The annual base salary for this position ranges from $130,000- $160,000 plus equity and benefits. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location." We'll include that as a paragraph.
Why Read AI? section: bullet points:
- Innovative: We bring AI to the masses with proactive technology that acts as the ultimate AI assistant. Built on our proprietary, patented technology, Read AI takes notes, surfaces information, facilitates collaboration, and learns you, making individuals and teams more effective. We launched Operator to capture and analyze conversations wherever they happen: On the go, spontaneously, in your office hallway, and at a coffee shop. We’ve also introduced our new desktop apps for Windows and macOS and our Android app, joining Read AI for iPhone and web.
- Massive Impact: AI's greatest impact will be on the ability to allow people to do more, taking away mundane tasks, and guiding them to the next best action.
- Growth Opportunities: Read AI is the fastest growing AI-copilot and meeting notetaker in history, and is one of the leading AI companies in the world, adding more than 1MM new customers every month. The company raised Series A and B in 2024, also was recognized as a Top Startup in Seattle by LinkedIn (2025), also notably a Top Company To Watch in 2025 by Inc Magazine, and is one of the Top AI Companies in Demand by Startups, according to a16z.
- Leadership: Learn more about CEO and Co-Founder David Shim in this Fortune Good Life profile and listen to him share his vision for AI Agents, Digital Twins and the Future of Work. CTO and Co-Founder Rob Williams was recently anointed as one of the most disruptive leaders in AI. For more on our technology, Co-Founder and VP Data Science Elliott Waldron goes behind-the-scenes on our patents and models in this tech brief.
- Collaborative Culture: Work in a supportive and collaborative environment with a diverse and talented team.
We need to ensure we don't include boilerplate like "Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." Remove that.
Also remove any duplicated lines: I don't see duplicates.
Now produce HTML. Ensure no extra markdown fences. Just raw HTML.
Let's craft.
We'll start with <
inside Pay. We must not include application instructions. There's none explicit besides maybe "Please note that the base pay shown is a guideline". That's fine. Now produce HTML fragment: start with maybe
About Us
...
thenResponsibilities
- ... etc. Then
Requirements
- ... etc. Then
Benefits
- ... etc. Then
Pay
...
. ThenWhy Read AI?
- ... etc.
Check for any duplicated content: The "About Us" paragraph appears at top; we will include that.
Now ensure we preserve all substantive information: The About Us paragraph includes details about Read AI, funding, mission. Keep that.
The Responsibilities: we need to capture all bullet points from "What You’ll Do". Let's parse:
Foundation and infrastructure
- Implement and operationalize the lifecycle platform, including moving priority journeys off of our legacy platform.
- Define the event, profile, account, plan, and usage data needed for segmentation and personalization, and partner with Engineering and Data on instrumentation, identity resolution, and measurement.
- Establish naming conventions, suppression rules, frequency policies, approval workflows, and QA standards.
- Build reusable components so routine experimentation doesn't require engineering.
- Ensure and improve upon our already high level of deliverability and engagement.
- Support localization and personalization at global scale.
Onboarding and activation
- Map the journey from account creation to calendar connection, first hosted meeting, first recap, repeat usage, and meaningful feature discovery — and reinforce value at the moment it becomes relevant.
- Build targeted programs for the specific drop-off points: registered but no calendar, connected but never hosted, received a recap but didn't return, used Read once and went quiet.
- Run coordinated in-product and out-of-product activation experiments with Product.
- Help users understand what Read does and what access it needs, without adding friction or educational homework that shrinks the number of users reaching value.
- Nudge users at the right time to enable discovery of features as well as upselling as the trial ends, or as new features are unlocked.
Engagement and habit formation
- Build behavioral journeys that drive repeat meetings and adoption of high-value capabilities.
- Base feature discovery on what a user has and hasn't experienced, not a generic product-news calendar.
- Coordinate email, in-product messaging, content, and webinars, personalized by role, workflow, and maturity — and give users reasons to return between launches.
Monetization, renewal, and expansion
- Connect demonstrated product value to relevant paid capabilities: free-to-paid, Pro-to-workspace, monthly-to-annual, workspace expansion.
- Build interventions for early churn risk, inactivity, downgrade intent, and upcoming renewal.
- Partner with CS on unmanaged and lightly managed customers.
- Identify power users who can become internal champions, and work with Sales and RevOps to surface product-qualified accounts — without pushing self-service customers into a human sales process they don't need.
Experimentation and measurement
- Maintain a prioritized experimentation roadmap with a clear hypothesis, audience, primary outcome, guardrails, and decision rule per test.
- Test across content, timing, trigger, channel, frequency, and offer.
- Measure incremental behavior and revenue change, not opens and clicks.
- Watch rates and gross outcomes so a better conversion rate doesn't hide fewer total activated or paying customers.
Quality and customer trust
- Own QA across audience selection, rendering, links, personalization, localization, tracking, and suppression.
- Maintain deliverability, consent, privacy, and preference management, and coordinate across teams to prevent over-messaging.
- Build feedback and survey programs that explain why users activate, disengage, convert, or churn.
Now Requirements: "What You’ll Need:" paragraph:
- 6+ years in lifecycle, CRM, retention, or growth marketing, for a high-volume SaaS (tens of millions to hundreds of millions of monthly sends), PLG, consumer, or prosumer product.
- Hands-on with Sendgrid, Customer.io, Iterable, Braze, HubSpot, Klaviyo, or comparable — including implementing or substantially rebuilding infrastructure, not only operating an established program.
- Measurable improvements in activation, retention, conversion, renewal, or expansion.
- Strong grasp of behavioral segmentation, triggered messaging, experimentation, and cohort analysis, plus the quantitative instincts to tell correlation from incremental impact.
- Comfort defining events, requirements, and measurement alongside engineers and data teams.
- Excellent writing, and experience coordinating email with in-product surfaces.
- Working knowledge of deliverability, consent, localization, and campaign QA.
- Connecting self-serve usage to workspace or enterprise adoption is strongly preferred.
Now Benefits: from "Why Read AI?" and also later: "We also offer low deductible health plans, as well as flexible time away and family leave programs." Also equity mentioned in Pay. So Benefits bullet list: low deductible health plans, flexible time away, family leave programs. Possibly also equity? But equity is part of Pay. We'll keep equity in Pay.
Pay: "The annual base salary for this position ranges from $130,000- $160,000 plus equity and benefits. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location." We'll include that as a paragraph.
Why Read AI? section: bullet points:
- Innovative: We bring AI to the masses with proactive technology that acts as the ultimate AI assistant. Built on our proprietary, patented technology, Read AI takes notes, surfaces information, facilitates collaboration, and learns you, making individuals and teams more effective. We launched Operator to capture and analyze conversations wherever they happen: On the go, spontaneously, in your office hallway, and at a coffee shop. We’ve also introduced our new desktop apps for Windows and macOS and our Android app, joining Read AI for iPhone and web.
- Massive Impact: AI's greatest impact will be on the ability to allow people to do more, taking away mundane tasks, and guiding them to the next best action.
- Growth Opportunities: Read AI is the fastest growing AI-copilot and meeting notetaker in history, and is one of the leading AI companies in the world, adding more than 1MM new customers every month. The company raised Series A and B in 2024, also was recognized as a Top Startup in Seattle by LinkedIn (2025), also notably a Top Company To Watch in 2025 by Inc Magazine, and is one of the Top AI Companies in Demand by Startups, according to a16z.
- Leadership: Learn more about CEO and Co-Founder David Shim in this Fortune Good Life profile and listen to him share his vision for AI Agents, Digital Twins and the Future of Work. CTO and Co-Founder Rob Williams was recently anointed as one of the most disruptive leaders in AI. For more on our technology, Co-Founder and VP Data Science Elliott Waldron goes behind-the-scenes on our patents and models in this tech brief.
- Collaborative Culture: Work in a supportive and collaborative environment with a diverse and talented team.
We need to ensure we don't include boilerplate like "Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time." Remove that.
Also remove any duplicated lines: I don't see duplicates.
Now produce HTML. Ensure no extra markdown fences. Just raw HTML.
Let's craft.
We'll start with <