Preparing for an InterSources interview requires a balanced strategy that showcases both your analytical rigor and your domain-specific expertise. You must demonstrate that you can step into a client-facing environment on day one and immediately add value.

Role-Related Knowledge – You must show a deep understanding of the specific business analysis domain you are interviewing for. Whether it is healthcare IT (Medicaid, Health Insurance), enterprise data management (Informatica MDM), or corporate finance/banking, you should be conversational in the industry's regulations, standard practices, and technical terminology.

Analytical & Problem-Solving Ability – Interviewers will evaluate how you break down highly ambiguous problems. You should demonstrate a structured approach to analyzing current-state workflows, identifying inefficiencies, and designing optimized future-state systems.

Structured Communication & Technical Writing – Because many Business Analyst roles at InterSources involve writing high-stakes documentation (such as APDs, RFPs, and SOPs), you must prove your ability to write clearly, concisely, and with absolute technical accuracy.

Stakeholder Leadership & Influence – You need to show that you can lead cross-functional teams, facilitate JAD sessions, manage client expectations, and drive consensus among stakeholders who may have conflicting goals.

The interview process at InterSources is designed to evaluate both your core consulting skills and your technical alignment with specific client projects. Because InterSources is an agile, client-focused organization, the process moves efficiently but maintains a high bar for quality and domain expertise.

The journey typically begins with an initial screening call with a recruiter to discuss your background, career goals, and basic alignment with the open position. Following this, you will progress to a technical and domain-focused assessment. This stage is often conducted by an internal practice lead or senior architect at InterSources who will dive deep into your methodologies, technical writing capabilities, and analytical skills. The final stage is usually a client-focused panel interview, where you will present your experience directly to the stakeholders you will be supporting, ensuring a strong cultural and technical fit.

This timeline illustrates the typical progression from your initial contact to the final offer stage. Candidates should use this visual flow to budget their preparation time, focusing heavily on domain-specific scenarios prior to the technical and client panel rounds. While the overall structure remains consistent, the exact duration of each phase may vary depending on the urgency of the client project.

To excel in the InterSources interview, you must understand the specific competencies that interviewers are trained to evaluate.

Technical Writing & Federal Documentation

For roles aligned with public sector projects, your ability to draft compliance-grade documentation is paramount. Interviewers will assess your understanding of federal funding structures and technical writing standards.

Be ready to go over:

• Advanced Planning Documents (APD) – Understanding the planning, implementation, and operational phases of federal grant proposals.
• Request for Proposal (RFP) Development – How to structure requirements to solicit competitive, compliant vendor bids.
• Standard Operating Procedures (SOP) – Creating clear, repeatable business instructions that bridge policy and technology.
• Advanced concepts (less common) – Federal financial participation (FFP) rate structures, Medicaid Management Information Systems (MMIS) certification standards.

Example scenarios:

• "Draft a brief outline of how you would justify a system modernization project to federal regulators in an APD."
• "How do you structure a functional requirement in an RFP to ensure vendors provide measurable, testable responses?"

Workflow Re-engineering & Data Modeling

If you are interviewing for a data-intensive or financial systems role, you will be evaluated on your ability to map complex processes and structure data flow.

Be ready to go over:

• As-Is vs. To-Be Modeling – Identifying process bottlenecks, redundancies, and compliance gaps in current-state workflows.
• Data Mapping & Integration – Aligning source system data fields with target schemas, especially within Informatica MDM pipelines.
• Functional Specification Design – Translating business rules into logical data models, flowcharts, and system requirements.
• Advanced concepts (less common) – Master Data Management (MDM) match-and-merge rules, entity resolution, dimensional data modeling.

Example scenarios:

• "Walk me through how you would redesign a manual child support payment allocation process to make it fully automated and auditable."
• "How do you handle data field mismatches when integrating legacy banking records into a centralized customer master database?"

Stakeholder Facilitation & JAD Sessions

Every Business Analyst at InterSources must act as a facilitator who can bring alignment to divergent groups.

Be ready to go over:

• Joint Application Development (JAD) – Designing, preparing for, and facilitating highly productive requirements-gathering workshops.
• Conflict Resolution – Managing disagreements between business units regarding system priorities and scope.
• Change Management – Strategizing how to prepare, support, and train end-users during major system rollouts.

Example scenarios:

• "Two key department heads disagree on the priority of a system feature. How do you facilitate a resolution without delaying the project timeline?"
• "Describe your process for preparing and executing a JAD session with participants ranging from database administrators to executive directors."