Financial Software Systems Pvt Ltd. Interview Experience
Question Details
Round 1 The first round was Technical coding and Logical reasoning round, which was further divided into 2 sub rounds.The first one had 2 coding questions, one on Linked ...
Full Details
Round 1 The first round was Technical coding and Logical reasoning round, which was further divided into 2 sub rounds. The first one had 2 coding questions, one on Linked List and another on Dynamic Programming along with MCQs on DBMS, OS, Digital Communication and other CSE topics. 3rd section consisted of logical reasoning and general aptitude questions. Most of them were easy to solve but proper time management is the key. It was a video proctored test with tab switching detection also. **Students who cleared the first half of the first round were called for the next half of the same round. The second one again had 4 coding problems, this time they were quite difficult and required complex analytical thinking for a concrete solution. A major problem was restricting in our code in time complexity mentioned in the question. This was accompanied by some tricky aptitude questions on permutation and combination, probability, height and distance problems, and geometry questions. Logical reasoning questions were also asked. Both the first half and the second half were conducted on a single day and was very tedious.
Round 2 After qualifying the first round, which was nothing less than a programming marathon, we were fast-tracked directly to the HR round. They asked simple questions about our family background, parent's occupation, why FSS, what errors you made in the previous code and how would you propose to solve it now. Any questions from our side were also addressed. Basically, they had an upper as well as lower cut-off, those who scored in between were shortlisted. At last, they selected some 20 students and I was one of them :) Just focus on your programming skills and hone your DSA knowledge. Practicing from GeeksforGeeks DSA questions was of great help. Thank You.
About This Question
This is a reported interview question from a financial software systems interview for a swe role during the recruiter round reported in 2019.
It covers the following topics: Linked List, Dynamic Programming, Sql, Probability Stats, Backtracking .
Difficulty rating: Easy
More Financial Software Systems Interview Questions
About Financial Software Systems Interview Reports
This question was reported by a candidate who interviewed at Financial Software Systems. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Financial Software Systems are the higher-signal extractions to take from this report.
For broader preparation context, the Financial Software Systems interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Financial Software Systems reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Financial Software Systems Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Financial Software Systems reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.