Why pre-screen system integration consultants before the client interview
Integration work is judged long after the consultant leaves, which is why the resumes are hard to read. A point-to-point connection built in a fortnight and a properly designed integration look identical at handover; the difference shows up two years later when a vendor changes an API and nobody can find where the mapping lives. A short screen surfaces how a candidate thinks about the failure cases, which is the part that predicts whether the work survives contact with production.
What actually matters when screening System Integration Consultant candidates
- 01
Technical proficiency
Check hands-on depth with integration platforms they name: MuleSoft, Boomi, SAP PI/PO, Azure Logic Apps, Kafka, plus REST, SOAP, EDI, IDoc and XSLT mapping work.
- 02
Systems and trade-offs
Probe how they chose between point-to-point, ESB, event streaming or iPaaS for a client, and how they handled idempotency, throughput limits and legacy ERP constraints.
- 03
Evidence and rigour
Test how they proved an integration worked: reconciliation counts, message replay after outages, SIT and UAT cycles, error queue monitoring, cutover dry runs before go-live.
- 04
Collaboration and communication
Assess how they run workshops with client business owners and third-party vendors, produce interface catalogues or mapping specifications, and handle scope disputes mid-project.
Pre-screening questions to ask System Integration Consultant candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
API and middleware depth
3 questions01Can you discuss your experience working with APIs?
Listen forBoth consuming and building, with authentication, versioning and rate limits addressed, plus what they did when a vendor changed an endpoint without notice.
API experience limited to clicking through a connector, or no awareness of versioning and breaking changes.
02Which integration tools are you most familiar with?
Listen forNamed middleware or platforms with an opinion on where each one stops being appropriate, based on something they built rather than product marketing.
Names every major platform equally, or cannot say what a tool did badly on a project they ran.
03What is your experience developing and managing real-time integration solutions?
Listen forA real-time flow with ordering and duplicate handling addressed, and a clear view on where near-real-time batching would have been the better call.
Treats real time as always preferable, or has no answer for out-of-order or duplicated messages.
Quick against maintainable
3 questions04How have you handled situations where an integration did not go as planned?
Listen forA specific failure with what broke, how they contained it, and whether records were lost or reconciled afterwards rather than quietly dropped.
Cannot name an integration that went wrong, or a failure that was resolved by someone else entirely.
05How do you ensure data security during a systems integration?
Listen forCredentials handled outside the code, transport and field-level protection where needed, and a view on minimising what actually crosses the boundary.
Credentials embedded in configuration, or all available fields synced because it was easier than filtering them.
06How do you maintain up-to-date documentation during an integration project?
Listen forField mappings and error handling recorded where the next person will look, with a handover that left someone able to change the integration.
Documentation written at the end if time allowed, or knowledge that left with them at the end of the engagement.
Integrations that helped
3 questions07Can you explain a complex integration project you have led?
Listen forThe systems named, what made it complex, and the decision they got wrong first, with their own role separated from the delivery team's.
Describes the programme rather than their part, or complexity that amounts to a large number of simple connections.
08Can you give examples of integration projects that delivered measurable return?
Listen forA before figure such as manual re-keying hours or an error rate, who owned that number, and what it became after the integration went live.
Percentage improvements with no baseline, or benefits claimed on the business case rather than measured afterwards.
09Can you describe your experience automating processes through systems integration?
Listen forA manual process removed entirely rather than partially, with what happens now to the exceptions that used to be handled by a person.
Automation that left a manual step in the middle, or no plan for the cases the automation cannot handle.
Holding the room
3 questions10How comfortable are you liaising with both technical and non-technical stakeholders?
Listen forA specific conversation where they had to say something a stakeholder did not want to hear, and how they kept the project moving afterwards.
Claims to bridge both worlds with no example, or describes business stakeholders as the source of scope problems.
11Have you designed a systems integration strategy from scratch?
Listen forA design with the constraints named: existing estate, in-house skills, budget, and something they deliberately excluded from scope and why.
A reference architecture with no constraints, or a strategy that assumes capability the client did not have.
12Do you have experience working in a cross-functional team environment?
Listen forWork alongside people who did not report to them, including how they got time from a team that had other priorities.
Only worked with dedicated project teams, or blames delays entirely on other departments.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical proficiency
35%5Names specific connectors, mapping languages and broker configurations used, and explains message transformation and retry logic without hedging.
Systems and trade-offs
25%5Compares architectures against real client constraints (licence cost, latency, batch windows) and admits where a chosen pattern later caused pain.
Evidence and rigour
25%5Cites reconciliation numbers, defect counts closed in SIT, and monitoring or alerting they built to catch failed messages in production.
Collaboration and communication
15%5Describes concrete artefacts (interface specs, RAID logs) and a vendor or stakeholder conflict they resolved without stalling the delivery date.
A quick point-to-point connection and a maintainable integration look identical at handover. A one-way video screen lets you hear how a candidate handles the failure cases before a client interview.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an integration consultant take?
Fifteen minutes across eight to ten questions, answered async. Enough to confirm the platforms they have integrated, hear how they handle failure and retries, and check they can talk to non-technical stakeholders before a client-facing interview.
Should the screen cover our specific systems?
Ask about your systems, but weight the answer lightly. Specific platform experience is useful and learnable. How they handle idempotency, retries and reconciliation transfers between platforms; familiarity with one vendor's product does not.
Evaluating answers
What is the strongest signal when screening an integration consultant?
A clear answer on what happens when the far end is unavailable. Consultants who have supported production describe queues, retries with backoff, and reconciliation for the records that fell through. Candidates who have only built happy paths do not mention any of it.
How do I judge claims about return on investment?
Ask what was measured and by whom. Strong candidates name a before figure, such as hours of manual re-keying or an error rate, and who owned the number. Percentages with no baseline are usually reconstructed after the fact.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
