If you run a payer platform on Facets or QNXT, you already know that “has Facets on the resume” tells you very little. The same platform name covers people who configure benefit plans, people who adjudicate and fix claims, developers who write extensions, testers, data analysts and business analysts. Hiring the wrong kind of expert can slow a configuration project down before it starts.
This guide is for hiring managers at health plans, TPAs and health tech firms who need to fill a claims or configuration role and want to screen candidates with confidence.
Start by naming the job inside the platform
Before you write the job description, decide which part of the platform the person will own. The most common role types are:
- Benefit and product configuration. Building and maintaining plans, products, benefit components, accumulators, cost-share rules and the service definitions that drive them.
- Provider and pricing configuration. Loading and maintaining provider records, networks, contracts, fee schedules and pricing logic, so that claims pay at the right rate.
- Claims analysis and adjudication support. Working pended and denied claims, tracing why a claim paid the way it did, fixing root causes in configuration and supporting reprocessing projects.
- Technical and development roles. Writing extensions and custom logic, building batch jobs and interfaces, and supporting upgrades and environment refreshes.
- Testing and QA. Writing test cases for new benefit years, regulatory changes and upgrades, and validating that configuration produces the expected claim outcome.
- Business and systems analysts. Turning business rules, contracts and policy into requirements the configuration team can build.
A strong benefit configurator and a strong pricing configurator can both be excellent hires, but they are rarely interchangeable on day one. Be specific in the job description and in your intake with any recruiter.
Facets vs QNXT experience: does it transfer?
Facets and QNXT solve similar problems for health plans, and the underlying concepts (members, providers, benefits, pricing, claims) are shared. A candidate who deeply understands how a benefit rule turns into a claim outcome in one platform will usually learn the other faster than someone new to core administration systems.
That said, the screens, data model, terminology and configuration approach are different. If your project is time-sensitive, such as a benefit-year build or an upgrade with a fixed go-live, prioritize hands-on experience in your exact platform. If you are hiring for a longer-term role and the candidate is strong in the concepts, cross-platform experience can be a reasonable trade-off.
The skills that separate strong candidates
Business knowledge of how a health plan pays claims
The best configuration and claims people understand the “why,” not just the screens. Look for working knowledge of:
- Line of business differences (commercial, Medicare Advantage, Medicaid) and how they change benefits and rules
- Cost-share concepts: deductibles, copays, coinsurance, out-of-pocket maximums and accumulators
- Provider contracting basics: fee schedules, DRG and per diem arrangements, capitation
- Coordination of benefits, eligibility and authorization rules
- Medical coding at the level the role needs (for example ICD-10-CM, CPT and HCPCS), and how codes drive pricing and edits
The BLS notes that computer systems analysts often specialize by industry and that an analyst working in healthcare “may need a thorough understanding of healthcare plans and programs such as Medicare and Medicaid” (BLS Occupational Outlook Handbook, Computer Systems Analysts). That domain knowledge is exactly what makes a configuration specialist productive.
Hands-on platform depth
Ask candidates to describe the actual work, not the project. Someone with real depth talks naturally about what they built, how they tested it and what broke. Vague answers (“I supported the Facets implementation”) are a signal to dig further.
SQL and data skills
Many claims and configuration problems are solved by querying the database to see what the system actually did. For analyst, testing and technical roles, comfortable SQL is close to essential. For pure configuration roles, it is a strong plus.
Understanding of the EDI flow
Claims arrive as X12 837 transactions and payments go out as 835s. A configuration specialist does not need to be an EDI developer, but they should understand how inbound data lands in the platform and how their configuration shows up on the remittance. (We cover EDI roles in more detail in a separate post.)
Change control and documentation
Configuration errors can affect large volumes of claims. Look for people who talk about peer review, test evidence, migration between environments and documentation without being prompted.
Interview questions that work
These questions tend to reveal real experience quickly:
- “Walk me through a claim that paid incorrectly. How did you find the root cause, and what did you change?”
- “How do you test a new benefit plan before it goes live? What do your test cases look like?”
- “Tell me about a provider contract or fee schedule you loaded. What made it tricky?”
- “How do you move configuration from development to test to production in your current team?”
- “Which parts of the platform have you never worked in?” (Honest answers here are a good sign.)
For technical roles, add a short practical exercise tied to the actual job, such as explaining what a query returns or reviewing a simple configuration scenario.
Red flags to watch for
- Platform names listed without any description of what the person built or fixed
- Only project-level language (“supported,” “was part of”) with no individual ownership
- No experience with testing or change control in a regulated environment
- Unclear understanding of the line of business you run
Choosing the right engagement model
Configuration work often comes in waves: benefit-year builds, regulatory changes, upgrades and migrations. A common approach is W2 contract or contract-to-hire for the peaks and direct hire for core platform owners. If you are unsure which model fits, our guide to direct hire, W2 contract, contract-to-hire and C2C walks through the trade-offs.
How ValiantIQ helps
Healthcare IT is ValiantIQ’s lead vertical. We recruit Facets and QNXT configuration, claims, EDI, revenue cycle and managed care talent for payers, providers and health tech firms on direct hire, W2, contract-to-hire or C2C terms. We screen for the specific part of the platform you need, so the profiles you review match the role, not just the keyword. Learn more about our Healthcare IT staffing or see current Healthcare IT hiring trends.
Ready to hire? Request talent with the role, platform and must-have skills, or book a 30-minute call to talk it through.