TSmithCode W2/software authority
Public-safe résumé company names support senior .NET, Autodesk, architecture, SDLC, data, integration, and engineering-systems evaluation.
Open routeResume authority · company, role, year, service proof
This page maps Thomas Smith's public-safe résumé company history from Essential Dental Care & Sapian R&D in Grand Prairie, Texas through CAD drafting, manufacturing systems, software architecture, Autodesk automation, and CAD Guardian consulting. Company names support credibility; private C2C opportunities stay private.
Four-lane authority rule
Public-safe résumé company names support senior .NET, Autodesk, architecture, SDLC, data, integration, and engineering-systems evaluation.
Open routePublic-safe company and role history supports CAD automation, quote/RFQ workflow, PDM/PLM, platform integration, and paid discovery buying decisions.
Open routeThe public timeline now extends before Fry Reglet through KinMetal, Fascinate, Interroll, Carson Tool & Mold, Essential Dental Care & Sapian R&D, and Nimiety Bio Company.
Open routeC2C company names and protected artifacts remain private unless specifically cleared. Public pages show capability patterns, not private opportunity names.
Open routePublic résumé authority records
Autodesk Developer / Architect · Software Architect / Platform Modernization
2025 contract context
Enterprise energy and infrastructure software context across C#/.NET, Autodesk automation, Inventor/BOM, Vault workflow, Revit/Navisworks context, UAT, and release readiness.
Current enterprise buyers need software operators who can connect internal platforms, engineering workflows, release gates, and stakeholder proof without turning every modernization effort into a rewrite.
Do not expose internal energy-utility workflows, private source, credentials, diagrams, ticket details, or customer-owned implementation artifacts publicly.
CAD Drafter · PLM-aware manufacturing operator
2024-2025 operating context
Frontline manufacturing drawing production across AutoCAD, SolidWorks, Windchill, Epicor, SugarCRM/CRM, Power BI, drawing packages, standards friction, and operator workflow evidence.
Manufacturing teams still need practical operators who understand CAD output, document control, ERP/CRM handoffs, and production-ready packages before automation is trusted.
Do not expose customer drawings, title blocks, part records, pricing, internal production files, screenshots, credentials, or protected workflow records publicly.
Senior Software Architect
2022-2023 resume-aligned context
Legacy .NET, WinForms/WebForms, internal business application architecture, SSO/IAM, licensing, security/compliance context, estimation, stakeholder communication, and delivery ownership.
Teams with trusted legacy applications need modernization that protects behavior, identity, security, and support ownership instead of forcing a blind rebuild.
Do not expose customer application names, source, security designs, licensing details, diagrams, credentials, or implementation artifacts publicly.
Lead IT Applications Developer / Senior IT Applications Developer
2021-2022 resume-aligned context
Industrial software context across data warehouse, ETL, APIs, CI/CD, reporting, Python, data ownership, source-to-consumer handoff, and operational visibility.
Industrial teams need data and integration owners who can connect reporting, source systems, validation, and API handoffs into supportable delivery paths.
Do not expose internal warehouse structure, source data, reports, credentials, diagrams, or customer-specific integration records publicly.
CAD Technical Manager / Operations Technology Specialist
2017-2021 operating context
Industrial manufacturing software and CAD operations context across 40+ internal tools, .NET, Blazor, WPF, WinForms, API surfaces, ERP-connected workflows, quote/RFQ logic, reporting, and production handoffs.
Manufacturers and architectural-product teams need operators who can translate quote, CAD, ERP, reporting, and production handoffs into governed tools without losing the realities of the shop floor.
Do not expose product records, quote logic, internal tools, pricing, customer data, source code, screenshots, or private workflow records publicly.
CAD Drafter / Designer
2016 resume-aligned early manufacturing context
Early metal-fabrication CAD and technical-business communication context, showing that the CAD Guardian lane was built from shop-facing drawing and manufacturing handoff work before later software automation roles.
Fabrication and manufacturing buyers still need CAD operators who understand that drawings are not just geometry; they are instructions, assumptions, tolerances, and communication paths for production teams.
Do not expose proprietary fabrication drawings, customer names, part geometry, shop methods, pricing, or internal production details publicly.
Junior CAD Designer
2016 resume-aligned design and fabrication context
Architectural, lighting, experiential, and fabrication documentation context across AutoCAD, Inventor, Mastercam, and design-support workflows.
Design-build and experiential teams need CAD documentation that can move from concept to fabrication without losing owner intent, material assumptions, or production constraints.
Do not expose customer concepts, fabrication drawings, shop files, installation details, proprietary models, or client-owned visuals publicly.
IT Administrator / CAD Drafter
2015-2016 resume-aligned manufacturing systems context
Manufacturing operations context across 2D/3D conveyor models, CAD drafting, local IT administration, onboarding/training, Windows Server troubleshooting, hardware support, vendor coordination, and Kaizen exposure.
Manufacturers need engineering workflow operators who can bridge CAD users, plant systems, IT support, vendors, and operational documentation instead of treating each function as a separate silo.
Do not expose plant security information, FOB/camera configuration, server details, vendor records, credentials, layouts, or protected operational procedures publicly.
CAD Drafter
2014-2015 resume-aligned tool and mold context
Tool-and-mold CAD drafting context, showing early exposure to manufacturing drawings, part interpretation, tooling documentation, and production handoff discipline.
Tooling and mold environments reward precise drawing interpretation, revision discipline, and clean handoff between design intent and production reality.
Do not expose customer tooling drawings, molds, part geometry, manufacturing process detail, customer identities, or internal files publicly.
CAD Technician / Technologist · Website, IT, and project support
2012-2014 Grand Prairie, TX early CAD/R&D context
Earliest CAD authority signal: dental-instrument product-development support, SolidWorks 2012 prototype creation, CAD library maintenance, manufacturer communication, OSHA/compliance awareness, IT support, website maintenance, data backup, and small-business project coordination.
Medical-device-adjacent and product-development teams need clear design outputs, revision discipline, vendor communication, and protected-data boundaries before any CAD or automation work becomes credible.
Do not expose patient information, clinical records, proprietary dental-instrument drawings, manufacturing vendors, protected health information, internal databases, or clinical-performance claims publicly.
CAD Technician / Material Consultant / Project Manager
2012-2013 Grand Prairie, TX early R&D context
Early R&D product workflow context using Pro-E Wildfire 5 and SolidWorks 2012, prototype support for gas-testing instruments, materials consultation, and small-team project coordination.
R&D buyers need practical CAD support that connects prototype assumptions, material constraints, documentation, and manufacturing handoff without leaking protected product knowledge.
Do not expose proprietary instrument concepts, product drawings, material formulas, test data, vendors, customer records, or protected research details publicly.
Private consulting boundary
CAD automation and engineering systems consulting support
Private review only
Not for public résumé company-name expansion. Keep C2C opportunity names, rates, SOW terms, private contacts, protected artifacts, and customer-owned detail out of public pages.
Public authority signal: The public authority signal should be the consulting capability pattern: platform parity, automation assessment, structured logs, validation outputs, scoped handoff, and protected evidence discipline.
Boundary: Do not publish C2C company names, SOWs, rates, private contacts, private client artifacts, implementation screenshots, credentials, or customer-owned documents without explicit written clearance.