EverPro - Web Developer

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, Qualifications (Required, Preferred), Responsibilities (Front-End Development & CMS Management, Site Performance & Technical Optimization, Conversion Rate Optimization (CRO) Support, Web Infrastructure & Governance, Cross-Functional Collaboration, Ways to Work & Team Posture). Also Benefits and Perks, Compensation (Pay). Also Where: Remote, US (Schedule? location). We need to include sections only when real content. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "EverCommerce uses approved artificial intelligence ..."? That's maybe not boilerplate but could be considered policy; but it's not required to keep? It's not substantive about the role; it's a general statement. Probably remove as it's not specific to role. Also remove "EverCommerce is an equal opportunity employer..." etc. Also remove "We look forward to reviewing your credentials..." etc. Also remove "Please note that you must be eligible to work without sponsorship..." maybe keep as part of location? It's a requirement but could be considered boilerplate? It's a specific eligibility requirement; but it's not a duty/benefit. Might keep as part of "Where" or a note. However instructions: remove EEO/equal-opportunity/scam-warning boilerplate. The sponsorship note is not EEO but maybe still boilerplate? It's a requirement for eligibility; could be kept as a short p under Where or Requirements. I'd keep it as a short p under "Location & Eligibility" maybe not a heading. But we only have headings for specific sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Position Summary (could be About the role). Qualifications Required and Preferred (could be Qualifications). Responsibilities (list of duties). Benefits and Perks (Benefits). Compensation (Pay). Where: Remote, US (Schedule? location). Could be Schedule? Actually schedule is about work hours; not given. Location is remote US. Could be under "Schedule"? Not appropriate. Maybe we can omit Schedule section because no schedule info. Could put location under "About the role" as a paragraph. We need to preserve all substantive information. So we need to include location and eligibility note. We'll create sections:

  About the role

  Position summary paragraph...

  Responsibilities

  • ... each duty as list items. We have many duty paragraphs; we can break into list items. We need to extract duties from the sections: Front-End Development & CMS Management, Site Performance & Technical Optimization, Conversion Rate Optimization (CRO) Support, Web Infrastructure & Governance, Cross-Functional Collaboration, Ways to Work & Team Posture. We'll create list items summarizing each bullet. But we must not invent or summarize away detail; we need to preserve ALL substantive information. That means we cannot condense too much; we need to keep details. However we can use list items each containing a sentence or multiple sentences; that's okay. We'll need to include all details from those sections. Let's extract each duty paragraph: Front-End Development & CMS Management: - Build, update, and maintain marketing landing pages and site sections across multiple product domains using CMS platforms (e.g., WordPress, Webflow, or equivalent). - Write clean, semantic HTML5, CSS3, and JavaScript to implement designs with pixel-level accuracy and cross-browser compatibility. - Configure and extend CMS themes, templates, custom page builders, and reusable component libraries. - Implement and maintain responsive design patterns optimized for mobile, tablet, and desktop breakpoints. Site Performance & Technical Optimization: - Own Core Web Vitals performance metrics (LCP, INP, CLS) across all product marketing sites, proactively identifying and resolving issues. - Implement image optimization, lazy loading, script deferral, CDN configuration, and caching strategies to drive measurable page speed improvements. - Execute technical SEO and AEO/GEO site-readiness requirements including schema markup (JSON-LD), meta tags, canonical tags, hreflang, and XML sitemaps. - Ensure AI bot crawl accessibility (Googlebot, GPTBot, ClaudeBot, PerplexityBot) by verifying robots.txt configurations, crawl permissions, and LLM-consumability of site content. - Monitor site health via platforms such as Google Search Console, Screaming Frog, or similar tools and surface issues to the organic growth team. Conversion Rate Optimization (CRO) Support: - Implement A/B and multivariate tests using experimentation platforms (e.g., Google Optimize, VWO, or equivalent), following a structured test-and-learn framework. - Support AI-referred CRO initiatives by building and testing landing page variants optimized for intent signals from AI-referred traffic sources. - Configure and maintain tracking infrastructure including GTM tag deployment, GA4 event schemas, and conversion pixel integration across paid and organic channels. - Partner with Paid Media and Organic Growth teams to build and QA campaign-specific landing pages, ensuring correct UTM parameter capture and downstream attribution. Web Infrastructure & Governance: - Maintain web development documentation including site maps, URL redirect logs, A/B test registers, and deployment runbooks. - Manage staging, UAT, and production deployment workflows using version control (Git) and maintain organized branching conventions. - Support the implementation of a human-in-the-loop web deployment approval process, coordinating review steps with the Marketing Leadership Team as scoped. - Ensure WCAG 2.1 AA accessibility compliance across all new and updated pages. - Monitor and maintain SSL certificates, domain configurations, and third-party script governance. Cross-Functional Collaboration: - Collaborate with agency partners and internal stakeholders to standardize web deployment workflows and documentation. - Act as a key implementation partner for SEO, AEO/GEO, and CRO initiatives originating from the Organic Growth and Paid Media teams, in coordination with the Manager, Web Development. - Partner with product marketing and brand teams to ensure new campaign launches are fully integrated with the site infrastructure on time and on spec. - Provide technical scoping estimates for incoming web requests, contributing input to roadmap discussions led by the Manager, Web Development. Ways to Work & Team Posture: - Operates effectively in a fast-moving environment where priorities shift to meet business needs, re-sequencing work without losing momentum. - Takes initiative to surface ideas, opportunities, and improvements that benefit Marketing and partner functions across the organization. - Brings a team-first mindset, shares context generously, pairs with peers and the agency partner to unblock work, and contributes beyond the strict scope of assigned tickets. - Communicates trade-offs clearly when priorities collide, recommending a path forward rather than waiting for direction. - Communicates technical problems and recommendations in plain language so non-technical partners understand the impact, the options, and what's being asked of them. - Thinks forward as web technologies, AI tooling, and the broader martech landscape evolve making implementation choices today that hold up tomorrow rather than optimizing only for the immediate ask. Now Qualifications Required and Preferred. Required: - 2–5 years of professional web development experience, with a portfolio demonstrating marketing site or SaaS product site work. - Proficiency in HTML5, CSS3, and JavaScript (vanilla JS; React & Next.js familiarity a plus). - Object-oriented PHP (Laravel a plus). - Hands-on CMS experience with at least one major platform (WordPress, Webflow, HubSpot CMS, or equivalent) including custom theme/template development. - Working knowledge of responsive design principles and cross-browser testing methodologies. - Familiarity with Core Web Vitals measurement, on-page performance optimization techniques, and the unique challenges of optimizing marketing sites where third-party scripts, CMS templates, and campaign launches constantly push against page speed. - Experience with Google Tag Manager, GA4, and conversion tracking implementation. - Version control proficiency using Git (branching, pull requests, merge workflows). - Strong communication skills with the ability to translate technical concepts for non-technical marketing stakeholders. Preferred: - Experience in a multi-product or multi-brand SaaS marketing environment. - Familiarity with technical SEO implementation including schema markup, structured data, and AEO/GEO content formatting. - Exposure to A/B testing and conversion rate optimization frameworks. - Understanding of marketing funnels, attribution models, and how web, analytics, CRM, and ad platforms connect end-to-end. - Knowledge of WCAG accessibility standards. - Experience working alongside an external agency or offshore development partner. - Familiarity with AWS, Cloudflare, or comparable cloud/CDN infrastructure. - Hands-on experience using AI coding assistants (e.g., GitHub, Claude Code) to accelerate development velocity, generate boilerplate, and debug complex front-end issues. - Familiarity with AI-native web tooling — including LLM-powered CMS and generative UI prototyping tools. - A demonstrated curiosity about integrating these capabilities into a marketing web workflow. - Working knowledge of what makes web content LLM-consumable: structured data, schema concise and authoritative prose patterns, and technical configurations that enable AI crawlers to surface site content in AI-generated search responses. We could combine Required and Preferred under Qualifications section, maybe separate subheadings? But only allowed headings are the list; we could just put all qualifications in a
    with maybe note which are preferred? But we need to preserve all info; we can include both required and preferred as list items, maybe prefix with "(Preferred)" for those. Alternatively we could have two subsections but not allowed headings besides the list. We could still use

    for "Required Qualifications" and "Preferred Qualifications" but those are not in the allowed list? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still use other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. Thus we can have a single Qualifications section with list items, marking preferred. Now Benefits and Perks: - Flexibility to work where/how you want within your country of employment – in-office, remote, or hybrid - Continued investment in your professional development - Day 1 robust health and wellness benefits, including an annual wellness stipend - 401k with up to a 4% match and immediate vesting - Flexible and generous (FTO) time-off - Employee Stock Purchase Program Now Compensation/Pay: - The target base compensation for this position is $75,000 - $80,000 per year in most US locations. Final offer amounts are determined by multiple factors including location, local market variances, and candidate experience and expertise, and may vary from the amounts listed above. Now Where/Location: - Where: Remote, US - The EverCommerce team is distributed globally, with teams in the U.S., Canada, the U.K., New Zealand, and Australia. With a widely distributed team, we are used to working remotely across different time zones. This role can be based anywhere in the United States – if you’re close to one of our offices, we can set you up in-office or you can work 100% remotely. - Please note that you must be eligible to work without sponsorship to qualify for this position, and this role may require travel to our Corporate Headquarters in Denver, Colorado, or to other office locations around North America. We could put this under a section "Location" but not in allowed headings. Could put under "About the role" as a paragraph. Or we could create a "Schedule" section? Not appropriate. Maybe we can omit Schedule entirely. The location info is substantive; we need to preserve it. We'll include it in About the role paragraph after