Source description
About the role
Compensation & Benefits
We 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 location
Office setup budget
Sabbatical/Retention of Services - after five years continuous service
Co-working policy - support for working outside home
Wellness assessments - biannual wellbeing assessments with a trained mental health specialist
Conference attendance - we cover expenses and encourage speaking opportunities
Open source time - contribute to projects you care about
Work Environment
Fully remote - work where you’re most productive
Global team - engineers across Europe, Americas and Asia
No on-call rotations - this isn't support work
Sustainable pace - we're here for the long term
Flexible hours - manage your own schedule
Growth & Impact
Upstream contributions - your work shapes Linux, not just client products
Technical leadership track - path to principal engineer, subsystem expertise or technical architecture roles
Consulting track - develop deeper client relationships, lead customer engagements or shape service offerings
Mentorship opportunities - both receiving and providing guidance
Conference speaking - we support presentation submissions and provide coaching
Recognition - your contributions are public, building your professional reputation
Culture & Values
Upstream first - we believe the best solutions benefit everyone
Transparency - open discussion about technical decisions, business constraints and project challenges
Pragmatism - perfect is the enemy of good; we ship quality code that solves real problems
Respect for expertise - we trust engineers to make technical decisions
Collaborative - we succeed by working together, internally and with the community
Sustainable pace - we're here for the marathon, not the sprint
A Day in the Life
Morning (your timezone):
Review overnight Mesa GitLab discussion on your patch series
Triage a rendering corruption report from a client - identify whether it is a driver bug or a spec interpretation issue
Respond to maintainer feedback on a Vulkan extension implementation
Pair debug session with a colleague on unexpected GPU hang behaviour
Midday:
Deep work: implement a missing feature in the Vulkan driver, cross-referencing the spec and hardware documentation
Quick video call with client team to walk through your proposed fix and explain the trade-offs
Review a colleague's DRM buffer management patch before they send it upstream
Help a colleague debug an issue to identify whether it is GPU related
Afternoon:
Reproduce a client issue locally using RenderDoc and Vulkan validation layers - narrow it down to a specific draw call
Update client on timeline, discuss whether a quick workaround or a proper upstream fix is the right move for their schedule
Join optional team discussion on how to handle a tricky synchronisation edge case
Write a clear commit message explaining not just what changed but why the hardware requires it
Some 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.
More at Collabora