Mphasis Digital Risk Technical Analyst Interview: Rounds, Questions and Preparation

What the job involves

A Technical Analyst in Indian IT services supports the design, testing, and maintenance of software applications for clients, often working on production support, defect triage, and small enhancements. Day to day involves reading logs, writing SQL queries, reproducing issues, documenting fixes, and coordinating with senior developers and client teams. In a digital risk or BFSI-focused employer like Mphasis Digital Risk, you may also work on data validation, compliance checks, and automation of repetitive monitoring tasks.

Role and Technical Knowledge

1. 1

   What is the difference between a defect, an incident, and a problem in an IT services project?

   A strong answer defines defect as a deviation from requirements, incident as an unplanned service disruption, and problem as the root cause of one or more incidents. Mention that incidents are handled by service desk while problems go to problem management.

2. 2

   How would you write a SQL query to find duplicate records in a customer table?

   Cover using GROUP BY with HAVING COUNT(*) > 1, and optionally a self-join or window function like ROW_NUMBER(). Explain that you would first identify the key columns that define a duplicate.

3. 3

   Explain the stages of the SDLC and where a Technical Analyst fits in.

   List requirements, design, development, testing, deployment, and maintenance. Say that a Technical Analyst typically supports testing, deployment, and maintenance, and may help with requirement clarification and documentation.

4. 4

   What is the difference between smoke testing, sanity testing, and regression testing?

   Smoke testing checks critical functionality after a build, sanity testing checks a specific fix, and regression testing ensures new changes did not break existing features. Give a small example for each in a web application.

Practical Scenarios

1. 5

   A client reports that a nightly batch job failed and no reports were generated. How would you troubleshoot?

   Start by checking job logs and scheduler status, then verify database connectivity, input file availability, and recent code changes. Suggest escalating with a clear timeline and impact if the fix is not immediate.

2. 6

   You are asked to validate data migrated from a legacy system to a new database. What steps would you take?

   Describe record counts, checksums, sample field-level comparisons, and business rule validation. Mention documenting mismatches and coordinating with the migration team for corrections.

3. 7

   How would you handle a situation where you cannot reproduce a defect that a user reported?

   Ask for exact steps, screenshots, user ID, timestamp, and environment details. Try the same steps with the same data and check logs. If still not reproducible, document your attempts and request a screen-sharing session.

4. 8

   You need to run a simple Linux command to check disk space on a production server. What command would you use and why?

   Mention df -h for human-readable disk usage and du -sh for directory sizes. Explain that you would avoid destructive commands and follow change management before touching production.

Behavioural and Situational

1. 9

   Tell me about a time you had to learn a new tool or technology quickly for a college project.

   Use the STAR method: describe the situation, the tool you learned, the actions you took, and the result. Emphasise self-learning through documentation and practice.

2. 10

   How would you handle a disagreement with a senior team member about the root cause of a bug?

   Show respect and data-driven thinking. Suggest presenting logs and evidence calmly, listening to their view, and escalating to the lead only if needed. Focus on resolving the issue, not winning the argument.

3. 11

   Describe a time you missed a deadline. What did you do?

   Be honest about a small, real example. Explain that you informed stakeholders early, reprioritised, and delivered in phases. Highlight what you changed afterwards to avoid repeats.

4. 12

   This role may require working in shifts or being on call. How do you feel about that?

   Show flexibility and awareness of IT services operations. Mention that you understand client time zones and are willing to adjust, while also planning rest and handovers responsibly.

HR and Company Fit

1. 13

   Why do you want to work as a Technical Analyst in an IT services company rather than a product company?

   Talk about exposure to multiple clients, domains, and technologies. Mention learning structured processes like ITIL and the opportunity to solve real business problems for clients.

2. 14

   What do you know about the digital risk and compliance domain in BFSI?

   Show basic awareness: data privacy, KYC, AML, fraud detection, and regulatory reporting. Say that you are eager to learn domain-specific tools and processes on the job.

3. 15

   Where do you see yourself in three years?

   Align your growth with the company: from handling tickets and testing to owning modules, mentoring juniors, and possibly earning certifications in cloud or data. Avoid saying you want to leave for higher studies immediately.

4. 16

   Are you comfortable relocating to a different city or client location?

   Answer clearly and positively if you are. Mention that you are open to relocation and understand that client projects may require it. If you have constraints, state them honestly but professionally.