Citi is seeking a Gen AI Solutions Product Architect to develop a modular, reusable Gen AI product suite that enables cross-functional teams to deploy AI solutions rapidly without deep business context.
Requirements
Hands-on experience with LLM integration (e.g., OpenAI, Anthropic, Llama 2) and frameworks (LangChain, LlamaIndex).
Expertise in RAG workflows: Document chunking (sentence transformers), vector DBs (Pinecone, FAISS), and hybrid search.
Familiarity with text-to-SQL systems, few-shot/chain-of-thought prompting, and traditional ML (clustering with scikit-learn, PyTorch).
Proficiency in Python, API design (FastAPI, Flask), and cloud platforms (AWS Sagemaker, Azure AI).
Experience with CI/CD, containerization (Docker), and infrastructure-as-code (Terraform).
Frontend integration (React/Streamlit for config UIs) and middleware (message queues, auth systems like R2D2).
Proven track record of building reusable ML/API products or internal platforms.
Responsibilities
Define the product vision and roadmap for reusable Gen AI modules (e.g., RAG, prompting frameworks, hybrid ML/LLM systems).
Architect parameterized, business-agnostic solutions that abstract complexity (e.g., pre-configured prompts, vector DB connectors, chunking logic).
Design APIs and microservices to expose modules as reusable components (e.g., “text-to-SQL service,” “RAG-as-a-service”).
Standardize patterns (e.g., prompt templates, chunking strategies, few-shot training pipelines) across use cases.
Integrate LLM workflows (e.g., OpenAI, Claude) with traditional ML (clustering, classification) and enterprise systems (databases, UI tools).
Optimize performance of Gen AI components (cost, latency, accuracy) and ensure scalability (e.g., load balancing for vector DBs).
Build developer tools (SDKs, UI templates) to help teams self-serve (e.g., drag-and-drop prompt builders, vector DB configurators).
Other
Bachelor’s/University degree in Computer Science, Data Engineering, Cloud Computing, Technology or a related field, or equivalent experience
Strong communication to bridge technical and non-technical stakeholders.
Community-building skills to drive adoption and contributions.
Agile/Scrum methodology and tools (Jira, GitHub Issues).
Pragmatic problem-solving (e.g., balancing customization vs. standardization).
