Platform Configuration Analyst

Location: Gurugram, Haryana, India NEOLYTIX  ·  INCREDIBLY Platform Configuration Analyst InCredibly Platform Configuration  |  Non-Ops  |  Gurugram DEPARTMENT Non-Ops EXPERIENCE 2–5 Years LOCATION Gurugram (Onsite) SHIFT US Shift REPORTS INTO Manager ⚠  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-headquartered healthcare managed services organization serving 270+ provider organizations across the United States, with delivery operations in Gurugram, Manila, and Chicago. InCredibly is the platform we built to run our credentialing, enrollment, and licensing operations: a rules-driven system that manages workflows, documents, timelines, and payer requirements across thousands of providers. The platform is configurable by design. Payer requirements, 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 not a development role. You are the person who decides how the platform thinks. Half the job is keeping the knowledge base accurate. The other half is turning what our operations team knows into configuration the platform can execute: workflow rules, stage templates, gate conditions, validation rules, and defaults that reduce manual work for analysts on the floor. What You Will Do 1. Knowledge Base & Rules Management Build and maintain the platform knowledge base: document checklists, validation rules, follow-up protocols, and workflow defaults, structured so the system acts on them rather than as prose for a human to read. Author configuration rules by work type, category, and variant. Keep them current as operational requirements evolve. Own the flag queue: triage issues raised by analysts, fix them, and route changes through the change-request approval workflow. 2. Workflow Configuration Translate operational patterns into workflow configuration: stage sequences, variant rules, SLA adjustments, gate requirements, and follow-up cadences. Design and test configuration changes before they go live. Version your changes, document why you made them, and maintain a clean audit trail. Coordinate with operations leads to understand process changes and translate them into updated configuration. 3. Schema & Data Model Partnership Work with the engineering team when a real-world rule does not fit the existing schema. Spot the mismatch, articulate why, and propose the change with enough context for a developer to act on it. Use SQL to validate your own work and verify data accuracy before changes hit production. 4. Measurement & Training Track what your rules do: reductions in manual touches, rework, and first-pass failures. Propose the next configuration improvement candidates from this data. Write SOPs by work type and brief 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 2 to 5 years configuring rules, data, or workflows in an enterprise platform. Backgrounds that translate well: benefit or provider configuration in payer systems (Facets, QNXT, HealthRules, Amisys), EHR application analysis (Epic, Oracle Health, Meditech), enterprise SaaS administration (Salesforce, ServiceNow, Workday, Pega), or business rules engine configuration. A demonstrated ability to take an unstructured source document, a policy, a set of requirements, an email thread, and decompose it into fields, conditions, exceptions, and checklists. You will be asked to show this in a work sample. Basic SQL: you use it to query, validate, and reconcile data. Not a course listing. Version control and change discipline: you document why you made a change, test before you push, and own the outcome when something breaks downstream. Clear written English. Other people will run the SOPs and playbooks you write. Strong Preference Experience with configurable workflow engines, BPM platforms, or business rules engines where you designed the rules, not just executed them. JIRA: used for managing configuration change requests, flag queues, and work tracking alongside engineering and operations teams. BPMN 2.0 awareness: ability to read and interpret process flow diagrams and translate them into platform workflow configuration. Prior experience working with US clients or in a US time-zone overlap model. Experience across more than one platform or system type: the ability to map a rule from one configuration environment to another. Nice-to-Have Exposure to US healthcare operations, RCM workflows, or provider credentialing and enrollment. Familiarity with credentialing technology platforms such as symplr, Modio Health, Medallion, or similar. Salesforce, ServiceNow, or Workday administration certification. Epic certification or formal Facets/QNXT training. Who You Are You see structure in a document that most people read as prose. A requirements page 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 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 business-adjacent field is an advantage but not required. SQL: actively used for validation and data checking, not just listed as a skill. Assessed in the work sample. Shift: US-aligned shift, onsite in Gurugram. Consistent availability during US business hours is required from day one. Notice Period: 60 to 90 days is typical for this profile. Please state your notice period clearly. Performance Expectations What success looks like: First 90 days: domain immersion complete. Playbooks, checklists, and follow-up defaults are live for the highest-volume work types. You own the flag queue and the change-request workflow. 6 months: your first configuration improvements 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 configuration roadmap with the Manager. Hiring Process Stage 1: Application review. Include a short note with your CV (150 to 200 words): 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 SQL usage check. Stage 3: Work sample (90-minute take-home, mandatory). You receive a business rules document and structure it into fields, conditions, checklists, and gate conditions. Skippable by nothing. Stage 4: Hiring manager interview with the Product Owner covering your work sample output and configuration approach. Stage 5: Domain and technical interview with Operations Leadership and Engineering. Stage 6: Offer. Why Join Neolytix Greenfield Ownership You define the rules layer of a live platform used in production every day. Not maintaining someone else's configuration. Not a ticket queue. Direct Access You work with the Product Owner and Operations Leadership directly. No multi-layer hierarchy between you and the decision. Domain You Can Learn US healthcare and credentialing operations are taught by the team. The configuration aptitude is what we hire for. Product Trajectory InCredibly is moving toward standalone software licensing. The person who defines how the platform encodes rules grows with it.