Role and level
Send the title, seniority, reporting line, and whether architecture ownership is expected.
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.
These are the facts recruiters and hiring teams usually need before right-to-represent or a technical screen.
Send the title, seniority, reporting line, and whether architecture ownership is expected.
Share the client disclosure path, right-to-represent language, exclusivity window, and submission deadline.
Name remote, hybrid, onsite, travel, timezone, and location constraints before scheduling.
Provide the approved range or rate from the hiring side; exact personal posture can move privately.
Clarify W2, C2C, 1099, contract-to-hire, full-time, benefits, duration, and conversion expectations.
Point to the resume, proof receipt, video, or category path the hiring team wants reviewed first.
The form prepares a copyable email draft from role facts only. Exact sensitive details can move privately.
Copy the compact version when the hiring team already knows the role, level, and proof request.
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.