> Markdown version of [/jobs/ext/1318631-principal-software-engineer-debug-tools](https://www.wearedevelopers.com/jobs/ext/1318631-principal-software-engineer-debug-tools). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Principal Software Engineer, Debug Tools - **Company:** Ampere Computing - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $237,000.0 - $338,500.0 - **Contract:** Permanent contract - **Skills:** Application Notes, ARM Architecture, Bash Shell, C++ (Programming Language), Computer Programming, Computer Engineering, Data Centers, Software Debugging, Software Design Documents, Linux, Emulators, Firmware, Revision Control Systems, Hardware Design, Joint Test Action (IEEE Standards), Python (Programming Language), Open Source Technology, Software Architecture, Software Engineering, System Software, 64bit, Git, Perf (Linux), Information Technology, Trace32, Powerview - **Published:** July 17, 2026 - **Apply:** https://www.dice.com/job-detail/37e1f032-3b8e-4001-83b6-67bd995f5930 ## About the Role * Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, or Software Engineering or related technical field & 12 years of related experience; or MS degree & 8 years; or PhD & 5 years * Proficiency with Arm architecture and ecosystem, including Armv8-a/v9-a and Armv7-m processor architectures, Arm Debug Interface Architecture, Arm CoreSight Architecture, Arm AMBA APB, AXI, AHB, and CHI protocols. * Proficiency in C/C++, Python, and Bash programming. * Experience using Arm Development Studio, TRACE32 PowerView, OpenOCD, and GDB debuggers. * Experience with instruction trace, bus trace, scan dumps, array dumps, and crash capture. * Experience with version control tools such as git, and software best practices. * Strong analytical, debugging, and testing methodology skills. * Proven ability to own problems and drive them to a resolution. * Experience with system software debugging, tracing, and analysis tools, such as perf, ftrace, etc, is recommended. ## Description As a core member of the Ampere Debug Tools team, you will be responsible for the architecture, design, and development of Debug Tools solutions for the next generation of Ampere products. This role is distinguished by deep technical ownership, architecture leadership, and cross-team influence. The Debug Tools Team is part of the Ampere Software Team. Our mission is to develop a comprehensive debug strategy and roadmap for internal debug capabilities, as well as to develop and deploy debug solutions for all internal and external Ampere SoC users. * Internal users include Debug Tools software users from the Virtual Platform, Emulation, Platform, Design Validation (DV), Post-Silicon Validation, Design For Test (DFT), Firmware, Operating System, Software, Performance, and Application Engineering teams. * External users include partners, ODMs, OEMs, datacenter, edge and embedded customers. * Debug solutions include Arm Development Studio, TRACE32 PowerView, and OpenOCD debuggers, Arm Self-Hosted Trace for Linux, and utilities for invasive debug, bus trace, instruction trace, array dump, and scan dump. This role will be for the lead of the Arm Development Studio implementation. What You'll Achieve: * Architect, design, develop, and deploy software-based Debug Tools for custom 64-bit Armv9 SoC and other processors. * Invent new debug tools and techniques for future products and technologies. * Influence the architecture and design team decisions with knowledge of internal and external debug tools on Ampere SoCs. * Contribute to software architecture and design documents, application notes, and other software product documentation. * Develop tooling for advanced debugging techniques, such as instruction trace, bus trace, array dump, scan dump, and ATE bootstrapping. * Develop open source JTAG and self-hosted trace and debugger software for internal and external use in debugging Ampere microprocessors. * Develop Arm Development Studio, TRACE32, and OpenOCD utilities for internal and external use in debugging Ampere microprocessors. * Perform pre-silicon bring-up of debug software on software simulators and hardware emulation platforms. * Collaborate with hardware design, architecture, post-silicon validation, and platform AE teams, as necessary, to resolve critical customer issues. ## Related Videos - [Passive ARM Assembly Skills for Debugging, Optimization (and Hacking)](https://www.wearedevelopers.com/videos/1083-passive-arm-assembly-skills-for-debugging-optimization-and-hacking) - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Unleashing the Full Potential of the Arm Architecture – Write Once, Deploy Anywhere](https://www.wearedevelopers.com/videos/940-unleashing-the-full-potential-of-the-arm-architecture-write-once-deploy-anywhere) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) ## Related Articles - [AI-Powered Debugging: The Future of Fixing Your Code](https://www.wearedevelopers.com/magazine/553-ai-powered-debugging-the-future-of-fixing-your-code) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [The Best Software Developer Blogs to Read](https://www.wearedevelopers.com/magazine/156-the-best-software-developer-blogs-to-read) - [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries) - [Dev Digest 129 - Now that's what I call private data!](https://www.wearedevelopers.com/magazine/468-dev-digest-129-now-that-s-what-i-call-private-data)