🎁 Antes de postularte, practica esta entrevista. Crea tu cuenta gratis en WorkMundi y recibe un Entrenamiento de Entrevista en HelpsYouSpeak — sin costo, sin tarjeta. Quiero mi entrenamiento →
Location: Fully Remote (Worldwide) - Focus on LATAM time zones (Americas) Employment Type: Full-time, B2B / Independent Contractor (or W2 for US-based candidates) Company: CloudLinux / TuxCare (DevJBS Inc.) About CloudLinux / TuxCare CloudLinux is the company behind the CloudLinux OS and a suite of security solutions for the Linux ecosystem. Our TuxCare division is a global leader in automated live patching for Linux kernels, enabling enterprises to apply critical security updates without rebooting or downtime. We also provide extended support for end-of-life Linux distributions, helping organizations maintain compliance and security beyond standard EOL dates. With a team of 250+ professionals and over 4,500 clients—including Dell, GoDaddy, IBM, and Zoom—we are committed to delivering robust, enterprise-grade infrastructure solutions. Our fully remote, global team operates across the US, Europe, Latin America, and beyond. Role Context: KernelCare ELS The KernelCare Extended Lifecycle Support (ELS) team is dedicated to backporting security fixes and critical bug patches from upstream Linux kernels to older, enterprise-used kernel versions. Our mission is to keep legacy systems secure and stable, even when the original vendor no longer provides support. This is a hands-on, engineering-heavy role . You will not just study patches—you will actively backport, build, validate, and deliver kernel updates to production-grade environments. You'll work closely with upstream Linux, RPM and Debian packaging systems, and modern automation tooling, including AI-assisted development workflows. Key Responsibilities Research & Analysis: Investigate upstream security (CVE) and bug fixes; analyze patch dependencies and impact on legacy kernels Backporting: Manually backport Linux kernel patches to older kernel versions used in RPM-based and Debian-based distributions Conflict Resolution: Resolve merge conflicts between upstream changes and target kernel codebases Kernel Packaging: Build and rebuild kernel source and binary packages using reproducible build environments for RPM and Debian ecosystems Validation & Testing: Validate patched kernels through build tests, runtime tests, and regression analysis to ensure stability Tooling & Automation: Enhance internal workflows (patch preparation, build automation, validation pipelines) using Python, Go, and Shell scripting AI Integration: Leverage agentic/AI-assisted development tools to accelerate tasks, while rigorously verifying every generated output Documentation & Collaboration: Document technical decisions, participate in code reviews, and communicate clearly with team members across time zones Requirements Must-Have Strong C proficiency and hands-on Linux debugging skills Proven commercial experience in Linux kernel development—specifically patching, backporting, or debugging Solid experience with Git, GNU build tools (make, autotools), and standard Linux developer utilities Experience building Linux kernels or distribution packages from source Scripting and automation skills: Python, Go, or Shell Practical exposure to AI-assisted development tools (e.g., Copilot, Codeium, or similar), with a disciplined approach to code verification English: Intermediate or higher (B1+), both written and spoken—you'll be working in an international team and communicating in English daily Strong ownership mindset, balanced technical judgment, and ability to articulate trade-offs Nice-to-Have Experience with RPM/SRPM or Debian kernel packaging Familiarity with security patching, CVE analysis, and extended lifecycle maintenance Working knowledge of Docker, QEMU, Jenkins, or other CI systems Experience designing kernel validation tests, analyzing core dumps, and investigating regressions Candidate Profile (Cultural Fit) Hands-on practitioner: You love working directly with kernel code, not just theorizing Methodical and detail-oriented: Kernel patching requires precision, reproducibility, and thorough validation Ownership-driven: You take responsibility for outcomes, document your work, and proactively communicate risks AI-curious but cautious: You embrace AI tools to accelerate development but never skip verification Remote-first compatible: You thrive in async environments with minimal supervision and clear communication Benefits 100% remote work with flexible hours — work from anywhere in the world (focus on LATAM-friendly time zones) 24 paid vacation days + 10 national holidays + unlimited sick leave Private medical insurance compensation Coworking space and sports/fitness reimbursement Professional development budget — conferences, courses, certifications Reward program for patentable ideas A collaborative, non-corporate environment with a strong engineering culture
Here's where they are and how to stand out in your next interview.
24.795Jobs
9.577IN
74%EN
That number includes positions in India (9,577), Poland (3,429), the United States (1,753), Singapore (787), and Brazil (779). If you're looking to move or work remotely, check which countries match your goals — then filter WorkMundi by location to see what's actually hiring near you.
Most developer ads you'll see are written in English: 18,397 of the 24,795. That doesn't tell you whether the job itself requires you to speak English or work in English daily, so read each posting carefully. Don't assume the language of the ad matches the language of the team.
The employers posting the most developer roles are Link Group (369 jobs), Upvanta (257), jobgether (226), and OfferZen (212). If you're applying to any of these, research their hiring patterns. They move fast and post often, which means they're either scaling hard or replacing people who didn't fit.
In your interview, expect this: 'Walk me through the last time you had to debug something that took you more than an hour. What was it, what did you try first, and what would you do differently?' Hiring managers ask this to see if you think systematically or just try random fixes. Have a real example ready with specifics.