Role fit
Can he own senior/staff engineering software architecture?
Best aligned to .NET, Autodesk, MicroStation, SolidWorks, CAD automation, WPF desktop systems, SQL-backed workflows, and technical ownership across engineering teams.
Software Leadership Context
Baltimore to Enterprise.
Origin story, engineering philosophy, and judgment signals for software leadership teams evaluating Thomas Divine Smith II for senior, staff, principal, or solution architect roles.
Every software leadership page keeps one primary action visible: Discuss Leadership Fit. Resume and PDF stay secondary so recruiters can still move at their own pace.
TL;DR. This supporting page explains the engineering judgment behind the leadership resume for Thomas Divine Smith II. Hiring teams should use it with the resume, proof portfolio, video demonstrations, hiring brief, and contact path.
Senior hiring readout
Senior Hiring Readout
The short version for engineering leaders.
Thomas Divine Smith II is a senior/staff .NET and CAD platform software architect for teams that need Autodesk, MicroStation, SolidWorks, CAD automation, Vault and ACC workflows, WPF desktop systems, SQL integrations, and engineering workflow ownership in one operator.
Review resume
Domain depth
Will he understand the users behind the requirements?
Early industrial CAD drafting, manufacturing workflows, Autodesk exposure since 2006, and production automation work give the software judgment practical context.
Interview signal
What should a technical panel validate first?
Use the video proof and portfolio to evaluate API reasoning, modernization posture, CAD workflow fluency, and communication under real constraints.
Decision path
How should recruiters route the opportunity?
This is the software leadership path for Thomas Smith. CAD Guardian LLC remains the separate consulting path for buyers.
Hiring manager signal
Hiring Manager Signal
Read the story as evidence of operating judgment.
This software leadership page explains why the resume keeps pointing at the same pattern: hands-on builder, CAD-heavy domain fluency, business-case discipline, and production ownership across engineering workflows.
Builder Pattern
Built computers at 14, modified game physics, then carried that systems instinct into CAD and manufacturing.
Practical architecture taste: Thomas can reason from user workflow to implementation details.
CAD Platform Continuity
Introduced to Autodesk in 2006, then specialized across Inventor, AutoCAD, Vault, ACC/BIM 360, CAD APIs, and cross-platform CAD workflow patterns.
Strong fit when the role needs software judgment plus engineering-domain fluency.
Self-Education Pressure
Read 90 computer books after becoming a father and converted internal work into a validated $200K outsourcing signal.
Evidence of durable learning velocity, not resume-padding curiosity.
Business Translation
Moved from shop-floor Excel and estimating workflows to cloud systems, integrations, and production automation.
Useful for teams that need an architect who can communicate with engineering, IT, operations, and finance.
Origin metrics
90
Computer books read after becoming a father
$200K
PO that validated the self-taught path
2006
Year introduced to Autodesk platform
Journey
1
Age 14 — Baltimore, MD
Early Computing
Built computers from age 14. First introduction to programming was creating custom mods for Quake 3 — including console commands to alter game physics.
2
2006 — High School
STEM Foundation
Graduated Project Lead The Way STEM program. Introduced to the Autodesk platform — the foundation of a career-long specialization.
3
Grand Prairie, TX
First Engineering Role
First engineering job at Sapian R&D — dental research and development. Created the Sapian Root Remover Kit, which progressed from a napkin sketch to adoption by an NBA Trail Blazers team physician.
4
Hiram, GA
Corporate Introduction
First corporate role at Interroll — introduced to German engineering practices and enterprise-scale manufacturing workflows.
5
Turning Point
Self-Education Catalyst
Read 90 computer books after the birth of my first child — driven by the need to buy a home before ever having lived in one. A $200K purchase order for outsourced work I was already doing internally validated the path to mastery.
6
Architectural Manufacturing → Enterprise
Career Acceleration
48 applications for the architectural metals industry. 12% sales lift for a $40M/year company. From Excel spreadsheets to cloud-based systems — estimating, engineering, sales, and manufacturing.
Engineering philosophy
Core Philosophy
Build it once and make it relevant to each user type for immediate business impact and zero rework. Cross-platform, mobile-responsive development from day one.
On Over-Engineering
MVP first. Over-engineering is intellectually stimulating on your own time, but if you want to deliver value, you ship what matters and stack on it.
On Technical Debt
Technical debt must be eliminated aggressively. A backlog is hard enough to keep up with — you don't want brittle code compounding the problem.
Scoping Principles
MoSCoW, KISS, Pareto, and YAGNI — guided by the original business case straight from the customer.
On Motivation
Business impact over hard problems. Simplicity delights me — I take no pride in things being difficult.
On Leadership
Lead from behind and in front. Prefer teams for mentoring and learning, but innovate alone because bravery requires independence from fear-driven decisions.
Technical perspectives
Expert positions on CAD automation, .NET modernization, and enterprise systems.
Autodesk Vault — #1 Mistake
Companies either don't set up lifecycles properly or create redundant lifecycles. Vault governance requires disciplined lifecycle design from day one.
.NET Migration Strategy
Minimal change, phased feature introduction. Don't rewrite — migrate incrementally with production safety at every step.
When Code Becomes Legacy
Code becomes legacy when it becomes a security risk. Age alone doesn't make code legacy — vulnerability does.
CAD Automation Misconception
The biggest misconception is that all CAD platforms are the same under the hood. Each platform has fundamentally different API architectures and integration patterns.
Modernize vs. Replace
Modernize when there are security risks or cost/time savings opportunities exceeding 20%. Otherwise, stabilize and govern what exists.
WPF in 2026
Still critical in most enterprise desktop environments. MVVM architecture keeps it relevant for CAD-hosted plugins, internal tools, and industrial applications.
The person
Father of two — a 7-year-old son and an 8-year-old daughter. I play Roblox with my kids on weekends, with ambitions to build a game together.
Active in the Atlanta Tech Village community. CAD Guardian's mission: lending Autodesk, MicroStation, SolidWorks, CAD workflow, and .NET automation experience to people who want to be better contributors to society and their families.
Long-term vision: combine CAD platform domain expertise, real estate curiosity, and software systems that turn technical leverage into practical operating value.
“With software, you can do a lot with zero dollars.”
FAQ
Common background questions
FAQ
Thomas Divine Smith II is an Atlanta-based senior/staff .NET and CAD platform software architect specializing in Autodesk, MicroStation, SolidWorks-aware CAD automation, Autodesk Vault, Autodesk Construction Cloud, WPF, SQL, and enterprise workflow systems.
This page supports software leadership evaluation of Thomas Smith. CAD Guardian LLC is the separate consulting path for Autodesk, MicroStation, SolidWorks, CAD workflow, and .NET modernization buyers.
Hiring managers should see a builder with early hands-on computing roots, Autodesk exposure since 2006, self-taught depth, enterprise manufacturing experience, and a bias toward shipping business-critical systems without unnecessary complexity.
Senior hiring managers should evaluate Thomas Smith as a senior/staff .NET and CAD platform software architect for Autodesk, MicroStation, SolidWorks, CAD automation, Vault and ACC workflows, WPF desktop systems, SQL integrations, engineering workflow modernization, and technical ownership across business-critical systems.
Technical interview panels should review the leadership resume, proof portfolio, video proof, and hiring brief to evaluate API reasoning, Autodesk and CAD workflow fluency, modernization judgment, communication, and production ownership.
Want to work with someone who ships?
From napkin sketch to production. Architecture ownership AND delivery in the same hands.