Interview Experience – FNZ (Analyst Developer) | Rejected | 2026

Mode of Application

A recruiter reached out to me via my Naukri profile regarding an Analyst Developer opportunity at FNZ

🔹 Round 1: Online Assessment (HackerRank)

The first round was an online test on HackerRank consisting of 8 questions.

• 1 SQL Question – Required performing a PIVOT operation on a table, testing data transformation and aggregation.
• 1 C# Coding Question – Given an interface, needed to implement required methods, using LINQ for data manipulation.
• 5 Aptitude MCQs – Basic logical reasoning and quantitative questions.

Overall, the round focused on practical SQL + clean C# implementation + basic aptitude.

🔹 Round 2: Technical Interview

1. Database Design

• Reviewed a 3‑table schema.
• Suggested adding Primary Keys, defining Foreign Key relationships, using ENUMs for fixed values, and using DECIMAL instead of FLOAT for monetary fields.
• Wrote 2 SQL queries based on the schema.

2. SQL Performance & Indexing

• Optimized a given query.
• Suggestions: add indexes, avoid correlated subqueries.
• Follow‑ups: What are indexes? Types (clustered, non‑clustered). How indexes improve performance.

3. C# Code Review

• Reviewed 2 code snippets.
• Key improvements: move DB logic to Repository layer, prevent SQL Injection (use parameterized queries), replace string return type with boolean.

4. Dependency Injection & SOLID

• Explained Dependency Injection (DI).
• Covered SRP (Single Responsibility Principle) and OCP (Open/Closed Principle).

5. Coding Round – Banking System

• Implemented Deposit & Withdraw.
• Created Savings Account (Min balance: 1000) and Current Account (Min balance: 0).
• Extended to Transfer between accounts.

6. Design Improvements

• Suggested Strategy Pattern for account‑specific rules.
• Suggested Factory Pattern for account creation.

🔹 Round 3: Culture Fit (Face‑to‑Face)

This was a face‑to‑face discussion focusing on mindset and alignment.

• Why FNZ?
• Why are you switching?
• What does FNZ do?
• What is your current role?
• What is the most challenging part of your current job?

My answer for challenge: I discussed requirement gathering from stakeholders and handling ambiguity.

Overall Experience

• Interview was very interactive and deep.
• Strong focus on fundamentals (SQL, C#), system design thinking, communication & clarity.
• Every concept mentioned was explored with detailed follow‑up questions.

Tips for Future Candidates

• Be strong in SQL (especially joins, indexing, pivoting).
• Practice LINQ‑based C# problems.
• Revise SOLID principles + design patterns.
• Be ready to justify every decision you make.
• Prepare real examples for behavioral questions.

Verdict: Rejected after Final Round