Minor corrections
This commit is contained in:
parent
bbaa77dc99
commit
b6ce8d079c
3 changed files with 7 additions and 7 deletions
|
@ -9,7 +9,7 @@
|
|||
devShell."${system}" = # architecture must be specified for devShell
|
||||
pkgs.mkShell {
|
||||
name = "resume";
|
||||
buildInputs = with pkgs;[ texlive.combined.scheme-medium ];
|
||||
buildInputs = with pkgs; [ texlive.combined.scheme-medium ];
|
||||
};
|
||||
};
|
||||
}
|
||||
|
|
BIN
resume.pdf
BIN
resume.pdf
Binary file not shown.
12
resume.tex
12
resume.tex
|
@ -65,7 +65,7 @@
|
|||
}
|
||||
% END RESUME DEFINITIONS %%%%%%%%%%%%%%%%%%%%%%%
|
||||
|
||||
\begin{document}
|
||||
\begin{document}
|
||||
\vspace*{-40pt}
|
||||
|
||||
%==== Summary ====%
|
||||
|
@ -121,9 +121,9 @@ Designation: & \textit{Associate Software Engineer}
|
|||
\vspace{-1mm}
|
||||
\begin{itemize} \itemsep 1pt
|
||||
\item PAY.ON offers a white-label payment structure for omni-channel transaction processing through one payment platform: eCommerce, mCommerce and mobile point-of-sale. The payment platform is fully PCI-certified, and meets the highest technology and security standards.
|
||||
\item Development experience in PAY.ON includes platform maintenance, mandate implementations, and end-to-end feature development across multiple modules. Further experince includes support resolution, platform monitoring and ensuring stablility across the stack. Acquired strong understanding of development process, tooling and infrastructure.
|
||||
\item Exposure to multiple payments APIs across different payment acquirers, and data transformation for each. Domain level understanding and integration experice in eCommerce payments industry.
|
||||
\item Agile (Scrum and Kanban) development experience in multiple teams on separate platform modules, inclusing APIs, configuration, business logic, platform security and front-end.
|
||||
\item Development experience in PAY.ON includes platform maintenance, mandate implementations, and end-to-end feature development across multiple modules. Further experience includes support resolution, platform monitoring and ensuring stablility across the stack. Acquired strong understanding of development process, tooling and infrastructure.
|
||||
\item Exposure to multiple payments APIs across different payment acquirers, and data transformation for each. Domain level understanding and integration experience in eCommerce payments industry.
|
||||
\item Agile (Scrum and Kanban) development experience in multiple teams on separate platform modules, including APIs, configuration, business logic, platform security and front-end.
|
||||
\item \textbf{Technologies}: Java/Spring, Spring Web MVC, PostgreSQL, Debian/Linux, Git/Gerrit
|
||||
\end{itemize}
|
||||
|
||||
|
@ -138,7 +138,7 @@ Designation: & \textit{Intern} \\
|
|||
\item Universal Payments Framework (UPF) provides purpose-built payments functionality to orchestrate all aspects of payments processing for any payment type, any channel, any currency and any network.
|
||||
\item Developed and maintained interfaces between various payments APIs, with differing protocols such as SOAP, ReST, ISO 8583, APACS etc. Acquired understanding of payments domain and API implementations.
|
||||
\item Implemented and extended internal test framework to interface with UPF, to allow automated test execution with simple Excel test generation. Implemented automatic test-case generation to ease on-boarding QA staff.
|
||||
\item \textbf{Technologies}: Java, XML, Subversion, Bash
|
||||
\item \textbf{Technologies}: Java, XML, SVN, Bash
|
||||
\end{itemize}
|
||||
|
||||
% \pagebreak
|
||||
|
@ -170,7 +170,7 @@ Designation: & \textit{Intern} \\
|
|||
\textit{International Journal of Engineering, Research and Technology} \\
|
||||
\vspace*{2mm}
|
||||
|
||||
{\textbf{Magnetic Levitation using Real-Time PID}} \hfill Mar 2019\\
|
||||
{\textbf{Magnetic Levitation using Real-Time PID}} \hfill Mar 2016\\
|
||||
\textit{National Conference for Students in Electrical and Electronics Engineering, VIIT} \\
|
||||
\vspace*{2mm}
|
||||
|
||||
|
|
Loading…
Reference in a new issue