Health Information Specialist I - Wyoming ( Temp + Remote)
Remote - United Statesfull time
Remote
senior
$200k–$240k
H1B: no
Datavant Health Information Specialist I at Datavant managing the operating model between security and engineering teams. Responsible for coordinating quarterly security planning cycles and ensuring accountability across teams.
Responsibilities
Own the quarterly security planning cycle end to end. Set and publish the calendar, adjust it quickly when engineering timelines shift, and manage carryover and close-out between quarters. Align the cycle with the audit and compliance calendar so teams know early when audit-driven work will land in their sprints.
Hold security leaders accountable throughout the cycle. Drive on-time submission of their engineering asks, and make sure each one arrives with what engineering needs to act on it: scope, owners, dates, and decisions. Make sure completed work is validated promptly, and escalate when commitments slip. Catch requests that arrive outside intake, and deconflict overlapping asks so engineering teams aren't asked for the same thing twice.
Design and run bi-weekly Scrum of Scrums sessions with engineering managers in each vertical. Define a format that ends every session with clear commitments, owners, and dates, and make the forum valuable enough that engineering managers want to attend. Track commitments against delivery, follow up directly on slips and absences, and escalate through vertical engineering leadership when needed.
Give leadership a clear, current view of security delivery. Maintain backlog structure in Jira, linked into company-wide roadmap structures. That way, readiness, commitments, progress, and risks can be reported by owner without manual reconstruction.
Convene and run working groups for upcoming security initiatives that need engineering input, so engineering helps shape what's asked of them before rollout. Drive each group to a decision and a documented outcome.
Continuously improve the cycle. Measure where it stalls, and fix the process, tooling, or incentives behind it rather than adding more process.
Qualification
A track record of owning a recurringStrong Jira (or equivalent) skillsClearWhat Helps You Stand Out
Required
A staff-level program manager to run the operating model between Datavant's security organization and Engineering. Security teams spanning compliance, IT assurance, identity and access management, security operations, and product security all need work from engineering and platform teams across every business vertical. This role owns the quarterly cycle that turns those needs into a planned, prioritized engineering backlog, and holds security leaders and engineering managers alike accountable for their timelines from intake through delivery.
Your focus is coordination and accountability: making sure the right inputs arrive on time, and that committed work lands on engineering teams, moves, and gets closed out. This isn't a check-the-box PMO role. We're looking for someone who builds a cycle that runs better every quarter, not someone who sends more reminders.
A track record of owning a recurring, cross-team planning or delivery cycle at organizational scale. You've run it through multiple iterations and made each one measurably better than the last.
Demonstrated ability to hold people accountable without formal authority, on both sides of a handoff, including leaders more senior than you. You're persistent and direct, comfortable escalating, and you keep relationships intact while doing it.
Experience bringing structure to a recurring forum or process that had lost focus. You've given a meeting a clear purpose, defined inputs and outputs, and made it something people showed up for because it was useful.
Experience coordinating work across a large number of teams and multiple business units at the same time, while keeping the details straight.
Fluency in how engineering teams plan and work: sprints, backlogs, capacity, and quarterly planning. Engineering managers see you as someone who makes their lives easier, not harder.
Strong Jira (or equivalent) skills, including workflows, issue hierarchies, JQL, and dashboards. You build the tracking and reporting yourself rather than waiting for someone else to.
Clear, concise written communication. You can write an ask that gets a usable answer the first time, and a status update a CISO can absorb in two minutes.
Comfort operating with little guidance across an enterprise-wide scope, including when deadlines compress and priorities compete.
The judgment to tell whether a stall is a process problem, a people problem, or a priority conflict that needs a leadership decision, and to handle each accordingly.
