AI Platform Engineer (Hybrid)

RTX · Cedar Rapids, IA · 1 mo ago

HybridFull-time

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive info. Let's parse content. First part: Date Posted, Country, Location, Position Role Type: Hybrid, U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person... etc. Security Clearance Type: None/Not Required, Security Clearance Status: Not Required. Then description: At RTX... The following position is to join our RTX Enterprise Services team: We are seeking an experienced AI Platform Engineer... Then "What You Will Do" list of duties. Then "What You Will Learn" list. Then "Qualifications You Must Have" list. Then "Qualifications We Prefer" list. Then "What We Offer" paragraph about benefits. Then "Work Location: This is a hybrid role..." includes schedule info? It mentions hybrid, eligible candidates must reside within commuting distance of various locations. Also "This position is classified as: Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader." That's schedule info. Then "The salary range for this role is 107,500 USD - 204,500 USD." That's pay. Then benefits details: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays." Also earlier "What We Offer" mentions parental leave, flexible work schedules, achievement awards, educational assistance and child/adult backup care. We need to include sections: About the role (maybe intro paragraph), Responsibilities (What You Will Do), Requirements (maybe U.S. Person requirement and security clearance?), Qualifications (must have and preferred?), Skills? Could combine qualifications and skills. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not create sections with filler. So we need to see if we have content for each. - About the role: we have introductory paragraph describing RTX and the role: "At RTX, the world's largest aerospace and defense company... The following position is to join our RTX Enterprise Services team: We are seeking an experienced AI Platform Engineer..." That's substantive. - Responsibilities: "What You Will Do" list. - Requirements: The U.S. Person requirement and security clearance (None/Not Required). Also maybe location/hybrid? But location maybe schedule. Requirements could include U.S. Person requirement. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements". We'll include that. - Qualifications: "Qualifications You Must Have" and "Qualifications We Prefer". Could combine into Qualifications section with two sublists? But we must use

for any list. Could have two lists under Qualifications heading: one for Must Have, one for Preferred. That's okay. - Skills: Could we extract skills from qualifications? Might be redundant. But we need to decide if we have specific skills content separate from qualifications. The qualifications include programming experience, cloud-native, observability, security concepts, etc. Those are skills. Could we create a Skills section summarizing those? However we must not invent or summarize away detail; we must preserve all substantive information. If we create a Skills section, we need to take content from somewhere else and not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid reorganizing, but we must not lose detail. If we move content from Qualifications to Skills, we still preserve it. But we need to avoid duplication? Not explicitly forbidden, but better to avoid duplication. Could keep Qualifications as is and not have Skills section if no distinct skills beyond qualifications. However the instruction says "Prefer a few substantive sections over many thin ones." So we could omit Skills if not needed. But we need to decide if we have content for Skills separate. The qualifications already cover skills. So we can omit Skills section. - Benefits: We have "What We Offer" paragraph and later benefits list. So we can include Benefits section. - Pay: Salary range. - Schedule: Hybrid work description. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Skills if no distinct content. Now we need to format. Use
for section headings. Use
- for any list of duties/requirements/benefits. Use
  for prose. We must not include markdown code fences. We must output only HTML fragment. Let's craft. First, About the role: combine the introductory paragraphs before "What You Will Do". That includes: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Join us and help shape the future of aerospace and defense. The following position is to join our RTX Enterprise Services team: We are seeking an experienced AI Platform Engineer to design, build, and operate the reusable software, services, infrastructure, and runtime capabilities that enable Artificial Intelligence and Machine Learning solutions to be developed, deployed, secured, observed, and scaled across RTX. The ideal candidate combines strong backend software engineering with cloud, DevOps, and AI platform experience. This is a hands-on engineering role focused on building production platform capabilities, not simply deploying infrastructure. You will work closely with AI Architects, Applied AI Engineers, application teams, cybersecurity, data, and enterprise technology organizations to provide secure and reusable capabilities that accelerate AI adoption across RTX." We can put that in
  . Now Responsibilities: "What You Will Do" list items. We'll extract each sentence as list item. List: - Design, develop, and operate scalable backend services, APIs, and distributed platform capabilities that support enterprise AI applications, models, and agents. - Build and integrate AI platform capabilities including model access and routing, AI gateways, agent runtimes, lifecycle management, tool integration, model serving, retrieval services, and related enterprise AI services. - Develop secure capabilities for agent and application identity, authentication and authorization, secrets management, tool access, permissions, and integration with enterprise systems. - Design and automate deployment across development, test, and production environments using cloud-native technologies, containers, Kubernetes, CI/CD, and infrastructure-as-code. - Build observability capabilities including logging, metrics, tracing, monitoring, alerting, execution telemetry, and cost visibility for AI applications and agentic workloads. - Develop platform capabilities supporting AI evaluation, model lifecycle management, MLOps, configuration, versioning, and production operations. - Design platform services for scalability, availability, resilience, performance, security, and support across commercial cloud, hybrid, on-premises, and restricted environments. - Partner with AI Architecture, Applied AI, Application Engineering, Cybersecurity, Data, and product teams to translate solution needs into reusable enterprise platform capabilities and continuously improve the developer experience. Now Requirements: U.S. Person requirement and security clearance. We have: "Position Role Type: Hybrid U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person. A U.S. Person is a lawful permanent resident as defined in 8 U.S.C. 1101(a)(20) or who is a protected individual as defined by 8 U.S.C. 1324b(a)(3). U.S. citizens, U.S. nationals, U.S. permanent residents, or individuals granted refugee or asylee status in the U.S. are considered U.S. persons. For a complete definition of “U.S. Person” go here. https://www.ecfr.gov/current/title-22/chapter-I/subchapter-M/part-120/subpart-C/section-120.62 Security Clearance Type: None/Not Required Security Clearance Status: Not Required" We need to preserve the link? Probably we can keep the URL as plain text. It's substantive. We'll include as maybe but not required. We'll just include the URL. We'll put in
  maybe with list? It's prose. We'll include the U.S. Person requirement paragraph and the security clearance statements. Now Qualifications: Must Have and Preferred. We'll create two

AI Platform Engineer (Hybrid)

Similar jobs