Remote Jobs for Digital Nomads

This is an opportunity to kickstart your career by joining Canonical. You will be working from our Canonical London Office and will be accountable for delivering technical support to our employees and customers, as well as facilitating AV support for office conferences and events. From problem qualification to full resolution, you will own and manage your cases. When needed, you will transfer your cases to your colleagues or involve senior engineers. Canonical is a leading provider of open source software and operating systems to the global enterprise and technology markets. Our platform, Ubuntu, is very widely used in breakthrough enterprise initiatives such as public cloud, data science, AI, engineering innovation and IoT. Our customers include the world's leading public cloud and silicon providers, and industry leaders in many sectors. The company is a pioneer of global distributed collaboration, with 1100+ colleagues in 75+ countries and very few office based roles. Teams meet two to four times yearly in person, in interesting locations around the world, to align on strategy and execution. The company is founder led, profitable and growing. This is an opportunity for an Linux Engineer/Administrator with a passion for Linux and Customer Success to build a career with Canonical and support the technical needs of customers leveraging Ubuntu and open source products. If you have a passion for technology and an eagerness to learn, then you will enjoy working with some of the best people in the industry at Canonical. You will be accountable for delivering an outstanding technical support experience on the full Desktop and Server technical stack at Canonical. From problem qualification to full resolution, you will own and manage your cases. When needed, you will transfer your cases to your colleagues or involve senior engineers. Your day to day job is to provide technical expertise, be an excellent communicator and a service-oriented professional. Every day you will have to make judgement calls to prioritise customer issues and maximise your effectiveness. You will also need to set time aside to learn about our new products and technologies and evolve as a professional. You will participate in various training sessions, team gatherings and Company events. Location: Office Based in London, England The role entails • Investigate issues reported by customers by researching and escalating issues • Work to resolve complex customer problems related to Canonical’s portfolio of products. • Ownership of results: Ensure that each support case owned by you is handled according to our Service Level Agreement (SLA) with the highest possible customer satisfaction by setting the right expectations and fulfilling your commitments. • Engage directly with customers and work collaboratively by phone, ticketing system, and remote sessions to resolve their issues. • Participate in a regular weekend working rotation. • Contribute new knowledge base articles and maintain existing articles, ensuring shared knowledge and lessons learned are available to customers. • Understanding Ubuntu development process to be able to set customer expectations correctly on timeline for a fix. What are we looking for in you • Professional written and spoken English with excellent presentation skills • Exceptional academic track record from both high school and university • Undergraduate degree in a technical subject or a compelling narrative about your alternative chosen path • Track record of going above-and-beyond expectations to achieve outstanding results • Work from our new, state of the art London, UK office and provide technical support for employees. • Familiarize with and own the technical infrastructure supporting the office and the stack supporting events and customer demos. • Provide technical onboarding support for new employees. • Provide technical and infrastructure support during office events. • Identify and suggest any opportunities to provide a better service • Experience with Linux troubleshooting (collecting logs and stack traces, fine-tuning by editing configuration files) • Experience with Linux integration with other environments (authentication/directory services, network file systems, etc.) • Hands-on and working experience in supporting Linux systems including any of: • Virtualization / Cloud - primarily using KVM or OpenStack. • Containers - especially with Docker, LXD/LXC, or Kubernetes. • Storage technologies - block, object and network. • Networking (bonding, firewalling, bridging, switching, network file system tuning, MTU issues, etc.). • Ability to learn quickly, thrive on change and handle the pressure of a customer facing job • Programming fundamentals in any language. • Ability to travel internationally twice a year for company events up to two weeks long • Extensive Customer support experience is key: • Customer needs are top priority. • Communicate professionally, emphaticall

ABOUT SUPABASE Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth. ABOUT THE ROLE We’re looking for a Brand Designer to join our Design Team (working with DevRel, Success, and Enterprise) and help shape our visual storytelling across a variety of mediums. You’ll work closely with cross-functional teams, helping us bring our ideas to life with compelling visuals that engage our developer community and amplify our brand at conferences, events, swag, and beyond. This role is ideal for someone who thrives in async, fast-paced environments and is excited about building developer tools that scale to millions. You will have opportunities to lead, propose, and execute projects across various formats—from polished presentations to impactful print designs—ensuring a cohesive and powerful brand presence across all touchpoints. WHAT YOU’LL BE RESPONSIBLE FOR - Shape our visual storytelling across decks, printed materials, YouTube content, and conference assets. - Collaborate with Marketing, DevRel, Success, Enterprise, and Event teams to bring creative ideas to life. - Craft cohesive and engaging visual narratives for presentations, digital assets, and physical materials. - Maintain strict brand consistency, ensuring all materials adhere to Supabase’s visual identity and messaging. - Execute end-to-end design projects across multiple channels, including print, video, and social media. - Set high standards for design quality, meticulous attention to detail, and visual communication that resonates with our community. YOU MIGHT BE A GOOD FIT IF YOU - Have strong proficiency in design tools like Figma, Adobe Creative Suite (InDesign, Illustrator, Photoshop), and presentation software. - Are comfortable designing across digital, print, and video formats (and know the difference between 300gsm and 100gsm paper). - Communicate clearly across both technical and non-technical audiences. - Have experience in async or globally distributed teams. - Are energized by creative storytelling and building an impactful, memorable brand presence for a developer audience. - Are comfortable navigating ambiguity, moving quickly, and proactively bringing new ideas to the table. - Balance iteration and scale: You focus on high-impact, incremental improvements rather than a "redo everything" approach, and you welcome collaborative feedback. WHAT WE OFFER - Fully Remote We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world. - ESOP Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together. - Tech Allowance Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work. - Health Benefits Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us. - Annual Off-Sites Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year. - Flexible Work We operate asynchronously and trust you to manage your own time. You know what needs to be done and when. - Professional Development Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth. ABOUT THE TEAM Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love. - 280+ team members - 55+ countries - 20+ languages spoken - $500M raised - 500,000+ community members We move fast, build in public, and use what we ship. If it’s in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support—not replace—existing tools and communities. HIRING PROCESS We keep things simple, async-friendly, and respectful of your time: 1. Apply – Our team will review your application. 2. Intro Call – A short video chat to get to know each other. 3. Interviews – Up to four calls with: - Team Leads - Future teammates - Someone cross-functional from product, growth, or engineering (depending on the role) - Someone from our leadership/founding team 4. Decision – We may follow up with a final question or go straight to offer. All communication is remote and we aim to move fast.

Deine Aufgaben: Du suchst eine studiengeeignete Rolle, in der Du praxisnah arbeitest und viel über operative Zusammenhänge lernst? In dieser Position unterstützt du unser Team bei Kundenprozessen, Koordinationsthemen und der laufenden Dokumentation. Mit Sorgfalt, Struktur und eigenen Ideen kannst Du hier echten Impact erzeugen. • Du unterstützt bei der Bearbeitung und Koordination operativer Kundenanliegen (B2B/B2C) und sorgst für saubere Nachverfolgung. • Du übernimmst Backend- und Systemaktivitäten für Full-Service-Kundeninstanzen (z. B. Datenpflege, einfache Systemschritte, Prüfung von Vorgängen). • Du unterstützt bei Bestell- und Versandprozessen (z. B. SIM-/RFID-Karten), inkl. Koordination mit externen Dienstleistern. • Du hilfst bei der Bearbeitung von Klärungsfällen (z. B. Beschwerden, Billing-/Abrechnungsfragen) nach definierten Kriterien und eskalierst bei Bedarf. • Du pflegst Dokumentation und operative Listen/Reports (z. B. Excel/Monday) und bringst Verbesserungsideen für effizientere Abläufe ein. Das bist du: • Du bist immatrikulierter Student:in (z. B. Marketing, Kommunikation, Medien, Wirtschaft oder ähnliches) und wohnst im Raum Köln • Du arbeitest sehr sorgfältig, zuverlässig und strukturiert und hast Spaß an operativen Prozessen. • Du bist sicher im Umgang mit MS Office (insb. Excel); Erfahrung mit Tools wie Monday ist ein Plus. • Du kommunizierst klar und freundlich und arbeitest gern mit verschiedenen Schnittstellen (intern/extern) zusammen. • Du sprichst fließend Deutsch und gut Englisch (schriftlich und mündlich). • Du bist flexibel einsetzbar und kannst mindestens 1x pro Woche im Kölner Büro unterstützen – idealerweise häufiger (z. B. für Versand/operative Aufgaben). Das bieten wir: Study Flex: Flexible Arbeitszeiten, die sich nach deinem Unileben und der Klausurenphase richten - du bestimmst, wann du am produktivsten bist! Remote friendly: Du arbeitest größtenteils aus dem Homeoffice. Unser Kölner Office steht dir jederzeit offen, wenn du mal vorbeischauen möchtest. Work from anywhere: Nutze deutschlandweit unsere knapp 50 Co-Working Spaces und arbeite, wo du willst. Eigenverantwortung & Impact: Du hast die Freiheit eigenständig zu arbeiten und in motivierten Teams wirklich etwas zu bewegen. Starker Teamspirit: Regelmäßige Team-Meetups in Köln - ob für gemeinsame Aktionen oder zum Austausch mit allen. Transparent & Fair: 15€/h im Bachelor und 16,50€/h im Master. Art der Beschäftigung Teilzeit, 16-20 Stunden, remote Lust Teil des Teams zu werden? Wir freuen uns auf deine Bewerbung! Alle Menschen sind bei uns willkommen, unabhängig von Geschlecht / geschlechtlicher Identität, Behinderung / Beeinträchtigung, Nationalität, ethnischer Herkunft, Religion / Weltanschauung, Alter, sexueller Orientierung. Hauptsache, du passt zu uns.

This is a remote role for candidates located in São Paulo , Brazil. 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 pro

This is a remote role for candidates located in Florianópolis, Brazil 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've spent the last two years rebuilding the platform from the ground up: new customer app, new Pro onboarding, job distribution engine, and data infrastructure. The foundation is solid. Now we're moving into expanded service verticals, dynamic pricing, and AI-powered features at scale. Quality needs to keep up. Our stack is PHP (Laravel) and React/React Native, with Cypress as our primary test framework. We actively use Claude Code as part of our engineering workflow, not as an experiment, but as a core part of how we work. The Role As we scale into new service verticals and grow the engineering team, quality can't be reactive. This role exists to make quality proactive: owning the automation coverage, shaping the bug process, and partnering closely with Product, Design, and the Data team to catch problems before they reach customers. You'll report to the Engineering Manager and be embedded across the engineering organization. This is hands-on and strategic, helping raise the quality ceiling for the whole team. What makes this role different: • Cross-functional influence : You work directly with engineers, PMs, Designers, and the Data team to surface risks early, understand requirements deeply, and propose better solutions. You may be embedded in one or two delivery teams. • Automation ownership : You own the strategy for building and expanding our automated test coverage, not just executing test cases someone else wrote. • Process shaper : You'll identify gaps in our quality process and have the authority to fix them, not just flag them. What You'll Own • Automated test coverage : Design and grow our E2E and integration test suite using Cypress. Set the strategy, prioritize coverage gaps, and raise the floor across the platform. • Bug process : Own the full lifecycle from triage to production fix. Keep it moving, keep stakeholders informed, and make sure nothing falls through the cracks. • Cross-functional quality partnership : Collaborate with PMs, Designers, and the Data team to review requirements, raise risks early, and define what "done" actually means. • Process improvement : Identify weaknesses in how we deliver software and propose solutions. Not just document them. • Exploratory testing : Test new features and existing flows on web and mobile across devices, catching what automation misses. Problems to Solve Keeping automation coverage sharp as the product evolves Our E2E coverage is solid. The challenge is staying ahead: bringing new ideas, exploring different types of coverage, and finding smarter ways to automate different aspects of the application as the product grows and new service verticals come online. Exploring new tools and leveraging AI to improve quality operations AI is changing how we build software, and it's changing how we can test it too. There's real opportunity here to use AI tools to increase output quality, cut repetitive work, and discover coverage gaps we'd otherwise miss. We want someone who actively explores that space, not someone who waits to be told what to use. What Success Looks Like (Year 1) • Automation coverage stays strong : New features ship with automated tests as a baseline, and coverage strategies evolve with the product. • Bug process runs smoothly : Triage to fix cycle is predictable and stakeholders know where things stand without having to ask. • Deep business knowledge : You understand how the marketplace works well enough to anticipate edge cases on your own. • Quality process improvement shipped : At least one meaningful improvement to how we deliver quality is in place and being used by the team. Requirements Who You Are AI-native. You use AI tools like Claude Code to write, maintain, and extend test code, not as a novelty, but as a standard part of how you work. You're comfortable with browser MCPs, agent workflows, and building scripts that automate the boring parts of QA. This is unlikely to be a good fit if you're skeptical of AI in the engineering workflow. Automation-first. Your default when you find a problem is to ask how to prevent it automatically. You build test infrastructure that outlasts any individual test case. This is unlikely to be a good fit if your strength is manual testing and automation is something you tolerate rather than drive. Customer-obsessed. You think like a user. When you're testing a flow, you're asking whether it actually works for a real customer, not just whether it matches the spec. This is unlikely to be a good fit if you treat quality

This is a remote role for candidates located in São Paulo , Brazil 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've spent the last two years rebuilding the platform from the ground up: new customer app, new Pro onboarding, job distribution engine, and data infrastructure. The foundation is solid. Now we're moving into expanded service verticals, dynamic pricing, and AI-powered features at scale. Quality needs to keep up. Our stack is PHP (Laravel) and React/React Native, with Cypress as our primary test framework. We actively use Claude Code as part of our engineering workflow, not as an experiment, but as a core part of how we work. The Role As we scale into new service verticals and grow the engineering team, quality can't be reactive. This role exists to make quality proactive: owning the automation coverage, shaping the bug process, and partnering closely with Product, Design, and the Data team to catch problems before they reach customers. You'll report to the Engineering Manager and be embedded across the engineering organization. This is hands-on and strategic, helping raise the quality ceiling for the whole team. What makes this role different: • Cross-functional influence : You work directly with engineers, PMs, Designers, and the Data team to surface risks early, understand requirements deeply, and propose better solutions. You may be embedded in one or two delivery teams. • Automation ownership : You own the strategy for building and expanding our automated test coverage, not just executing test cases someone else wrote. • Process shaper : You'll identify gaps in our quality process and have the authority to fix them, not just flag them. What You'll Own • Automated test coverage : Design and grow our E2E and integration test suite using Cypress. Set the strategy, prioritize coverage gaps, and raise the floor across the platform. • Bug process : Own the full lifecycle from triage to production fix. Keep it moving, keep stakeholders informed, and make sure nothing falls through the cracks. • Cross-functional quality partnership : Collaborate with PMs, Designers, and the Data team to review requirements, raise risks early, and define what "done" actually means. • Process improvement : Identify weaknesses in how we deliver software and propose solutions. Not just document them. • Exploratory testing : Test new features and existing flows on web and mobile across devices, catching what automation misses. Problems to Solve Keeping automation coverage sharp as the product evolves Our E2E coverage is solid. The challenge is staying ahead: bringing new ideas, exploring different types of coverage, and finding smarter ways to automate different aspects of the application as the product grows and new service verticals come online. Exploring new tools and leveraging AI to improve quality operations AI is changing how we build software, and it's changing how we can test it too. There's real opportunity here to use AI tools to increase output quality, cut repetitive work, and discover coverage gaps we'd otherwise miss. We want someone who actively explores that space, not someone who waits to be told what to use. What Success Looks Like (Year 1) • Automation coverage stays strong : New features ship with automated tests as a baseline, and coverage strategies evolve with the product. • Bug process runs smoothly : Triage to fix cycle is predictable and stakeholders know where things stand without having to ask. • Deep business knowledge : You understand how the marketplace works well enough to anticipate edge cases on your own. • Quality process improvement shipped : At least one meaningful improvement to how we deliver quality is in place and being used by the team. Requirements Who You Are AI-native. You use AI tools like Claude Code to write, maintain, and extend test code, not as a novelty, but as a standard part of how you work. You're comfortable with browser MCPs, agent workflows, and building scripts that automate the boring parts of QA. This is unlikely to be a good fit if you're skeptical of AI in the engineering workflow. Automation-first. Your default when you find a problem is to ask how to prevent it automatically. You build test infrastructure that outlasts any individual test case. This is unlikely to be a good fit if your strength is manual testing and automation is something you tolerate rather than drive. Customer-obsessed. You think like a user. When you're testing a flow, you're asking whether it actually works for a real customer, not just whether it matches the spec. This is unlikely to be a good fit if you treat quality as a

This is a remote role for candidates located in Belo Horizonte, Brazil 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've spent the last two years rebuilding the platform from the ground up: new customer app, new Pro onboarding, job distribution engine, and data infrastructure. The foundation is solid. Now we're moving into expanded service verticals, dynamic pricing, and AI-powered features at scale. Quality needs to keep up. Our stack is PHP (Laravel) and React/React Native, with Cypress as our primary test framework. We actively use Claude Code as part of our engineering workflow, not as an experiment, but as a core part of how we work. The Role As we scale into new service verticals and grow the engineering team, quality can't be reactive. This role exists to make quality proactive: owning the automation coverage, shaping the bug process, and partnering closely with Product, Design, and the Data team to catch problems before they reach customers. You'll report to the Engineering Manager and be embedded across the engineering organization. This is hands-on and strategic, helping raise the quality ceiling for the whole team. What makes this role different: • Cross-functional influence : You work directly with engineers, PMs, Designers, and the Data team to surface risks early, understand requirements deeply, and propose better solutions. You may be embedded in one or two delivery teams. • Automation ownership : You own the strategy for building and expanding our automated test coverage, not just executing test cases someone else wrote. • Process shaper : You'll identify gaps in our quality process and have the authority to fix them, not just flag them. What You'll Own • Automated test coverage : Design and grow our E2E and integration test suite using Cypress. Set the strategy, prioritize coverage gaps, and raise the floor across the platform. • Bug process : Own the full lifecycle from triage to production fix. Keep it moving, keep stakeholders informed, and make sure nothing falls through the cracks. • Cross-functional quality partnership : Collaborate with PMs, Designers, and the Data team to review requirements, raise risks early, and define what "done" actually means. • Process improvement : Identify weaknesses in how we deliver software and propose solutions. Not just document them. • Exploratory testing : Test new features and existing flows on web and mobile across devices, catching what automation misses. Problems to Solve Keeping automation coverage sharp as the product evolves Our E2E coverage is solid. The challenge is staying ahead: bringing new ideas, exploring different types of coverage, and finding smarter ways to automate different aspects of the application as the product grows and new service verticals come online. Exploring new tools and leveraging AI to improve quality operations AI is changing how we build software, and it's changing how we can test it too. There's real opportunity here to use AI tools to increase output quality, cut repetitive work, and discover coverage gaps we'd otherwise miss. We want someone who actively explores that space, not someone who waits to be told what to use. What Success Looks Like (Year 1) • Automation coverage stays strong : New features ship with automated tests as a baseline, and coverage strategies evolve with the product. • Bug process runs smoothly : Triage to fix cycle is predictable and stakeholders know where things stand without having to ask. • Deep business knowledge : You understand how the marketplace works well enough to anticipate edge cases on your own. • Quality process improvement shipped : At least one meaningful improvement to how we deliver quality is in place and being used by the team. Requirements Who You Are AI-native. You use AI tools like Claude Code to write, maintain, and extend test code, not as a novelty, but as a standard part of how you work. You're comfortable with browser MCPs, agent workflows, and building scripts that automate the boring parts of QA. This is unlikely to be a good fit if you're skeptical of AI in the engineering workflow. Automation-first. Your default when you find a problem is to ask how to prevent it automatically. You build test infrastructure that outlasts any individual test case. This is unlikely to be a good fit if your strength is manual testing and automation is something you tolerate rather than drive. Customer-obsessed. You think like a user. When you're testing a flow, you're asking whether it actually works for a real customer, not just whether it matches the spec. This is unlikely to be a good fit if you treat quality as

This is a remote role for candidates located in Campinas, Brazil. 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've spent the last two years rebuilding the platform from the ground up: new customer app, new Pro onboarding, job distribution engine, and data infrastructure. The foundation is solid. Now we're moving into expanded service verticals, dynamic pricing, and AI-powered features at scale. Quality needs to keep up. Our stack is PHP (Laravel) and React/React Native, with Cypress as our primary test framework. We actively use Claude Code as part of our engineering workflow, not as an experiment, but as a core part of how we work. The Role As we scale into new service verticals and grow the engineering team, quality can't be reactive. This role exists to make quality proactive: owning the automation coverage, shaping the bug process, and partnering closely with Product, Design, and the Data team to catch problems before they reach customers. You'll report to the Engineering Manager and be embedded across the engineering organization. This is hands-on and strategic, helping raise the quality ceiling for the whole team. What makes this role different: • Cross-functional influence : You work directly with engineers, PMs, Designers, and the Data team to surface risks early, understand requirements deeply, and propose better solutions. You may be embedded in one or two delivery teams. • Automation ownership : You own the strategy for building and expanding our automated test coverage, not just executing test cases someone else wrote. • Process shaper : You'll identify gaps in our quality process and have the authority to fix them, not just flag them. What You'll Own • Automated test coverage : Design and grow our E2E and integration test suite using Cypress. Set the strategy, prioritize coverage gaps, and raise the floor across the platform. • Bug process : Own the full lifecycle from triage to production fix. Keep it moving, keep stakeholders informed, and make sure nothing falls through the cracks. • Cross-functional quality partnership : Collaborate with PMs, Designers, and the Data team to review requirements, raise risks early, and define what "done" actually means. • Process improvement : Identify weaknesses in how we deliver software and propose solutions. Not just document them. • Exploratory testing : Test new features and existing flows on web and mobile across devices, catching what automation misses. Problems to Solve Keeping automation coverage sharp as the product evolves Our E2E coverage is solid. The challenge is staying ahead: bringing new ideas, exploring different types of coverage, and finding smarter ways to automate different aspects of the application as the product grows and new service verticals come online. Exploring new tools and leveraging AI to improve quality operations AI is changing how we build software, and it's changing how we can test it too. There's real opportunity here to use AI tools to increase output quality, cut repetitive work, and discover coverage gaps we'd otherwise miss. We want someone who actively explores that space, not someone who waits to be told what to use. What Success Looks Like (Year 1) • Automation coverage stays strong : New features ship with automated tests as a baseline, and coverage strategies evolve with the product. • Bug process runs smoothly : Triage to fix cycle is predictable and stakeholders know where things stand without having to ask. • Deep business knowledge : You understand how the marketplace works well enough to anticipate edge cases on your own. • Quality process improvement shipped : At least one meaningful improvement to how we deliver quality is in place and being used by the team. Requirements Who You Are AI-native. You use AI tools like Claude Code to write, maintain, and extend test code, not as a novelty, but as a standard part of how you work. You're comfortable with browser MCPs, agent workflows, and building scripts that automate the boring parts of QA. This is unlikely to be a good fit if you're skeptical of AI in the engineering workflow. Automation-first. Your default when you find a problem is to ask how to prevent it automatically. You build test infrastructure that outlasts any individual test case. This is unlikely to be a good fit if your strength is manual testing and automation is something you tolerate rather than drive. Customer-obsessed. You think like a user. When you're testing a flow, you're asking whether it actually works for a real customer, not just whether it matches the spec. This is unlikely to be a good fit if you treat quality as a ch

This is a remote role for candidates located in Porto Alegre, Brazil 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've spent the last two years rebuilding the platform from the ground up: new customer app, new Pro onboarding, job distribution engine, and data infrastructure. The foundation is solid. Now we're moving into expanded service verticals, dynamic pricing, and AI-powered features at scale. Quality needs to keep up. Our stack is PHP (Laravel) and React/React Native, with Cypress as our primary test framework. We actively use Claude Code as part of our engineering workflow, not as an experiment, but as a core part of how we work. The Role As we scale into new service verticals and grow the engineering team, quality can't be reactive. This role exists to make quality proactive: owning the automation coverage, shaping the bug process, and partnering closely with Product, Design, and the Data team to catch problems before they reach customers. You'll report to the Engineering Manager and be embedded across the engineering organization. This is hands-on and strategic, helping raise the quality ceiling for the whole team. What makes this role different: • Cross-functional influence : You work directly with engineers, PMs, Designers, and the Data team to surface risks early, understand requirements deeply, and propose better solutions. You may be embedded in one or two delivery teams. • Automation ownership : You own the strategy for building and expanding our automated test coverage, not just executing test cases someone else wrote. • Process shaper : You'll identify gaps in our quality process and have the authority to fix them, not just flag them. What You'll Own • Automated test coverage : Design and grow our E2E and integration test suite using Cypress. Set the strategy, prioritize coverage gaps, and raise the floor across the platform. • Bug process : Own the full lifecycle from triage to production fix. Keep it moving, keep stakeholders informed, and make sure nothing falls through the cracks. • Cross-functional quality partnership : Collaborate with PMs, Designers, and the Data team to review requirements, raise risks early, and define what "done" actually means. • Process improvement : Identify weaknesses in how we deliver software and propose solutions. Not just document them. • Exploratory testing : Test new features and existing flows on web and mobile across devices, catching what automation misses. Problems to Solve Keeping automation coverage sharp as the product evolves Our E2E coverage is solid. The challenge is staying ahead: bringing new ideas, exploring different types of coverage, and finding smarter ways to automate different aspects of the application as the product grows and new service verticals come online. Exploring new tools and leveraging AI to improve quality operations AI is changing how we build software, and it's changing how we can test it too. There's real opportunity here to use AI tools to increase output quality, cut repetitive work, and discover coverage gaps we'd otherwise miss. We want someone who actively explores that space, not someone who waits to be told what to use. What Success Looks Like (Year 1) • Automation coverage stays strong : New features ship with automated tests as a baseline, and coverage strategies evolve with the product. • Bug process runs smoothly : Triage to fix cycle is predictable and stakeholders know where things stand without having to ask. • Deep business knowledge : You understand how the marketplace works well enough to anticipate edge cases on your own. • Quality process improvement shipped : At least one meaningful improvement to how we deliver quality is in place and being used by the team. Requirements Who You Are AI-native. You use AI tools like Claude Code to write, maintain, and extend test code, not as a novelty, but as a standard part of how you work. You're comfortable with browser MCPs, agent workflows, and building scripts that automate the boring parts of QA. This is unlikely to be a good fit if you're skeptical of AI in the engineering workflow. Automation-first. Your default when you find a problem is to ask how to prevent it automatically. You build test infrastructure that outlasts any individual test case. This is unlikely to be a good fit if your strength is manual testing and automation is something you tolerate rather than drive. Customer-obsessed. You think like a user. When you're testing a flow, you're asking whether it actually works for a real customer, not just whether it matches the spec. This is unlikely to be a good fit if you treat quality as a

Requirements : At least 5 years of experience in Data Science, including production-level model deployment. Proficiency in Python programming (Tensofrlow, PyTorch, Scikit-Learn) and advanced SQL skills. Experience with large-scale data processing and ML models. Proven track record with complex predictive modeling, recommendation systems, and optimization techniques. Ability to translate business challenges into ML solutions. Working knowledge of at least one public cloud environment (Azure, GCP…

Masz doświadczenie w pracy z instytucjami publicznymi lub w sprzedaży rozwiązań dla sektora publicznego, poparte konkretnymi sukcesami Lubisz kontakt z klientem i potrafisz budować długotrwałe, partnerskie relacje Cechuje Cię pozytywne nastawienie, determinacja i satysfakcja z osiągania ambitnych celów Dobrze organizujesz swoją pracę i sprawnie działasz w dynamicznym środowisku Interesujesz się nowymi technologiami i chcesz rozwijać swoje kompetencje w obszarze ICT, IoT i cybersecurity Chcesz p…

Wir suchen jemanden, der Verantwortung übernimmt - nicht nur Tickets bearbeitet. Bei DrAnsay machen wir die Gesundheitsversorgung einfacher. Wir helfen Menschen dabei, ihre Krankmeldung schnell, digital und ohne unnötigen Aufwand zu erhalten. Unser Produkt funktioniert, weil unser Team funktioniert - und wir brauchen jetzt jemanden, der unsere Kundenerfahrung vollständig in die Hand nimmt. Das ist keine klassische Support-Rolle, bei der du Tickets öffnest und schließt. Wir suchen jemanden, der jede Kundenanfrage als Signal versteht, jede Prozesslücke als Chance und jede Eskalation als Möglichkeit, DrAnsay besser zu machen. Über DrAnsay DrAnsay ist ein digitales Health-Unternehmen mit einer klaren Mission: Eine Krankmeldung in Deutschland zu bekommen sollte kein bürokratischer Albtraum sein. Wir haben eine schnelle, digitale Lösung entwickelt, die tausenden Menschen monatlich hilft. Wir kommunizieren klar, dokumentieren Entscheidungen und schaffen Transparenz - damit wir schnell und ohne Chaos vorankommen. Remote-first-Unternehmen skalieren nicht durch endlose Meetings, sondern durch Sichtbarkeit, Vertrauen, Dokumentation und starke Kommunikation. Wir sind ein kleines Team mit echter Eigenverantwortung, schnellen Entscheidungen und einer Kultur, die Ergebnisse über Optik stellt. Wir bauen Produkte, die die Gesundheit von Menschen verbessern – und wir glauben, dass nachhaltiger Output bessere Ergebnisse erzeugt als eine Burnout-Kultur. Wir messen Engagement nicht an Online-Status oder Überstunden, sondern an Verlässlichkeit, Konsistenz und starken Ergebnissen. Die Rolle Du bist die erste Anlaufstelle für alle Kundenanfragen - hauptsächlich per E-Mail. Du arbeitest nicht nach einem Skript. Du verstehst Probleme, löst sie und gibst strukturiertes Feedback an Produkt und Legal weiter, damit DrAnsay besser wird. In den ersten 6–12 Monaten wirst du das CS-Geschäft vollständig kennenlernen und anschließend ein eigenes Projekt im Customer Service Team übernehmen. Das übernimmst du • Alle eingehenden Kundenanfragen per E-Mail : Du antwortest, löst und verantwortest. • Qualitätsfeedback-Schleifen : Du erkennst Muster, Prozesslücken und Produktprobleme und gibst sie strukturiert weiter (Produkt, Legal). • Eskalationsmanagement : Du erkennst und eskalierst Ausfälle, technische Probleme und Prozessfehler schnell und klar. • Dein eigenes Projekt : Innerhalb von 12 Monaten übernimmst du eine definierte CS-Verbesserung Initiative. • Klare interne Kommunikation : Die richtigen Personen bleiben informiert, async-first, ohne Informationsrauschen.