Thompson Gray Business Analyst interview questions & guide 2026

While interview questions can vary based on the specific team or project requirements, the following categories represent the core areas Thompson Gray focuses on during the assessment process. Use these to identify patterns in your own professional experience.

Business Process & RPA Knowledge

This category tests your understanding of how to translate manual business tasks into automated workflows.

• How do you approach gathering requirements for a process that has never been documented before?
• Can you explain the difference between a high-level process map and a keystroke-level process design document?

Preparation for Thompson Gray requires a blend of technical process knowledge and a deep understanding of the consultancy mindset. You should be ready to articulate how your work adds value to the client’s mission.

Process Analysis Proficiency – You must demonstrate an ability to deconstruct workflows into granular, actionable steps. Interviewers look for your ability to create Process Design Documentation (PDD) and identify the specific "keystroke" details required for successful bot development.

Client-Facing Communication – As a Business Analyst, you are the face of the project. You need to show that you can lead virtual meetings, manage stakeholder expectations, and translate technical status updates into clear, professional briefings for governance boards.

Adaptability & Domain Awareness – Given the focus on the DoD and Army FM community, you should be prepared to discuss your experience working within regulated environments. Even if you lack specific government experience, showing an understanding of security, compliance, and structured project management is vital.

The interview process at Thompson Gray is designed to evaluate both your technical competence in process improvement and your ability to thrive in a remote, collaborative environment. You can expect a professional, focused dialogue that assesses your ability to serve as a bridge between customers and developers. The rigor is centered on your past experiences with automation, your methodology for documentation, and your communication style.

The process is generally structured to move from a high-level screening of your background to more technical discussions regarding your specific analysis tools and methodology. Expect to discuss your experience with tools like UiPath or the Power Platform, as well as your history of managing project lifecycles from discovery to deployment.

This timeline illustrates the progression from initial qualification to final assessment. Use this structure to manage your preparation; early rounds will likely focus on your resume and behavioral fit, while later stages will dive deep into your technical problem-solving capabilities. Candidates should be prepared to provide specific examples of past automation projects during the mid-to-late stages.

Requirements Gathering & Documentation

This is the heart of your role. You are evaluated on your ability to capture processes with precision. Strong candidates provide concrete examples of how they translated vague user requests into detailed, logic-driven documentation that developers could execute without further clarification.

Be ready to go over:

• The tools you use for process mapping (e.g., Visio, process recording software).
• Your methodology for validating requirements with Subject Matter Experts (SMEs).
• How you maintain documentation integrity throughout the project lifecycle.

Example questions or scenarios:

• "Walk me through how you capture a process that involves multiple legacy systems."
• "What do you do if a client insists on automating a process that is clearly inefficient?"

Stakeholder Management

You will be evaluated on your ability to influence, facilitate, and manage expectations. Success here means showing that you can act as a trusted advisor who balances customer needs with technical reality.

Be ready to go over:

• Strategies for leading virtual workshops and meetings.
• How you handle conflict between client expectations and developer capacity.
• Techniques for keeping stakeholders informed on project status and metrics.

Example questions or scenarios:

• "How do you handle a scenario where a stakeholder changes their requirements mid-development?"
• "Describe your process for presenting project status to a governance board."

As a Business Analyst at Thompson Gray, you will own the end-to-end lifecycle of automation projects. Your primary responsibility is to lead the document, design, build, test, and deploy phases of RPA projects. You will work closely with developers, ensuring that the "keystroke level" details you capture are accurately reflected in the final software bot.

Beyond documentation, you will act as a primary point of contact for your customers. This involves briefing them on RPA capabilities, tracking metrics and financial projections for each automation, and facilitating communication across teams. You will also participate in the governance of the RPA process, ensuring that all projects align with organizational standards and quality expectations.

To be competitive for the Business Analyst position, you need a mix of analytical experience and strong professional communication skills.

• Must-have skills:

  • A BA/BS or MA/MS in Business Administration or Computer Science.
  • Up to 3 years of experience in business process improvement, analysis, or consulting.
  • Proficiency in creating Process Design Documentation (PDD) and SOPs.
  • Ability to obtain and maintain a Secret-level clearance.
  • Experience with remote work and virtual project management tools.

• Nice-to-have skills:

  • Certifications in UiPath or Power Platform.
  • Prior experience working with DoD clients or in the Army FM community.
  • PMP certification.

Q: How long does the hiring process typically take? A: While timelines vary based on project urgency, you can expect a professional, structured process that moves efficiently once you are identified as a strong fit. Expect at least 2–3 rounds of interviews.

Q: Do I need a Secret clearance to apply? A: You must be a U.S. citizen capable of obtaining a Secret-level clearance. While holding an active clearance is highly desired and will expedite your hiring, it is not always a mandatory requirement to start the interview process.

Q: How much focus is there on actual coding? A: This is a Business Analyst role, not a developer role. You do not need to be a programmer, but you must be comfortable understanding how code works, interacting with developers, and learning the capabilities of automation software.

Q: What is the work culture like at Thompson Gray? A: The culture is professional, collaborative, and results-oriented. Given the remote-first nature of many roles, you will need to be self-motivated and highly skilled at virtual communication.

• Own your documentation: If you have samples of PDDs or process maps (with sensitive information redacted), be prepared to describe the logic behind them.
• Master the virtual environment: Since you will lead remote workshops, ensure your video presence is professional, your audio is clear, and your screen-sharing skills are polished.
• Focus on the "Why": Don't just explain what you did; explain the business value, the time saved, or the accuracy improved by your automation efforts.

The Business Analyst role at Thompson Gray offers a unique opportunity to drive meaningful change through automation within high-impact government sectors. By focusing on your ability to map complex processes, manage stakeholder expectations, and bridge the gap between technical teams and operational needs, you position yourself as an essential partner in the company's mission.

Success in these interviews comes down to your preparation and your ability to articulate your analytical methodology clearly. You can explore additional interview insights, practice questions, and preparation resources on Dataford to further refine your approach and boost your confidence.

The provided salary data reflects the market range for this position, which can vary significantly based on your specific level of experience, certifications, and the complexity of the project you are supporting. Use this range as a benchmark to understand the seniority and scope of the role, but focus your negotiation strategy on the specific value and specialized skills you bring to the team.