Remote Jobs für Digitale Nomaden

Ownership mindset nie czekasz na instrukcje, widzisz problem i działasz. Doświadczenie w prowadzeniu technicznych projektów IT (zarządzanie zadaniami, testowanie, współpraca z klientem). Zarządzanie zadaniam i , testowanie, współpraca z klientem). English fluent rozmowy z klientami anglojęzycznymi są dla Ciebie oczywiste i komfortowe. US time zones friendly gotowość do okazjonalnej pracy popołudniami (strefy czasowe US, w tym Kalifornia). Znajomość narzędzi PM/QA (np. Jira, Clickup, Monday etc)…

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 1200+ 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. The role of a Technical and Reporting Accountant at Canonical: If you are passionate about the technology industry and want to work for a company that aligns with your interests, we might be the place for you! Canonical, and our world class Ubuntu product, attracts some of the leading talent from around the world. Come and work with exceptional people and advance your career in Finance! Our Finance team is growing and it's a really exciting time to join the team. We are looking for bright, motivated people who have a passion for making a difference. You will be seeking an opportunity to drive process improvements and change, input your ideas and truly contribute to a highly productive team. We are looking for an exceptional Technical and Reporting Accountant with IFRS experience to help us ready the business for public market scrutiny through our planned IPO. The right candidate will have domain expertise and a passion for IFRS. Location: This role may be office based in London, or Remote in EMEA Time Zones. What your day will look like • Research and interpret new and existing accounting standards • Provide technical accounting advice for complex transactions • Draft accounting papers and policy documentation • Monitor regulatory changes and assess their impact on the business • Assist with the year end external audit process and support the internal audit team • Assist in the month end reporting process to deliver timely and accurate information to management • Ensure compliance with relevant accounting standards (e.g. IFRS, local GAAP) • Assist in the preparation of statutory accounts and annual reports across multiple subsidiaries and jurisdictions • Support the finance team's wider plans to prepare for an IPO • Improve the efficiency of financial processes and procedures and monitor compliance • Share knowledge between team members to ensure cover is available when needed • Actively develop your own skills to ensure current knowledge of applicable standards and regulations • Establish strong relationships with key colleagues outside the wider finance team What we are looking for in you • Exceptional academic track record and subsequent career performance. • Bachelor's degree in Accounting or equivalent. • Qualified accountant (ACCA, ACA, ACMA, CPA, etc.). • Strong knowledge of IFRS and local GAAP. • Experience in financial reporting and statutory accounts preparation. • Experience at a large public accounting firm, or public multinational corporate accounting department preferred. • NetSuite or similar enterprise grade systems experience. • Business level written and spoken English. • Sincere personal motivation aligned with our mission. • International travel 2-4 times a year for company events up to two weeks long. In addition we expect that you will match our values, by being: • Precise, taking care to deliver correctness and clarity. • Reliable, delivering high quality work that builds trust and confidence. • Accessible, collaborating to build products and systems that are usable. • Adroit, blending enthusiasm, knowledge, adaptability, style and character. What we offer colleagues We consider geographical location, experience, and performance in shaping compensation worldwide. We revisit compensation annually (and more often for graduates and associates) to ensure we recognize outstanding performance. In addition to base pay, we offer a performance-driven annual bonus or commission. We provide all team members with additional benefits which reflect our values and ideals. We balance our programs to meet local needs and ensure fairness globally. • Distributed work environment with twice-yearly team sprints in person • Personal learning and development budget of USD 2,000 per year • Annual compensation review • Recognition rewards • Annual holiday leave • Maternity and paternity leave • Team Member Assistance Program & Wellness Platform • Opportunity to travel to new locations to meet colleagues • Priority Pass and travel upgrades for long-haul company events About Canonical Canonical is a pioneering tech firm at the forefront of the global move to open source. As the company that publishes Ubuntu, one of the most important open-source projects and the plat

ABOUT SUPABASE Supabase is the open-source Postgres development platform. Over 7,000,000 developers — from indie hackers to teams inside Wells Fargo, Coinbase, Audi, and Capital One — build on Supabase, and every one of them meets the product through the same five surfaces: the SDKs https://supabase.com/docs/reference, the docs https://supabase.com/docs, the dashboard https://supabase.com/dashboard, the Management API https://supabase.com/docs/reference/api/introduction, and the CLI https://supabase.com/docs/reference/cli/introduction. They are the product to every developer who touches Supabase. These interfaces now have a second audience: coding agents. Claude, Codex, Lovable, Bolt (and more) now read our docs, call our SDKs, use our APIs, and drive the CLI on behalf of developers. As the PM for these surfaces, you will define how Supabase will be as readable, predictable, and trustworthy as possible, both to humans and agents alike. WHAT YOU WILL DO - Talk to customers across the full spectrum. From indie developers wiring up a side project, to AI-native platforms generating Supabase apps for their own users, and to enterprise teams integrating the Management API into their internal control planes, you will find the real blockers and ensure we are building the right things, in the right order. - Own the problem statement and requirements behind every interface bet. Define what we should build next (and why) to make Supabase the best developer experience in the world, collaborating closely with Engineering and Design. - Set the bar for what "agent-friendly" means on Supabase. Decide how the SDK reads to a coding agent, how the docs are retrieved and quoted, how APIs are discovered, and how the CLI behaves when something automated is driving it. For you "AI-friendly" will not be a slogan but a reality, proven by specific changes you mill make and measure. - Define how each launch is measured before it ships. You will set clear goals that measure how a change actually moves developer activation, docs comprehension, agent task success, or API adoption—and you’ll use that insight to guide what we do next. - Keep engineering, design, and leadership aligned. Engineering and design teams across every Supabase surface ship into the experience you own. Communicate what's coming, why, and in what order, and make sure it feels like one product, not five. WHO YOU ARE - 7+ years of product management experience on developer tools, or an ex-founder with strong product instincts. You're technical enough to read an architecture doc, follow a design discussion, and ask the right questions. - You've shipped a public SDK, CLI, dashboard, or API that external developers depend on. Not features that happened to touch an SDK; you owned the surface. You’re equally adept at API design, docs IA, and dashboard flows, and you've made the trade-offs between them in production. - You understand the landscape is evolving. You’re familiar with how coding agents (such as Claude, Codex and Cursor) consume SDKs, docs, and APIs, and how to optimize for developers using them. - You're biased toward speed. You'd rather ship something imperfect and learn than spend another sprint refining a spec. - You build with what you own. You install the CLI, call the Management API, read the docs end-to-end, and write real code against supabase-js. You develop opinions through first-hand use, not screenshots. - You use AI to move faster. You use AI tools to compress the slow parts of the job (research, drafting, synthesizing feedback) so you spend more time on judgment calls, and you've built enough with agents to have real opinions on what makes an interface agent-friendly. - You work async by default. Supabase is fully remote. You make decisions in writing and move work forward without meetings. 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, bo

Fondata nel 1979, SII Group è una società di consulenza internazionale con oltre 100 sedi in quattro continenti, specializzata in IT ed Engineering consulting. Nell'ambito dei nostri progettinel settore Aerospace & Defence , SII Italia è alla ricercadi un/una Remote Sensing Signal Processing Engineer . Sede di lavoro: Roma (ibrido) Settore: Aerospace & Defence Responsabilità principali: Siamo alla ricerca di un/a Remote Sensing Signal Processing Engineer di talento da inserire nel nostro team d…

GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software. * Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on GitLab data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of GitLab. An overview of this role The Customer Success Architect (CSA) team focuses on the themes of align, enable, and expand. The Customer Success Architect (CSA) is a highly strategic position designed to provide unparalleled value to our customers by aligning our platform with their unique business objectives and driving long-term success. The CSA role is a pivotal addition to our customer success team, focusing on building strong, consultative relationships with our key customers. Our CSAs will serve as trusted advisors, leveraging their deep understanding of DevSecOps best practices, industry trends and our software capabilities to help customers navigate complex challenges and achieve their desired outcomes. Additionally, our team serves as liaisons between the customer and the GitLab ecosystem, streamlining collaboration with Product Management, Engineering, Sales, Professional Services, and others. CSM handbook . What You’ll Do • Partner with our customers in taking what was established in the pre-sales command plan, and turning the customers desired positive business outcomes into actionable objectives • Know the GitLab platform, our more common best practices, and use cases in order to guide the customer • Understand the customer journey and be able to guide them on future adoption • Act as the GitLab liaison for GitLab questions, issues, or escalations. Work with GitLab Support, Product Management (i.e., roadmaps), or other teams as needed • Own a book of assigned customers, with a focus on increasing adoption, ensuring retention and growth, and overall customer satisfaction • Remain knowledgeable and up-to-date on GitLab releases • Provide immediate onboarding activities • Work with assigned customers to build Customer Success Plans, establishing critical goals, or other key performance indicators and aid the customer in achieving their goals • Program manage account escalations Provide insights with respect to the availability and applicability of new features in GitLab as relevant • Support GitLab Services in identifying and recommending training opportunities What You’ll Bring • Understanding of Git and typical branching strategies • Knowledge of software development lifecycle and development pipeline • Understanding of continuous integration, continuous deployment, DevSecOps • Prior experience in Customer Success or equivalent history of increasing satisfaction, adoption, and retention • Experience partnering with customers to define and achieve business outcomes • Familiarity working with customers of sizes relevant to the assigned segment • Exceptional verbal, written, organizational, presentation, and communications skills • Detailed oriented and analytical Strong team player but self-starter • Project management experience & skills • Strong technical, analytic, and problem-solving skills • Alignment with our values, and willingness to work in accordance with those values • Ability to travel if needed and comply with the company’s travel policy • Demonstrated progressive experience in a related function is required with direct customer advocacy and engagement experience in post-sales or professional services functions • Fluent German About the team The Customer Success Architect (CSA) team focuses on hands-on technical enablement, adoption, utilization and maturity - while maintaining strong customer relationships and business alignment. How GitLab Supports Full-Time Employees • Benefits to support your health, finances, and well-being • Flexible Paid Time Off • Team Member Resource Groups • Equity Compensation & Employee Stoc

Für einen deutschlandweit tätigen IT-Dienstleister mit rund 400 Mitarbeitenden wirst du Teil eines 10-köpfigen Teams, das den stabilen und sicheren Betrieb komplexer IT-Infrastrukturen im SAP-Basis-Umfeld verantwortet. (Senior-) SAP Basis Administrator/in, primär Remote (m/w/d) Aufgaben Sicherstellung und Weiterentwicklung einer stabilen und leistungsfähigen SAP-Systemlandschaft (ERP 6.0 und S/4HANA) im Rahmen unserer Business Solutions Mitwirkung an konzeptionellen Themen sowie Übernahme koord…

We are still looking for the very Top Talent…and we would be delighted if you were to join our team! More in details, UST is a multinational company based in North America, certified as a Top Employer and Great Place to Work company with over 35.000 employees all over the world and presence in more than 35 countries. We are leaders on digital technology services, and we provide large-scale technologic solutions to big companies. What we look for? We are seeking a skilled Platform Data Enginee…

ABOUT THE ROLE We’re looking for a Product Security Engineer to join our team and help strengthen how security is built into Supabase’s products, platform, and engineering workflows as we continue to scale. You’ll work closely with software engineers, infrastructure teams, and technical leadership, helping us proactively reduce risk earlier in the development lifecycle and ship securely by default. This role is ideal for someone who thrives in async, fast-paced environments and is excited about building developer tools that scale to millions. Success in this role means improving the security posture of the product without becoming a blocker to speed, autonomy, or builder velocity. WHAT YOU’LL OWN In this role, you’ll: - Identify and close gaps across application security, secure design review, and vulnerability management. - Conduct threat modeling, secure design reviews, and code reviews to identify practical remediation paths. - Partner closely with engineering teams to provide product-focused security expertise and shape a modern security program. - Mature how we think about security in a developer-first environment, balancing pragmatism with strong technical judgment. - Distinguish between theoretical risk and material business risk to prioritize security efforts effectively. - Improve security posture through scalable mechanisms like tooling, automation, secure defaults, and developer-friendly guardrails. - Support security incident response by helping triage, investigate, and coordinate remediation for product and platform security issues. - Participate in security on-call rotations, helping respond to urgent security events with clear judgment and calm execution. - Help manage and mature our bug bounty and vulnerability disclosure processes, including triage, validation, prioritization, and coordination with engineering teams. YOU MIGHT BE A GOOD FIT IF YOU - Have strong experience in product security, application security, or security engineering. - Are comfortable working with cloud-native, developer tools, SaaS, platform, or infrastructure products. - Communicate clearly across both technical and non-technical audiences, especially in a written, asynchronous environment. - Are energized by solving real-world problems for developers and navigating ambiguity while moving quickly. - Possess a deep understanding of application security fundamentals, including auth, session management, APIs, and secrets handling. - Have experience with vulnerability triage, bug bounty programs, responsible disclosure, or security incident response. - Are comfortable participating in potential security on-call rotation and can balance urgency, risk, and practical remediation. - Have experience with or interest in Postgres, Kubernetes, or building security guardrails that enable rather than enforce. 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

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're restructuring engineering around initiative teams : a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: • You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. • You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. • You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. • The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own • The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. • Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. • Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). • The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. • A high bar for what ships under your name — production correctness, security posture, 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 staff-level quality Most of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech lead You don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not features The initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) • Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). • Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted b

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're restructuring engineering around initiative teams : a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: • You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. • You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. • You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. • The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own • The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. • Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. • Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). • The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. • A high bar for what ships under your name — production correctness, security posture, 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 staff-level quality Most of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech lead You don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not features The initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) • Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). • Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted b

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're restructuring engineering around initiative teams : a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: • You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. • You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. • You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. • The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own • The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. • Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. • Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). • The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. • A high bar for what ships under your name — production correctness, security posture, 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 staff-level quality Most of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech lead You don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not features The initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) • Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). • Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted by a

Elastic, the Search AI Company, enables everyone to find the answers they need in real time, using all their data, at scale — unleashing the potential of businesses and people. The Elastic Search AI Platform, used by more than 50% of the Fortune 500, brings together the precision of search and the intelligence of AI to enable everyone to accelerate the results that matter. By taking advantage of all structured and unstructured data — securing and protecting private information more effectively — Elastic’s complete, cloud-based solutions for search, security, and observability help organizations deliver on the promise of AI. What Is The Role: As part of the Platform Engineering department, the Traffic team is crafting, building, and improving the multi-cloud platform at scale for Elastic Cloud Hosted and Serverless . We grow and mature our distributed network services and solutions for multiple cloud service provider platforms. We are built on Kubernetes, Go/Scala, and custom orchestration architectures. In your daily life with us, you will participate in coding, innovating technical designs, crafting solutions, improving resilience, and prioritizing security, bug fixes, and features. For example, Debugging Azure Networking for Elastic Cloud Serverless is part of our efforts, and we want your experience to contribute to a truly exceptional customer experience! What You Will Be Doing: • Taking an engineering approach in leading technical initiatives for automating network engineering efforts to guarantee the reliability of the global Elastic infrastructure. . • Growing our global Platform infrastructure to meet the increasing scaling demands by developing and maintaining software, codebases, tooling and automations. • Collaborating in an environment with an inclusive approach, and focusing on operational perfection which uplifts others. • Preventing repeated customer impact in response to major incidents and prioritised problem management. Our on call rotation is spread well, and we address complex customer concerns too. What You Bring: • 10+ years in Software Engineering with product success in delivering Cloud network solutions. You collaborate with engineers as an authority in identifying, implementing and delivering solutions. Experience in public cloud, Go and managed Kubernetes services is advantageous. • Success and lessons of experiences from striving for 'progress not perfection' in the name of Platform reliability. We want to hear about your customer first approach in solving operational problems for both today and the future. • Passion for developing solutions that involve inclusive communication methods to grow and strengthen partner and team relationships. Examples of working in distributed teams or working remotely is desirable. Bonus Points: You don't need to have all of these items, but these represent the types of work you will do as a Software Engineer at Elastic. • You have designed and built a SaaS product in a public cloud ideally built using Infrastructure-as-Code tooling such as Crossplane or Terraform • You have built Kubernetes-at-scale infrastructure, ideally across multiple cloud providers, and the vital automation to support it. • You have written product features or functions in Golang or other programming languages. • You have worked with containerized services (such as Docker.) • You have proven results in leading and improving cross-team engineering initiatives. • You have experience in system administration with professional skills in Linux on distributed systems at scale. • You have diagnosed or designed, implemented and created solutions with the Elastic Stack. • You are experienced in a self-organizing and sharing in a globally distributed team environment. • You strengthen team members in bringing out the best of each other by uplifting others with coaching and mentoring. Compensation for this role is in the form of base salary. This role does not have a variable compensation component. The typical starting salary range for new hires in this role is listed below. In select locations (including Seattle WA, Los Angeles CA, the San Francisco Bay Area CA, and the New York City Metro Area), an alternate range may apply as specified below. These ranges represent the lowest to highest salary we reasonably and in good faith believe we would pay for this role at the time of this posting. We may ultimately pay more or less than the posted range, and the ranges may be modified in the future. An employee's position within the salary range will be based on several factors including, but not limited to, relevant education, qualifications, certifications, experience, skills, geographic location, performance, and business or organizational needs. Elastic believes that employees should have the opportunity to share in the value that we create together for our shareholders. Therefore, in addition to cash compensation, this role is currently eligible to participate