Yovo Manolov

• Project: Platform for Loan management

Loan management bank application for internal usage.

- Methodology: waterfall

- Test env deployments and servers were maintained by the devs: Microsoft Server (Apache Web server as a gateway to Apache Tomcat containers)

- Manual testing done by devs before passing the ticket to the QA team and deploying it to QA env

- SOAP communication with ESB services and other applications.

- Exposing new SOAP services as well as consuming such in tha application

Tools & Technologies:

Java EE, Eclipse; Struts 2, JSP, JSTL, MS SQL Server, JPA, CVS, Apache Web Server with Apache Tomcat web container. Communication with other apps with ESB SOAP services. Exposing different services using the SOAP protocol within the same application.

Project: Early Warning Signals

• Project: Early Warning Signals

Deals with delayed loans and management protocols for the delayed loans, etc.

Struts 1, again with MS SQL Server. Enterprise application wrapped as EAR from three different projects and deployed to IBM WebSphere. It was relying on lots of stored procedures interacting with the backend. Transactional operations in the stored procedures. Maintaining the front end as well as the back end. Waterfall methodology. During this project life span I was mentoring 2 trainees with the knowledge I had gained from the first project I worked on.

Tools & Technologies:
Java EE, Eclipse; Struts 1; MS SQL Server (stored procedures as main business logic), JPA, CVS, IBM WebSphere. Communication with other apps with ESB SOAP services. Exposing and consuming SOAP services.

• Project: Credit register dependency system retirement
  

Longer project with a release after an year of development of big functionality which helped to retire another system. With this implementation the organisation managed to cut the costs associated with the retired system. We delivered custom implementation to replace the old system . I was able to take the decisions on how to implement the code inside the monolith application that was going to replace the retired system. During the project life span I was mentoring a new team member. Team of seven members: 4 Developers (2 Java, 2 FICO OMDM devs), 1 QA (manual + automation tests), Product Owner and Project Manager, Scrum.

Tools & Technologies:
Java EE, Eclipse; Struts 2; MS SQL Server, JPA, GitLab, Git, Jira, Apache Web Server with Apache Tomcat web container. Communication with other apps with ESB SOAP services. Modifying and consuming, different SOAP services.

Project: Payments reformatting system
The project was about reformatting payments between big corporations and banks. Basically, we had input text file for payments and an output file requirements. And our job was to make an implementation which will reformat the payments. The benefit I had from working on this project was learning how to write code following clean code and architectural best practices and writing unit and integration tests. I worked with more experienced developers and was able to learn from them. I learned how to do PR reviews, how to work with Jenkins on user level. Not to configure Jenkins jobs, but just to use results from the builds, such as logs, if the job fails. We were following the Scrum principles.

Tools & Technologies:

Java EE, InteliJ, PostgreSQL, Junit4/5, BitBucket, Jenkins JBoss application server with dockerized local environment. Jira, Scrum, Kanban, Windows

Project: Ticket management application

The application was hosted on very big cloud infrastructure with multiple shards and tenants on each shard. There was centralized logging and monitoring implemented with Splunk and SignalFX. I was in a team supporting the monolith module responsible for query search (Not by my choice. I like cloud-native development, but it still was a valuable experience). While it was rewritten as a microservice by another team, our team was responsible for optimizing the queries translation from custom query language to JQL. We also had SLO targets monitoring, and investigation of performance drops. We had a rotation role responding to the questions and requests of other teams as well as on-call rotation with my teammates during which we supported failures in our module 24/7. What I learned from this project was to try to be proactive in my work. Take more decisions on my own and try to suggest improvements to the system. We had CI/CD in place and I was responsible for deploying my implementations on pre-prod and prod environments using feature flags and gradual rollout strategy. We used LaunchDarkly for feature flag management.

Tools & Technologies:

Java 8/11, InteliJ Postgres DB, Docker, Mac OS, Git, BitBucket, LaunchDarkly, SignalFx, Splunk, Confluence, Jira

I was maintaining a fleet of microservices focused on account and access management. I maintained their Confluence docs. Clarified business requirements, did code reviews, and worked closely with other teams and different professionals: QAs, POs, TLs. There were performance improvement tasks, DB investigations, etc. My latest task was about integrating Google ReCaptcha in login and registration flows. I was also responsible for delivering release artifacts for each task and sometimes providing them for procedures such as GLI certification. In my first weeks,I improved the documentations of many services and built sequence and activity diagrams with PlantUML to understand the services well enough and provide clarity for other teams. I also maintained the Swagger docs up to date with every task. During my time here I took part in the onboarding of one new colleague as well.

Technologies:

Spring Boot, Java 11, Microsoft SQL Server, RabbitMQ, Swagger, Jenkins, Maven, Nexus, plantUml, Grafana, Linux shell, ssh