Data Solutions Architect | AI

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "Actual salary will be based on a variety of factors... Estimated Pay Range: $160,000 USD - $180,000 USD". So Pay section exists. Benefits: "The Perks" includes comprehensive medical, dental, vision, 401(k), etc. So Benefits section exists. Schedule: Not mentioned. So we should not include Schedule. Also we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Skills" could be derived from qualifications? The posting includes "Required Qualifications" and "Preferred Qualifications". Could treat "Requirements" as required qualifications, "Qualifications" as preferred? Or we could combine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content. We have "About the role": The description of what you'll do, includes many paragraphs. So we can put that under About the role. Responsibilities: Could be the bullet list of duties under "What You'll Do". That includes many responsibilities. So we can put that under Responsibilities. Requirements: Could be the "Required Qualifications". So we put that under Requirements. Qualifications: Could be the "Preferred Qualifications". So we put that under Qualifications. Skills: Could be derived from required qualifications like proficiency in Python, etc. But we might not need a separate Skills section if content overlaps. However we could still include Skills if we have specific skill list. The posting includes proficiency in Python and at least one additional language, hands-on experience with cloud data platforms, working knowledge of modern AI architectures, outstanding communication, etc. Those could be considered skills. But we already have them in Required Qualifications. To avoid duplication, maybe we skip Skills section. The instruction: prefer a few substantive sections over many thin ones. So we could combine Required and Preferred into Requirements and Qualifications. Skills maybe not needed. Benefits: The Perks section. Pay: Estimated Pay Range. We must not include Schedule. We must remove boilerplate: The initial "Who is Trace3?" etc includes marketing fluff about company. That is not part of job posting? It's part of the posting but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview may be considered part of the posting but not necessarily boilerplate. However it's not about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company overview? It's part of the posting but not about the role. The heading "About the role" could include that overview? Usually "About the role" is about the role, not company. But we could include a brief company description under About the role? Might be okay. However the instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The company overview is not metadata; it's substantive info about the employer. Should we keep it? Probably yes, as it's part of the posting. But we need to place it somewhere. Could be under About the role as a preamble. Or we could create a separate section like "About Trace3" but not in allowed headings. Since only allowed headings are those listed, we should fit it into one of those sections. Probably "About the role" can include both role description and company overview. But the instruction says "About the role" is a section heading example; we can use it for role description. Might be okay to include company overview there as well. We need to output only HTML fragment, no /. Use

for headings,

• for lists,

  for prose. We need to preserve all substantive information: that includes the list of responsibilities under "What You'll Do". We need to convert that into a list (

  • ). Also the "Required Qualifications" and "Preferred Qualifications" as lists. Also "The Perks" as list. Also pay range as a paragraph. We must not include duplicated lines. Ensure we don't repeat. Let's extract content. First, company overview: "Who is Trace3?Trace3 is a leading Transformative IT Authority, providing unique technology solutions and consulting services to our clients. Equipped with elite engineering and dynamic innovation, we empower IT executives and their organizations to achieve competitive advantage through a process of Integrate, Automate, Innovate.Our culture at Trace3 embodies the spirit of a startup with the advantage of a scalable business. Employees can grow their career and have fun while doing it!Trace3 is headquartered in Irvine, California. We employ more than 1,200 people all over the United States. Our major field office locations include Denver, Indianapolis, Grand Rapids, Lexington, Los Angeles, Louisville, Texas, San Francisco. Ready to discover the possibilities that live in technology? Come Join Us!" Then there are some cultural traits: "Street-Smart - Thriving in Dynamic Times..." etc. Those are maybe part of company culture. Could be included in About the role or maybe omitted as boilerplate? It's not legal boilerplate; it's cultural description. Might be considered substantive. But we can include it under About the role as well. Then "What You’ll Do As a Data Solutions Architect, you will own the end-to-end lifecycle of technical proof work across the Data and Experiences BU." Then bullet-like paragraphs: "Pre-Sales and Client-Facing Technical Work", "AI Innovation and Capability Development", "Delivery Enablement", "Thought Leadership and Team Contribution". Each has multiple sentences. We need to turn each of these into list items? Could treat each bullet as a list item. Or we could keep prose. The instruction: Use
    • for any list of duties/requirements/benefits. So we should convert duties into list. Thus under Responsibilities (

      Responsibilities

      ) we will have
      • each duty. Let's list duties: - Pre-Sales and Client-Facing Technical Work: * design, build, and present client-facing proofs of concept (POCs) and proofs of value (POVs) that demonstrate Trace3’s technical differentiation. * These are live, configured, Trace3-branded environments built on the client’s data, workflows, integration points. * Own the scoping, architecture, build, and presentation of these assets. * Lead AI capability demonstrations across the BU’s core technology plays, including agentic AI architectures, retrieval-augmented generation (RAG) systems, multimodal AI pipelines, MLOps platforms, and AI-native data and analytics stacks. * Be the person in the room who can answer “can you show me that working?” with a yes – and then show it. * Partner with Practice Directors and field SAs during active sales pursuits to define POC success criteria, scope minimum viable architectures, and ensure that every proof of concept is designed to answer a specific technical question – not to impress, but to advance the deal. - AI Innovation and Capability Development: * Be a visible, opinionated AI forward thinker within the BU. * Track emerging AI capabilities across the vendor ecosystem, evaluate their relevance to Trace3’s client base, and translate that evaluation into actionable technical assets: working prototypes, architecture reference guides, and intake recommendations for the Accelerators build pipeline. * Build reusable AI accelerator assets – prompt libraries, agent frameworks, RAG pipeline templates, evaluation harnesses, and fine-tuning playbooks – that reduce the time required to stand up AI capabilities from scratch on client engagements. * Build these assets in collaboration with the TAMs, Practice Directors, and Delivery teams who will use them. * Drive the Accelerators group’s contribution to the Pre-Sales Intelligence Evaluation Suite (CXE, DPE, SPE, IFE) – a set of AI-powered research evaluations that give Trace3 sellers an informed, opinionated starting position before the first client meeting. * Build, test, and refine the agent prompts, research workflows, and output templates that make these evaluations repeatable and high-quality. - Delivery Enablement: * Build technical tooling that makes the Delivery Organization faster and more consistent. This includes configuration automation scripts that reduce platform stand-up time, automated UAT frameworks that catch issues early in the delivery lifecycle, and documentation automation pipelines that generate as-built artifacts as a byproduct of the delivery process rather than a manual effort at the end. * Serve as the technical escalation path for Practice Directors and SAs who encounter questions they cannot answer – new vendor capabilities, integration edge cases, regulatory requirements that affect architecture decisions. * Research, document, and communicate findings in a form that the requesting team can use immediately. - Thought Leadership and Team Contribution: * Contribute to the Accelerators group’s internal knowledge base, publishing technical briefs, architecture patterns, and lessons learned from every significant POC or accelerator build. * Mentor junior team members and contribute to the continuous development of the team’s collective capability. * Represent the Accelerators group in vendor technical briefings, partner advisory boards, and internal BU forums. We could break each bullet into separate
      • items, but maybe keep each major duty as a
      • containing multiple sentences. That's okay. Now Required Qualifications list: - Bachelor’s degree in computer science, engineering, mathematics, or a related field, or equivalent professional experience - 5 or more years of experience in solutions architecture, data architecture, or AI architecture with a track record of client-facing technical delivery - 3 or more years of hands-on experience building and deploying AI or machine learning solutions in production or near-production environments - Demonstrated experience designing and building POCs and POVs for enterprise clients, including scoping, architecture, build, and executive presentation - Proficiency in Python and at least one additional language (SQL, Scala, JavaScript, or R) - Hands-on experience with cloud data platforms (Snowflake, Databricks, or equivalent) and at least one major cloud provider (AWS, Azure, or GCP) - Working knowledge of modern AI architectures including large language models (LLMs), RAG systems, vector stores, knowledge graphs, and agentic frameworks - Outstanding communication and presentation skills with both technical and executive audiences, including the ability to present complex AI concepts to non-technical stakeholders - Strong organizational and time management skills with the ability to manage multiple concurrent POC and accelerator builds in a fast-moving environment Preferred Qualifications list: - Master’s degree in computer science, AI, machine learning, or a related field - Experience with MLOps platforms and practices (model versioning, monitoring, drift detection, retraining pipelines) - Experience with agentic AI frameworks (LangChain, LangGraph, AutoGen, CrewAI, or equivalent) - Experience with ETL and data pipeline architecture at scale (Apache Spark, Kafka, Flink, or equivalent) - Familiarity with CCaaS, UCaaS, or contact center AI platforms (Genesys, Five9, Cisco, or equivalent) - Relevant AI or cloud certifications (Azure AI Engineer, Google Cloud Professional ML Engineer, AWS Machine Learning Specialty, or equivalent) - Experience in a consulting or professional services environment where you have owned client-facing technical deliverables end-to-end - Experience building and maintaining demo environments or technical accelerator libraries for reuse across multiple engagements Now Benefits (The Perks): - Comprehensive medical, dental and vision plans for you and your dependents - 40