Principal Software Engineer

Principal Software Engineer

Full-Time 63000 - 77000 £ / year (est.) Hybrid
A

At a Glance

  • Tasks: Lead the development of a cutting-edge desktop platform using Electron and Chromium.
  • Company: Join Autodesk, a leader in innovative software solutions.
  • Benefits: Enjoy competitive pay, flexible work options, and growth opportunities.
  • Other info: Collaborative hybrid work environment with a focus on mentorship and technical leadership.
  • Why this job: Make a real impact on technology that shapes the future.
  • Qualifications: 8+ years in software engineering with expertise in JavaScript, TypeScript, and Node.js.

The predicted salary is between 63000 - 77000 £ per year.

Autodesk is looking for a Principal Software Engineer to provide technical leadership for a new Electron and Chromium-based desktop platform for Autodesk web applications. In this hands-on individual contributor role, you will define the platform architecture, lead complex technical decisions, and guide engineers building the Electron runtime, Windows integrations, automated delivery systems, and shared platform capabilities. You will combine deep technical expertise with broad influence, helping the team deliver a secure, maintainable, and reusable desktop platform while remaining actively involved in design, implementation, debugging, and code review.

Responsibilities

  • Platform architecture and technical direction - approximately 30%: Define and evolve the architecture of the Electron desktop platform, including process boundaries, native capabilities, application interfaces, security controls, runtime configuration, and product integration patterns.
  • Hands-on platform engineering - approximately 25%: Design, prototype, implement, and review complex functionality across Electron, Chromium, Node.js, TypeScript, Windows APIs, and supporting native components.
  • Technical leadership and mentoring - approximately 20%: Guide engineers through design and implementation decisions, mentor team members, review complex changes, establish engineering standards, and help the team develop expertise in desktop platform engineering.
  • Cross-team integration and platform adoption - approximately 15%: Work with product teams and Autodesk platform teams responsible for security, identity, software distribution, telemetry, crash reporting, graphics, and other shared capabilities.
  • Operational readiness and engineering quality - approximately 10%: Partner with quality and release engineering to define release gates, runtime upgrade policies, observability, supportability, and production-readiness requirements.

Own the overall technical architecture of the shared desktop platform and ensure clear boundaries between reusable platform capabilities and product-specific functionality. Define secure communication patterns between hosted web applications and privileged desktop functionality, including process isolation, inter-process communication, native API exposure, navigation controls, and application trust boundaries. Establish the strategy for using and upgrading Electron and Chromium, including supported versions, configuration and build options, runtime feature enablement, compatibility assessment, and response to security updates. Keep the platform as close as practical to supported upstream Electron and Chromium capabilities, avoiding unnecessary customization and long-term maintenance burden. Lead the design of native Windows capabilities such as application lifecycle management, hardware and system-information access, GPU preference, protocol handling, operating-system integration, and enterprise deployment behaviour. Define stable interfaces through which Autodesk web applications can consume desktop capabilities without creating product-specific implementations or forks. Work with the P3 Senior Software Engineer to break larger platform objectives into technical designs, implementation plans, dependencies, and incremental deliverables. Provide technical guidance and mentorship to the P2 Software Engineer, helping them develop deeper expertise in Electron, Chromium, Node.js, Windows, debugging, and secure application design. Partner with the team's SDET and CI/CD/Release Engineer to ensure the platform is testable, buildable, reproducible, diagnosable, and capable of being released through automated delivery pipelines. Define technical requirements for build, packaging, signing, release promotion, rollback, and runtime qualification while leaving day-to-day pipeline implementation with the engineer responsible for CI/CD and release automation. Work closely with Autodesk application-security specialists to develop threat models, address security findings, apply Electron and Chromium security best practices, and ensure privileged desktop functionality is exposed safely. Collaborate with specialist graphics and rendering teams on interfaces and requirements related to memory, GPU selection, hardware visibility, and runtime capabilities while keeping graphics implementation within the owning teams. Lead evaluation of new Electron and Chromium releases, significant runtime capabilities, Windows platform changes, and other technologies that may affect the platform. Diagnose the most difficult technical issues spanning Electron, Chromium, Node.js, Windows, application lifecycle, memory, security, installation, and hosted web applications. Use profiling, crash diagnostics, runtime tracing, native debugging tools, and Chromium developer tooling to understand complex system behaviour. Write and review architecture decision records, technical designs, platform interfaces, operational runbooks, and engineering standards. Proactively identify architectural risks, technical debt, reliability concerns, and opportunities to simplify the platform before they become delivery or support problems. Ensure technical decisions consider the needs of future Autodesk products as well as the immediate requirements of Forma. Help establish an onboarding model that allows additional Autodesk web applications to adopt the desktop platform through well-defined configuration and integration points. Participate in hiring and help establish the technical bar for engineers joining the team.

Minimum Qualifications

  • Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience.
  • 8+ years of professional software engineering experience.
  • Strong software engineering experience with JavaScript or TypeScript and Node.js.
  • Significant experience designing and delivering complex software systems or platform capabilities.
  • Experience with Electron, Chromium-based applications, desktop application development, or comparable systems-level application platforms.
  • Strong understanding of application architecture, process boundaries, asynchronous systems, security, and software lifecycle management.
  • Experience leading technical design and implementation across multiple engineers.
  • Ability to take ambiguous or open-ended technical problems from investigation through architecture, implementation, and production delivery.
  • Strong debugging skills across multiple components, processes, or technology layers.
  • Experience with automated testing, continuous integration, source control, code review, and modern software delivery practices.
  • Experience communicating technical trade-offs and influencing decisions across engineering teams.
  • Demonstrated ability to mentor engineers and raise engineering quality through technical leadership.

Preferred Qualifications

  • Deep experience with Electron architecture, including main, renderer, and preload processes, context isolation, inter-process communication, and security configuration.
  • Strong understanding of Chromium architecture, runtime configuration, feature flags, release lifecycle, and developer tooling.
  • Experience with C++, native Node.js modules, or interoperability between JavaScript and native platform APIs.
  • Experience developing software using Windows APIs or other systems-level Windows technologies.
  • Experience diagnosing memory, process, performance, startup, or crash problems in Chromium-based or native desktop applications.
  • Familiarity with Electron or Chromium build tooling such as GN and Ninja.
  • Experience with Windows application packaging, installers, code signing, updating, and enterprise software deployment.
  • Experience designing shared APIs, SDKs, runtimes, or platform components consumed by multiple products or engineering teams.
  • Experience with desktop application threat modelling and secure application architecture.
  • Experience with software supply-chain security, dependency management, vulnerability response, and release provenance.
  • Experience defining operational standards for a customer-facing desktop application.

The Ideal Candidate

You enjoy solving technical problems that do not fit neatly into a single layer of the technology stack. You are equally comfortable discussing platform architecture, reviewing TypeScript, investigating Chromium behaviour, debugging a Windows issue, examining a crash report, or helping an engineer reason through a difficult design problem. You remain hands-on while thinking beyond your own code. You recognise when a local implementation decision could create a long-term platform problem and work with the team to find a simpler, more maintainable solution. You provide technical leadership through clarity and expertise rather than hierarchy. You help other engineers make good decisions, explain complex trade-offs in accessible terms, and create an environment where engineers can increasingly operate independently. You think of the desktop application as a platform rather than a one-off product wrapper. You care about creating clear interfaces, reducing unnecessary customisation, maintaining secure boundaries, and designing capabilities that can be reused by future Autodesk products. You are comfortable operating in areas of uncertainty, gathering evidence, comparing alternatives, making recommendations, and changing direction when new technical information becomes available.

We are building a new desktop platform that enables Autodesk's web-based products to deliver richer, higher-performance experiences on Windows. Forma is the first product adopting the platform, with the longer-term goal of creating reusable desktop capabilities for additional Autodesk products. You will join a new cross-functional platform team working across Electron, Chromium, Windows desktop integration, software delivery, security, quality, and enterprise deployment. As the technical lead for the team, you will work closely with software engineers, quality and release engineers, product partners, and specialist engineering teams across Autodesk. This is a hybrid working position based out of Autodesk's Sheffield office. The role combines in-person collaboration with colleagues in Sheffield with work across distributed engineering teams throughout Autodesk.

Learn More About Autodesk

Welcome to Autodesk! Amazing things are created every day with our software – from the greenest buildings and cleanest cars to the smartest factories and biggest hit movies. We help innovators turn their ideas into reality, transforming not only how things are made, but what can be made. We take great pride in our culture here at Autodesk – it’s at the core of everything we do. Our culture guides the way we work and treat each other, informs how we connect with customers and partners, and defines how we show up in the world. When you’re an Autodesker, you can do meaningful work that helps build a better world designed and made for all. Ready to shape the world and your future? Join us!

Salary transparency

Salary is one part of Autodesk’s competitive compensation package. Offers are based on the candidate’s experience and geographic location. In addition to base salaries, our compensation package may include annual cash bonuses, commissions for sales roles, stock grants, and a comprehensive benefits package.

Belonging

We take pride in cultivating a culture of belonging where everyone can thrive.

In-Person Onboarding and Identity Verification

This role may require in-person onboarding and/or in-person ID verification.

Principal Software Engineer employer: Autodesk, Inc.

At Autodesk, we pride ourselves on being an exceptional employer, particularly for the Senior Director, Operations Business Partner role in our Global Expansion team. Our dynamic work culture fosters collaboration and innovation, empowering employees to take ownership of their projects while providing ample opportunities for professional growth and development. Located in a vibrant tech hub, we offer competitive benefits and a supportive environment that values accountability and results, making it an ideal place for those seeking meaningful and impactful careers.

A

Contact Details:

Autodesk, Inc. Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Principal Software Engineer

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Autodesk, Inc. or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Autodesk, Inc..

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Autodesk, Inc..

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Autodesk, Inc. that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Principal Software Engineer

Technical Leadership
Platform Architecture
Electron
Chromium
Node.js
TypeScript
Windows APIs

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Autodesk, Inc..

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Autodesk, Inc. and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Autodesk, Inc.

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Autodesk, Inc. uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.