SpotMe - Senior Product Manager - Life Sciences Meetings Management (Europe/US - Remote)

Remote (Europe/US) - Hybrid3w ago

In Office Senior EMEA Life Sciences Software Senior Product Manager Claude Technical Writing Salesforce CAIA Close

Requirements

• Life-sciences meetings, compliance, or transparency operations. You have built or operated workflows spanning approval, budgeting, ToV, and closure, and you know what EFPIA and Sunshine disclosure mean in practice. • Life-sciences meetings, compliance, or transparency operations. • HCP data and integration fluency. Identity across Veeva, Salesforce, OneKey, and NPI; match rates; what a data team expects from a write-back. • HCP data and integration fluency. • Domain-to-product translation. A messy operating process becomes states, rules, configuration, permissions, and audit events, with regulation separated from customer policy. • Domain-to-product translation. • Sequencing. The smallest production slice that proves the model without hiding the hard architectural or compliance question. • Sequencing. • Bias to execute. You ship, prototype, and put things in front of users in days, not spend weeks describing the problem. You drive decisions to a close and pull others along. • Bias to execute. • Precise writing and direct communication. Specs detailed enough to build and review, plain words, disagreement in the open. • Precise writing and direct communication. • Technical and AI fluency. You work in Claude Code or OpenAI Codex, you understand code, data flows, and architecture well enough to challenge an engineering design. You know the software development lifecycle deeply, from RFC and specification through review, release, and support. AI takes you from evidence to a testable artifact in hours. • Technical and AI fluency.

Responsibilities

• Take over the first customer’s move from their meeting request form to Onomi 360: spec, build, history migration, customer session. • Get set up with AI-based toolkit and the Onomi 360 codebase, and use both in your daily work. • Meet the early access customers (design partners) for Onomi 360. • The first customer live on meeting request and approvals in Onomi 360, measured against their baseline. • The roadmap priorities for the next two quarters defined, and the first priorities specified to build depth with engineering. • A clean separation everyone uses: aspirational (slides), forward-looking (prototype-based demo), and committed (roadmap and backlog). • The full end-to-end MeetingsEQ product specified and engineering-reviewed, request through approval, budget, HCP registration, ToV, and reporting. • One customer replacing Excel with the Onomi 360 ToV module, and the first live account expanded from request and approval into budget, ToV, or venue sourcing. • One customer closing a full ToV reporting cycle in Onomi 360 instead of Excel. • Three accounts running request to closure in production, and the org-wide calendar or HCP engagement view used outside compliance. • Onomi 360 winning the meetings-management scope in RFPs.