Headquarters: Porto Alegre, State of Rio Grande do Sul, Brazil URL: http://lawnstarter.com About LawnStarter 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. About Engineering at LawnStarter We build in small, focused initiative teams: a Product Engineer working alongside a PM and a designer, supported by an Engineering Manager who helps you grow. You'll also work shoulder-to-shoulder with engineering peers across initiatives in a shared codebase. The whole team owns whether the work moves its metric. AI coding agents are a force multiplier here — they give a small, senior team the leverage to ship more, faster, and at a higher bar for quality. We hire engineers who are wired for ownership and energized by shipping to a real marketplace with customers and pros on both sides. The Role You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong. Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer. A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at a staff-level quality bar Most of the code on your initiative will be authored by AI agents. The craft is making them ship as if a senior engineer wrote it: prompts that encode our conventions, evals that catch issues before merge, tests that exercise the edges, observability that catches a regression before a customer does. How do you build a workflow that lets a small team ship far more than its size would suggest? Owning decisions with high autonomy You have real latitude to make and document technical calls quickly — with architect review on the big architectural ones and peers to pressure-test your thinking. How do you move fast, keep your team aligned, and stay accountable to the outcome? Shipping outcomes, not features Each initiative is measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit-economics shift. You're accountable for the number alongside your team. How do you scope to actually move it, decide what *not* to build, and have the discipline to follow up 2-4 weeks after launch? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved their metric (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Requirements Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself. Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked. Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer. A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls. Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews. Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both. Good to Know An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it. A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them. Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high. Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira 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. Benefits Competitive salary of USD $80,000-$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow To apply: https://weworkremotely.com/remote-jobs/lawnstarter-staff-software-engineer-product-4

Headquarters: Campinas, State of São Paulo, Brazil URL: http://lawnstarter.com About LawnStarter 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. About Engineering at LawnStarter We build in small, focused initiative teams: a Product Engineer working alongside a PM and a designer, supported by an Engineering Manager who helps you grow. You'll also work shoulder-to-shoulder with engineering peers across initiatives in a shared codebase. The whole team owns whether the work moves its metric. AI coding agents are a force multiplier here — they give a small, senior team the leverage to ship more, faster, and at a higher bar for quality. We hire engineers who are wired for ownership and energized by shipping to a real marketplace with customers and pros on both sides. The Role You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong. Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer. A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at a staff-level quality bar Most of the code on your initiative will be authored by AI agents. The craft is making them ship as if a senior engineer wrote it: prompts that encode our conventions, evals that catch issues before merge, tests that exercise the edges, observability that catches a regression before a customer does. How do you build a workflow that lets a small team ship far more than its size would suggest? Owning decisions with high autonomy You have real latitude to make and document technical calls quickly — with architect review on the big architectural ones and peers to pressure-test your thinking. How do you move fast, keep your team aligned, and stay accountable to the outcome? Shipping outcomes, not features Each initiative is measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit-economics shift. You're accountable for the number alongside your team. How do you scope to actually move it, decide what *not* to build, and have the discipline to follow up 2-4 weeks after launch? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved their metric (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Requirements Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself. Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked. Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer. A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls. Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews. Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both. Good to Know An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it. A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them. Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high. Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira 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. Benefits Competitive salary of USD $80,000-$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow To apply: https://weworkremotely.com/remote-jobs/lawnstarter-staff-software-engineer-product-3

Headquarters: Belo Horizonte, State of Minas Gerais, Brazil URL: http://lawnstarter.com About LawnStarter 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. About Engineering at LawnStarter We build in small, focused initiative teams: a Product Engineer working alongside a PM and a designer, supported by an Engineering Manager who helps you grow. You'll also work shoulder-to-shoulder with engineering peers across initiatives in a shared codebase. The whole team owns whether the work moves its metric. AI coding agents are a force multiplier here — they give a small, senior team the leverage to ship more, faster, and at a higher bar for quality. We hire engineers who are wired for ownership and energized by shipping to a real marketplace with customers and pros on both sides. The Role You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong. Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer. A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at a staff-level quality bar Most of the code on your initiative will be authored by AI agents. The craft is making them ship as if a senior engineer wrote it: prompts that encode our conventions, evals that catch issues before merge, tests that exercise the edges, observability that catches a regression before a customer does. How do you build a workflow that lets a small team ship far more than its size would suggest? Owning decisions with high autonomy You have real latitude to make and document technical calls quickly — with architect review on the big architectural ones and peers to pressure-test your thinking. How do you move fast, keep your team aligned, and stay accountable to the outcome? Shipping outcomes, not features Each initiative is measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit-economics shift. You're accountable for the number alongside your team. How do you scope to actually move it, decide what *not* to build, and have the discipline to follow up 2-4 weeks after launch? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved their metric (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Requirements Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself. Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked. Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer. A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls. Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews. Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both. Good to Know An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it. A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them. Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high. Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira 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. Benefits Competitive salary of USD $80,000-$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow To apply: https://weworkremotely.com/remote-jobs/lawnstarter-staff-software-engineer-product-2

Headquarters: Florianópolis, State of Santa Catarina, Brazil URL: http://lawnstarter.com About LawnStarter 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. About Engineering at LawnStarter We build in small, focused initiative teams: a Product Engineer working alongside a PM and a designer, supported by an Engineering Manager who helps you grow. You'll also work shoulder-to-shoulder with engineering peers across initiatives in a shared codebase. The whole team owns whether the work moves its metric. AI coding agents are a force multiplier here — they give a small, senior team the leverage to ship more, faster, and at a higher bar for quality. We hire engineers who are wired for ownership and energized by shipping to a real marketplace with customers and pros on both sides. The Role You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong. Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer. A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at a staff-level quality bar Most of the code on your initiative will be authored by AI agents. The craft is making them ship as if a senior engineer wrote it: prompts that encode our conventions, evals that catch issues before merge, tests that exercise the edges, observability that catches a regression before a customer does. How do you build a workflow that lets a small team ship far more than its size would suggest? Owning decisions with high autonomy You have real latitude to make and document technical calls quickly — with architect review on the big architectural ones and peers to pressure-test your thinking. How do you move fast, keep your team aligned, and stay accountable to the outcome? Shipping outcomes, not features Each initiative is measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit-economics shift. You're accountable for the number alongside your team. How do you scope to actually move it, decide what *not* to build, and have the discipline to follow up 2-4 weeks after launch? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved their metric (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Requirements Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself. Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked. Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer. A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls. Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews. Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both. Good to Know An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it. A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them. Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high. Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira 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. Benefits Competitive salary of USD $80,000-$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow To apply: https://weworkremotely.com/remote-jobs/lawnstarter-staff-software-engineer-product-1

Headquarters: São Paulo, Brazil URL: http://lawnstarter.com About LawnStarter 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. About Engineering at LawnStarter We build in small, focused initiative teams: a Product Engineer working alongside a PM and a designer, supported by an Engineering Manager who helps you grow. You'll also work shoulder-to-shoulder with engineering peers across initiatives in a shared codebase. The whole team owns whether the work moves its metric. AI coding agents are a force multiplier here — they give a small, senior team the leverage to ship more, faster, and at a higher bar for quality. We hire engineers who are wired for ownership and energized by shipping to a real marketplace with customers and pros on both sides. The Role You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make most calls yourself and bring significant architectural decisions to architect review; you document them, and revisit if the data says you were wrong. Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. Most lines will be agent-authored, and you're accountable for them — held to the same standard as the rest of the team working in a shared codebase. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. The initiative outcome — the metric the initiative was set up to move. With your PM, you present results 2-4 weeks post-launch and share the "did it work" answer. A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at a staff-level quality bar Most of the code on your initiative will be authored by AI agents. The craft is making them ship as if a senior engineer wrote it: prompts that encode our conventions, evals that catch issues before merge, tests that exercise the edges, observability that catches a regression before a customer does. How do you build a workflow that lets a small team ship far more than its size would suggest? Owning decisions with high autonomy You have real latitude to make and document technical calls quickly — with architect review on the big architectural ones and peers to pressure-test your thinking. How do you move fast, keep your team aligned, and stay accountable to the outcome? Shipping outcomes, not features Each initiative is measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit-economics shift. You're accountable for the number alongside your team. How do you scope to actually move it, decide what *not* to build, and have the discipline to follow up 2-4 weeks after launch? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3-4 initiatives end-to-end, and at least two clearly moved their metric (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Requirements Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today — daily, on production work. You have real opinions about prompts, evals, agent loops, and review workflows, and you know when to let the agent run versus write it yourself. Operating at a lead level. Whatever your current title, you've been the person making the call, shipping the hard thing, and standing behind whether it worked. Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." You read the post-launch dashboard and own the answer. A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers in a shared codebase. You bring engineering judgment to product calls and product judgment to engineering calls. Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind — agent workflows, evals, runbooks, post-launch reviews. Customer- and pro-minded. This is a real marketplace with real people on both sides, and you care about the outcomes for both. Good to Know An individual-contributor role with room to grow. People management sits with the EM — but the path into management is an open door for those who want it. A product-engineering role, end-to-end. You ship features that move metrics; platform and architecture work happen inside the initiative when the outcome needs them. Hands-on, with a high quality bar. Agents handle much of the implementation; you bring the judgment, design, safety, and accountability. The bar is high. Shipping to a live marketplace. With $100M+ in bookings, customers and pros use what you ship within the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira 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. Benefits Competitive salary of USD $80,000-$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow To apply: https://weworkremotely.com/remote-jobs/lawnstarter-staff-software-engineer-product

Headquarters: new york, New York, United States URL: http://bask.health Bask is the best telehealth platform on the market. Our mission is to empower entrepreneurs and businesses to launch a DTC telemedicine company quickly and easily, abstracting away the complexities of the industry into an easy-to-use platform. With hundreds of features to meet the unique needs of telehealth, we put all the tools in our customers' hands for success. We are a rapidly growing startup, and we work with care and intention to create a high-performance company with the following in mind: Speed Wins. Make decisions, move quickly, and know that if things go wrong, it's okay for you and the company. Intuition, Then Data. We're a data-driven company. We start with our instincts and then use data to validate our decisions and improve Miles, Not Inches. Thinking small is a self-fulfilling prophecy. Favor bold ideas over incremental changes Customer-Obsession. We are obsessed with helping all our customers launch multi-billion-dollar companies with ease. We accomplish this by knowing our customers incredibly well and finding ways to make their businesses better. Ownership & Accountability, together. We embody a culture of extreme ownership, accountability, and teamwork. We count on every team member to take responsibility for their work, embrace a proactive mindset to overcome challenges, and work together to achieve our collective success A look into the day to day: Building logic based questionnaires (asynchronous visits) through the Bask software (if you have experience with building logic based workflows, you'll be great at this!) Helping customers launch and upsell medications from start to to finish Triaging bask software and order related questions and issues that come up for any of your accounts, any time of the day We're Looking For A self-starter who is passionate about enhancing the customer experience; you take pride in demonstrating the value of the products and services to your customers. You think outside of the box, excel at creative problem-solving, and are comfortable taking on projects that you have potentially never done before! You are a people-person - empathetic, self-aware, low ego, and extremely positive - and are comfortable working in a small collaborative team where you'll wear many hats. You are passionate and proficient in written and spoken communications. Customer Success at Bask Health is AI-first and customer-obsessed. Work starts in an LLM to clarify intent and context, moves into research and execution, is validated with real patients and partners, and is continuously refined as we learn. AI and self-serve research are default parts of the workflow, not side experiments. We are looking for Customer Success people who take full ownership of their accounts, treat AI as a real collaborator, and care deeply about the patient and provider experience. What You'll Do Work AI-first: Use LLMs as your starting point to draft communications, structure problems, and think through customer needs. Apply your own judgment to refine the output and make it human. Validate with real customers and iterate: Test your approaches with real patients, providers, and partners. Use what you learn to improve how we serve them — before issues become patterns. Make automation legible and trustworthy: Help customers understand what Bask's platform is doing on their behalf. Communicate clearly and proactively to build trust while keeping their experience simple. Share AI-native workflows: Document prompts, processes, and workflows that work. Share them across the Customer Success team so we raise the bar together. In this job, you will: Build strong relationships with Bask's customers and own the full customer lifecycle, including onboarding, value realization, engagement strategies, expansion, and renewals Partner with customer stakeholders to develop custom engagement initiatives that drive user adoption and support the unique needs of their patients Manage all current customer data Analyze customer engagement metrics and use them to communicate value, trends, and opportunities with key stakeholders Deliver program demos, provide insightful technical answers, and recommend creative ways to get the most out of the Bask platform Finding comfort in working in a fast-paced startup environment Believing no task is too small and no task is too tall Requirements 7+ years of experience in Customer Success, Client Services, or Customer Success at a SaaS organization Experience in e-commerce Experience with large- to enterprise-sized customer book of business Creative problem solver with a determination to succeed Independent and motivated, with the wisdom to seek help where needed An entrepreneur Highly articulate, ability to communicate effectively both when speaking and writing Highly organized, with the ability to juggle multiple projects in a fast-paced environment Comfortable collaborating with different teams (product, sales, marketing, etc.) To apply: https://weworkremotely.com/remote-jobs/bask-health-senior-customer-success-manager

Headquarters: Frankfurt, Germany URL: https://www.lightupnet.de Technical Product Lead for Innovative Telecom Services - 100% Remote - 6 hours per day Creating Telecom-centric Web Services You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. We are a small, 100% remote telecommunications services company based in Germany and Switzerland established in 1998. Our team currently consists of 10 people working remotely across different countries and time zones. We build and operate innovative web-based products in the telecommunications and ISP space for retail, business and enterprise clients and telecom operators. Our projects sit at the intersection of telecom infrastructure, customer-facing web applications, automation, billing, provisioning, and operational processes. We are now looking for a Technical Product Lead to take ownership of translating complex telecom product ideas into clear technical concepts, development tasks, and working software. The role You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. We are looking for someone with a strong technical background who can understand complex infrastructure-driven services, structure them into practical web projects, and lead developers through implementation. You will work directly with the General Manager and act as the bridge between business ideas, telecom/ISP knowledge, product requirements, and software development. Your job is to make sure that ideas become clear specifications, that developers know exactly what to build, and that projects move forward with quality, speed, and technical sanity. Responsibilities You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. Translate high-level product and business ideas into clear technical concepts, specifications, user stories, and development tickets Lead and coordinate a small remote developer team Break down complex telecom/ISP workflows into practical web application features Define MVPs, priorities, milestones, and delivery plans Review developer output from a functional and technical perspective Challenge unclear requirements, weak architecture, and poor implementation choices Ensure that web applications are built with scalability, maintainability, security, and operational reality in mind Help design customer portals, admin backends, provisioning flows, billing-related workflows, APIs, dashboards, and internal tools Identify technical risks, blockers, dependencies, and missing pieces early Keep projects moving without unnecessary meetings or corporate overhead Report progress, risks, and decisions directly to the General Manager What we are looking for You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. You should be a technical generalist with a strong product sense. Ideally, you come from one or more of these backgrounds: Technical Product Lead Engineering Lead Tech Lead Solution Architect Senior DevOps Engineer Senior Sysadmin ISP / Telecom Engineer Technical company builder Fractional CTO You do not necessarily need to be the main developer yourself, but you must understand enough to lead developers, evaluate technical decisions, and know when something is overbuilt, underbuilt, unclear, or simply wrong. Required experience You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. Strong understanding of web applications, APIs, databases, backend systems, and software delivery Profound knowledge of Linux (CentOS, Ubuntu, other distros) environments Good understanding of networking concepts such as TCP/IP, DNS, routing, IPv4/IPv6, firewalls, VPNs and related infrastructure Experience working with developers and turning requirements into clear technical tasks Ability to structure complex systems into manageable modules, milestones, and deliverables Practical understanding of security, monitoring, logging, reliability, and operational requirements Experience working in remote teams Strong written communication skills in English Perfect English grammar without using AI Ability to work independently and take ownership Nice to have You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. Yes, sorry for repeating this over and over and but people tend to just scroll and apply without reading, so we want to make sure this is clear from the beginning. :-) Experience in telecommunications, ISP, hosting, datacenter, VoIP, SIP, cloud infrastructure, or B2B SaaS Understanding of Linux environments, many years of experience with Linux/GNU command line tools from a time before AI, Python, Bash and/or PHP or all of them, other programming/scripting languages, Proxmox, Virtual Machines, Apache/nginx, MariaDB, MySQL, PostgreSQL, server hardware & networking gear, IPMI / KVM-over-IP, BGP, IP address management, CIDR, provisioning systems, billing workflows, customer portals, network automation Experience building or managing self-service platforms for customers or internal teams Experience with small companies, startups, founder-led teams, or distributed freelancer teams Hands-on development experience, even if you no longer want to code full-time German language skills are a plus, but not mandatory What makes this role different You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. This role is for someone who enjoys the messy middle between product, technology, business, and execution. You should be comfortable taking a rough idea like: “We need a customer portal for managing telecom services, provisioning, billing, and support workflows.” and turning it into: a clear product concept a technical architecture implementation phases developer tickets acceptance criteria priorities risks delivery checkpoints We need someone who understands what should be built, why it matters, and how to get developers to build it properly. Working style You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. 100% Remote Freelancer agreement 6 hours per day work-time (Monday to Friday) Monthly salary: 2000 EUR Direct collaboration with the General Manager Small team, fast decisions, low bureaucracy Focus on practical delivery, not corporate process You may be a good fit if you... By the way, you would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. Have a strong technical background but also understand product and customers Can speak with developers, management, and business stakeholders Are comfortable with telecom, ISP, infrastructure, and web platforms Like creating clarity from vague ideas Can write excellent technical specifications and tickets Know how to push developers without micromanaging them Prefer pragmatic execution over endless meetings Have worked in small, remote, technically complex environments Can challenge assumptions and make things move forward How to apply PS: You would work 6 hours per day, Monday to Friday. Freelancer contract. The monthly salary is 2000 EUR. You can apply via WWR or by sending an E-Mail to jobs@lightupnet.de Please send us: A short introduction about your background Ideally, your CV Relevant projects you have led or helped build Your experience with telecom, ISP, infrastructure, SaaS, or web platforms You can apply via WWR or by sending an E-Mail to jobs@lightupnet.de We are especially interested in people who have previously worked as technical company builders, engineering leads, solution architects, senior sysadmins, DevOps leads, or technical product leads in infrastructure-heavy environments. You can apply via WWR or by sending an E-Mail to jobs@lightupnet.de   To apply: https://weworkremotely.com/remote-jobs/lightup-network-solutions-gmbh-co-kg-technical-product-lead-for-innovative-telecom-services

Headquarters: United States URL: http://bask.health Bask is the best telehealth platform on the market. Our mission is to empower entrepreneurs and businesses to launch a DTC telemedicine company quickly and easily, abstracting away the complexities of the industry into an easy-to-use platform. With hundreds of features to meet the unique needs of telehealth, we put all the tools in our customers hands for success. We are a rapidly growing startup, and we work with care and intention to create a high-performance company with the following in mind: Speed Wins. Make decisions, move quickly, and know that if things go wrong, it's okay for you and the company. Intuition, Then Data. We're a data-driven company. We start with our instincts and then use data to validate our decisions and improve Miles, Not Inches. Thinking small is a self-fulfilling prophecy. Favor bold ideas over incremental changes Customer-Obsession. We are obsessed with helping all our customers launch multi-billion-dollar companies with ease. We accomplish this by knowing our customers incredibly well and finding ways to make their businesses better. Ownership & Accountability, together. We embody a culture of extreme ownership, accountability, and teamwork. We count on every team member to take responsibility for their work, embrace a proactive mindset to overcome challenges, and work together to achieve our collective success A look into the day to day: Building logic based questionnaires (asynchronous visits) through the Bask software (if you have experience with building logic based workflows, you'll be great at this!) Helping customers launch and upsell medications from start to to finish Triaging bask software and order related questions and issues that come up for any of your accounts, any time of the day We're Looking For A self-starter who is passionate about enhancing the customer experience; you take pride in demonstrating the value of the products and services to your customers. You think outside of the box, excel at creative problem-solving, and are comfortable taking on projects that you have potentially never done before! You are a people-person - empathetic, self-aware, low ego, and extremely positive - and are comfortable working in a small collaborative team where you'll wear many hats. You are passionate and proficient in written and spoken communications. Customer Success at Bask Health is AI-first and customer-obsessed. Work starts in an LLM to clarify intent and context, moves into research and execution, is validated with real patients and partners, and is continuously refined as we learn. AI and self-serve research are default parts of the workflow, not side experiments. We are looking for Customer Success people who take full ownership of their accounts, treat AI as a real collaborator, and care deeply about the patient and provider experience. What You'll Do Work AI-first: Use LLMs as your starting point to draft communications, structure problems, and think through customer needs. Apply your own judgment to refine the output and make it human. Validate with real customers and iterate: Test your approaches with real patients, providers, and partners. Use what you learn to improve how we serve them — before issues become patterns. Make automation legible and trustworthy: Help customers understand what Bask's platform is doing on their behalf. Communicate clearly and proactively to build trust while keeping their experience simple. Share AI-native workflows: Document prompts, processes, and workflows that work. Share them across the Customer Success team so we raise the bar together. In this job, you will: Build strong relationships with Bask's customers and own the full customer lifecycle, including onboarding, value realization, engagement strategies, expansion, and renewals Partner with customer stakeholders to develop custom engagement initiatives that drive user adoption and support the unique needs of their patients Manage all current customer data Analyze customer engagement metrics and use them to communicate value, trends, and opportunities with key stakeholders Deliver program demos, provide insightful technical answers, and recommend creative ways to get the most out of the Bask platform Finding comfort in working in a fast-paced startup environment Believing no task is too small and no task is too tall Work Weekends Requirements 5+ years of experience in Customer Success, Client Services, or Customer Success at a SaaS organization Experience in e-commerce Experience with large- to enterprise-sized customer book of business Creative problem solver with a determination to succeed Independent and motivated, with the wisdom to seek help where needed An entrepreneur Highly articulate, ability to communicate effectively both when speaking and writing Highly organized, with the ability to juggle multiple projects in a fast-paced environment Comfortable collaborating with different teams (product, sales, marketing, etc.) To apply: https://weworkremotely.com/remote-jobs/bask-health-customer-success-account-manager-1

Headquarters: Infiniti Group Ltd URL: https://infinitiownerclub.com Application link: https://infinitiownerclub.com/work/weworkremotely Infiniti Group operates at the crossroads of digital assets, analytical market research, and algorithm-informed trading methods. We are dedicated to building a team of motivated beginners who want hands-on exposure to financial markets and real trading situations. We are looking for a Junior Crypto Trader — a role designed for those at the very start of their professional journey. If you're interested in reading market trends, executing trades, and working with data to inform your decisions, this is a great fit. You will trade independently but with structured oversight and regular feedback from experienced traders. There are no strict performance targets. Our focus is on developing your practical trading abilities in live crypto markets. No previous work experience is needed — we provide complete training. Key Responsibilities Place buy and sell orders in cryptocurrency markets while following risk rules and basic strategies. Watch real-time price changes, trading volumes, and order book movements. Use charts, technical indicators, and market signals to guide trade entries and exits. Keep track of active positions and assess potential gains or losses. Follow crypto news and understand how events may affect prices. Work with industry-standard trading interfaces and analytics dashboards. Review your own trading results regularly to identify strengths and areas to improve. Build a deeper understanding of market behavior and trading techniques over time. What We Offer A chance to grow inside an international company with a global outlook. 100% remote work — you can operate from any location. Flexible hours and adjustable workload. Access to professional-grade trading tools and live market data. Use of advanced analytics and reporting systems. A clear roadmap for professional growth with increasing responsibility over time. Ongoing help and feedback from seasoned market practitioners. Hands-on training on professional trading platforms, guided by experienced mentors. Requirements Basic computer literacy (using browsers, platforms, hotkeys). Stable internet connection and a laptop or PC. English at intermediate level or higher (to understand news and interface). Ability to focus during market hours (flexible, but attentive). Willingness to learn and ask questions. Application link: https://infinitiownerclub.com/work/weworkremotely To apply: https://weworkremotely.com/remote-jobs/infiniti-group-ltd-entry-level-junior-trader-remote-1

Sometimes we don't have a job opening that fits your interests or experience. We'd love to receive your resume for our files.Thank you for your interest in Nelson Motors & Equipment!