[Hiring] Principal AI Platform Engineer @Iconma Portal

Role Description

Our client, a Digital Infrastructure company, is looking for a Principal AI Platform Engineer for their Remote location.

• The ISD team runs its delivery work through a shared library of Claude toolkits: pricing engines, deployment pipelines, dashboards, a reference architecture catalog, and an Obsidian knowledge base, all wired to Smartsheet and SharePoint and driven by six named Claude agents.
• We need someone to own that platform and make it usable by the whole team, not just the people who can read the code.
• Responsibilities include:
  • Keep it running and extend it.
  • SharePoint and Smartsheet integrations, the dashboards and reports the team publishes, the shared Python library underneath.
  • Take the toolkits off the context window.
  • Run it in GitHub, with the data kept out.
  • Open the knowledge base to the team.
• This is hands-on build work. The deliverable is working code and documentation someone can follow without asking.

Qualifications

• Toolkits: 9 registered toolkits plus a shared _platform library, ~200 Python files, ~62,000 lines, 33 skills, 6 named agents.
• Version control: None today. A 692 MB SharePoint folder synced to each person's Mac.
• Knowledge base: ISD Brain, an Obsidian vault of 926 markdown pages, 875 raw sources, 377 meeting summaries, 836 MB.
• Systems of record: Smartsheet for REQ tracking, price sheets and the backlog; SharePoint for the library and published outputs.
• Access model: Four roles already defined: owner, maintainer, operator, consumer. Writes to a system of record are gated on a human yes.
• Users: A small team. Most are not engineers and will never read the code.

Requirements

• Claude Code, at depth. You have built with it, not just used it.
• GitHub and CI. You have migrated an existing body of work into version control and kept its history and attribution intact.
• Python. Confident writing and testing pipelines with the standard library.
• Experience building with AI tools. Real delivery with agentic systems and RAG.
• Handling of confidential material. The toolkits carry customer pricing, deal content, partner terms and named-account detail.
• Respect for provenance. Everything this team publishes carries a number that someone will act on.
• Jira and Confluence. You manage a backlog and write design docs and runbooks that other people use.
• Translating technical work into business value. You can say what a pipeline or an agent is worth in terms they care about.
• Most of this work sits between someone else's domain knowledge and the code. You draw it out, work in the open, share a rough version early rather than a finished one late.
• A large share of the output is prose read by people with no engineering background. It has to be clear and concise.

Benefits

• Health Benefits
• Referral Program
• Excellent growth and advancement opportunities