Sr Director of Integrations & Special Project

About the Role

Revelation Pharma operates a nationwide network of compounding pharmacies and continues to grow through acquisition. Integrations are not occasional side work; they are part of how the company operates. Much of that work touches patient data, so the standard has to reflect it. Our core values are Patient Centric, Passionate, and Relentless, and they apply here too.

Special Projects will own the cross-functional problems that sit between product engineering, IT, pharmacy operations, and other parts of the company. Sometimes the answer is to automate it, sometimes to buy it, sometimes to wire two systems together, and sometimes to tell people it isn’t worth doing. Most of the job is working out which, and being able to defend the call afterward.

Leadership is the first job. You’ll carve out a new Special Projects division within IT and turn a loose collection of cross-functional work into a function with clear priorities, standards, and ownership. The people assigned to Special Projects will report to you, including the AI Automation Engineer and Technical Business Analyst. The final size and mix of the division are not fixed. You’ll also pull in expertise from elsewhere in the company when the work calls for it.

You won’t spend most of your week writing code, but you do need to be able to. Your team should see you read their work, review it properly, and pick up a piece of it yourself when the situation calls for that. It’s how the standard actually gets set. Telling people what good looks like doesn’t get you there on its own.

A lot of the job comes down to deciding what “good enough to ship” means here and then holding the line on it. The answer changes depending on what the thing does and who it touches, which is what makes it hard. We handle patient data, so the floor is high. But not everything needs to be built like it’s going to the moon.

Why This Role Matters

We have made a large investment in a proprietary pharmacy management system. The product engineering team that builds it is dedicated to that product; it is not a pool of developers for side work. Special Projects exists because cross-functional problems still need an owner who can prove out whether a problem is real, then build it, integrate it, or find the company that already sells it. If something grows into a product capability, you’ll help move it to the product team.

As we grow through new sites and acquisitions, the number of systems that have to talk to each other grows with us. Getting that right is the difference between an acquisition that takes three months to absorb and one that takes a year.

What You’ll Own

Building and leading the division comes first. The rest of the work falls into three technical areas.

The Team

• Build and lead a team whose size and mix will change with the work. Everyone assigned to Special Projects reports to you. You’ll also work with people from other parts of the company on specific initiatives. Give each person clear ownership and help them get better at the work
• Set the standard for testing, review, documentation, and data quality, then adjust it per project. A one-off internal script and something that touches prescriptions don’t get the same treatment
• Give the team direction they can act on. Clear priorities, a view on what matters this quarter, and honest feedback when work isn’t there yet
• Decide how work and people move into and out of Special Projects. Make the handoffs explicit so nobody is half-committed to two priorities without a clear owner
• Define roles as the division grows, and hire when dedicated capacity is the right answer

Build, Buy, or Don’t

• Evaluate vendors, run pilots when they will answer a real question, and make a recommendation you can defend. You own the call either way
• Tell people when something isn’t worth doing, and explain why in a way that lands

Third-Party Integrations

• Own how the systems we run on connect to each other and to outside partners
• Get data out of systems you didn’t design and can’t change, and keep those connections running when the other side changes something without telling you
• Build security in from the start: dedicated service identities, least-privilege access, MFA, and structured logs that show exactly what ran and when. Much of this work touches PHI and must stand up to a HIPAA audit
• Turn one-off work into repeatable playbooks: per-system modules, documented processes, data quality checklists

Automation, Including AI

• Direct the team’s work automating pharmacy workflows: document understanding, data extraction, intelligent field mapping, and multi-step task execution
• Own the data extraction approach for pharmacy management systems (APIs, database exports, file drops, and agent-driven UI automation where nothing better exists)
• Use AI responsibly on messy data: map inconsistent legacy records to clean schemas, with enough validation and reconciliation that pharmacy teams can trust the result
• Require the evaluation and human-review loops that make AI automation safe in a pharmacy setting: confidence thresholds, exception queues, and audit trails for every automated action
• Set practical standards for how AI gets used across the business: which tools, what data can go where, and what a business-built app needs before it touches PHI. Some of those get rebuilt properly and some get shut down

What Success Looks Like

In your first year:

• Your direct reports have clear direction, know what they own, and are better at the work than when they started
• The division has clear boundaries: people know what belongs in Special Projects, who owns it, and when work moves back to another team
• There are practical standards in place for AI tools and business-built applications that involve PHI
• At least one meaningful AI-assisted pharmacy workflow is in production, with measurable operational impact
• Our first legacy-system extraction and integration work has been turned into repeatable modules and playbooks
• There’s a clear roadmap for the team, including which capabilities we should develop internally and which we should buy

What You Bring

• Experience building production systems that involve sensitive or regulated data. This is a firm requirement, because you will be deciding what can touch PHI and your work has to stand up to a HIPAA audit
• 10+ years in software with real production ownership, including time spent leading engineers and developing them. This is not a first management role
• You’ve raised the quality of a team’s work before, and you did it by holding yourself to that standard rather than by adding process
• You’ve over-built something, and you’ve under-built something, and you took different lessons from each. You can tell a perfectionist that something is finished, and tell a fast worker that something isn’t
• You’ve chosen vendors and can walk us through how you decided, including one you turned down and why. You’ve made a build-vs-buy call you’d still defend, and bonus if you’ve made one you got wrong and can talk about it
• You can read code, give a useful review, and take on a piece of the work when needed. You do not need to be the strongest engineer on the team, but you do need to know what good work looks like
• Comfortable in Python or TypeScript, and in SQL
• Experience getting data out of systems you didn’t design and can’t change
• Experience operating automation in production: observability, failure handling, deployment, and incident response
• Security-minded by default. You should be able to explain how you’d design automation that a customer’s IT team would approve
• A clear view on when AI is the right tool and when it isn’t, and on how to make probabilistic systems safe enough for regulated data
• You can work effectively with pharmacists and engineers, and translate between the two without talking down to either group
• Self-directed. You’ll get clear goals and a lot of autonomy, not a ticket queue

Nice to Have

• Healthcare or pharmacy data experience (PMS platforms, NCPDP, HL7/FHIR, Surescripts)
• HIPAA compliance experience on the engineering side (BAAs, audit logging, PHI handling)
• Hands-on experience building production systems on LLMs (Anthropic, OpenAI, or similar): agents, tool use, structured extraction, evals. Not just chat integrations
• Browser/UI automation experience (Playwright, Selenium, or computer-use agents) and comfort reverse-engineering legacy applications: undocumented schemas, flat-file exports, quirky Windows software
• Experience with OCR / document AI on scanned or semi-structured documents
• Windows systems administration background (services, Task Scheduler, event logs)
• You’ve developed people who came into technical work sideways instead of through a CS degree
• Experience in a private equity-backed, high-growth, or acquisition-driven healthcare organization

Who Thrives in This Role

This role is for someone who wants to build a function, not inherit one. The team will not have a fixed size or mix, but everyone assigned to Special Projects will report to you. You’ll also work with people across the company when a project needs their expertise. You’ll have a lot of say in how that model works and who joins the division. The work directly affects real pharmacies and the people who work in them. It is a senior role that still keeps you close to the work. If you want to set direction while other people do all the building, this isn’t the one.

Benefits

• Health care insurance (medical, dental, vision)
• Life insurance
• Supplemental insurance
• PTO
• 401(k) matching
• Sick leave

Logistics

Remote anywhere in the US. No travel required. We ask for at least four hours of daily overlap with Eastern Time.

Equal Opportunity

Revelation Pharma is an equal opportunity employer. We are committed to building a team that represents a variety of backgrounds, perspectives, and skills. Employment decisions are based on qualifications, merit, and business needs.