Working at Ankr Health: Culture, Pace and Who Thrives

The Collision That Drives the Engine

A medical oncologist who treated patients until early 2024 now runs a company that plugs into Epic, eClinicalWorks, and Athena from a laptop. The salaried team building those integrations sits in Houston, Minneapolis, Atlanta, and Bengaluru; no central office appears in any current posting. That collision — clinical urgency meeting distributed engineering — sets the operating rhythm at Ankr Health.

The company occupies an unusual intersection: a health-tech product that must satisfy hospital IT security reviews, physician workflow demands, and billing compliance, built on a median pay band of $90,000 across roles spanning three U.S. time zones and India. The geographic spread is not a "remote-friendly" policy layered on a headquarters. It is the structure.

Decision-making flows from Dr. Arpit Rao (also referred to as Dr. Ray Rao), the founder who treated cancer patients until six to seven months before a September 2022 YouTube interview. In that interview, he described the product's logic as an extension of his own evening problem: physicians drowning in after-hours messages, losing, according to the John C Lin, MD interview, roughly $100,000 per provider per year in unbillable time. The platform automates consent, interpreter bridging, scheduling, insurance verification, and drafts about 80 percent of a billable note, all triggered from inside the EHR. That clinical origin shapes prioritization. Features are framed around reimbursement codes and workflow elimination, not user engagement metrics.

The pace implied by the product demo is high-stakes and synchronous: a physician clicks a button at 5:30 p.m., and within a minute the patient, interpreter, and scheduling are live on a call. That real-time orchestration across EHR APIs, telephony, and billing rules requires coordination between the Houston-based healthcare domain engineer, the Bengaluru mobile team, and the sales reps closing deals with urology, cardiology, and GI groups. Yet the hiring plan — independent reps, distributors, and SDRs across three U.S. metros — reads more like a distributed sales motion than a unified product organization.

What holds this together? The mission statement — "Empowerment, Simplicity, Trust" — sits on the About page. But the operating reality is a small, remote-first team navigating hospital procurement cycles, EHR sandbox access, and a founder whose clinical credibility opens doors. A separate Glassdoor profile for ANKR Inc. (a different company, ankr.com) describes that entity as "run more like a defi investment studio than a traditional tech startup" with "murky" finances and team members "pulled into founder side projects or investment opportunities." That review does not pertain to Ankr Health.

Values and Operating Principles

Ankr Health's operating principles read like a case study in deliberate constraint. Rao has described the core architectural choice as "model first and human second" — a phrasing that functions as a filter for product and hiring decisions. In an April 2025 podcast interview, he explained that most competitors in the cancer navigation space built human-first services layered with software later. Ankr inverted that: a proprietary foundational machine learning model (referred to as GSM, then GSEM-4) predicts which patients will develop specific side effects within 48 hours, and human outreach triggers only when the model flags risk. That inversion lets a small team cover a national footprint without staffing a 24/7 call center. The research describes a clinically validated cohort of roughly 1,500 patients spanning East Coast to West Coast sites, and the AstraZeneca partnership that went live with Lynparza, both cited as proof points that the model-first approach works at pharma scale.

The second principle is equally visible in the revenue model. Rao walked away from a direct-to-consumer strategy despite investor pressure — "I literally had investors shut the door on my face because we weren't D2C" — because he judged the per-patient price unaffordable for most Americans. Instead, Ankr sells to pharmaceutical manufacturers who bear the cost as a retention tool for their own drugs. The pitch is quantitative: a 16 percent treatment discontinuation rate from side effects, Dr. Arpit Rao found, translates, the Healthcare Theory Podcast reported, to roughly $300 million in annual foregone revenue per blockbuster asset, or, as Dr. Arpit Rao's figures put it, $3 billion over the remaining patent life. Ankr's model, validated to keep patients on therapy an extra two months, converts that leakage into a 4–5x ROI for pharma. The company's first pharma deal took two years to close after the strategic pivot, a timeline Rao characterizes as "gruesome" but necessary to prove the model in the buyer's own financial terms.

Third, the product is designed to disappear into existing clinical workflows. Ankr embeds inside Epic, eClinicalWorks, Athena, and other major EHRs; a clinician clicks a button inside the EMR and within a minute the system has dialed the patient, secured consent, arranged an interpreter if needed, verified insurance, and queued a billable note capturing roughly 80 percent of documentation requirements. The demo Rao gave framed the value as turning a $0, unpaid phone call into a $75 reimbursable encounter with "no hassle." That integration-first stance reflects a broader principle: adoption friction is the enemy, and the only way to win in healthcare IT is to meet clinicians where they already work.

Fourth, the team operates with a distributed, multi-location footprint that mirrors the national patient population it serves. First-party board data shows active postings in Houston (Senior Engineer, Sales Development Representative), Minneapolis (Senior SDR, remote), Atlanta (Senior SDR, remote), and Bengaluru (Hybrid App Developer, React Native), a spread that spans those same time zones and two continents for a company with nine salaried roles on the board. The remote-first structure is not a pandemic artifact; it is the logical consequence of selling a national pharma service from day one. Rao's own background — five FDA approvals in four years across prostate, bladder, and kidney cancer programs, followed by a successful exit of a global second-opinion platform (Delhi Health, 2014) — suggests a career built on coordinating expertise across geography rather than concentrating it in a headquarters.

Fifth, technical self-sufficiency is treated as a cultural baseline, not a specialist requirement. In the 2025 interview, Rao urged listeners to "get comfortable with the idea that you can be on your computer… typing in instructions, and for the computer to spit back some output," adding that a few months of coding practice lets domain experts "dream big and not rely on the limitation of finding a technical person." That mindset appears in the hiring slate: the Senior Engineer role in Houston lists a healthcare domain requirement alongside a $70,000–$100,000 band, while the Bengaluru mobile role carries a ₹1,000,000–₹1,700,000 band, both implying that engineers are expected to understand clinical context, not just ship features.

Finally, the company frames its ambition in patient-reach terms rather than valuation milestones. "Four million Americans a year is kind of our target," Rao said, referencing the 2 million patients who start cancer treatment annually plus adjacent high-risk populations in GI, rheumatology, and neurology. International expansion into non-English-speaking markets (specifically India and China) is described as the next greenfield, with investor interest already inbound. The operating principle here is scale through specificity: own the oncology-pharma niche completely, then replicate the model-first architecture into neighboring therapeutic areas where the same side-effect economics apply.

Taken together, these principles form a coherent system: model-first architecture enables proactive care; pharma-paid economics align incentives and avoid patient affordability barriers; EHR-native integration removes adoption friction; distributed staffing matches the national service footprint; technical fluency across roles keeps product velocity high; and a patient-count north star keeps the roadmap anchored to clinical impact. Whether that system sustains as the team grows past its current headcount is the open question the next sections will test.

What the Hiring Bar Selects For

Ankr Health's hiring pattern reveals a company building a distributed sales and engineering engine around a healthcare AI platform, and the roles it posts signal exactly which capabilities it cannot buy off the shelf. The common thread across every posting: proximity to the buyer. Ankr sells AI agents (Mira for inbound calls, Frank for scheduling, Sol for scribing) into independent medical groups that run on Athena, eClinicalWorks, Epic, or Greenway. The founder's interview frames the pitch as "recreating the support system that exists until 4:30 p.m. on demand," and cites customer modeling showing that amount in recovered revenue. That number only lands if the salesperson speaks the language of practice administrators: RVUs, prior-auth denials, MIPS reporting, and the economics of a five-person group leaving, Dr. Rao's data shows, half a million dollars on the table. The SDR roles in Houston, Minneapolis, and Atlanta map to major independent-practice corridors; the Senior Engineer role explicitly requires "healthcare domain" knowledge, not just React or Python fluency.

Remote-first appears in the architecture of the listings themselves. The Atlanta and Minneapolis SDR roles are tagged "Remote (Atlanta, GA, US)" and "Remote (Minneapolis, MN, US)"; not hybrid, not relocation-required. The Independent Reps listing is explicitly "US / Remote (US)." Only the Houston SDR and Senior Engineer roles name a city without a remote qualifier, and even the Bengaluru developer role is labeled "Hybrid." This distribution matches the company's stated footprint: a workforce that operates across time zones to support clinics that never close. The product itself reinforces the requirement: Mira answers calls "during clinic hours, after hours, weekends, and holidays," and the platform's value prop is "be available when your patients are." Candidates who have only worked 9-to-5 SaaS cycles will miss the operational rhythm.

The hiring bar also selects for regulatory fluency. Ankr's marketing leads with "All servers in continental USA," "HIPAA and SOC2 compliance," and "$4 million in cyber liability coverage," a direct response to federal and state crackdowns on offshored call centers. The Bengaluru engineering role exists, but patient data does not leave US borders. Engineers who cannot design for data residency, audit logging, and business-rule engines that "sift through about 100,000 permutations & combinations of insurance, patient, provider, department, clinic, organization and other filters" will not clear technical screens. The Frank scheduling agent's BRMS (business rules management system) is described as explaining its decisions and escalating edge cases instead of guessing, a design philosophy that demands engineers comfortable with deterministic logic, not just probabilistic LLM prompting.

No verified employee reviews for Ankr Health specifically appear in public sources beyond the two Glassdoor entries. The Indeed profile showing eight reviews as of October 2025 belongs to "Anker Shipng," a delivery and logistics operation whose reviewers describe van routes, DSP management, and 190-stop days. Those reviews are not about Ankr Health, the healthcare AI company, and conflating the two would mislead candidates. The naming similarity (Anker vs. Ankr) appears to be the only overlap.

What the research does show about Ankr Health's workforce comes from first-party job postings on Zero G Talent's board and the founder's public comments. The board lists nine salaried roles with a typical salary band of $44k–$142k (median $90k), spanning a Hybrid App Developer in Bengaluru (₹10–17 lakh/year), a Senior Engineer (Healthcare Domain) in Houston at $70–100k, and multiple Sales Development Representative positions in Houston, Minneapolis, and Atlanta at $60–90k or $120–140k. The roles are distributed across Houston, Minneapolis, Atlanta, Bengaluru, and remote U.S. locations, consistent with a small, multi-location team.

In a YouTube interview, the founder (a former practicing medical oncologist who moved to Ankr full-time six to seven months prior) described the company's mission: recreating the clinical support system that disappears after 4:30 p.m. He noted that a five-person physician group loses roughly $500,000 annually in uncompensated after-hours calls, time that also drives burnout. Ankr's AI employees, he said, are already deployed at SouthLake Orthopaedics (Alabama's largest independent orthopedics group) and GI Specialists of Georgia, embedded in major EHRs and preparing about 80% of billable clinic notes.

The absence of substantial public employee commentary (positive or negative) is itself a signal: the company is early, small, and operating below the radar of typical review platforms. Candidates should treat this as a data gap, not a red flag, and ask directly about team dynamics, onboarding, and feedback loops during interviews. The distributed structure (Houston, Minneapolis, Atlanta, Bengaluru, plus remote) means communication norms and meeting cadences will shape daily experience more than any published review could.

Who Thrives Here and Who Burns Out

Ankr Health's team operates across Houston, Minneapolis, Atlanta, and Bengaluru, a distributed footprint that compresses time zones into an 11-hour spread. People who thrive here share a specific cluster of traits. First, they treat regulatory ambiguity as a design constraint, not a blocker. Ankr's early EHR integrations across Epic, eClinicalWorks, and Athena mean engineers and product people must ship features that satisfy HIPAA, state privacy laws, and FDA guidance simultaneously, often before that guidance exists. Candidates who have built in regulated environments (fintech, medtech, aerospace) adapt faster than those from consumer tech.

Second, they operate with high autonomy and low ceremony. The job postings for Senior Engineer and Sales Development Representative roles list responsibilities like "lead the integration and implementation of Electronic Health Record systems" and "collaborate with cross-functional teams to design robust RPA solutions," language that implies ownership, not ticket-taking. With roughly nine salaried roles across three continents, there is no product manager to write specs for every edge case. The YouTube demo shows the product handling consent, interpreter routing, insurance verification, and 80 percent of clinical note generation autonomously. Engineers who need detailed tickets before writing code will stall; those who can reverse-engineer requirements from a clinician's workflow video will ship.

Third, they tolerate (and often prefer) asynchronous communication across time zones. The board data shows salaried roles spanning $44k–$142k (median $90k) with explicit remote designations for Minneapolis and Atlanta. People who equate "culture" with daily standups in a shared office will feel isolated. People who measure progress by merged PRs and closed deals, not by hours visible on Slack, accumulate leverage.

Fourth, they connect personally to the clinical problem. The demo video quantifies the stakes: a five-person oncology group loses that amount in such calls; a single 11-minute callback prevents a $1,600 ER visit and generates $75 in billable revenue. Engineers who have watched a family member navigate cancer treatment, or sales reps who have shadowed infusion nurses, sustain motivation through the inevitable compliance slogs. Abstract mission statements don't hold weight when debugging an HL7 feed late on a Friday.

Who burns out? Four profiles appear repeatedly in the structural pressures.

The structure-dependent operator. Someone who needs a defined career ladder, regular 1:1s with a dedicated manager, and clear promotion criteria will find an org chart that hasn't solidified. The company is still in the "everyone does everything" phase: the same Senior Engineer posting asks for EHR integration, RPA design, and HIPAA adherence. There is no "level 2 to level 3" playbook yet.

The regulatory idealist. People who believe healthcare should move at the speed of software ("move fast and break things") collide with the reality that correcting a misclassified device after launch is 10x more expensive than doing it right at the start. Ankr's space rewards paranoia about liability, not disruption theater.

The time-zone rigid. If your productive window is fixed and you treat chat as synchronous, you will either burn out trying to be available for Bengaluru mornings and Atlanta evenings, or you will become a bottleneck. The distributed model works for people who batch communication, document decisions aggressively, and default to written over verbal.

The pure technologist. Ankr's product touches patients directly, the demo shows a non-English-speaking patient getting an interpreter auto-routed, consent captured, and a billable visit scheduled within minutes. Engineers who want to optimize model latency without ever speaking to a clinician or seeing a clinical workflow will build the wrong thing. The company's value proposition is "win-win-win for the patient, for the health care system, and also for the physician." If that triad doesn't resonate viscerally, the grind of SOC2 compliance, EHR sandbox testing, and state-by-state CPOM analysis will erode motivation faster than equity vesting can replenish it.

The filter is simple: Can you ship reliable, compliant software in a domain where errors show up in patient harm reports, while collaborating asynchronously across three continents with minimal process? If yes, the autonomy and clinical impact are unusual. If no, the same factors become the exit interview.

The oncologist who clicked "end visit" at that time and watched the system dial the patient, route the interpreter, and queue the note: that is the loop Ankr bets its culture on. The team that builds it never meets in a hallway. They meet in the log files.

Working in AI? Zero G Talent tracks the openings: see every open Ankr Health role, browse AI jobs, the companies hiring, and the people building the field.