Hiring contact

Send the role facts before RTR.

Use this page for recruiters, hiring managers, and interview teams evaluating Thomas Smith for software architecture, CAD platform, .NET, industrial systems, and engineering workflow leadership.

Recruiter checklist

Answer the first questions before the submission window closes.

These are the facts recruiters and hiring teams usually need before right-to-represent or a technical screen.

Before RTR

Role and level

Send the title, seniority, reporting line, and whether architecture ownership is expected.

Before RTR

Client and RTR

Share the client disclosure path, right-to-represent language, exclusivity window, and submission deadline.

Before RTR

Work model

Name remote, hybrid, onsite, travel, timezone, and location constraints before scheduling.

Before RTR

Compensation range

Provide the approved range or rate from the hiring side; exact personal posture can move privately.

Before RTR

Engagement shape

Clarify W2, C2C, 1099, contract-to-hire, full-time, benefits, duration, and conversion expectations.

Before RTR

Proof request

Point to the resume, proof receipt, video, or category path the hiring team wants reviewed first.

Guided hiring intake

Make the role-fit decision faster.

The form prepares a copyable email draft from role facts only. Exact sensitive details can move privately.

Guided intake

Build the first message around the decision.

This prepares an email draft from routing facts only. Name what should stay small before files, tools, AI options, or platform decisions expand.

cadg.opportunity_intake
Best for: senior .NET, CAD platforms, Autodesk systems, technical leadershipDecision signals: role level, architecture ownership, delivery context, interview path
Open email draft

Build the first message from shareable routing facts. Keep files, credentials, source material, private notes, compensation details, and named counterparties out of the first contact unless the proper private channel is already established.

Fast hiring payload

Use the short path when the role is already clear.

Copy the compact version when the hiring team already knows the role, level, and proof request.

Hiring

Review software leadership proof

Best for: Recruiters, hiring managers, and technical interviewers evaluating senior software leadership fit.

Use this path when the decision is role fit, interview readiness, resume proof, technical leadership, or architecture ownership.

Role title and level:Compensation range:Location and work model:Technical ownership expected:Interview timeline:Proof or resume detail you want reviewed first:

A serious first reply can confirm role fit or mismatch and point to the most relevant resume, proof, or walkthrough material.

Send role details, compensation posture, and interview timeline first. References or deeper proof can move later through the appropriate hiring channel.