Senior Software Engineer, Desktop Platform (US East Coast)

June 13, 2026

Other Jobs To Apply

At Docker, we make app development easier so developers can focus on what matters. Our remote-first team spans the globe, united by a passion for innovation and great developer experiences. With over 20 million monthly users and 20 billion image pulls, Docker is the #1 tool for building, sharing, and running apps—trusted by startups and Fortune 100s alike. We’re growing fast and just getting started. Come join us for a whale of a ride!Docker Desktop is one of the core pillars of the Docker suite—powering the workflows of millions of developers worldwide. According to the Stack Overflow Developer Survey, Docker has been ranked the most-used, most-desired, and most-admired developer tool for multiple years running. Joining the Desktop Platform team means shaping the experience behind one of the most loved tools in modern software development.The Desktop Platform team is responsible for the core lifecycle of Docker Desktop, including installation, updates, startup, and key shared components used by every Docker Desktop feature team. Our work ensures that Docker Desktop is reliable, and easy to adopt, while providing the modular foundations that enable other teams to build and ship with confidence.In this role, you will design, develop, and maintain the systems that define the Docker Desktop experience end to end. You’ll improve update and install reliability, reduce startup time, strengthen diagnostics, refine shared platform components such as settings and feature flags, and contribute to the architectural evolution that accelerates development across all Desktop teams.The successful candidate has strong systems and OS fundamentals and thinks like a platform engineer—designing modular, predictable components that scale across teams. They bring sound technical judgment, contribute thoughtfully to architectural discussions, and use data to guide decisions. They collaborate effectively across engineering groups and are comfortable owning ambiguous, cross-cutting problems that shape the long-term health of Docker Desktop.<h1>Responsibilities</h1><ul style="min-height:1.5em"><li>Design, develop, and maintain core lifecycle components of Docker Desktop, including installation, update, startup, and shared platform systems.</li><li>Collaborate closely with product teams to ensure seamless integration with shared platform components.</li><li>Contribute to documentation, knowledge sharing, and technical discussions that raise the clarity and quality of engineering within the Desktop ecosystem.</li><li>Write high-quality code with strong test coverage (unit, integration, and end-to-end) and support healthy engineering practices across the team.</li><li>Collaborate with our Delivery team on CI, release pipeline reliability, and lifecycle automation improvements that support faster and safer Desktop releases, especially when cross-team coordination is required.</li></ul><h1>Qualifications</h1><ul style="min-height:1.5em"><li>5+ years of experience building backend or systems software, ideally in Go or similar languages.</li><li>Experience working on cross-platform desktop applications or lifecycle components (installers, updaters, system services).</li><li>Demonstrated ability to design modular, maintainable system components that scale across teams.</li><li>Comfortable working with observability, telemetry pipelines, performance metrics, and system health diagnostics.</li><li>Strong problem-solving skills and the ability to work through ambiguity and cross-cutting technical challenges.</li><li>Excellent communication skills for cross-team collaboration, design reviews, and technical documentation.</li><li>Understanding of operating system internals, installers/updaters, virtualization, networking, or OS-level APIs.</li><li>Experience with CI/CD systems, build pipelines, or release engineering workflows is a plus.</li></ul>We know that great candidates don’t always meet 100% of the qualifications listed. If you're excited about this role and believe you can have an impact, we encourage you to apply—even if your experience doesn’t perfectly align with every requirement.<h1>What to Expect</h1><h2>First 30 Days</h2><ul style="min-height:1.5em"><li>Meet your team, your onboarding buddy, and key collaborators across Docker Desktop.</li><li>Set up your development environment and become familiar with the Desktop Platform architecture, lifecycle systems, and key internal components.</li><li>Contribute your first small changes—bug fixes, reliability improvements, or performance tweaks.</li><li>Participate in design discussions and pair programming to gain exposure to our tooling and workflows.</li></ul><h2>First 90 Days</h2><ul style="min-height:1.5em"><li>Drive or co-drive a larger feature, from design to development.</li><li>Present findings, technical proposals, or insights to the team through proposal reviews or internal demos.</li><li>Influence roadmap priorities based on what you’ve learned about the system’s strengths, gaps, and opportunities.</li></ul><h2>One Year Outlook (First Year)</h2><ul style="min-height:1.5em"><li>Deliver measurable impact with the team.</li><li>Lead architectural or cross-cutting platform initiatives that improve development velocity or user experience.</li><li>Help shape long-term technical direction with well-considered proposals and influence cross-team engineering practices.</li><li>Become a go-to engineer for complex issues and a trusted partner to teams building on top of the platform.</li></ul>We use Covey as part of our hiring and / or promotional process for jobs in NYC and certain features may qualify it as an AEDT. As part of the evaluation process we provide Covey with job requirements and candidate submitted applications. We began using <a target="_blank" rel="noopener noreferrer nofollow" href="https://getcovey.com/product/covey-scout-inbound">Covey Scout for Inbound</a> on April 13, 2024.Please see the independent bias audit report covering our use of Covey <a target="_blank" rel="noopener noreferrer nofollow" href="https://getcovey.com/nyc-local-law-144">here</a>.Perks<ul style="min-height:1.5em"><li>Freedom & flexibility; fit your work around your life</li><li>Designated quarterly Whaleness Days</li><li>Home office setup; we want you comfortable while you work</li><li>16 weeks of paid Parental leave</li><li>Technology stipend equivalent to $100 net/month</li><li>PTO plan that encourages you to take time to do the things you enjoy</li><li>Quarterly, company-wide hackathons</li><li>Training stipend for conferences, courses and classes</li><li>Equity; we are a growing start-up and want all employees to have a share in the success of the company</li><li>Docker Swag</li><li>Medical benefits, retirement and holidays vary by country</li></ul>Docker embraces diversity and equal opportunity. We are committed to building a team that represents a variety of backgrounds, perspectives, and skills. The more inclusive we are, the better our company will be.Due to the remote nature of this role, we are unable to provide visa sponsorship.#LI-REMOTE

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...