Front-End Developer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description: "ARE YOU A FUTURE PLAIDMATE?" etc. We need to parse content.
We need to extract sections: maybe "About the role" (intro), "Responsibilities" (What You'll Do), "Requirements" (Who You Are), maybe "Skills" (list of technologies). Benefits, Pay, Schedule: there is a line about work schedule/hours: "Work schedule/hours: This position requires occasional nonstandard work hours in accordance with project needs, deadlines, deliverables, and urgent client requests." That's schedule info. Benefits not mentioned. Pay not mentioned. So we should not include Benefits or Pay sections.
We need to avoid repeating job title as heading. The job title is "Digital + Content Marketing Manager". Not to be used as heading.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We need to output only HTML fragment.
Let's structure:
About the role
... intro paragraph(s) ...
Then Responsibilities
list items from "What You'll Do" sections.
We need to capture each bullet: Development & Build, Creative Collaboration, Website Management & Maintenance, Collaboration & Agency Life. Each has sub-bullets. We can flatten into list items.
We must preserve details.
Let's extract:
Development & Build:
- Turn Figma designs into fast, responsive, production-ready websites and landing pages.
- Build and edit sites in WordPress and Elementor, including custom CSS, JavaScript, and theme work.
- Use automated development tooling as a core part of your workflow, directing the build and validating every output.
- Develop custom WordPress plugins, components, and functionality that extend what our marketing sites can do.
- Support builds on our modern stack (Next.js, React, Storyblok, Vercel, Supabase) as we grow beyond WordPress and Elementor.
- Build to functionality requirements and use cases, then iterate until it’s right.
Creative Collaboration:
- Bring ideas to designers early: animation, interaction, and unique functionality they may not know is possible.
- Recommend JavaScript libraries and motion approaches (GSAP, Framer Motion, and similar) that elevate the design.
- Apply a strong sense of UX to every build, from how things move to how they feel.
Website Management & Maintenance:
- Test your own work across browsers and devices before it ships. Catch the details.
- Own the ongoing management of our client website portfolio on WP Engine and Vercel: plugin and core updates, security, backups, uptime, performance, and troubleshooting.
- Handle client site edits, fixes, and small enhancement requests with quick turnaround.
- Help maintain internal standards for code quality, performance, and accessibility.
Collaboration & Agency Life:
- Work hand-in-hand with designers, account leads, and leadership from concept through launch.
- Participate in client meetings as needed, explaining technical options in plain language.
- Support PLAID’s own website and internal tools as applicable.
Now Requirements/Who You Are:
Who You Are:
- A doer and a collaborator with a positive attitude.
- Front-end focused and code-aware, fluent in WordPress and Elementor, with a real feel for how good websites should look and work.
- Comfortable adopting new development tools quickly and making them the way you work, not an add-on.
- Curious and willing to move with us as our platforms and stack evolve.
- A clear communicator who owns their work.
- Missing a must-have or two? No problem! Convince us why you’re the best candidate!
We could treat as Requirements or Qualifications. Use Requirements
maybe.
Also Skills: maybe list technologies: WordPress, Elementor, custom CSS, JavaScript, automated development tooling, Next.js, React, Storyblok, Vercel, Supabase, GSAP, Framer Motion, WP Engine, etc. But we already have them in responsibilities. Could create Skills section but might duplicate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section? But we need headings only when posting has real specific content. The posting does not explicitly label "Skills". It lists technologies within responsibilities and who you are. Could still create a Skills section summarizing them, but that might be summarizing. Better to keep Responsibilities and Requirements sections.
Schedule: we have schedule info. So Schedule
with Work schedule/hours: This position requires occasional nonstandard work hours in accordance with project needs, deadlines, deliverables, and urgent client requests.
No Benefits or Pay.
Now About the role: need to capture intro paragraphs before "The Role". The posting: "ARE YOU A FUTURE PLAIDMATE? Do you consistently ask, “What’s Next?”Are you nimble and able to adapt to rapidly changing situations?Do you thrive in a fast-paced environment?Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award-winning, full-service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives. The Role"
We need to preserve all that. We'll put in maybe multiple sentences. Could combine into one paragraph.
Let's craft:
Are you a future Plaidmate? Do you consistently ask, “What’s Next?” Are you nimble and able to adapt to rapidly changing situations? Do you thrive in a fast‑paced environment? Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award‑winning, full‑service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives.
Now The Role heading? Actually after that they say "The RoleYou’ll be the builder..." We could treat that as part of About the role or maybe separate. But we already have About the role. Could incorporate "The Role" description into About the role as well. But we might duplicate. Better to treat "The Role" as part of About the role. The content after "The Role" is description of role: builder on web team etc. That is substantive. Should we put that under About the role or Responsibilities? It's more about role description. Could be part of About the role. But we already have Responsibilities section for duties. The role description includes: "You’ll be the builder on our web team: part front-end developer, part creative collaborator, part power user of automated development tooling. One day you’re turning a Figma design into a polished, production-ready site, the next you’re showing a designer what a scroll animation could do for their concept, or building a custom plugin that gives a client something off-the-shelf can’t. You’ll build hands-on in WordPress and Elementor, work with automated development tooling every day, and experiment with agentic workflows where the use case fits. You direct the work, test it, refine it, and own the result. You’ll collaborate closely with design, account, and leadership to bring websites and applications to life."
That seems like responsibilities as well. Could merge with Responsibilities. But we already have a detailed Responsibilities list from "What You'll Do". The role description is more narrative overview. Could keep as part of About the role.
Thus About the role will include intro + The Role description.
Let's combine.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's write:
About the role
Are you a future Plaidmate? Do you consistently ask, “What’s Next?” Are you nimble and able to adapt to rapidly changing situations? Do you thrive in a fast‑paced environment? Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award‑winning, full‑service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives. You’ll be the builder on our web team: part front‑end developer, part creative collaborator, part power user of automated development tooling. One day you’re turning a Figma design into a polished, production‑ready site, the next you’re showing a designer what a scroll animation could do for their concept, or building a custom plugin that gives a client something off‑the‑shelf can’t. You’ll build hands‑on in WordPress and Elementor, work with automated development tooling every day, and experiment with agentic workflows where the use case fits. You direct the work, test it, refine it, and own the result. You’ll collaborate closely with design, account, and leadership to bring websites and applications to life.
Responsibilities
- Turn Figma designs into fast, responsive, production-ready websites and landing pages.
- Build and edit sites in WordPress and Elementor, including custom CSS, JavaScript, and theme work.
- Use automated development tooling as a core part of your workflow, directing the build and validating every output.
- Develop custom WordPress plugins, components, and functionality that extend what our marketing sites can do.
- Support builds on our modern stack (Next.js, React, Storyblok, Vercel, Supabase) as we grow beyond WordPress and Elementor.
- Build to functionality requirements and use cases, then iterate until it’s right.
- Bring ideas to designers early: animation, interaction, and unique functionality they may not know is possible.
- Recommend JavaScript libraries and motion approaches (GSAP, Framer Motion, and similar) that elevate the design.
- Apply a strong sense of UX to every build, from how things move to how they feel.
- Test your own work across browsers and devices before it ships. Catch the details.
- Own the ongoing management of our client website portfolio on WP Engine and Vercel: plugin and core updates, security, backups, uptime, performance, and troubleshooting.
- Handle client site edits, fixes, and small enhancement requests with quick turnaround.
- Help maintain internal standards for code quality, performance, and accessibility.
- Work hand-in-hand with designers, account leads, and leadership from concept through launch.
- Participate in client meetings as needed, explaining technical options in plain language.
- Support PLAID’s own website and internal tools as applicable.
Requirements
- A doer and a collaborator with a positive attitude.
- Front-end focused and code-aware, fluent in WordPress and Elementor, with a real feel for how good websites should look and work.
- Comfortable adopting new development tools quickly and making them the way you work, not an add-on.
- Curious and willing to move with us as our platforms and stack
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to output only HTML fragment. Let's structure:
About the role
... intro paragraph(s) ...
ThenResponsibilities
- list items from "What You'll Do" sections.
We need to capture each bullet: Development & Build, Creative Collaboration, Website Management & Maintenance, Collaboration & Agency Life. Each has sub-bullets. We can flatten into list items.
We must preserve details.
Let's extract:
Development & Build:
- Turn Figma designs into fast, responsive, production-ready websites and landing pages.
- Build and edit sites in WordPress and Elementor, including custom CSS, JavaScript, and theme work.
- Use automated development tooling as a core part of your workflow, directing the build and validating every output.
- Develop custom WordPress plugins, components, and functionality that extend what our marketing sites can do.
- Support builds on our modern stack (Next.js, React, Storyblok, Vercel, Supabase) as we grow beyond WordPress and Elementor.
- Build to functionality requirements and use cases, then iterate until it’s right.
Creative Collaboration:
- Bring ideas to designers early: animation, interaction, and unique functionality they may not know is possible.
- Recommend JavaScript libraries and motion approaches (GSAP, Framer Motion, and similar) that elevate the design.
- Apply a strong sense of UX to every build, from how things move to how they feel.
Website Management & Maintenance:
- Test your own work across browsers and devices before it ships. Catch the details.
- Own the ongoing management of our client website portfolio on WP Engine and Vercel: plugin and core updates, security, backups, uptime, performance, and troubleshooting.
- Handle client site edits, fixes, and small enhancement requests with quick turnaround.
- Help maintain internal standards for code quality, performance, and accessibility.
Collaboration & Agency Life:
- Work hand-in-hand with designers, account leads, and leadership from concept through launch.
- Participate in client meetings as needed, explaining technical options in plain language.
- Support PLAID’s own website and internal tools as applicable.
Now Requirements/Who You Are:
Who You Are:
- A doer and a collaborator with a positive attitude.
- Front-end focused and code-aware, fluent in WordPress and Elementor, with a real feel for how good websites should look and work.
- Comfortable adopting new development tools quickly and making them the way you work, not an add-on.
- Curious and willing to move with us as our platforms and stack evolve.
- A clear communicator who owns their work.
- Missing a must-have or two? No problem! Convince us why you’re the best candidate!
We could treat as Requirements or Qualifications. Use
- Turn Figma designs into fast, responsive, production-ready websites and landing pages.
- Build and edit sites in WordPress and Elementor, including custom CSS, JavaScript, and theme work.
- Use automated development tooling as a core part of your workflow, directing the build and validating every output.
- Develop custom WordPress plugins, components, and functionality that extend what our marketing sites can do.
- Support builds on our modern stack (Next.js, React, Storyblok, Vercel, Supabase) as we grow beyond WordPress and Elementor.
- Build to functionality requirements and use cases, then iterate until it’s right.
- Bring ideas to designers early: animation, interaction, and unique functionality they may not know is possible.
- Recommend JavaScript libraries and motion approaches (GSAP, Framer Motion, and similar) that elevate the design.
- Apply a strong sense of UX to every build, from how things move to how they feel.
- Test your own work across browsers and devices before it ships. Catch the details.
- Own the ongoing management of our client website portfolio on WP Engine and Vercel: plugin and core updates, security, backups, uptime, performance, and troubleshooting.
- Handle client site edits, fixes, and small enhancement requests with quick turnaround.
- Help maintain internal standards for code quality, performance, and accessibility.
- Work hand-in-hand with designers, account leads, and leadership from concept through launch.
- Participate in client meetings as needed, explaining technical options in plain language.
- Support PLAID’s own website and internal tools as applicable.
- A doer and a collaborator with a positive attitude.
- Front-end focused and code-aware, fluent in WordPress and Elementor, with a real feel for how good websites should look and work.
- Comfortable adopting new development tools quickly and making them the way you work, not an add-on.
- Curious and willing to move with us as our platforms and stack
Requirements
maybe. Also Skills: maybe list technologies: WordPress, Elementor, custom CSS, JavaScript, automated development tooling, Next.js, React, Storyblok, Vercel, Supabase, GSAP, Framer Motion, WP Engine, etc. But we already have them in responsibilities. Could create Skills section but might duplicate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section? But we need headings only when posting has real specific content. The posting does not explicitly label "Skills". It lists technologies within responsibilities and who you are. Could still create a Skills section summarizing them, but that might be summarizing. Better to keep Responsibilities and Requirements sections. Schedule: we have schedule info. SoSchedule
withWork schedule/hours: This position requires occasional nonstandard work hours in accordance with project needs, deadlines, deliverables, and urgent client requests.
No Benefits or Pay. Now About the role: need to capture intro paragraphs before "The Role". The posting: "ARE YOU A FUTURE PLAIDMATE? Do you consistently ask, “What’s Next?”Are you nimble and able to adapt to rapidly changing situations?Do you thrive in a fast-paced environment?Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award-winning, full-service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives. The Role" We need to preserve all that. We'll put inmaybe multiple sentences. Could combine into one paragraph. Let's craft:
Are you a future Plaidmate? Do you consistently ask, “What’s Next?” Are you nimble and able to adapt to rapidly changing situations? Do you thrive in a fast‑paced environment? Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award‑winning, full‑service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives.
Now The Role heading? Actually after that they say "The RoleYou’ll be the builder..." We could treat that as part of About the role or maybe separate. But we already have About the role. Could incorporate "The Role" description into About the role as well. But we might duplicate. Better to treat "The Role" as part of About the role. The content after "The Role" is description of role: builder on web team etc. That is substantive. Should we put that under About the role or Responsibilities? It's more about role description. Could be part of About the role. But we already have Responsibilities section for duties. The role description includes: "You’ll be the builder on our web team: part front-end developer, part creative collaborator, part power user of automated development tooling. One day you’re turning a Figma design into a polished, production-ready site, the next you’re showing a designer what a scroll animation could do for their concept, or building a custom plugin that gives a client something off-the-shelf can’t. You’ll build hands-on in WordPress and Elementor, work with automated development tooling every day, and experiment with agentic workflows where the use case fits. You direct the work, test it, refine it, and own the result. You’ll collaborate closely with design, account, and leadership to bring websites and applications to life." That seems like responsibilities as well. Could merge with Responsibilities. But we already have a detailed Responsibilities list from "What You'll Do". The role description is more narrative overview. Could keep as part of About the role. Thus About the role will include intro + The Role description. Let's combine. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's write:About the role
Are you a future Plaidmate? Do you consistently ask, “What’s Next?” Are you nimble and able to adapt to rapidly changing situations? Do you thrive in a fast‑paced environment? Think you could be THE PLAID AGENCY’s next Digital + Content Marketing Manager? We’re THE PLAID AGENCY…an award‑winning, full‑service advertising agency specializing in customer insights, fundamental fierceness and a passion to deliver. We are growing and searching for a highly motivated Digital + Content Marketing Manager to join our team. This is a "roll up your sleeves" opportunity to jump in and create, execute and evaluate digital and traditional marketing strategies and initiatives. You’ll be the builder on our web team: part front‑end developer, part creative collaborator, part power user of automated development tooling. One day you’re turning a Figma design into a polished, production‑ready site, the next you’re showing a designer what a scroll animation could do for their concept, or building a custom plugin that gives a client something off‑the‑shelf can’t. You’ll build hands‑on in WordPress and Elementor, work with automated development tooling every day, and experiment with agentic workflows where the use case fits. You direct the work, test it, refine it, and own the result. You’ll collaborate closely with design, account, and leadership to bring websites and applications to life.
Responsibilities
Requirements