Lead Software Architect — AI Platform Engineering

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified checked Jun 13, 2026

Salary

Not verified

401(k) match

Reported from DOL Form 5500 industry filing (not employer-specific)

Was this benefit information wrong? Tell us.

Market context

U.S. role benchmark (BLS OEWS)

$111,944 U.S. median for this role

Projected growth (BLS Employment Projections)

+13.7% - Much faster than average

Matched to SOC 15-1252 - Data and ML aggregate by role bucket.

Source: U.S. Bureau of Labor Statistics, OEWS, May 2024 and Employment Projections, 2024-2034.

Role

Role function

Data From the posting source

Seniority

Senior From the posting source

Schedule

Shift type

Not verified

Weekend work

Not verified

Company

Equity

Offered Verified - SEC 10-K source

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Lead Software Architect — AI Platform Engineering UNAVAILABLE, UNAVAILABLE, US Basic Qualifications Bachelor's degree in Engineering, plus a minimum of 10 years of relevant experience; or Master's degree in Engineering, plus a minimum of 8 years of relevant experience. Responsibilities for this Position What You'll Own The platform architecture. You will define the technical vision for the AI platform - its service boundaries, data flows, integration contracts, and deployment topology. This is hands-on architecture work, not from a whiteboard, but from working code and real operational feedback. The tech stack. You will select, evaluate, and when necessary replace the tools, frameworks, and services your team depends on. You own the technical direction and are expected to defend it with evidence, not authority. Production code. You will write code. You will review code. You will debug production systems at the point of failure. This is not a management role that occasionally looks at a pull request. Engineering culture. You will set the engineering standards for the platform team - CI/CD practices, testing expectations, observability requirements, operational toil automation, and documentation norms. You will model the standard, not just write it down. Production reliability. You own the operational health of the platform - SLOs, incident response, capacity planning, and the automation that keeps systems self-healing at 2 AM so your team doesn't have to. You treat production as a product, not an afterthought. Technical decisions across organizational bo

Read the full description at careers-gdms.icims.com. FewerJobs shows a preview and links to the original posting.