Professional Documents
Culture Documents
Prakash Malik - DevOps
Prakash Malik - DevOps
Objective
A flexible, dedicated & self-disciplined individual, seeking an opportunity to play a
challenging and creative role in development, planning and research with commitment to serve
the organization for its growth and development.
Professional Profile
14+ years working Experience in Software Development, Infrastructure Support, DevOps,
SRE and with Build and Release in Software fields.
Currently working in DevOps Engineer with CI/CD, Jenkins, GitHub, Ansible,
SonarQube (Code Quality check), AWS, Dockers, Terraform , Build ( Maven) and Release
with shell scripting.
Having working Experience in Infra/Application support, Production Support.
Good Knowledge in cloud in various services like VPC, EC2, IAM in AWS Storage
Services (S3), Load balancing, Autos scaling.
Functional expertise in programming in C++ in UNIX/Linux Environment for developing
various applications.
Having Knowledge in networking and socket programming, protocols like TCP/IP, UDP, and
IPC.
Working knowledge in IBM MQ Series, WebLogic Console, Control-M, Apache, Tomcat.
Working knowledge in ITRS Genes Monitoring Tool, TWS.
Exposure in GDB 3.3 Debugging Tool, CVS, SVN and Make File.
Strong knowledge in Oracle9i (SQL & PL/SQL), Pro*C.
Understanding of complete SDLC (Agile Method), ITIL processes, Jira and Confluence.
Strong working knowledge in UNIX (SUN SOLARIS) & LINUX Environment and Shell
Scripting in UNIX and Power Shell.
Strong working knowledge in Finance, Investment Banking and Storage, HealthCare,
Telecom, supply chain domain.
Professional qualification
Master’s in computer application (M.C.A) having 67 % from Utkal University,
Orissa in 2004.
MPhil in Mathematics having 70% from Utkal University, Orissa in 2006
MSc (Mathematics) from Utkal University in 2000.
Technical Summary
Language : C++,Core Java, Pro*C.
Scripting Language : Shell Script, Python
Operating System : UNIX (Sun Solaris), Linux, Xshell.
Database : Oracle 10g, PL/SQL,
Protocol : TCP/IP, UDP,RTP,RTCP,IPC.
Supporting Tools : GDB, GCC, CVS, Make file, Putty, Geneos, WebLogic, MQ
DevOps Tools : Jenkin, AWS, Azure, GIT, BURT, CI/CD, Git, Bitbucket,Docker
Monitoring Tools : Kibana,Grafana, ELK, Geneous.
Project Profile:
Project#1
Title : RTPE(Real Time Payment Engine)
Organization : TCS Bangalore
Client : ING Bank(Netherland)
Operating System : Linux (RHEL6)
Scripting : Unix Shell scripting
Process : DevOps (Jenkin, Git, Ansible, CI/CD), Azure, AWS and Terraform.
Tools : TWS, ServiceNow, CyberArk (Access), Kubernetes.
Database : Oracle(11g)
Duration : From Oct 2020 till date
Role : Team Lead
Team Size : 10
Description:
This project is basically Banking domain; ING Bank (Netherlands) is a Banking services which is
involved to Banking services to customers. There are two modules i.e. IncomingRecall and
outgoingRecall Module. There are two applications which is running both Tibco application and Java
application. All the Java application is running on ING Private cloud Machine. Recall means requesting
our money through Bank from Depter to Creditor. Whenever Request has raised by other bank
Customer to ING Bank only that is IN-ComingRecall and whenever Recall Request is raised by ING
Bank/ING Customer that that is call OutgoingRecall.
Description:
This project is basically financial domain; Ameriprise Financial Inc. in USA is a financial service which is
involved to financial services to customers. There are four modules i.e. Source Module, Pre-staging
Module, Staging Module, Final Module. This project purely follows the DevOps process. There are
fifteen applications of this project i.e SAT,SRT,WTM,FEDS,ADTrax,Auditrax,Hotlist,Compliance
Tracker,PTA,SAM,Riskconnect,HERT,eDocs,CLRDS and AFD. This project mainly track the financial
case involving suspected Money Fraud, Money Lanundering,Investigation,Physical Security and alert
on artifacts for possible anomalies. This system will collect all data from all modules and also produces
the SAR’S (Suspicious Activity Reports) for the Governments. This also provides the Business users an
interface to investigate alerts/case.
Project # 6
Title : Summit Application.
Client : Misys (Romania)
Organization : Symphony Services Corp Pvt India Ltd.
Language : C++, Pro*C.
Database : Oracle9i( PL/SQL)
Operating System : UNIX
Duration : From Sept -2008 to Oct- 2009
Role : Team Member
Description:
Summit provides integrated Trading, Operations, and Risk Management software products to
banks, financial institutions, and capital markets participants worldwide. Summit has
developed business-specific solutions on a common infrastructure, for Fixed Income, Treasury,
Derivatives, and Commercial Lending. Straight through trading and processing allows users to
consolidate businesses, minimize operation risk, reduce transaction processing costs and obtain
intra-day risk management information at the desk or enterprise level. Worldwide portfolios
can be managed locally or centrally. Summit is a modular, high-performance system based on a
real-time architecture that is open, scalable, and extendable. Summit’s architecture is designed
to allow customers to take full advantage of their existing technology infrastructure, and to
extend and customize the system according to their business needs. Client’s may extend
Summit to meet their specific needs using our various APIs to access Summit’s functionality
from current programming technologies and components such as .NET, C++, XML, Java, and
VB. The system scales from a single trading desk to global implementations involving
thousands of users and trades per day.
Role & Responsibilities
Coding in C++.
Involving in understanding the Business flow
Was involved in the coding phase of the project.
Understanding the HLD and LLD of the project.
Tasks including fixing bugs & Enhancements into the existing projects.
Also wrote test plans procedures for performing unit testing
Writing SQL Queries.
Using the debugging tools gdb for debug the code.
Was using the CVS for version control tool.
Project # 7
T2L is the EMBARQ application which is responsible for formatting customer billing
statements. Our main objective is how we will extract the CRB billing data from Mainframe
(CBL) & will run this CRB billing data in UNIX environments. If it runs successfully then this
CRB billing data will send in to Mainframe (CBL) environments. After execute this CRB
billing data in mainframe it creates print-ready invoices in IBM AFP format.