Brand Manager
Shameless Foods · Santa Ana, CA · 1 mo ago
On-siteMarketing$90k–$110k/yrFull-time
We need to output HTML fragment with sections: About Us, The Role (maybe not needed as heading? The Role is a heading but we can treat as section heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings for sections that have content: About Us, Responsibilities (maybe "What You'll Do" is responsibilities), Requirements, Benefits. Also maybe "The Role" is not a standard heading but could be considered "About the role". However they said do NOT repeat the job title as a heading. The Role is not job title; it's a description. Could treat as "About the role". But they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" heading for the description of role. Then "Responsibilities" for What You'll Do. Then "Requirements". Then "Benefits". Also maybe "Qualifications" could be same as Requirements but we can skip if not distinct. We'll include About the role, Responsibilities, Requirements, Benefits.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings for sections that have content: About Us, Responsibilities (maybe "What You'll Do" is responsibilities), Requirements, Benefits. Also maybe "The Role" is not a standard heading but could be considered "About the role". However they said do NOT repeat the job title as a heading. The Role is not job title; it's a description. Could treat as "About the role". But they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" heading for the description of role. Then "Responsibilities" for What You'll Do. Then "Requirements". Then "Benefits". Also maybe "Qualifications" could be same as Requirements but we can skip if not distinct. We'll include About the role, Responsibilities, Requirements, Benefits.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to not include Pay or Schedule sections unless posting actually states them. It does state Salary: $90k - $110K. That's pay info. So we should include a Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we need Pay section because salary is given. Also Benefits section is present. Schedule? Not mentioned (full-time). Could we include Schedule? It says Job Type: Full-time. That's schedule info. Should we include Schedule section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Full-time is specific content. So we could include Schedule section with "Full-time". However they said prefer a few substantive sections over many thin ones. Might combine Schedule into Pay? But they said use headings for Pay, Schedule separately. Could include both.
We need to not repeat the job title as a heading. The job title is Brand Manager. Not used.
We need to not put Job ID/requisition numbers as headings — none.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content:
About Us: paragraph(s) describing eJam.
The Role: description of role (the paragraph after "The Role Shameless makes better-for-you candy...").
Responsibilities: bullet list from "What You'll Do" sections: includes sub-sections Brand Marketing, Sales Partnership, Retail Execution, Project Management, Agency/Team Coordination. Each has multiple bullet-like sentences. We'll turn each sentence into
- maybe grouped under subheadings? But we only allowed
for section headings, not subheadings. Could we embed ? Not allowed. Probably we just list all responsibilities as
- under a single
. But we might lose grouping. However instruction: Use - for any list of duties/requirements/benefits. So we can make a list for responsibilities. We'll capture each duty as separate
- . We'll need to parse the responsibilities text.
Let's extract responsibilities:
From "What You'll Do":
Brand Marketing:
- Maintain the brand and retail marketing calendar across Retail, DTC, Amazon, and TikTok as the team's shared source of truth
- Keep Sales, Ops, Creative, and Growth on the same dates and priorities, surfacing conflicts early as timing shifts
- Take strategy from channel leads on each NPD drop (omnichannel, channel-exclusive, and retailer-exclusive) and translate it into clear delivery points: what partners get, in what format, by when
- Review work for brand and creative detail before it reaches leadership — typography and color, claims that match the pack, copy that sounds like Shameless, assets sized right for each channel — and hold that consistency as the same launch shows up in very different formats
Sales Partnership:
- Partner with Sales to turn brand and channel plans into executable retail programs, so teams know what is happening, when, where, and what they need to do
- Keep Sales ahead of upcoming launches, retailer programs, and promotions with clear summaries of timing, deliverables, assets, and next steps
- Be the point of contact between Brand and Sales, so sales teams have what they need to take programs to retail partners
Retail Execution:
- Support retailer-specific programs from brief through launch, keeping assets, copy, product information, and approvals aligned to retailer submission and in-market dates
- Track launch readiness across key accounts, catching gaps in assets, content, approvals, or timing before they become issues
- Make sure retail assets are accurate, complete, properly formatted, and ready for retailer use across digital and physical touchpoints
Project Management:
- Build timelines backwards from the in-market date, then break projects into tasks and briefs for the right internal owner or agency partner
- Capture action items from every call (who, what, by when) and see them through to close
- Keep everyone current on status, with an early heads-up when something needs attention
- Route completed work to heads of department for review, pull feedback into one clear set of revisions, and keep the asset trail current so anyone can find the latest brief, approved creative, and plan
Agency/Team Coordination:
- Serve as the day-to-day contact for agencies touching the brand: branding and creative, retail marketing (paid ads, .com listing management), and influencer
- Write and update clear briefs — objective, audience, deliverables, date — and keep agencies current on calendar changes and priority shifts
- Track deliverables against the brief and flag timing or decisions for the Head of Brand
- Agency budgets, scopes, and contracts sit with the Head of Brand + GM, so this role can stay focused on the work itself.
We'll convert each bullet to
- .
Requirements: bullet list from "Let's Work Together if:" and "Bonus Points". We'll combine.
Let's extract requirements:
- 4-5 years of brand or retail marketing experience in CPG and DTC. Food, beverage, or snacking is a plus
- Hands-on experience maintaining a multi-channel marketing calendar across retail and ecommerce
- Experience turning strategy into assigned tasks and keeping Sales, internal teams, and agency partners on schedule
- A good eye for brand and creative detail. You can look at a layout, a pack callout, or a line of copy and tell when something's off
- Strong written and verbal communication, especially in briefs and status updates, and comfort in a fast-moving environment where priorities shift
- Familiarity with Google Workspace and a project management platform (ClickUp, Asana, Monday, or similar)
- Working fluency with AI tools, Claude in particular, and a habit of using them to streamline the day to day: drafting briefs and recaps, turning calls into action items, and building templates and workflows that cut down manual admin
- Based within roughly 30 miles of our Santa Ana office, since this role is on-site
Bonus Points (these are also requirements but optional):
- Launching new products into mass or grocery retail
- Retail media platforms (Roundel, Walmart Connect, Kroger Precision Marketing, Instacart) and retailer .com content management
- TikTok Shop or subscription DTC experience
- Influencer and creator program management
We'll include all as
- under Requirements.
Benefits: list from "Benefits" section:
- Competitive base salary designed to reward high performance and impact
- 401(k) plan with company matching
- Comprehensive health benefits including medical, dental, and vision coverage
- Stock option plan so you can share in the value you help build
- Generous paid time off and company holidays
- Real ownership and autonomy to drive measurable growth
- Ongoing professional development opportunities as we scale
Note: The Benefits section also had a line "Benefits Benefits Competitive base salary..." duplicate "Benefits". We'll just list items.
Pay: Salary: $90k - $110K. We'll put in
maybe.
Schedule: Full-time.
We need to decide headings: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Also About Us maybe as a section? The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Us. But we have About Us content. Should we include it? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Probably we should include About Us as a section heading maybe "About the company" but not in list. However they said "Prefer a few substantive sections over many thin ones." Including About Us adds another section. But it's substantive. I'd include About Us as a heading maybe "About the company". But they didn't list that as example; but we can still use for any section heading. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical headings but not exclusive. So we can add About Us.
Thus final HTML:
About Us
...
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
Salary: $90k - $110K
Schedule
Full-time
Make sure no extra whitespace? It's fine.
Now craft the About Us paragraph: combine the two paragraphs: "eJam is a bootstrapped consumer products company that has built, scaled, and exited multiple brands — all without ever taking a dollar of outside capital. Our portfolio includes category leaders ranked at the top of Amazon, carried in major retailers nationwide, and sold across DTC, marketplaces, and every channel in between. We're not a startup hoping something works. We're a team that has done it repeatedly — taken products from zero to eight figures, landed them on retail shelves nationwide, and built real brands that consumers love. We operate like a holding company with the speed of a startup: small team, no bureaucracy, massive ownership. This is the place where you'll see the entire machine — sourcing, product development, packaging, manufacturing, compliance, marketing, marketplace strategy, retail — all under one roof. If you want to learn how consumer products actually get built and shipped at scale, there is no faster education than this."
About the role paragraph: "Shameless makes better-for-you candy: low sugar, high fiber, no artificial dyes. We're growing quickly across retail, DTC, Amazon, and TikTok. As Brand Manager, you'll keep brand plans moving into market — and make sure Sales has what they need to execute them. You'll help manage the brand and retail marketing calendar, translate strategy into clear programs and realistic timelines, and keep Sales, Ops, Creative, Growth, and agency partners aligned on what's happening, when, and what needs to happen next. You'll be the connective tissue between strategy and execution, making complex plans simple and actionable for the teams responsible for bringing them to life. It's a hands-on role that will suit you if you enjoy organizing complexity, driving follow
for prose. We need to not include Pay or Schedule sections unless posting actually states them. It does state Salary: $90k - $110K. That's pay info. So we should include a Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we need Pay section because salary is given. Also Benefits section is present. Schedule? Not mentioned (full-time). Could we include Schedule? It says Job Type: Full-time. That's schedule info. Should we include Schedule section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Full-time is specific content. So we could include Schedule section with "Full-time". However they said prefer a few substantive sections over many thin ones. Might combine Schedule into Pay? But they said use headings for Pay, Schedule separately. Could include both. We need to not repeat the job title as a heading. The job title is Brand Manager. Not used. We need to not put Job ID/requisition numbers as headings — none. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: About Us: paragraph(s) describing eJam. The Role: description of role (the paragraph after "The Role Shameless makes better-for-you candy..."). Responsibilities: bullet list from "What You'll Do" sections: includes sub-sections Brand Marketing, Sales Partnership, Retail Execution, Project Management, Agency/Team Coordination. Each has multiple bullet-like sentences. We'll turn each sentence into
for section headings, not subheadings. Could we embed ? Not allowed. Probably we just list all responsibilities as
- . But we might lose grouping. However instruction: Use
- for any list of duties/requirements/benefits. So we can make a list for responsibilities. We'll capture each duty as separate
- . We'll need to parse the responsibilities text. Let's extract responsibilities: From "What You'll Do": Brand Marketing: - Maintain the brand and retail marketing calendar across Retail, DTC, Amazon, and TikTok as the team's shared source of truth - Keep Sales, Ops, Creative, and Growth on the same dates and priorities, surfacing conflicts early as timing shifts - Take strategy from channel leads on each NPD drop (omnichannel, channel-exclusive, and retailer-exclusive) and translate it into clear delivery points: what partners get, in what format, by when - Review work for brand and creative detail before it reaches leadership — typography and color, claims that match the pack, copy that sounds like Shameless, assets sized right for each channel — and hold that consistency as the same launch shows up in very different formats Sales Partnership: - Partner with Sales to turn brand and channel plans into executable retail programs, so teams know what is happening, when, where, and what they need to do - Keep Sales ahead of upcoming launches, retailer programs, and promotions with clear summaries of timing, deliverables, assets, and next steps - Be the point of contact between Brand and Sales, so sales teams have what they need to take programs to retail partners Retail Execution: - Support retailer-specific programs from brief through launch, keeping assets, copy, product information, and approvals aligned to retailer submission and in-market dates - Track launch readiness across key accounts, catching gaps in assets, content, approvals, or timing before they become issues - Make sure retail assets are accurate, complete, properly formatted, and ready for retailer use across digital and physical touchpoints Project Management: - Build timelines backwards from the in-market date, then break projects into tasks and briefs for the right internal owner or agency partner - Capture action items from every call (who, what, by when) and see them through to close - Keep everyone current on status, with an early heads-up when something needs attention - Route completed work to heads of department for review, pull feedback into one clear set of revisions, and keep the asset trail current so anyone can find the latest brief, approved creative, and plan Agency/Team Coordination: - Serve as the day-to-day contact for agencies touching the brand: branding and creative, retail marketing (paid ads, .com listing management), and influencer - Write and update clear briefs — objective, audience, deliverables, date — and keep agencies current on calendar changes and priority shifts - Track deliverables against the brief and flag timing or decisions for the Head of Brand - Agency budgets, scopes, and contracts sit with the Head of Brand + GM, so this role can stay focused on the work itself. We'll convert each bullet to
- . Requirements: bullet list from "Let's Work Together if:" and "Bonus Points". We'll combine. Let's extract requirements: - 4-5 years of brand or retail marketing experience in CPG and DTC. Food, beverage, or snacking is a plus - Hands-on experience maintaining a multi-channel marketing calendar across retail and ecommerce - Experience turning strategy into assigned tasks and keeping Sales, internal teams, and agency partners on schedule - A good eye for brand and creative detail. You can look at a layout, a pack callout, or a line of copy and tell when something's off - Strong written and verbal communication, especially in briefs and status updates, and comfort in a fast-moving environment where priorities shift - Familiarity with Google Workspace and a project management platform (ClickUp, Asana, Monday, or similar) - Working fluency with AI tools, Claude in particular, and a habit of using them to streamline the day to day: drafting briefs and recaps, turning calls into action items, and building templates and workflows that cut down manual admin - Based within roughly 30 miles of our Santa Ana office, since this role is on-site Bonus Points (these are also requirements but optional): - Launching new products into mass or grocery retail - Retail media platforms (Roundel, Walmart Connect, Kroger Precision Marketing, Instacart) and retailer .com content management - TikTok Shop or subscription DTC experience - Influencer and creator program management We'll include all as
- under Requirements.
Benefits: list from "Benefits" section:
- Competitive base salary designed to reward high performance and impact
- 401(k) plan with company matching
- Comprehensive health benefits including medical, dental, and vision coverage
- Stock option plan so you can share in the value you help build
- Generous paid time off and company holidays
- Real ownership and autonomy to drive measurable growth
- Ongoing professional development opportunities as we scale
Note: The Benefits section also had a line "Benefits Benefits Competitive base salary..." duplicate "Benefits". We'll just list items.
Pay: Salary: $90k - $110K. We'll put in
maybe. Schedule: Full-time. We need to decide headings: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Also About Us maybe as a section? The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Us. But we have About Us content. Should we include it? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Probably we should include About Us as a section heading maybe "About the company" but not in list. However they said "Prefer a few substantive sections over many thin ones." Including About Us adds another section. But it's substantive. I'd include About Us as a heading maybe "About the company". But they didn't list that as example; but we can still use
for any section heading. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical headings but not exclusive. So we can add About Us. Thus final HTML:
About Us
...
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
Salary: $90k - $110K
Schedule
Full-time
Make sure no extra whitespace? It's fine. Now craft the About Us paragraph: combine the two paragraphs: "eJam is a bootstrapped consumer products company that has built, scaled, and exited multiple brands — all without ever taking a dollar of outside capital. Our portfolio includes category leaders ranked at the top of Amazon, carried in major retailers nationwide, and sold across DTC, marketplaces, and every channel in between. We're not a startup hoping something works. We're a team that has done it repeatedly — taken products from zero to eight figures, landed them on retail shelves nationwide, and built real brands that consumers love. We operate like a holding company with the speed of a startup: small team, no bureaucracy, massive ownership. This is the place where you'll see the entire machine — sourcing, product development, packaging, manufacturing, compliance, marketing, marketplace strategy, retail — all under one roof. If you want to learn how consumer products actually get built and shipped at scale, there is no faster education than this." About the role paragraph: "Shameless makes better-for-you candy: low sugar, high fiber, no artificial dyes. We're growing quickly across retail, DTC, Amazon, and TikTok. As Brand Manager, you'll keep brand plans moving into market — and make sure Sales has what they need to execute them. You'll help manage the brand and retail marketing calendar, translate strategy into clear programs and realistic timelines, and keep Sales, Ops, Creative, Growth, and agency partners aligned on what's happening, when, and what needs to happen next. You'll be the connective tissue between strategy and execution, making complex plans simple and actionable for the teams responsible for bringing them to life. It's a hands-on role that will suit you if you enjoy organizing complexity, driving follow