Interview Experience – FNZ (Analyst Developer) | Rejected | 2026
Mode of Application: A recruiter reached out to me via my Naukri profile regarding a Analyst Developer opportunity at FNZ
🔹 Round 1: Online Assessment (HackerRank)
The first round was an online test on HackerRank consisting of 8 questions.
Breakdown:
-
1 SQL Question
- Required performing a PIVOT operation on a table
- Tested understanding of data transformation and aggregation
-
1 C# Coding Question
- Given an interface, needed to implement required methods
- Most of the logic involved 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
- 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
stringreturn type with boolean
4. Dependency Injection & SOLID
-
Explained Dependency Injection (DI)
-
Covered:
- SRP (Single Responsibility Principle)
- OCP (Open/Closed Principle)
5. Coding Round – Banking System
-
Implemented:
Deposit&Withdraw- Savings Account (Min balance: 1000)
- Current Account (Min balance: 0)
-
Extended to:
- Transfer between accounts
6. Design Improvements
Suggested:
- Strategy Pattern → for account-specific rules
- Factory Pattern → for account creation
🔹 Round 3: Culture Fit (Face-to-Face)
This was a face-to-face discussion focusing on mindset and alignment.
Questions asked:
- 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
- Explained how handling ambiguity and aligning expectations can be difficult
💡 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

