You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
10 days ago
warning
Heads-up
Requirements and responsibilities
About This RoleBuild open source graphics drivers that run on real hardware. You will work directly in the Vulkan driver stack, contributing upstream to Mesa and the Linux DRM subsystem, and solving problems that affect how GPUs are used across the Linux ecosystem.This isn't just maintenance work. You will be debugging real hardware behaviour, reading GPU specs and kernel internals and writing code that ends up in distributions used by millions of people. The work is technically deep and the feedback loop is direct.The role combines low-level systems programming with open source collaboration. You will work alongside experienced graphics engineers, develop genuine expertise in how modern GPUs work from the kernel up, and grow into a contributor that the broader open source graphics community knows by name.Location: Fully remoteTravel: Optional conference attendanceWhat You'll Actually DoUpstream First: Contribute directly to Mesa and the Linux DRM subsystem, writing Vulkan driver code that lands in mainline and ships to users worldwideReal-World Impact: Work on graphics drivers for hardware used across Linux desktops, embedded devices and consumer products that people depend on every daySolve Hard Problems: Debug GPU behaviour that has no documentation, reverse engineer hardware quirks and fix rendering issues that manifest as a corrupted frame with no obvious cause. The GPU did something unexpected and it is your job to find out whyCommunity Collaboration: Work with Mesa and kernel maintainers, participate in code review across the open source graphics community and represent Collabora at conferences like XDC and FOSDEMClient Partnership: Translate hardware vendor and client requirements into upstream-compatible solutions while advocating for approaches that benefit the broader ecosystem. Help clients understand why investing in open source driver quality serves their long-term goalsNavigate Constraints: Balance upstream correctness with real-world pressures: hardware bring-up timelines, vendor NDAs, performance targets and client deadlines, while keeping code quality high enough to pass maintainer reviewBe a Technical Advisor: Explain complex driver and GPU architecture decisions to product teams, provide honest assessments of what is and isn't possible and build trust through transparent communicationWhat we’re looking forRequiredVulkan - solid understanding of the core spec; command buffers, render passes, synchronisation, memory management and pipelines. Familiarity with Vulkan validation layers and debugging workflowBasic understanding of GPU hardware concepts - queues, tilers vs IMR, memory hierarchiesLinux kernel basics - comfortable reading and navigating kernel codeDRM fundamentals - GEM/buffer management, dma-buf/prime buffer sharing, fence and sync objects, GPU job submission pathsMesa architecture awareness - Gallium, driver structureBasic understanding of how userspace drivers interact with kernelC and C++ - comfortable with pointer arithmetic, memory management, kernel-style codingNice to haveGit - mailing list patch workflow (not just GitHub PRs)Comfortable reading specs and documentation independentlyNot afraid of large unfamiliar codebasesOpen source contribution mindset - code review, public communication, upstream firstExisting Mesa or kernel patch historyExperience with a specific GPU family (ARM/AMD/Intel)Python for tooling/scriptingRust programming skillsUnderstanding of KMS fundamentals or Wayland clientsWhat We OfferCompensation & BenefitsWe offer a competitive benefits package tailored to each country in which we have employees, plus a core global benefit offering accessible to all Collaborans. Our core benefits include:Competitive salary based on experience and locationOffice setup budgetSabbatical/Retention of Services - after five years continuous serviceCo-working policy - support for working outside homeWellness assessments - biannual wellbeing assessments with a trained mental health specialistConference attendance - we cover expenses and encourage speaking opportunitiesOpen source time - contribute to projects you care aboutWork EnvironmentFully remote - work where you’re most productiveGlobal team - engineers across Europe, Americas and AsiaNo on-call rotations - this isn't support workSustainable pace - we're here for the long termFlexible hours - manage your own scheduleGrowth & ImpactUpstream contributions - your work shapes Linux, not just client productsTechnical leadership track - path to principal engineer, subsystem expertise or technical architecture rolesConsulting track - develop deeper client relationships, lead customer engagements or shape service offeringsMentorship opportunities - both receiving and providing guidanceConference speaking - we support presentation submissions and provide coachingRecognition - your contributions are public, building your professional reputationCulture & ValuesUpstream first - we believe the best solutions benefit everyoneTransparency - open discussion about technical decisions, business constraints and project challengesPragmatism - perfect is the enemy of good; we ship quality code that solves real problemsRespect for expertise - we trust engineers to make technical decisionsCollaborative - we succeed by working together, internally and with the communitySustainable pace - we're here for the marathon, not the sprintA Day in the LifeMorning (your timezone):Review overnight Mesa GitLab discussion on your patch seriesTriage a rendering corruption report from a client - identify whether it is a driver bug or a spec interpretation issueRespond to maintainer feedback on a Vulkan extension implementationPair debug session with a colleague on unexpected GPU hang behaviourMidday:Deep work: implement a missing feature in the Vulkan driver, cross-referencing the spec and hardware documentationQuick video call with client team to walk through your proposed fix and explain the trade-offsReview a colleague's DRM buffer management patch before they send it upstreamHelp a colleague debug an issue to identify whether it is GPU relatedAfternoon:Reproduce a client issue locally using RenderDoc and Vulkan validation layers - narrow it down to a specific draw callUpdate client on timeline, discuss whether a quick workaround or a proper upstream fix is the right move for their scheduleJoin optional team discussion on how to handle a tricky synchronisation edge caseWrite a clear commit message explaining not just what changed but why the hardware requires itSome days are heads-down driver work with hours spent in a debugger. Others involve more client communication and architectural discussion. You will find a balance that suits the project and your strengths.Our Interview ProcessWe respect your time and provide a clear, structured process:Application Review (within 1 week) - we look at your code and contributionsInitial Chat (30 min) - casual conversation about your experience and our workTechnical Interview (2 - 3h)Technical Deep-Dive - discuss kernel architecture, past debugging challenges and how you approach problem-solving (no whiteboard coding)Code Review Session - review real patches together, discuss trade-offsClient Scenario Discussion - talk through a realistic customer situation: balancing technical debt, timeline pressure and upstream goals (we want to see your thought process, not a "right answer")Head of Open Source Software Consulting team Discussion (60 min) - meet the Head of Open Source Software Consulting team, ask about day-to-day work and how Collabora works, discuss compensation and benefits.Offer (within 1 week of final interview)Total timeline: 3-4 weeks from application to offerWe provide feedback at every stage, and you'll always know where you stand.What Happens NextInitial response within 1 weekEven if we don't move forward, we'll tell you whyCollabora's CommitmentWe're committed to building a diverse team and inclusive environment. We encourage applications from people underrepresented in tech.We evaluate candidates based on skills and contributions, not pedigree. If you're unsure whether you qualify, apply anyway —imposter syndrome is real and you might be exactly who we're looking for.We recognise that the combination of deep kernel expertise and consulting skills is rare. If you're strong in one area and interested in developing the other, we want to hear from you.
Optionally, you can add more information later (benefits, pre-screening questions, etc.)