[Hiring] Principal Software Engineer @Black Tree Gaming

Role Description

We’re hiring a Principal Software Engineer to join our App Engineering team and help lead the technical direction of Vortex, our flagship desktop mod manager used by millions of PC gamers.

• You'll be one of the most senior technical voices on the team: writing production code, making architectural calls, and raising the bar for everyone around you through mentorship and example.
• If you've spent your career going deep on hard systems problems, performance, concurrency, platform integration, API design and you want that depth to matter to millions of real users, this is that role.

Why is this role unique?

• A native desktop application running on wildly varied consumer hardware and OS configurations.
• 500+ supported games, each with its own file formats, load order logic, and installer quirks.
• Deep OS-level integration: file systems, the Windows registry, drives, processes, code signing, auto-update.
• A public extension API with an active third-party developer ecosystem building on top of your work.
• A large, vocal, technically engaged user base that stress-tests every release in the wild.
• You'll help shape the systems behind mod installation, sorting, conflict resolution, downloads, and profile management for millions of active users and you'll help take Vortex from Windows-first to genuinely cross-platform.

Requirements

• Ship high-impact work across the Electron main process, renderer, and extension layers.
• Own the hardest bugs in the codebase: race conditions, performance regressions, gnarly state issues.
• Drive architecture decisions that span multiple teams, in partnership with engineering management.
• Review code and set technical standards through example, not just process.
• Mentor engineers across levels in Electron, React, TypeScript, and the modding domain.
• Steward a public extension API used by an active third-party developer community.
• Identify and pay down technical debt in a large, long-lived, actively used codebase.
• Work closely with Product, Design, QA, Community, and Backend to turn ambiguous problems into shipped features.
• Improve build, packaging, and release tooling for the whole team.