Principal AI Engineer

Randstad Digital Americas · Latonia Lakes, KY · 1 mo ago

Engineering$85–$86/hrContract

We need to output HTML fragment with sections for headings that have content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: Job Summary (maybe "About the role"?). There's a location, job type, salary, work hours, education. We need to decide which sections to include. We have: - Job Summary: description of background etc. Could map to "About the role". We'll include that. - Responsibilities: present. - Qualifications: present (Bachelor's degree or equivalent experience etc.) - Skills: present (list of many skills). Could be a Skills section. - Benefits: posting mentions "Randstad Digital offers a comprehensive benefits package, including: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's specific benefits. So include Benefits. - Pay: posting includes salary: $85 - 86 per hour. Also "Pay offered to a successful candidate will be based on several factors ..." but we have specific hourly rate. So include Pay. - Schedule: work hours: 8am to 5pm. So include Schedule. - Possibly also "Requirements" but we have Qualifications; maybe we can combine. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if distinct. The posting has "Qualifications" section with bullet-like text. It also has "education: Bachelors". Might treat that as Qualifications. Could also have Requirements (maybe the experience etc). But we can just use Qualifications for that content. Avoid duplicate/thin sections. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, accommodation, etc. Also remove "Equal Opportunity Employer:" lines, accommodation line, "This posting is open for thirty (30) days." Also remove "location: Covington, Kentucky job type: Contract salary: $85 - 86 per hour work hours: 8am to 5pm education: Bachelors" maybe we need to keep location? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location, job type, etc are minor metadata; we could fold into a short
maybe under About the role? Or we could drop them. But we need to preserve ALL substantive information; location, job type, salary, work hours, education are substantive? The instruction says we should include Pay and Schedule sections if posting actually states them. So we need to keep salary and work hours. Location and job type maybe minor; we could include them in a short paragraph under About the role or maybe drop? The instruction: "fold minor metadata into a short
or drop it." So we can include a short
with location, job type, education maybe. But we already have education in Qualifications? Actually Qualifications includes Bachelor's degree or equivalent experience etc. So education is covered there. So we could drop location and job type as minor metadata, or include them in a short paragraph. We need to preserve ALL substantive information; location might be substantive but maybe considered minor. I'd include a short
under About the role: "Location: Covington, Kentucky | Job type: Contract". That preserves. Now we need to output HTML fragment only, no markdown fences. Let's craft:

About the role

Location: Covington, Kentucky | Job type: Contract

Strong full-stack engineering background with modern languages and frameworks such as Python, TypeScript, Node.js, APIs, React, and Next.js. Hands-on experience deploying and scaling applications within cloud environments such as AWS, Azure, or Google Cloud. Experience with modern platform engineering and DevOps practices, including containers, Kubernetes, Infrastructure-as-Code, and cloud-native architectures. Strong understanding of software architecture, design patterns, security, and reliability principles for enterprise-scale applications. Excellent problem-solving skills, sound technical judgment, and a passion for building innovative solutions. Ability to collaborate effectively across engineering, data, product, and business teams while driving initiatives from concept to production.

Responsibilities

As an early member of this organization, you will play a key role in shaping technical direction, influencing engineering best practices, and delivering AI-powered solutions from concept through production.
Work directly with business leaders, product teams, architects, data scientists, and engineers to identify high-value use cases and build secure, scalable, enterprise-grade AI capabilities that drive measurable business outcomes.
Translate emerging AI capabilities into practical applications.
Example use cases include developing AI-powered capabilities that improve advisor effectiveness and client engagement, such as:

Automated meeting preparation and research
Intelligent call summarization and insight generation
Automated follow-up and workflow orchestration
Knowledge retrieval and recommendation systems
AI-assisted decision support and productivity tools
Workflow automation leveraging enterprise data sources and communication channels

But note nested

is okay but maybe better to have separate

Principal AI Engineer

About the role

Responsibilities

Responsibilities

Qualifications

Skills

Benefits

Pay

Schedule

Similar jobs