Oscilar - Product Manager

• Full-stack AML product depth. You've shipped product across at least two of the five areas above - in production, with real users, under real regulatory scrutiny. You've sat in a room where an examiner asked a question about your system and understood exactly what was at stake. You know what a BSA officer worries about before an exam, and you build product that addresses it. • Full-stack AML product depth. • AML strategy knowledge. You understand how AML programs are designed and calibrated, not just executed. You know why scenario thresholds drift over time and how to fix it. You know the difference between a structuring typology and a layering typology and have an opinion on which detection approach fits each. You understand model drift, backtesting methodology, and what a model validation report covers. You can engage a Chief Compliance Officer on their AML program design and add something to the conversation - not just listen. • AML strategy knowledge. • Technical and data fluency. Your engineers trust your specs. You can read a data schema, write a query to validate a hypothesis, and spot when an ML model is being misapplied. You understand the explainability problem in AI-assisted compliance decisions - not as an abstract concern, but as a concrete product constraint - and you have a position on how to solve it. • Technical and data fluency. • Regulatory literacy. BSA, FinCEN, OFAC, FATF. You understand what examiners are looking for, what triggers an MRA, and how to build a defensible audit trail. You've worked in an environment where regulatory guidance was unclear, evolving, or in conflict with shipping speed - and you made the call anyway. • Regulatory literacy. • Bias toward speed. You use AI tools to move faster, test sooner, and learn earlier. You do in a week what takes a month elsewhere. • Bias toward speed. • What success looks like: • 30 days: You've run discovery with at least 5 AML/compliance buyers - BSA officers, heads of financial crimes, CCOs - and produced a written synthesis that surfaces at least one insight we didn't already have. You've reviewed our current AML product surface and identified the two biggest gaps relative to what buyers actually need. • 30 days: • 60 days: You've delivered one complete PRD - spec'd, reviewed by engineering and Jason, and ready to build. You have a clear point of view on the SAR narrative automation problem: what to build, what not to build, and why. You've pressure-tested it with at least two practitioners who aren't already sold on it. • 60 days: • 90 days: You're already the PM on calls with CCO prospects. You have a 12-month AML roadmap with clear prioritization rationale. And you've shipped at least one thing to production. • 90 days: