Time since we first saw it
Day 172
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
United States
Open 5 months, first seen by us 172 days agoLocation type: RemoteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Product & EngineeringFrom the employer’s posting
Will you now or in the future require visa sponsorship to work in the United States?From the employer’s application form
Background in software engineering with at least five years of experience, the last two spent building and operating production AI systems. Shipped agentic workflows, RAG pipelines, or LLM-powered applications to real users. Strong Python fundamentals across APIs and async systems, which is the foundation the AI work sits on. Comfortable picking the practical solution over the clever one.
5+ years software engineering; 2+ years building and shipping production agentic AI or RAG systems
Who You Are Background in software engineering with at least five years of experience, the last two spent building and operating production AI systems. Shipped agentic workflows, RAG pipelines, or LLM-powered applications to real users. Strong Python fundamentals across APIs and async systems, which is the foundation the AI work sits on. Comfortable picking the practical solution over the clever one. Fluent in LangChain, LangGraph, PydanticAI, or AutoGen, with hands-on experience with vector databases, retrieval evaluation, and observability tooling such as LangSmith, RAGAS, Arize, or Langfuse. Prior fintech or banking experience is a genuine advantage, not a checkbox.
• AI eval and observability tooling: LangSmith, RAGAS, DeepEval, Arize, Langfuse, or equivalent • REST APIs, async Python, microservices; Azure cloud experience preferred Strongly Preferred
• Fintech, banking, or regulated industry experience • Graph databases (Neo4j, ArangoDB, Dgraph) and MCP / connector architecture • Multi-agent or planner-based AI architectures
Titan builds AI software for banks: purpose-built small language models, a banking ontology, and AI bankers that financial institutions can trust.
In the employer’s words · Read in context · Company website ↗
Open 5 monthsWe first saw this posting 172 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 172
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
4 open jobs
Check the employer’s posting for the current role and application details.
Already applied? Track this application
Titan builds AI software for banks: purpose-built small language models, a banking ontology, and AI bankers that financial institutions can trust. Our models outperform general-purpose LLMs by 30 to 80 percent on banking tasks. We operate under the compliance, audit, and model-risk standards that banking requires.
Why This Role ExistsTitan is growing from a handful of live banking customers to thirty, then to hundreds. This role sits across the AI Toolbelt and Product Engineering lanes, owning the production AI systems that bank employees use every day — agent workflows, retrieval pipelines, and LLM integration layers. We bring a problem and expect a working solution.
What You Own• Agent orchestration frameworks for multi-step reasoning, tool use, and constraint-based problem solving across banking workflows
• RAG pipelines covering embedding generation, chunking, hybrid retrieval, and retrieval evaluation, calibrated for banking document types
• LLM integration layers connecting banking models, APIs, and knowledge bases into reliable, auditable inference workflows
• Evaluation infrastructure including behavioral contracts, regression baselines, and production observability for non-deterministic AI outputs
• Backend services and APIs powering client-facing AI products at bank-tier uptime requirements
Who You AreBackground in software engineering with at least five years of experience, the last two spent building and operating production AI systems. Shipped agentic workflows, RAG pipelines, or LLM-powered applications to real users. Strong Python fundamentals across APIs and async systems, which is the foundation the AI work sits on. Comfortable picking the practical solution over the clever one.
Fluent in LangChain, LangGraph, PydanticAI, or AutoGen, with hands-on experience with vector databases, retrieval evaluation, and observability tooling such as LangSmith, RAGAS, Arize, or Langfuse. Prior fintech or banking experience is a genuine advantage, not a checkbox.
Required Qualifications• 5+ years software engineering; 2+ years building and shipping production agentic AI or RAG systems
• Agent framework experience: LangChain, LangGraph, PydanticAI, AutoGen, or Semantic Kernel
• RAG stack proficiency: embedding models, vector DBs (Pinecone, Weaviate, Milvus, FAISS), hybrid search, retrieval evaluation
• LLM integration depth: tool calling, structured outputs, multi-step reasoning, behavioral regression testing
• AI eval and observability tooling: LangSmith, RAGAS, DeepEval, Arize, Langfuse, or equivalent
• REST APIs, async Python, microservices; Azure cloud experience preferred
Strongly Preferred• Fintech, banking, or regulated industry experience
• Graph databases (Neo4j, ArangoDB, Dgraph) and MCP / connector architecture
• Multi-agent or planner-based AI architectures
• Multi-tenant SaaS with auditability and compliance requirements
What Success Looks LikeWithin 90 days, ownership of at least one production AI workflow end to end with measurable improvements shipped to the retrieval or agent layer. Within six months, the go-to person on the team for hard agent and retrieval problems, operating independently from a high-level brief through to recommendation and implementation. At one year, a senior anchor on the AI engineering function with a track record of pulling others up and a credible path to leading other AI Engineers.
Compensation and Structure• Competitive base and meaningful equity.
• Remote (US). Occasional travel to client sites and team offsites.
New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
United States
• Agent orchestration frameworks for multi-step reasoning, tool use, and constraint-based problem solving across banking workflows • RAG pipelines covering embedding generation, chunking, hybrid retrieval, and retrieval evaluation, calibrated for banking document types • LLM integration layers connecting banking models, APIs, and knowledge bases into reliable, auditable inference workflows
• Agent framework experience: LangChain, LangGraph, PydanticAI, AutoGen, or Semantic Kernel • RAG stack proficiency: embedding models, vector DBs (Pinecone, Weaviate, Milvus, FAISS), hybrid search, retrieval evaluation • LLM integration depth: tool calling, structured outputs, multi-step reasoning, behavioral regression testing
More relevant text appears in the full description.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting