Objectives - The problems you will solve

In your first month, you will:

• 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.

After 3 months, you will have:

• 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).

After 6 months, you will have:

• 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.

After 12 months, you will have:

• 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.

What you need to be great at

• 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.
• HCP data and integration fluency. Identity across Veeva, Salesforce, OneKey, and NPI; match rates; what a data team expects from a write-back.
• Domain-to-product translation. A messy operating process becomes states, rules, configuration, permissions, and audit events, with regulation separated from customer policy.
• Sequencing. The smallest production slice that proves the model without hiding the hard architectural or compliance question.
• 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.
• Precise writing and direct communication. Specs detailed enough to build and review, plain words, disagreement in the open.
• 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.

What we want to hear about

• Life-sciences meetings and transfer of value. Tell us about a meetings or transfer-of-value process you built or ran end to end, from request through approval, budget, HCP registration, and disclosure. Where did it break, and what did you change? This is the process Onomi 360 replaces, and we want someone who has lived it.
• From operating process to product. Tell us about a messy process you turned into a product: which rules you made fixed, which you made configurable, what you integrated, and what you left manual. That translation is the heart of this role.
• Shipping fast. Tell us about the last thing you shipped or prototyped within two weeks of first hearing the problem. What did you skip, and what did users do with it? Here you put working software in front of pharma design partners every few weeks, not slides.
• Building with AI. Tell us about something you built yourself with Claude Code or another AI tool that changed a product decision, and what it taught you about the code or the architecture underneath. AI-assisted development is how we build, and you will have real freedom to use it.

Fluent English (written and spoken). Remote, based in Europe or in the US Eastern or Central time zones, with about 10-20% travel to design partners and industry events.

SpotMe recruits, compensates, and promotes regardless of race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, parental status, or veteran status.