Thomas M is a seasoned software engineer and cloud security specialist with 18 years of experience bridging low-level build systems, Apple platform tooling, and large-scale cybersecurity for public sector clients. At Google Cloud Security he fuses deep technical mastery in SecOps, threat intelligence, and AI-driven agentic capabilities to deliver mission-scale solutions for federal agencies, while continuing hands-on engineering work on Apple-related tooling at Google. His open-source contributions to high-profile Bazel projects (rules_apple, bazel, tulsi, rules_swift) and Google Objective-C client libraries show a strong focus on build automation, CI/CD, and pragmatic fixes that improve developer UX and error handling. Prior roles at Mandiant, FireEye, and Blue Coat reflect a track record of translating complex security requirements into deployable architectures and winning customer trust across pre- and post-sales cycles. A former Navy flight-deck leader, he brings disciplined operational instincts and rapid decision-making to high-pressure technical problems.
18 years of coding experience
15 years of employment as a software developer
BSEE BS Electronic Engineering Computer Science, BSEE BS Electronic Engineering Computer Science at Capitol Technology University
Contributions:21 releases, 54 reviews, 156 commits in 7 years 5 months
Contributions summary:Thomas primarily focused on updating and maintaining the build and testing infrastructure for the Google Toolbox for Mac project. Their contributions included modifying shell scripts for running unit tests, adding pragmas to suppress deprecation warnings, and improving code organization. The user made changes to support symlink invocation and relayed arguments to the GoogleTest testing framework, indicating a focus on enhancing the testing process. They also contributed to refactoring efforts to streamline the build and test process.
Contributions:2 reviews, 469 commits, 58 PRs in 5 years 3 months
Contributions summary:Thomas primarily focused on modifying the `tools/plisttool` and related files to improve plist variable substitutions. They ensured that info_plist_option substitutions did not contain variable references and threw errors for malformed variable references. Additionally, the user updated the entitlements handling to include the target the work was being done for, improving error messages, and added support for the product name and bundle name substitutions.
bazelplatformsrulesapplebazel-rules
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.
Request Free Trial
Thomas M - Rapid Innovation & Specialist (RIS) Team