0% found this document useful (0 votes)
55 views4 pages

Deloitte Interview

Interview

Uploaded by

bisht3.dheeraj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
55 views4 pages

Deloitte Interview

Interview

Uploaded by

bisht3.dheeraj
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

​.

Cheat Sheets​
🔹 Java Cheat Sheet (Core Concepts)​

​●​ ​OOPs Principles:​

​○​ ​Encapsulation → Hiding data with getters/setters.​

​○​ ​Inheritance → Parent-child class reuse.​

​○​ ​Polymorphism → Compile-time (overloading), Runtime (overriding).​

​○​ ​Abstraction → Abstract classes & Interfaces.​

​●​ ​Collections Framework:​

​○​ ​
List​​→ ArrayList, LinkedList.​

​○​ ​
Set​​→ HashSet, TreeSet.​

​○​ ​
Map​​→ HashMap, TreeMap.​

​○​ ​Iterators & Streams API.​

​●​ ​Exception Handling:​

​○​ ​Checked vs Unchecked.​

​○​ ​
try-catch-finally​ throw​
​,​​ throws​
​,​​ ​.​

​●​ ​Multithreading Basics:​

​○​ ​Thread class, Runnable interface.​

​○​ ​
synchronized​​keyword.​

​○​ ​Executors & Thread pools.​

​●​ ​Important Keywords:​

​○​ ​
final​ static​
​,​​ transient​
​,​​ volatile​
​,​​ ​.​
🔹 SQL Cheat Sheet​

​Joins:​

SELECT [Link], [Link]​



FROM Employees e​

INNER JOIN Departments d ON e.dept_id = [Link];​

​●​ ​Types: INNER, LEFT, RIGHT, FULL.​

​●​ A
​ ggregate Functions:​
COUNT, SUM, AVG, MIN, MAX, GROUP BY, HAVING​
​ ​.​

​Subqueries:​

SELECT name FROM Employees​



WHERE salary > (SELECT AVG(salary) FROM Employees);​

​​

​●​ ​Indexes:​​Improve performance but slow down inserts.​

​Transactions:​

BEGIN;​

UPDATE accounts SET balance = balance - 500 WHERE id=1;​

UPDATE accounts SET balance = balance + 500 WHERE id=2;​

COMMIT;​

​●​

🔹 Banking Terms Cheat Sheet​



​●​ ​CBS (Core Banking System):​​Centralized system for​​all banking operations.​

​●​ E
​ OD/BOD Jobs:​​End-of-Day / Beginning-of-Day batch​​jobs for reconciliation &​
​settlements.​

​●​ ​Reconciliation:​​Matching financial records (e.g.,​​payments vs account balances).​

​●​ ​KYC (Know Your Customer):​​Verification of customer​​identity.​

​●​ ​AML (Anti-Money Laundering):​​Regulations to prevent​​illegal transactions.​


​●​ ​RTGS/NEFT/IMPS:​​Real-time and batch payment systems.​

​●​ ​SWIFT:​​Global messaging network for international​​payments.​

​●​ ​Basel III:​​Banking risk & capital regulation.​

​●​ ​Digital Banking:​​Internet banking, wallets, APIs,​​Open Banking.​

📝 2. Interview Q&A​

🔹 Technical Questions​

​ 1.​​Explain OOPs concepts with banking examples.​
Q
👉​ ​​Inheritance:​​SavingsAccount extends Account.​
👉​ ​​Polymorphism:​​Different loan types (HomeLoan,​​CarLoan) overriding interest calculation.​
👉​ ​​Encapsulation:​​Customer details hidden with getters/setters.​
👉 Payment​​implemented​​by​​
​ ​​Abstraction:​​Abstract class​​ UPI​ NEFT​
​,​​ ​.​

​Q2.​​How would you optimize a slow SQL query?​

​●​ ​Use proper indexes.​

SELECT *​
​●​ ​Avoid​​ ​.​

​●​ ​Use joins instead of subqueries where possible.​

​●​ ​Check execution plan.​

​●​ ​Partition large tables.​

​Q3.​​What happens if an EOD batch fails?​

​●​ ​Identify failure point via logs.​

​●​ ​Rollback incomplete transactions.​

​●​ ​Communicate with stakeholders (Ops/Compliance).​

​●​ ​Rerun the job or trigger manual intervention.​

​●​ ​Document root cause & implement monitoring.​


​Q4.​​Difference between HashMap and ConcurrentHashMap in Java?​

​●​ ​HashMap → Not thread-safe.​

​●​ ​ConcurrentHashMap → Thread-safe, uses segmentation for concurrency.​

​Q5.​​How would you design an API for Loan Origination?​

POST /loan/apply​
​●​ ​Expose endpoints:​​ GET /loan/status/{id}​
​,​​ POST​
​,​​
/loan/approve​
​ ​.​

​●​ ​Security: OAuth2/JWT.​

​●​ ​Validation: Ensure KYC, credit score checks.​

​●​ ​Idempotency for requests (avoid duplicate loan creation).​

🔹 Scenario-Based Questions​

​ 1.​​A critical batch job failed during EOD, delaying​​payments. How do you handle it?​
Q
👉​ Approach: Incident triage → Logs → Rollback → Communicate with stakeholders → Fix​
​→ Prevent recurrence.​

​ 2.​​Client asks for a new regulatory report within​​2 days. What do you do?​
Q
👉​ Approach: Gather exact requirements → Estimate impact → Prioritize tasks → Leverage​
​existing reporting framework → Deliver MVP report → Continuous enhancements.​

​ 3.​​You are leading a team and a junior developer​​introduces a bug in production. How do​
Q
​you manage?​
👉 ​ Approach: Fix issue immediately → Conduct RCA → Mentor junior → Introduce peer​
​reviews & automation.​

​ 4.​​How would you migrate a CBS from on-prem to cloud?​


Q
👉​ Approach: Assessment → Data migration strategy → Security/compliance alignment →​
​Phased migration → UAT & rollout → Monitor performance.​

​ 5.​​During sprint planning, you find client requirements​​are unclear. What do you do?​
Q
👉​ Approach: Raise as blocker → Conduct clarification session with BA/client → Document​
​assumptions → Adjust estimation after clarification.​

You might also like