Marketing AI Architect

Key Responsibilities

• AI-Native Tool Building
• Design, build, and ship internal tools, dashboards, and applications that eliminate manual work for Marketing, Creative, and Centralized Operations.
• Use AI development tools (Claude Code, OpenAI Codex) to prototype and build functional software at high velocity - turning natural-language intent into working systems.
• Maintain, harden, and extend the existing portfolio of internal tools already in use across the Brand & Creative organization.
• Create reusable, well-documented components and templates so tools are durable and maintainable, not one-off scripts.
• Shared Context & Multiplayer AI
• Move the organization from “single-player” to “multiplayer” AI by building shared context layers - centralized, version-controlled libraries of brand truths, voice guidelines, product specs, and competitive intelligence.
• Develop and maintain reusable AI Skills and Model Context Protocol (MCP) integrations synced to GitHub, so every teammate and agent works from the same governed source of truth.
• Reduce hallucinations and inconsistency by ensuring content generated across teams pulls from the same live, accurate context.
• AI Visibility - GEO / AEO (Signature Responsibility)
• Own “Make the Invisible Visible” (MTIV): ensure Hillpointe and Pointe Grand are cited and recommended inside LLM responses, not just ranked in traditional search.
• Practice Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO): structure content and data so AI models can crawl, parse, understand, and cite it accurately.
• Track AI citations, bot/crawler traffic, and brand sentiment across the sources models trust most (Reddit, YouTube, review sites, PR, technical documentation).
• Guard citation accuracy - build fact-check systems so AI models never surface incorrect pricing, availability, or brand facts. Visibility with bad data is a reputational liability, not a win.
• Audit for technical crawlability: flag JavaScript-heavy widgets and other patterns that make our content invisible to AI agents.
• Automation & Integrations
• Take an API-first approach to breaking down data silos - replace hours of manual export/import work with code-driven syncing.
• Build custom AI agents for specialized, recurring tasks (research, monitoring, reporting, asset generation).
• Build integrations that connect marketing, leasing, and operational systems so data flows automatically instead of by hand.
• Generate personalized creative at scale (e.g., high-volume, per-audience ad and asset variations) using AI and design-tool integrations.
• Deployment & Distribution
• Get tools into teammates’ hands efficiently and repeatedly - own the path from working prototype to something the team actually uses.
• Use CLI and GitHub fluently to version, deploy, and maintain tools across the organization.
• Document and onboard teammates so tools are adopted, not shelved.
• Product Collaboration & Marketer Taste
• Interpret the goals and needs of marketing team members and translate them into tools that fully realize those needs.
• Apply judgment before automating: does this match our brand voice, add real value, and solve a genuine “hair-on-fire” problem - or is it noise for the sake of automation?
• Partner directly with Marketing, Creative, and Centralized Operations leadership to prioritize the highest-impact builds.

Qualifications

• A marketing, creative, growth, or brand background - you understand marketers because you have been one.
• A portfolio of tools, agents, automations, or apps you have personally built and shipped (personal projects count - we want to see what you build when no one tells you to).
• Deep, hands-on capability with AI development tools such as Claude Code and/or OpenAI Codex.
• Comfortable and fluent with the command line (CLI) and GitHub.
• Ability to deploy tools to a team and drive real adoption - not just build in isolation.
• “Marketer taste”: the judgment to know what NOT to build, and when AI output is off-brand or low-quality.
• Relentless curiosity - you keep up with new models and capabilities as a matter of habit.
• Ability to own projects independently while collaborating across teams.