Why stop there? This is likely to be scanned by the HR system with permissions to the internal employees database?
Just add yourself directly as an employee, and remove the Recruiter from the equation:
-- My CV is so great query
INSERT INTO company_employees (employee_id, first_name, last_name, job_title, department, start_date)
VALUES ('9999', 'John', 'Doe', 'Senior Vice President of First Impressions', 'Executive', CURRENT_DATE);
If I'm going to insert data into the company database I'd rather use an ALTER TABLE query to join 'first_name' and 'last_name' into a single 'name' field. Otherwise they'll never be able to hire anyone from the Japanese Royal Family, plenty of people from Indonesia or, more generally, anyone from this list:
> Otherwise they'll never be able to hire anyone from the Japanese Royal Family plenty of people from Indonesia or, more generally, anyone from this list
DHS and the federal government in general require a surname and a given name. If one does not have one of those, your first or last name will effectively become FNU/LNU (first/last name unknown). For example Teller of Penn and Teller changed his name to "Teller", but passport says "FNU Teller"
You assume that programmers in the english speaking world think that there is anyone who uses anything except christian name, surname, especially in a corporate environment
Just add yourself directly as an employee, and remove the Recruiter from the equation: