Pear VC
Founding AI Engineer - Manhattan Labs
About this role
Manhattan Labs is seeking a Founding AI Engineer to design and develop an AI-driven compliance platform tailored for community banks. This role entails building the core architecture and systems necessary for financial compliance and contributing to the transformation of regulatory processes through innovative technology.
What you'll do
- Design and build agentic systems for complex financial data
- Develop scalable backend services for document processing
- Manage productionization of AI systems, including evaluation pipelines
- Enhance platform security with authentication and monitoring features
- Establish CI/CD practices and incident response strategies
- Collaborate with the founding team on architecture and product direction
What they're looking for
- Proficiency in TypeScript and Python
- Experience with LLM integrations or RAG systems
- Document processing and entity extraction expertise
- Strong understanding of API design and relational databases
- Ability to debug across frontend and backend systems
- Experience in startup environments
Benefits
- Competitive salary and equity
- Generous employee benefits
- [Unknown]
- [Unknown]
- [Unknown]
- [Unknown]
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Pear VC
Pear VC invests in and supports AI-driven enterprise software companies building automation platforms, compliance systems, and specialized tools across industries like financial services, insurance, and software development. The portfolio companies are hiring founding and senior engineers to design core infrastructure, build AI systems, and develop scalable backend platforms alongside their leadership teams.
View all jobs at Pear VCLikely interview questions
- Walk us through a production LLM or RAG system you shipped end-to-end. What were the biggest challenges in moving from prototype to reliable product, and how did you handle accuracy/latency tradeoffs?
- Describe your experience with document processing pipelines (PDFs, OCR, messy real-world data). What tools did you use, and how did you handle extraction quality and validation?