Windows Migration Engineer

Role summary

We are seeking a technology engineer with 5 to 8 years of overall experience, including at least 3 years of Windows desktop migration experience (planning, cutover, validation, and post-migration issue resolution). As a Migration Engineer, you will work daily with a pre-assigned set of users to ensure their business-critical applications function correctly on their new Azure-hosted desktop. You will troubleshoot issues end-to-end, coordinate fixes with partner teams, and communicate clearly with users across diverse roles (e.g., trading, engineering, operations, senior management).

Key responsibilities

Execute user migrations following the factory playbook, tracking progress and outcomes

Validate end-user functionality on NDS.Next desktops (e.g. M365 Suite, Firmwide common applications (e.g., digital assistant tools), Business apps from an internal app store, Web applications and line-of-business tools

Perform application testing, defect reproduction, and regression checks before and after migration. This involves handling access and network‑related impacts during desktop migrations. The person should be able to identify and resolve connectivity or access issues efficiently as part of the migration work.

Troubleshoot and resolve issues across Windows, applications, and desktop environment configuration. Issues will be routed by the helpdesk team. This involves troubleshooting postmigration related to issues.

Write clear user updates and technical notes; manage expectations and drive closure

Provide structured reporting on your assigned workload (status, risks, blockers)

Must-have skills

Strong familiarity with Windows desktop environments and application behavior

Proficiency in cloud application connectivity and access management, including core networking concepts and operational troubleshooting – we are looking for senior profiles who can handle issue from these areas in case they occur during migration.

Python or Java coding proficiency for automation and diagnostics - Any scripting knowledge is acceptable, such as Shell, Perl or Unix or any other scripts. Java or Python is not mandatory.

Strong debugging and problem isolation skills (logs, configs, repro steps)

Strong application testing knowledge (test design, validation, regression mindset) - This refers to testing applications on remote desktops after migration. The migration engineer should ensure that all applications which worked before the migration are functioning correctly after the desktops are migrated.

Excellent written and verbal communication, including explaining technical issues to non-technical audiences

Strong personal project management skills (follow process, manage your queue, accurate reporting)