Welding Subject Matter Expert
Core
Technical authority on weld joint design, process, qualification, and inspection for copper, aluminum, and stainless-steel alloys, bridging engineering, quality, and operations.
Role type
Senior Subject Matter Expert (Welding)
Builds
Welding Procedure Specifications (WPS) and Procedure Qualification Records (PQR) compliant with ASME and AWS codes
Domain
Manufacturing / Welding Engineering
Deliverable
production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work -> physical/clinical work (Note: Corrected to 'physical/clinical work' based on schema options, but context is manufacturing. The schema options are fixed. Let's re-evaluate. The options are: production ML models | product features | dashboards & analysis | research | client delivery | infrastructure | physical/clinical work. None fit perfectly. 'Infrastructure' is closest for process/tooling, but 'physical/clinical' is for hands-on. Given the 'hands-on expertise' and 'fabrication hurdles', 'physical/clinical work' is the only option involving physical fabrication, even if the label is odd for industrial welding. However, looking at the instruction 'one of: ...', I must pick one. 'Infrastructure' usually means cloud/IT. 'Physical/clinical' is for doctors/nurses. This is a schema mismatch. I will select 'physical/clinical work' as it implies physical fabrication work in this specific constrained list, or 'infrastructure' if interpreted as process infrastructure. Let's look at the responsibilities: 'Recommend and implement improvements to welding sequences, fixtures, and tooling'. This is process improvement. 'Infrastructure' is the best fit among the limited options for non-software, non-physical-person work, but 'physical/clinical' is often used for 'hands-on'. Let's assume the schema intends 'physical/clinical' to cover 'physical fabrication'. I will use 'physical/clinical work' to denote the physical nature of the welding work.