Sai Harsha Nandanuru

I’m part of a cross-functional team developing a secure, cloud-ready web application that enables investment bankers and financial analysts to log billable hours while traveling or working remotely—especially when disconnected from the company network. The solution streamlines time tracking and reporting, which is crucial for internal billing, compliance, and productivity analytics. My focus lies in backend development using Spring Boot, integrating robust data services and cloud infrastructure while supporting a responsive React-based UI.

Key Responsibilities:

• Built the backend for a web app that helps financial analysts log their work hours while traveling, even without access to the company network.
• Created easy-to-use APIs with Spring Boot that power dropdowns and other app features, making the user experience smooth and responsive.
• Worked with both SQL and NoSQL databases to store and fetch data quickly and reliably for the app.
• Helped deploy the app to the cloud using Azure and worked with WebSphere servers to keep everything running securely and smoothly.
• Supported the front-end team by making sure the backend data connects well with the React user interface.
• Took part in regular planning meetings to understand what the users needed and turned those ideas into working features.
• Made updates and improvements based on feedback from real users, helping them save time and avoid frustration.
• Worked with the team to test, deploy, and maintain the app so it’s always ready and reliable for bankers on the move.

I worked on a backend system called Zookeeper Pool of Locks (ZKPL), which helped control the number of data requests going to systems like Elasticsearch to avoid overload. I also worked on data matching, address correction, and handled some data movement and processing tasks.

Key Responsibilities:

• Built a locking system using Java and Zookeeper to safely control how many requests were sent to Elasticsearch, avoiding slowdowns and crashes.
• Helped connect large datasets from HDFS to Elasticsearch for matching and comparison, making it easier for teams to find and analyze the right data.
• Created REST APIs to share matched data with other systems and users in a simple and clear way.
• Used SOAP services to clean up and correct address data through a DQM server, improving overall data quality.
• Wrote code to move and process large amounts of data (ETL), helping different systems share and use information more easily.
• Worked closely with other developers to make sure the system was stable, fast, and easy to use.
• Made regular improvements to backend logic based on team needs and helped solve issues quickly when they came up.

I worked with Java, SQL, and Spring Boot to support internal applications and reports. I also helped analyze store data and improve small backend features that supported business operations.

Key Responsibilities:

• Helped build and improve internal tools using Java and Spring Boot that supported everyday store operations.
• Wrote SQL queries to pull useful data from databases and shared insights with the team to help with decision-making.
• Supported small backend features and fixed bugs in existing code to keep systems running smoothly.
• Assisted in testing new features before they went live, helping catch issues early and save time.
• Learned from senior developers and took part in team discussions to understand how real-world retail systems work.
• Helped analyze sales and store data, giving the team a better view of customer patterns and stock movement.

Wizart was ań implementation partner for my role in the QA automation team at Citi Bank. We helped make sure the bank’s applications worked smoothly by writing automated tests, reducing the need for manual testing and catching bugs early.

Key Responsibilities:

• Wrote automated test scripts to check if Citi Bank’s apps worked correctly, helping reduce manual testing time.
• Found and reported bugs early in the development process, making the apps more reliable and stable.
• Worked with the development team to understand new features and made sure tests were ready before releases.
• Ran regular test cycles and tracked results to keep the team updated on the health of the software.
• Helped improve testing processes by suggesting small changes that saved time and effort.
• Learned how large banking systems work and followed strict testing rules to keep data and processes safe.