Senior Engineer-Device Driver

Role

We are seeking a Senior Windows Device Driver Engineer for our Windows Kernel Development team to build, debug, and maintain kernel-mode drivers and user-mode components. This role requires strong hands-on expertise in Windows internals and low-level debugging, and is expected to grow into technical leadership—mentoring engineers and owning a component end-to-end—while remaining primarily an individual contributor.

You will work closely with a Windows Kernel Development team based in Chennai, own a driver component or feature area, and collaborate across QA, product, and support to ship production-grade driver code. If you have strong hands-on Windows driver experience and are ready to start taking on technical leadership, we want you on this team.

Responsibilities

• Design, implement, and maintain Windows kernel-mode drivers, user-mode components (e.g., mini-filters, WFP network callouts, WDF function drivers).
• Debug complex, low-level issues such as crash dumps, BSODs, race conditions, and IRQL violations, using tools like WinDbg.
• Own a driver component or feature area end-to-end, from design through shipping and support.
• Build and maintain the user-mode components around your driver, including services, DLLs, and COM interfaces, primarily in C/C++.
• Participate in code reviews, help onboard and mentor less experienced engineers, and contribute to technical design decisions for your team.
• Work with QA/test to ensure driver stability and, where applicable, support certification processes (WHQL/HLK).
• Collaborate with cross-functional teams (product, QA, support) to translate requirements into robust, production-ready driver code.

Required Experience & Expertise

• 5–8 years of professional software engineering experience, with hands-on Windows Systems/Kernel Development.
• Hands-on experience building or maintaining Windows kernel-mode drivers and/or user-mode components (KMDF, WDM, WDF, UMDF, mini-filter, WFP, or similar).
• Strong C and/or C++ skills at a systems level (primary language requirement), with C# as a secondary language (e.g., tooling, services, test harnesses).
• Solid understanding of Windows internals (memory management, process/thread scheduling, IRQL, synchronization).
• Experience with WinDbg or equivalent kernel debugging tools, and comfort reading crash dumps.
• Some early leadership signal: you've owned a module or feature, mentored a teammate, or acted as the de facto technical lead on something.
• Nice-to-have: experience with file-system mini-filters or WFP network drivers, driver signing/WHQL/HLK exposure, user-mode systems experience (Windows services, DLLs, COM), or endpoint security related technologies.
• Bachelor's or Master's degree in Computer Science, Information Security, Engineering, or a related discipline.