Role fit
Senior, staff, principal, solution architect, platform architect, CAD platform architect, and Autodesk solutions architect roles.
Leadership Proof Portfolio
Leadership evidence for Thomas Divine Smith II: enterprise engagements, AutoLISP and AutoCAD automation relevance, flagship Autodesk builds, architectural manufacturing software, manufacturing CAD and product-data systems experience, video-backed technical depth, and measurable results across CAD, .NET, SQL, and engineering workflows.
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 proof page gives hiring teams the evidence layer behind the leadership resume: measurable enterprise outcomes, flagship Autodesk builds, architectural manufacturing software, manufacturing CAD/product-data systems experience, and recorded technical work that can be reviewed before a fit call.
Explore Proof
Hiring answer
Thomas Divine Smith II is a senior/staff .NET and CAD platform software architect in Atlanta, GA. The leadership proof portfolio shows Autodesk/MicroStation/SolidWorks-aware role fit through shipped systems, measurable operating outcomes, and public technical evidence before a hiring screen.
Role fit
Senior, staff, principal, solution architect, platform architect, CAD platform architect, and Autodesk solutions architect roles.
Proof base
Enterprise systems, flagship Autodesk builds, public video demos, leadership resume, and recruiter forwarding brief.
Operating evidence
$2M+ measurable value, 24% Autodesk cost reduction, up to 75% drawing throughput gains, and 15+ systems shipped.
Next action
Open a leadership fit conversation with role scope, compensation range, location posture, and interview timeline.
Recruiter keyword proof
Recruiter keyword proof
For contract or software leadership screens like AutoLISP, AutoCAD customization, structured data to CAD, legacy drawing standardization, and drafter-ready outputs, this page gives the proof path before the first call.
AutoLISP / AutoCAD
Relevant where legacy AutoLISP routines, AutoCAD customization, blocks, attributes, standards, or drawing-update workflows need senior engineering judgment.
C#/.NET bridge
Strongest when scripting-era CAD automation needs API boundaries, validation, packaging, logging, and maintainable .NET architecture.
Structured inputs
Fit for workflows that turn engineering data, product metadata, or request intake into drafter-ready drawing creation and updates.
Legacy standardization
Useful for teams modernizing older CAD drawings, drafting conventions, templates, and review loops without losing production control.
Recruiter evidence
Recruiter Evidence
This is the software leadership proof layer for Thomas Divine Smith II. It gives recruiters and hiring managers the claim, evidence, and next artifact in one scan instead of making them reconstruct the story from separate pages.
Role fit
Senior/staff .NET and CAD platform architecture across engineering, manufacturing, and construction workflows.
Resume and hiring brief →
Measurable impact
24% Autodesk licensing reduction, up to 75% drawing throughput gain, and $2M+ measurable operating value.
Flagship outcomes →
Technical depth
AutoLISP, AutoCAD, C#/.NET CAD automation, Inventor, Vault, ACC/BIM 360, MicroStation, SolidWorks-aware workflows, WPF, SQL, ERP, and production integration ownership.
Video proof library →
Manufacturing CAD systems
Delivered manufacturing CAD and data automation across modular belting drawing requests, SolidWorks/AutoCAD/DraftSight workflows, SugarCRM request intake, Epicor product-data context, drawing-number logic, drawing finder/search workflows, PTC Windchill/PDM readiness, Power BI-style reporting, and C#/.NET productivity tooling.
CAD Guardian proof →
Architectural manufacturing software
Built and maintained a multi-module .NET/VB desktop engineering suite touching Inventor API document, part, assembly, drawing, parameter, iProperty, BOM, Pack-and-Go, PDF, DXF, CAD configurator, Excel quote/BOM, label/barcode, RFQ/job-folder, lifecycle/status, labor allocation, and deployment packaging workflows.
Consulting proof →
Hiring manager translation
Hiring manager translation
The CAD and manufacturing software evidence is not decoration. It gives interviewers concrete threads to test: API boundaries, data quality, product rules, handoff risk, deployment packaging, and how Thomas turns manual engineering work into governed .NET systems.
Evidence 01
Inventor API parameter, iProperty, drawing, BOM, PDF, DXF, and Pack-and-Go automation.
Proves
Can own CAD platform automation below the surface-level plugin demo.
Interview angle
Ask about API boundaries, failure modes, and how manual CAD handoffs become safe repeatable workflows.
Evidence 02
CAD configurators, quote/RFQ, BOM, Excel, label, folder, lifecycle, and deployment tooling.
Proves
Understands engineering software as an operating system across estimating, engineering, production, and IT.
Interview angle
Ask how he would separate product rules, CAD model logic, data access, and release packaging.
Evidence 03
Manufacturing CAD drafting queues, product metadata, PDM readiness, archive lookup, and shop-floor context.
Proves
Automation judgment is grounded in real drafting constraints rather than abstract SaaS assumptions.
Interview angle
Ask how he validates drawing inputs before automating outputs and downstream reporting.
Evidence 04
Public proof across Autodesk cost reduction, drawing throughput lift, shipped systems, and video demos.
Proves
Can move from architecture to delivery and leave measurable evidence behind.
Interview angle
Ask for the first 90-day plan for a CAD/.NET platform modernization role.
Architecture proof
Architectural Manufacturing Software + CAD Automation Experience
Thomas’s software background includes internal .NET/VB tooling for architectural manufacturing workflows: Autodesk Inventor API automation, CAD configurators, parameter and iProperty updates, Pack-and-Go, automated drawings, PDF shop packs, DXF exports, BOM extraction/classification, Excel quote/BOM workflows, label and barcode generation, RFQ/job-folder tooling, engineering queue/status surfaces, lifecycle modules, and deployment packaging. That experience helps him design engineering software that respects both the CAD model and the business process around it.
CAD Guardian helps manufacturers modernize the space between CAD models, product configuration, quote/RFQ data, BOMs, drawing packages, PDFs, DXFs, labels/barcodes, project folders, lifecycle status, desktop deployment, and production handoff. Thomas’s prior architectural manufacturing software work gives him practical context for building automation that serves engineering, estimating, operations, production, IT, and deployment together.
Source-review boundary
The approved software folder was reviewed for project structure, dependency references, safe class and method names, and API usage surfaces. Public claims stay at sanitized capability level: no source code, CAD resources, proprietary rules, formulas, internal paths, or customer/project identifiers are exposed.
Signal
22 C# projects, 2 VB projects, and 322 source files reviewed locally at taxonomy/API level
Signal
Uses Autodesk Inventor API concepts: documents, assemblies, parts, drawings, parameters, iProperties, BOM structures, Pack-and-Go, PDF export, DXF export, and drawing views
Signal
Private research artifacts show a one-application operating model with JSON load/save, customer/order/project context, lifecycle status, CAD intake, estimating, configurators, drawing automation, BOM merge, labels, and labor allocation reporting
Signal
Connects CAD automation to quote/RFQ, estimating, BOM, Excel, labels, project folders, lifecycle status, and production handoff
Signal
Frames manufacturing software around engineering, estimating, operations, deployment, and the manual steps automation should remove
Inventor + Excel API use
Problems automated
Algorithmic patterns
Manual work replaced
Open assemblies, drawings, and spreadsheets by hand
Guided workflow opens, updates, saves, exports, closes, and packages the right artifacts
Manually edit CAD parameters, suppress features, and update title-block data
Configurator-driven inputs update model parameters, iProperties, drawing views, and output metadata
Build BOM spreadsheets from visual inspection or copied model data
Model metadata feeds classified Excel outputs with review points for missing or ambiguous data
Export shop-pack PDFs, submittals, and DXFs one file at a time
Drawing/PDF/DXF routines compress repeated export, naming, and folder-handoff steps
Maintain labels, barcodes, page layouts, and workbook cleanup as fragile spreadsheet work
Excel automation creates print-ready labels and merge-ready BOM workbooks from structured tables
Support internal tools with unclear versions, feature exposure, and release workflow
Versioned desktop packaging, feature configuration, update checks, and user-reporting patterns improve supportability
Reusable pattern
Connect, open/update/save/close documents, set parameters/iProperties, control drawing updates, package CAD resources, and protect operator workflows.
Reusable pattern
Read assembly BOM views, classify parts, extract manufacturing metadata, populate Excel tables, merge workbooks, and flag missing data.
Reusable pattern
Generate or update drawing documents, sheets, drawing views, PDF submittals, shop packs, and governed DXF output paths.
Reusable pattern
Move from product rules and model parameters into quote/RFQ context, CAD packages, BOMs, labels, folders, and production handoff.
Reusable pattern
Turn product-line tables into print-ready box/part labels with page breaks, paper sizing, barcode assets, and PDF export.
Reusable pattern
Support app shell configuration, web-service boundaries, XML/JSON workflow state, feature toggles, queue/status modules, lifecycle views, user reporting, versioning, and release packaging.
01
Inventor model
02
Configurator
03
Quote/RFQ
04
BOM
05
Drawing/PDF/DXF
06
Labels
07
Handoff
Built
Inventor API helper library
Built
Excel automation helper library
Built
Pack-and-Go packaging helper
Built
Column cover configurator
Built
Door frame configurator
Built
BOM generator and BOM merger
Built
Drawing/PDF/DXF automation
Built
RFQ intake and quote folder automation
Built
Engineering CAD queue/status tooling
Built
RFQ/quote and job-folder tooling
Built
Label/barcode generator
Built
Lifecycle, order, customer, project, and labor allocation modules
Built
Requirements, MVP, workflow-status, and user-documentation artifacts for internal adoption
Built
Versioned desktop release/update tooling
Case-story angles
From fragile Inventor macros to a governed API automation layer
From hand-built BOM spreadsheets to model-driven Excel outputs with review flags
From repetitive drawing packages to automated PDF/DXF handoff
From product configurator rules to job-specific CAD packages and shop deliverables
From ad hoc labels and barcodes to print-ready production workbook automation
From isolated tools to a versioned internal engineering software suite
Manufacturing CAD
Manufacturing CAD + Product Data Systems Experience
Thomas’s recent manufacturing CAD background includes delivered drawing request automation, drawing-number logic, drawing finder/search workflows, ERP/product-data mapping, and production dashboard work across SolidWorks, AutoCAD, DraftSight, SugarCRM, Epicor, PTC Windchill, Power BI-style reporting, and C#/.NET productivity tooling. He also authored ERP/API/PDM/PLM integration strategy around the real flow from request intake to drawing output, revision review, production handoff, and operational reporting.
CAD Guardian helps engineering and manufacturing teams modernize the messy middle between CAD files, SolidWorks/AutoCAD/DraftSight workflows, CRM request intake, ERP product data, drawing requests, PDM/PLM systems, and shop-floor reporting. The work is grounded in delivered drafting-floor automation and integration strategy, not abstract software assumptions.
Recent source signal
Private local review covered completed-project queues, hundreds of CAD/drawing handoff artifacts, SolidWorks part/assembly/drawing files, CAD templates, documentation, macros, C#/.NET drawing-number and archive-search tooling traces, dashboard documentation, and ERP/API integration strategy artifacts.
Signal
Delivered drawing request automation, drawing-number logic, drawing finder/search workflows, ERP/product-data mapping, and production dashboard work from real manufacturing CAD queues
Signal
Improved drawing throughput from 8/day to 12-14/day and reduced clarification loops by 60% by cleaning up request intake and structured data handling
Signal
Connects SolidWorks parts, assemblies, drawings, templates, AutoCAD/DraftSight 2D workflows, SugarCRM intake, Epicor product-data context, PTC Windchill/PDM readiness, Power BI-style reporting, and C#/.NET tooling
Signal
Separates delivered tools from authored ERP/API/PDM/PLM integration strategy while keeping automation grounded in request intake, drawing output, revision review, shop-floor handoff, and operational reporting
01
CRM request intake
02
Drawing-number logic
03
SolidWorks/AutoCAD/DraftSight
04
ERP/product data
05
PDM/PLM readiness
06
Production dashboard
Recent SolidWorks evidence
Fast service angles
SolidWorks drawing and PDM readiness audit
Drawing request intake cleanup
Drawing-number and drawing-code logic review
CAD template and drawing standard review
ERP-to-CAD product data mapping
Product metadata normalization
Drawing archive/search starter
CAD-to-production handoff map
Production-floor productivity dashboard scope
ERP/API/PDM/PLM integration roadmap
SolidWorks/AutoCAD/DraftSight workflow modernization discovery
Industrial CAD foundation
Industrial CAD Foundation
Prior Interroll CAD drafting work with conveyor and material-handling drawing packages, including assembly drawings, fabrication details, BOM coordination, DXF outputs, and manufacturing handoff documentation before advancing into Autodesk, MicroStation, SolidWorks-aware, and .NET software architecture.
CAD automation is safer when the architect understands the production artifacts engineers, drafters, and fabrication teams depend on.
Private-source boundary
Private Interroll portfolio evidence was reviewed locally for capability themes only. Raw PDFs, DXFs, title blocks, part numbers, dimensions, customer names, and source drawings are not published.
Signal
Assembly drawings and detail/fabrication package awareness
Signal
BOM coordination, drawing metadata, and revision-pressure context
Signal
DXF outputs and manufacturing handoff documentation
Signal
Bridge from drafting constraints to CAD platform/.NET automation design
Interroll archive signal
1,000+ PDF drawing-package artifacts and 90+ DXF/fabrication outputs reviewed locally
Interroll archive signal
Evidence of carriers, conveyor modules, chutes, guarding, camera-tunnel, release, and handoff package patterns
Interroll archive signal
Dated package organization spanning pre-release, monthly work folders, PDF binders, and laser-output folders
Outcome metrics
15+
Enterprise systems architected and shipped
$2M+
Measurable value delivered to operations
10+
Years in .NET, Autodesk, and workflow systems
Flagship impact
Flagship impact
Hiring teams can scan scale, rescue work, and lifecycle ownership without relying on a static graphic.
Multi-module internal engineering software suite for architectural manufacturing
22+2
C# and VB project surface reviewed privately
322
Source files reviewed at taxonomy/API level
CAD→BOM
Inventor, Excel, labels, folders, and handoff
Rescued a failing high-profile infrastructure project
3yr
Engagement duration
50+
Drawings per shop pack
Pack
Model, drawing, BOM, and output handoff
End-to-end product lifecycle from RFI to shipping
RFI→Ship
Full lifecycle coverage
E2E
End-to-end automation
1
Unified pipeline
Hiring risk reduction
Hiring risk reduction
The pattern is consistent: Thomas owns ambiguous engineering software problems, turns them into governed systems, and leaves behind measurable operating improvements.
Governance
Vault lifecycle, category, security, and property controls reduced repeat issues by 60%.
Throughput
Structured drawing requests increased output from 8 drawings/day to 12-14 drawings/day.
Cost control
Autodesk token licensing model reduced licensing spend by 24% in 7 months.
Reliability
ERP modernization improved application performance by 18% and reduced defects by 20%.
Career proof
Autodesk Developer / Architect
Jul 2025 - Dec 2025
Remote
CAD Automation Developer
2024 - 2025
Suwanee, GA
Senior Software Architect
Sep 2022 - Mar 2023
Atlanta, GA
Senior IT Applications Developer
Dec 2021 - Jun 2022
Minneapolis, MN
Operations Technology Specialist
2017 - 2021
Alpharetta, GA
Flagship projects
Signature builds that demonstrate scale, rescue capability, and full-lifecycle delivery.
Multi-module internal engineering software suite for architectural manufacturing
Built and maintained internal .NET/VB engineering tools around Inventor API automation, CAD configurators, BOM extraction, drawing/PDF/DXF output, Excel quote/BOM workflows, labels, RFQ/job-folder tooling, lifecycle/status tracking, labor allocation reporting, web services, XML/JSON data flow, quote-to-cash visibility, governed master data, transaction states, Power BI-style analytics, and desktop release support.
22+2
C# and VB project surface reviewed privately
322
Source files reviewed at taxonomy/API level
CAD→BOM
Inventor, Excel, labels, folders, and handoff
Stack: .NET, VB, Autodesk Inventor API, Excel Interop, Squirrel packaging, NUnit
Rescued a failing high-profile infrastructure project
Created a column cover configurator pattern that automated model setup, assemblies, drawing packages, BOM handoff, naming/folder structure, and repeatable output generation over a multi-year architectural manufacturing engagement.
3yr
Engagement duration
50+
Drawings per shop pack
Pack
Model, drawing, BOM, and output handoff
Stack: Autodesk Inventor API, Pack-and-Go, Excel automation, .NET/VB
End-to-end product lifecycle from RFI to shipping
The most complex integration delivered — Autodesk API across the entire product lifecycle, connecting estimating, engineering, manufacturing, and shipping into a single automated pipeline.
RFI→Ship
Full lifecycle coverage
E2E
End-to-end automation
1
Unified pipeline
Stack: Autodesk Inventor API, Vault API, .NET, SQL Server, ERP Integration
Video evidence
28+ technical videos on the @tsmithcad YouTube channel — real Autodesk API work since 2017, long before AI-generated code.
Featured Content
Channel Impact
FAQ
FAQ
Thomas Divine Smith II is a senior/staff .NET and CAD platform software architect with public proof across Autodesk, MicroStation, SolidWorks-aware workflows, enterprise systems, CAD automation, governed integrations, and measurable operating outcomes including $2M+ value delivered, 24% Autodesk cost reduction, and up to 75% drawing throughput gains.
The strongest leadership fit is senior, staff, principal, solution architect, platform architect, CAD platform architect, or Autodesk solutions architect work where .NET, CAD automation, Autodesk, MicroStation, SolidWorks, enterprise integration, data governance, and production delivery ownership matter.
Recruiters should send the role title, compensation range, location posture, interview timeline, and why Autodesk, .NET, CAD automation, or enterprise workflow depth matters for the role.
Thomas Divine Smith II has hands-on industrial CAD drafting experience from prior Interroll conveyor and material-handling drawing-package work, including assembly drawings, fabrication details, DXF outputs, BOM coordination, and manufacturing handoff documentation. That drafting foundation supports his later work in Autodesk automation, MicroStation and SolidWorks-aware CAD workflow modernization, Vault/PDM governance, and .NET engineering systems. Interroll is referenced as prior work history only; no endorsement or source drawing publication is implied.
Thomas Divine Smith II combines senior .NET software architecture with recent manufacturing CAD and data automation ownership. His Habasit America background includes delivered work across modular belting drawing requests, SolidWorks/AutoCAD/DraftSight workflows, SugarCRM request intake, Epicor product-data context, drawing-number logic, drawing finder/search workflows, PTC Windchill/PDM readiness, Power BI-style production dashboards, and C#/.NET productivity tooling, plus authored ERP/API/PDM/PLM integration strategy. That gives his CAD automation and engineering systems work practical grounding in real drafting, revision, metadata, and shop-floor handoff problems.
Thomas Divine Smith II has experience with .NET/VB engineering workflow tooling for architectural manufacturing, including Autodesk Inventor API automation for parameters, iProperties, assemblies, drawings, PDFs, DXFs, and BOMs; Excel automation for quote and BOM outputs; CAD configurator tooling; label and barcode generation; RFQ/job-folder workflows; engineering queue/status surfaces; lifecycle tracking; and desktop deployment packaging. This background supports his work in CAD automation, engineering systems modernization, and CAD Guardian consulting.
Yes. Thomas Divine Smith II is strongest where AutoLISP or legacy AutoCAD automation intersects with AutoCAD customization, C#/.NET, structured engineering data, drawing standardization, and production CAD workflow modernization. His proof is especially relevant for teams automating drawing creation or updates from validated inputs while keeping outputs drafter-ready for review.
A hiring manager should evaluate Thomas Smith through API boundaries, data quality, product-rule separation, deployment packaging, and measurable handoff risk reduction. His software leadership proof connects Inventor API automation, CAD configurators, BOM/drawing/PDF/DXF workflows, Excel outputs, labels, manufacturing CAD context, and shipped .NET systems to interview-ready evidence.
Yes. The public software leadership proof page provides resume, metrics, case-pattern evidence, videos, and a hiring brief for initial evaluation. After role fit, compensation range, location posture, and interview timeline are clear, Thomas can coordinate appropriate next-step verification such as references, private technical walkthrough context, or NDA-safe supporting material without publishing confidential employer, client, drawing, source-code, or customer details.
Thomas Smith has public proof across enterprise software leadership engagements, flagship Autodesk builds, 15+ shipped systems, $2M+ in measured operating value, a 24% Autodesk cost reduction, and up to 75% drawing throughput gains.
The software leadership proof portfolio covers Autodesk Inventor, AutoCAD, Autodesk Vault, Autodesk Construction Cloud, BIM 360, MicroStation, SolidWorks-aware workflows, architectural manufacturing software, manufacturing CAD drafting, product data, PDM readiness, .NET, WPF, SQL Server, ERP integrations, CAD automation, governed data pipelines, and engineering workflows.
This page supports software leadership evaluation of Thomas Divine Smith II. CAD Guardian LLC is the separate consulting path for Autodesk, MicroStation, SolidWorks, CAD workflow, and .NET modernization buyers.
Hiring
Overview
15+ enterprise systems shipped. Architecture ownership AND production delivery in the same hands.