[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fVo4JjzWYenaEuvL71j0fAp2Eouqqe2f0mXBesYGuxDY":3},{"company":4,"total":9,"remoteCount":9,"salaryMin":10,"salaryMax":10,"topCategories":11,"topCountries":18,"jobs":23},{"slug":5,"name":6,"logo":7,"variants":8},"lawnstarter","LawnStarter","https:\u002F\u002Fremotive.com\u002Fjob\u002F2090890\u002Flogo",[6],3,null,[12,15],{"name":13,"count":14},"Engineering",2,{"name":16,"count":17},"Design",1,[19,21],{"name":20,"count":14},"Anywhere in the World",{"name":22,"count":17},"Brazil",[24,64,72],{"id":25,"slug":26,"title":27,"company":6,"company_logo_url":7,"category":13,"subcategory":28,"job_type":29,"experience_level":30,"remote_type":31,"country":22,"city":10,"language":32,"salary_min":10,"salary_max":10,"salary_currency":33,"salary_type":10,"skills":34,"benefits":10,"description_short":56,"source_url":57,"apply_url":57,"source_site":58,"is_active":59,"is_featured":60,"views_count":61,"click_count":61,"posted_at":62,"collected_at":63,"expires_at":10,"visa_sponsorship":60,"company_size":10},54084,"staff-product-engineer-lawnstarter-a3d75ce1e21d","Staff Product Engineer","Product Management","full-time","lead","remote","en","USD",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"AWS","backend","frontend","php","react","security","UI\u002FUX","AI\u002FML","jira","react native","research","documentation","laravel","Typescript ","people management","prototyping","engineering management","marketplace","github","REST","datadog","\u003Cp>\u003Cstrong>About LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services — operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>About Engineering at LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>We're restructuring engineering around \u003Cstrong>initiative teams\u003C\u002Fstrong>: a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric.\u003C\u002Fp>\n\u003Cp>We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides.\u003C\u002Fp>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Role\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle.\u003C\u002Fp>\n\u003Cp>You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What makes this role different:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>You lead AI agents, not humans.\u003C\u002Fstrong> Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>You own an outcome, not a ticket queue.\u003C\u002Fstrong> Problem-framing through production through the metric review 2–4 weeks after launch.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>You partner horizontally with PM and design.\u003C\u002Fstrong> No tech lead above you. No architect approval. No ticket grooming committee.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The bar is staff, not senior.\u003C\u002Fstrong> You make the call when the call needs to be made. If you're waiting to be told, this isn't the role.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>What You'll Own\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The technical approach\u003C\u002Fstrong> — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agent-led implementation quality\u003C\u002Fstrong> — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cross-functional partnership\u003C\u002Fstrong> — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The initiative outcome\u003C\u002Fstrong> — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the \"did it work\" answer.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A high bar for what ships under your name\u003C\u002Fstrong> — production correctness, security posture, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Problems to Solve\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Leading AI agents at staff-level quality\u003C\u002Fstrong>\u003Cbr>Most of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team?\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Owning an outcome without a tech lead\u003C\u002Fstrong>\u003Cbr>You don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists?\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Shipping outcomes, not features\u003C\u002Fstrong>\u003Cbr>The initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to \u003Cem>not\u003C\u002Fem> build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling?\u003C\u002Fp>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>What Success Looks Like (Year 1)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Initiative outcomes hit\u003C\u002Fstrong> — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agent workflow that travels\u003C\u002Fstrong> — The prompts, evals, and review loop you built for your initiative are adopted by at least one other engineer on an adjacent initiative.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cycle time\u003C\u002Fstrong> — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter than the pre-restructure baseline.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zero \"agent-shipped that\" incidents\u003C\u002Fstrong> — No customer- or pro-facing regression traceable to agent-authored code that you missed in review.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Visible leverage\u003C\u002Fstrong> — Other engineers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Who You Are\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI-native.\u003C\u002Fstrong> Claude Code, Cursor, Codex, or equivalent are how you ship — daily, on production work. You have opinions about prompts, evals, agent loops, MCP servers, and review workflows, and you know when to let the agent run vs. write it yourself. This is unlikely to be a good fit if you describe AI coding as \"something you're exploring\" or prefer to write everything by hand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Already operating at lead level.\u003C\u002Fstrong> You may currently be titled Senior, Staff, Lead, or Principal — but in practice you've been the person making the call, shipping the hard thing, and answering for whether it worked. This is unlikely to be a good fit if you've always had a tech lead breaking down the work for you.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Outcome-driven, not output-driven.\u003C\u002Fstrong> You measure your week in \"did the metric move\" and \"did the experience get better,\" not in tickets closed. You read the post-launch dashboard and you own the answer. This is unlikely to be a good fit if you take pride in volume of code shipped or feel uncomfortable being measured on a number you don't fully control.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>A strong horizontal partner.\u003C\u002Fstrong> You hold your own with a strong PM and a strong designer. You bring engineering judgment to product calls and product judgment to engineering calls. This is unlikely to be a good fit if you hide behind \"that's product's decision\" or default to RICE-scoring tickets handed down to you.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Decisive and documented.\u003C\u002Fstrong> Architecture decisions, data-model choices, rollout plans — you write them down, get fast input, and move. This is unlikely to be a good fit if you wait for consensus on questions that have a clear right answer, or if you make calls and never write them down.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Raises the floor, not just the ceiling.\u003C\u002Fstrong> Your impact compounds beyond your own initiative because you leave artifacts — agent workflows, evals, runbooks, post-launch reviews. This is unlikely to be a good fit if you're a lone wolf who ships brilliantly but leaves nothing reusable behind.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cares about customers and pros.\u003C\u002Fstrong> This is a real-world marketplace with real people on both sides. This is unlikely to be a good fit if you're chasing pure engineering elegance over business and customer outcomes.\u003C\u002Fp>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>This Role Is NOT\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A tech lead in an old-style team.\u003C\u002Fstrong> No 4–5 engineers reporting up to you on technical direction. The team is you + PM + designer + EM, with AI agents doing most of the implementation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A management role today.\u003C\u002Fstrong> People management is the EM's job in this role. That said, the path can grow into management for those who want it — it's an open door, not a closed one.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A platform-only or architecture-only role.\u003C\u002Fstrong> You're a Product Engineer. You ship features that move metrics, end-to-end. Platform work happens inside the initiative when it's needed for the outcome.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A \"let AI do everything\" role.\u003C\u002Fstrong> Agents handle implementation grunt work. You handle judgment, design, safety, and accountability. The bar is \u003Cem>higher\u003C\u002Fem> than the old senior bar, not lower.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A research role.\u003C\u002Fstrong> This is shipping to a marketplace with $100M+ in bookings. Customers and pros are using what you ship inside the same week.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp> \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Tech You'll Touch\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>AI agents\u003C\u002Fstrong> — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Backend\u003C\u002Fstrong> — PHP\u002FLaravel\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Frontend\u003C\u002Fstrong> — TypeScript\u002FReact\u002FReact Native (customer & pro apps, web and mobile)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data\u003C\u002Fstrong> — Redshift, dbt, Segment, Airflow\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Infra\u003C\u002Fstrong> — AWS, Datadog, Sentry, GitHub Actions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation & process\u003C\u002Fstrong> — Brain (Claude Code skills + docs repo), Confluence, Jira\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You don't need every box checked. You need deep skill in at least one of our stacks plus credible production experience with AI coding agents.\u003C\u002Fp>\n\u003Cp>\u003Cbr>\u003Cbr>\u003Cstrong>Benefits\u003C\u002Fstrong>\u003Cbr>\u003Cbr>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Competitive salary of USD $80,000–$100,000 annual base\u003C\u002Fli>\n\u003Cli>Work from anywhere\u003C\u002Fli>\n\u003Cli>High ownership and autonomy\u003C\u002Fli>\n\u003Cli>Fast-moving team that loves to build, learn, and grow\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fremotive.com\u002Fremote-jobs\u002Fproduct\u002Fstaff-product-engineer-2090890","remotive",true,false,0,"2026-05-21T16:42:09+00:00","2026-05-23T11:06:46.453837+00:00",{"id":65,"slug":66,"title":27,"company":6,"company_logo_url":10,"category":13,"subcategory":10,"job_type":29,"experience_level":30,"remote_type":31,"country":20,"city":10,"language":32,"salary_min":10,"salary_max":10,"salary_currency":33,"salary_type":10,"skills":10,"benefits":10,"description_short":67,"source_url":68,"apply_url":68,"source_site":69,"is_active":59,"is_featured":60,"views_count":61,"click_count":61,"posted_at":70,"collected_at":71,"expires_at":10,"visa_sponsorship":60,"company_size":10},49794,"staff-product-engineer-lawnstarter-1ff511a4225e","\u003Cp>\n \u003Cstrong>Headquarters:\u003C\u002Fstrong> São Paulo, Brazil\n \u003Cbr>\u003Cstrong>URL:\u003C\u002Fstrong> \u003Ca href=\"http:\u002F\u002Flawnstarter.com\">http:\u002F\u002Flawnstarter.com\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp>\u003Cstrong>About LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services — operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>About Engineering at LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>We're restructuring engineering around \u003Cstrong>initiative teams\u003C\u002Fstrong>: a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric.\u003C\u002Fp>\n\u003Cp>We're betting that 1-2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides.\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Role\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle.\u003C\u002Fp>\n\u003Cp>You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What makes this role different:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>You lead AI agents, not humans.\u003C\u002Fstrong> Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>You own an outcome, not a ticket queue.\u003C\u002Fstrong> Problem-framing through production through the metric review 2-4 weeks after launch.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>You partner horizontally with PM and design.\u003C\u002Fstrong> No tech lead above you. No architect approval. No ticket grooming committee.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>The bar is staff, not senior.\u003C\u002Fstrong> You make the call when the call needs to be made. If you're waiting to be told, this isn't the role.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What You'll Own\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>The technical approach\u003C\u002Fstrong> — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Agent-led implementation quality\u003C\u002Fstrong> — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Cross-functional partnership\u003C\u002Fstrong> — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth).\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>The initiative outcome\u003C\u002Fstrong> — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2-4 weeks post-launch and share the \"did it work\" answer.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A high bar for what ships under your name\u003C\u002Fstrong> — production correctness, security posture, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Problems to Solve\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Leading AI agents at staff-level quality\u003C\u002Fstrong>\u003Cbr>Most of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team?\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Owning an outcome without a tech lead\u003C\u002Fstrong>\u003Cbr>You don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists?\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Shipping outcomes, not features\u003C\u002Fstrong>\u003Cbr>The initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to \u003Cem>not\u003C\u002Fem> build, and have the discipline to follow up 2-4 weeks after launch even when the next initiative is calling?\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What Success Looks Like (Year 1)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>Initiative outcomes hit\u003C\u002Fstrong> — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it).\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Agent workflow that travels\u003C\u002Fstrong> — The prompts, evals, and review loop you built for your initiative are adopted by at least one other engineer on an adjacent initiative.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Cycle time\u003C\u002Fstrong> — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter than the pre-restructure baseline.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Zero \"agent-shipped that\" incidents\u003C\u002Fstrong> — No customer- or pro-facing regression traceable to agent-authored code that you missed in review.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Visible leverage\u003C\u002Fstrong> — Other engineers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Who You Are\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI-native.\u003C\u002Fstrong> Claude Code, Cursor, Codex, or equivalent are how you ship — daily, on production work. You have opinions about prompts, evals, agent loops, MCP servers, and review workflows, and you know when to let the agent run vs. write it yourself. This is unlikely to be a good fit if you describe AI coding as \"something you're exploring\" or prefer to write everything by hand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Already operating at lead level.\u003C\u002Fstrong> You may currently be titled Senior, Staff, Lead, or Principal — but in practice you've been the person making the call, shipping the hard thing, and answering for whether it worked. This is unlikely to be a good fit if you've always had a tech lead breaking down the work for you.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Outcome-driven, not output-driven.\u003C\u002Fstrong> You measure your week in \"did the metric move\" and \"did the experience get better,\" not in tickets closed. You read the post-launch dashboard and you own the answer. This is unlikely to be a good fit if you take pride in volume of code shipped or feel uncomfortable being measured on a number you don't fully control.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>A strong horizontal partner.\u003C\u002Fstrong> You hold your own with a strong PM and a strong designer. You bring engineering judgment to product calls and product judgment to engineering calls. This is unlikely to be a good fit if you hide behind \"that's product's decision\" or default to RICE-scoring tickets handed down to you.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Decisive and documented.\u003C\u002Fstrong> Architecture decisions, data-model choices, rollout plans — you write them down, get fast input, and move. This is unlikely to be a good fit if you wait for consensus on questions that have a clear right answer, or if you make calls and never write them down.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Raises the floor, not just the ceiling.\u003C\u002Fstrong> Your impact compounds beyond your own initiative because you leave artifacts — agent workflows, evals, runbooks, post-launch reviews. This is unlikely to be a good fit if you're a lone wolf who ships brilliantly but leaves nothing reusable behind.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cares about customers and pros.\u003C\u002Fstrong> This is a real-world marketplace with real people on both sides. This is unlikely to be a good fit if you're chasing pure engineering elegance over business and customer outcomes.\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>This Role Is NOT\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>A tech lead in an old-style team.\u003C\u002Fstrong> No 4-5 engineers reporting up to you on technical direction. The team is you + PM + designer + EM, with AI agents doing most of the implementation.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A management role today.\u003C\u002Fstrong> People management is the EM's job in this role. That said, the path can grow into management for those who want it — it's an open door, not a closed one.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A platform-only or architecture-only role.\u003C\u002Fstrong> You're a Product Engineer. You ship features that move metrics, end-to-end. Platform work happens inside the initiative when it's needed for the outcome.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A \"let AI do everything\" role.\u003C\u002Fstrong> Agents handle implementation grunt work. You handle judgment, design, safety, and accountability. The bar is \u003Cem>higher\u003C\u002Fem> than the old senior bar, not lower.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A research role.\u003C\u002Fstrong> This is shipping to a marketplace with $100M+ in bookings. Customers and pros are using what you ship inside the same week.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Tech You'll Touch\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>AI agents\u003C\u002Fstrong> — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Backend\u003C\u002Fstrong> — PHP\u002FLaravel\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Frontend\u003C\u002Fstrong> — TypeScript\u002FReact\u002FReact Native (customer & pro apps, web and mobile)\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Data\u003C\u002Fstrong> — Redshift, dbt, Segment, Airflow\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Infra\u003C\u002Fstrong> — AWS, Datadog, Sentry, GitHub Actions\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Documentation & process\u003C\u002Fstrong> — Brain (Claude Code skills + docs repo), Confluence, Jira\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You don't need every box checked. You need deep skill in at least one of our stacks plus credible production experience with AI coding agents.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefits\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Competitive salary of USD $80,000-$100,000 annual base\u003C\u002Fli>\n\u003Cli>Work from anywhere\u003C\u002Fli>\n\u003Cli>High ownership and autonomy\u003C\u002Fli>\n\u003Cli>Fast-moving team that loves to build, learn, and grow\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Cp>\u003Cstrong>To apply:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-staff-product-engineer\">https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-staff-product-engineer\u003C\u002Fa>\u003C\u002Fp>","https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-staff-product-engineer","weworkremotely","2026-05-21T13:21:50+00:00","2026-05-22T11:05:26.737057+00:00",{"id":73,"slug":74,"title":75,"company":6,"company_logo_url":10,"category":16,"subcategory":10,"job_type":29,"experience_level":76,"remote_type":31,"country":20,"city":10,"language":32,"salary_min":10,"salary_max":10,"salary_currency":33,"salary_type":10,"skills":10,"benefits":10,"description_short":77,"source_url":78,"apply_url":78,"source_site":69,"is_active":59,"is_featured":60,"views_count":61,"click_count":61,"posted_at":79,"collected_at":80,"expires_at":10,"visa_sponsorship":60,"company_size":10},45497,"senior-webflow-designer-lawnstarter-d6d89f82515b","Senior Webflow Designer","senior","\u003Cp>\n \u003Cstrong>Headquarters:\u003C\u002Fstrong> United States\n \u003Cbr>\u003Cstrong>URL:\u003C\u002Fstrong> \u003Ca href=\"http:\u002F\u002Flawnstarter.com\">http:\u002F\u002Flawnstarter.com\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp>\u003Cstrong>About LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>LawnStarter is the nation's leading on-demand marketplace for lawn care and related services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>About Growth at LawnStarter\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Our Growth team drives customer acquisition and conversion across four brands — LawnStarter, Lawn Love, Home Gnome, and ProBase. The marketing sites are central to that work: thousands of organic SEO pages, landing pages, and core site experiences that need to move as fast as the team iterating on them. Today, making changes to our marketing sites requires engineering support. That bottleneck slows down testing, kills momentum, and means conversion opportunities sit on the table. We're moving to Webflow as the source of truth for our marketing sites, and we need someone to own that transition and everything that follows.\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Role\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>You'll report to the Director of Design but sit on the Growth team day-to-day, working alongside the entire Growth team including the Technical Growth Manager, the CRO Specialist, data analysts, SEO, Paid, and content. Your job is to make our marketing sites fast to change, beautiful, on-brand, and optimized for conversion — without needing an engineer every time something needs to move.\u003C\u002Fp>\n\u003Cp>You'll start with Home Gnome, building it right from the ground up in Webflow. From there, you'll bring LawnStarter, Lawn Love, and ProBase into a componentized Webflow design system. This is a chance to define how all four brands show up on the web.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The three Growth team roles you'll work with most closely\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The Designer, Technical Growth Manager, and CRO Specialist are three peers on the Growth team — one tight unit, not three separate orgs. The work runs as a constant collaboration, with the design loop iterating on every test result:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>You (Senior Webflow Designer)\u003C\u002Fstrong> — design the foundation: page templates, page architecture, the component library and design system, interactions and animations, and the UX\u002FUI standards (usability, accessibility, conversion best practices) every page is held to. The system you build needs to be robust and flexible enough that the Technical Growth Manager and CRO Specialist can spin up new pages from it without coming back to design every time. You step in when there's a new template, a new pattern, a major test-driven iteration, or a brand-new flow.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Technical Growth Manager\u003C\u002Fstrong> — takes your templates, page architecture, and components and makes them production-ready: CMS architecture, programmatic page infrastructure, production page builds, structured data, analytics implementation, and the same-day test rollout SLA. Once the foundation is in place, they spin up new pages directly from the system — that's how the team moves fast.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>CRO Specialist\u003C\u002Fstrong> — owns the conversion testing roadmap, test design, hypotheses, and reads results. They can also spin up test pages from your templates and components when speed matters. You and the CRO Specialist work tightly together: they bring the conversion lens, you bring the design and UX lens, and you iterate on templates, page architecture, and components based on what the data shows.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The whole model only works through close collaboration. The system isn't handed off and forgotten — it evolves as the three of you ship, test, and learn together.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What makes this role different:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>You design AND build in Webflow\u003C\u002Fstrong>: This isn't a Figma-to-handoff role. You design the page templates, page architecture, components, and UX\u002FUI standards that define the marketing sites, and you build them directly in Webflow. Design happens in Webflow, not Figma.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Embedded with Growth, not siloed in Design\u003C\u002Fstrong>: You sit with the people running experiments, analyzing conversion data, and optimizing funnels. Design decisions here are measured in conversion rates, not likes.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Multi-brand site ownership\u003C\u002Fstrong>: You design the marketing site experience across four brands — each with its own identity, sharing a foundation you build and maintain.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>AI-native by default\u003C\u002Fstrong>: Claude Code and Claude are core to how you work, not novelty add-ons.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What You'll Own\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>The marketing site design and foundation across four brands\u003C\u002Fstrong>: Page templates, page architecture (section flow, hierarchy, layout patterns), navigation, key flows, hero patterns, conversion patterns. The system you design needs to be flexible and robust enough that the Technical Growth Manager and CRO Specialist can spin up new pages directly from it — without coming back to design for every page.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Visual design and brand execution at a high bar\u003C\u002Fstrong>: This is core to the role. The marketing sites need to look modern, polished, and unmistakably on-brand for each of the four brands — and they need to hold up against the best marketing sites on the web. You're the quality bar for typography, spacing, hierarchy, color, imagery, composition, and all the details that separate good from great. Strong visual design and disciplined brand execution are non-negotiable.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Webflow design system and component library\u003C\u002Fstrong>: Build and maintain the system across all four brands — components, design tokens, page templates, shared interaction patterns. The system is the source of truth for how every brand looks, behaves, and is built, and the foundation the Technical Growth Manager and CRO Specialist build new pages from.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>UX\u002FUI, usability, and accessibility\u003C\u002Fstrong>: You bring the discipline. Every component, template, and page reflects current best practices for usability, conversion, and WCAG accessibility. This isn't a checklist run at the end — it's how you design from the start.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Interactions and motion\u003C\u002Fstrong>: A core part of the role, not a finishing touch. You design and build purposeful interactions and animations — micro-interactions, scroll behavior, loading states, motion-driven storytelling — that elevate the brands and make pages feel premium. You use Webflow's native tools where they fit and write custom CSS or JS when they don't.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Test-ready designs and variants\u003C\u002Fstrong>: Partner closely with the CRO Specialist. You design the templates, components, and variants that power tests so they can be spun up and iterated quickly. The CRO Specialist defines hypotheses and reads results; together you iterate on the templates and components based on what wins. The Technical Growth Manager rolls winners out.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Production handoff and QA\u003C\u002Fstrong>: Hand off completed templates and built components to the Technical Growth Manager, who wires them into the CMS, builds production pages, and ships at scale. You stay involved through QA so production matches design intent — and you iterate on the system based on what the team learns shipping it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Problems to Solve\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Our marketing sites depend on engineering for every change\u003C\u002Fstrong> Today, even simple updates require a developer. That means the Growth team can't iterate at the speed they need to. New pages wait in a queue. You're the design half of the unblock: a Webflow design system the Technical Growth Manager can build with, so marketing site changes happen fast without engineering involvement.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Our marketing sites aren't designed at the level we need\u003C\u002Fstrong> Functional, but not designed. There are no shared page templates, no Webflow component library, no design tokens, no consistent UX\u002FUI patterns, no interaction language. You build the foundation: a designed site, page templates, a component library, and the UX\u002FUI standards (usability, accessibility, conversion best practices) that everything is held to. The Technical Growth Manager makes it production-ready; you make it worth shipping.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Thousands of SEO pages need to look modern, feel premium, and convert\u003C\u002Fstrong> We have over a thousand organic SEO pages across our brands. These pages drive significant traffic and revenue, but they need to look modern, feel polished, be accessible, and maintain brand and UX consistency at scale. You design the page templates, the components, and the UX patterns; the Technical Growth Manager wires them into the CMS and ships them at scale. Together you make the SEO portfolio look like a real brand, not a content farm.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Four brands need to look distinct but share a foundation\u003C\u002Fstrong> Home Gnome, LawnStarter, Lawn Love, and ProBase each have their own visual identity. But the underlying design system — components, tokens, interaction patterns — should be shared where it makes sense.\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What Success Looks Like (Year 1)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>Home Gnome fully designed and live in Webflow\u003C\u002Fstrong> — page templates, components, interactions, and UX\u002FUI standards that meet a high bar for visual design, brand execution, usability, and accessibility, with the Technical Growth Manager scaling it across pages without engineering\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A complete Webflow design system the team can self-serve from\u003C\u002Fstrong> — components, design tokens, page templates, and UX\u002FUI standards solid enough that the Technical Growth Manager and CRO Specialist can spin up new pages directly from the system without coming back to design every time\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Test-ready designs and variants ready to iterate fast\u003C\u002Fstrong> — when the CRO Specialist needs a hero variant, a new template, or a CTA test, the components are ready to test or you ship the new design quickly and iterate based on results\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>SEO templates designed for scale\u003C\u002Fstrong> — page templates that set the visual, UX, and accessibility bar across thousands of programmatic pages the Technical Growth Manager wires into the CMS\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Interactions and motion that make the brands feel premium\u003C\u002Fstrong> — purposeful animation across the design system, not bolted-on after launch\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>WCAG-compliant by default\u003C\u002Fstrong> — accessibility is a baseline, not a project\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A working iteration loop with the CRO Specialist\u003C\u002Fstrong> — test results consistently flow back into your templates and components\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Site design migration underway\u003C\u002Fstrong> for LawnStarter and Lawn Love\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>The Technical Growth Manager and CRO Specialist consider you essential\u003C\u002Fstrong> — they can't imagine shipping or testing without you\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Requirements\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Who You Are\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>A top-tier visual and brand designer.\u003C\u002Fstrong> Strong visual design and disciplined brand execution are at the core of this role, not a side requirement. Your work is modern, polished, and unmistakably on-brand. You hold up against the best marketing sites on the web. You care deeply about typography, spacing, hierarchy, color, imagery, composition, and the details that separate good from great. You can execute within established brand guidelines while pushing the visual quality forward, and you can hold the line across four distinct brands without letting any of them drift. This is unlikely to be a good fit if visual design or brand discipline is secondary to your other skills, or if you rely heavily on templates without elevating them.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>A Webflow expert.\u003C\u002Fstrong> You've built and maintained complex, multi-page Webflow sites with real architectural rigor — not just pretty one-pagers. You understand component architecture, design systems, dynamic content, advanced interactions, and how to keep a large site clean and performant. You can structure a page so it works at scale, not just for one hero shot. This is unlikely to be a good fit if you've only used Webflow for small projects or treat it as a visual tool rather than a design and build platform.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>UX\u002FUI disciplined.\u003C\u002Fstrong> You bring real expertise in usability, accessibility (WCAG), and conversion best practices — and you apply it to every component, template, and page. You can articulate why a layout works (or doesn't) for the user, not just how it looks. You design for clarity, scannability, and performance, and you treat accessibility as a baseline, not a finishing touch. This is unlikely to be a good fit if you can't speak to UX principles beyond aesthetics or treat usability and accessibility as someone else's job.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Collaborative by default.\u003C\u002Fstrong> This role only works through tight collaboration with the Technical Growth Manager (on production handoff and feasibility) and the CRO Specialist (on test design and iteration). You give and take feedback well, you're comfortable handing off work and staying involved through QA, and you treat test results as input rather than judgment. This is unlikely to be a good fit if you prefer to work alone or get defensive when data contradicts your design choices.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Growth-team fluent.\u003C\u002Fstrong> You've worked alongside CMOs, SEO teams, paid teams, content teams, CRO specialists, data analysts, and engineers before. You understand conversion funnels, A\u002FB testing, and how to support experiments and iterate quickly. You make decisions based on data, not just aesthetics. This is unlikely to be a good fit if you've only worked in brand or product design teams and aren't familiar with the pace and priorities of growth.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Self-directed and fast.\u003C\u002Fstrong> You take a brief, run with it, and ship. You don't need someone managing your queue or reviewing every decision. When there's a new template to design, a new pattern to add to the system, or a test result that points to an iteration, you turn it around quickly without sacrificing quality. This is unlikely to be a good fit if you need detailed direction for each project or prefer a slower, more deliberate pace.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI-native.\u003C\u002Fstrong> You use Claude Code and Claude as core parts of your workflow — generating component code, exploring design directions, drafting interaction logic, and accelerating everything from naming to layout iteration. You treat AI as a design and build partner, not a novelty. This is unlikely to be a good fit if you're skeptical of AI tools or insist on building everything from scratch.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Technically capable beyond Webflow native.\u003C\u002Fstrong> Webflow's native tools won't cover everything — especially the interactions, animations, and complex components you'll build. You can write custom CSS and JavaScript when Webflow falls short, and you can read enough code to debug a third-party embed or extend an existing component. The Technical Growth Manager owns tracking and integrations; you own the code that makes the design system feel alive. This is unlikely to be a good fit if you strictly avoid code or rely on others to handle anything beyond drag-and-drop.\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>This Role Is NOT\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>A Figma-to-Webflow production role\u003C\u002Fstrong>: The design system for growth and marketing lives in Webflow. You're not translating someone else's mockups — you're designing and building directly.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>The production builder for SEO and CMS pages\u003C\u002Fstrong>: The Technical Growth Manager owns CMS architecture, programmatic page infrastructure, and the production builds for thousands of SEO URLs. You design the templates and components; the Technical Growth Manager wires them into production.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>The owner of test rollouts\u003C\u002Fstrong>: The Technical Growth Manager owns running tests live and the same-day rollout SLA. Your job is upstream — shipping the variants and components that make tests possible.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A brand design role\u003C\u002Fstrong>: You'll maintain brand consistency, but you're not creating brand identities.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A role with a clean starting point\u003C\u002Fstrong>: The current marketing sites need significant work. You're inheriting complexity and building toward simplicity — not maintaining something that already works well.\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>A solo design role\u003C\u002Fstrong>: You'll collaborate regularly with the Director of Design and the brand\u002Fproduct design team on component development and brand standards. Day-to-day, your closest partners are the Technical Growth Manager and CRO Specialist on the Growth team.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Benefits\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cstrong>Base salary\u003C\u002Fstrong>: $110K - $140K.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>401k\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Healthcare\u003C\u002Fstrong>: Medical, dental, and vision\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Fully remote\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\n\u003Cstrong>Unlimited PTO\u003C\u002Fstrong>: We focus on results. Take what you need.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u002Fp>\n\u003Cp>\u003Cem>LawnStarter provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, or genetics. We comply with applicable state and local laws governing nondiscrimination in employment.\u003C\u002Fem>\u003C\u002Fp>\n\n\u003Cp>\u003Cstrong>To apply:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-senior-webflow-designer\">https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-senior-webflow-designer\u003C\u002Fa>\u003C\u002Fp>","https:\u002F\u002Fweworkremotely.com\u002Fremote-jobs\u002Flawnstarter-senior-webflow-designer","2026-05-20T18:10:26+00:00","2026-05-21T11:05:19.424783+00:00"]