Platform Configuration Analyst - Neolytix

NEOLYTIX · INCREDIBLY

Platform Configuration Analyst

Product & Technology | InCredibly Provider Data Intelligence | Gurugram

DEPARTMENT

Product & Technology

EXPERIENCE

3-6 Years

LOCATION

Gurugram (Onsite)

SHIFT

US Shift

REPORTS INTO

Product Owner, InCredibly

Anti-Profile: If your career has been processing credentialing applications or filing payer submissions, this is not the role. If you have built the templates, decision tables, playbooks, or configuration rules that others follow, it is. Rule-encoding aptitude is what we are hiring. US credentialing and enrollment domain we teach.

US Shift: This role operates on a US-aligned shift from our Gurugram office. Consistent availability during US business hours is required. Apply only if you can commit to this onsite.

About the Role

Neolytix is a US healthcare managed services organization running credentialing, payer enrollment, provider licensing, and revenue cycle operations for physician groups, health systems, and MSOs across the United States. InCredibly is the platform we built to run that work: a rules-driven system that manages the full credentialing, enrollment, and licensing lifecycle across thousands of providers, hundreds of payers, and every US state.

The platform is configurable by design. Payer requirements, state licensing rules, document checklists, follow-up protocols, and workflow variants live in a rules layer and knowledge base, not in code. When the rules are right, the platform does the work. When they are missing or wrong, people do it by hand. This role owns that rules layer.

This is not a delivery role and it is not a development role. You are the person who decides how the platform thinks. Half the job is keeping the knowledge base accurate: payer playbooks, the state board library, document checklists, the specialty and taxonomy crosswalk, follow-up protocols, and the SOP library. The other half is turning what our operations team knows into configuration the platform can act on: workflow rules, stage templates, gate conditions, validation rules, and defaults that remove manual steps from analysts' work.

What You Will Do

1. Knowledge Base & Payer Rules

• Build and maintain payer playbooks: enrollment steps, portal details, required data fields, required documents, turnaround times, and escalation contacts, structured so the platform acts on them rather than as prose for a human to read.

• Maintain the state licensing and supervisory rules library across all US states: license requirements, fees, continuing education, supervisory agreement rules, and renewal cycles.

• Author document checklists and validation rules by work type and payer category.

• Maintain the specialty and taxonomy crosswalk and the mapping of provider types to payer requirements.

2. Workflow Configuration

• Translate operational patterns into workflow configuration: variant rules, stage insertions and skips, SLA adjustments, follow-up cadences, and gate requirements.

• Design and test configuration changes before they go live. Version your changes, document why you made them, and maintain a clean audit trail.

• Own the knowledge base flag queue: triage issues raised by analysts, fix them, and route changes through the change-request approval workflow.

3. Schema & Data Model Partnership

• Work directly with engineering when a real-world rule does not fit the schema. Spot the mismatch, articulate why, and propose the change with enough context for a developer to act on it.

• Read and interpret JSON configuration payloads. Use SQL to validate your own work before it hits production.

4. Measurement & Training

• Track what your rules do: reductions in manual touches, rework, and first-pass failures. Propose the next automation candidates from this data.

• Write SOPs by work type and train analysts on how configuration changes affect their workflows. You write for people who will run the process, not for a file.

What You Bring

Must-Have

• 3 to 6 years configuring rules, data, or workflows in an enterprise healthcare system. Typical backgrounds: payer benefit or provider configuration (Facets, QNXT, HealthRules, Amisys, Tapestry), EHR application analysis (Epic, Oracle Health/Cerner, Meditech), or provider data management platforms.

• A demonstrated ability to take an unstructured source: a policy PDF, a payer manual, a state regulation, and decompose it into fields, conditions, exceptions, and checklists. You will be asked to show this in a work sample.

• Working data literacy: SQL for querying and validating data, spreadsheet modelling, and enough JSON familiarity to read a configuration payload. You do not write application code.

• Version control and change discipline: you document why you made a change, test before you push, and have caused a downstream problem with a configuration change at least once. You can tell us what control you added afterward.

• Clear written English. Other people will run the playbooks and SOPs you write.

Strong Preference

• Exposure to US provider credentialing, payer enrollment (CAQH, PECOS, Medicaid portals), or provider licensing.

• Experience with configurable workflow engines, BPM platforms, or business rules engines.

• NCQA credentialing standards familiarity.

• Experience working with US healthcare clients or in a US time-zone overlap model.

Nice-to-Have

• Salesforce, ServiceNow, or Workday administration certification.

• Exposure to symplr, Modio Health, Medallion, or similar credentialing technology vendors.

• Epic certification or Facets/QNXT formal training.

Who You Are

• You see structure in a document that most people read as prose. A payer manual is a schema to you before it is a process.

• You break things before calling a configuration complete, because you have actually tested it. You can describe a rule you built that caused a downstream failure, and the control you added afterward.

• You write documentation that the person after you can follow without asking questions.

• You push back on vague requirements because you know what happens when a rule is ambiguous and live.

Eligibility Criteria

• Education: Graduate degree in any discipline. Computer science, information systems, or a healthcare-adjacent field is an advantage but not required.

• SQL: actively used for validation and reconciliation, not listed as a course. You will be assessed on this in the work sample.

• Written English: your resume and your application note are the first samples. Applications without the 200-word note (see hiring process) are not reviewed first.

• Location and Shift: Gurugram, onsite, US shift. Consistent availability during US business hours is required from day one.

• Notice Period: 60 to 90 days is expected for this profile. State your notice period clearly.

Performance Expectations

What success looks like:

• First 90 days: domain immersion complete. You have worked real cases across credentialing, enrollment, and licensing alongside our analysts. Playbooks, checklists, and follow-up defaults are live for the highest-volume payers. You own the flag queue and the change-request workflow.

• 6 months: your first automation rules are in production and measured. Analysts treat the knowledge base as the source of truth rather than their own notes.

• 12 months: the rules layer, not analyst memory, drives most routine work. You are defining the next automation roadmap with the Product Owner.

Hiring Process

• Stage 1: Application review. A 200-word note must accompany your CV: describe one rule, template, or configuration you built that removed manual work. What was the source? How did you structure it? What happened after it went live? Applications with the note are reviewed first.

• Stage 2: TA screening call (20 minutes). Role fit, configuration background, and data literacy check.

• Stage 3: Work sample (90-minute take-home, mandatory). You receive a real US state or payer document and structure it into fields, conditions, checklists, and gate conditions. This step is not skippable and no resume substitutes for it.

• Stage 4: Hiring manager interview with the Product Owner, Raj Bhatnagar. Covers your work sample output, your configuration approach, and your thinking on schema design.

• Stage 5: Domain and technical interview with Operations Leadership and a member of the engineering team.

• Stage 6: Offer.

Why Join Neolytix

Greenfield Ownership

You define the rules layer of a live US healthcare platform. You are not maintaining someone else's configuration or working through a ticket queue.

Direct Access

You work with the Product Owner and Operations leadership directly. There is no multi-layer hierarchy between you and the decision.

Rare Skill Formation

Deep knowledge of US credentialing, enrollment, and licensing is scarce and valuable globally. We teach it, from a team that has done it for years.

Product Trajectory

InCredibly is moving toward standalone software licensing. The person who defines how the platform encodes rules grows with it.

Questions? Reach out to Lakshay at Neolytix Talent Management | This document is confidential and for internal use only