Jan 2015 – Jul 2016 · 1 yr 6 mos · Noida, Uttar Pradesh, India

Feb 2012 – Dec 2014 · 2 yrs 10 mos · Greater Hyderabad Area

• Microsoft Office on Android (Word, Excel and PowerPoint)
• Ownership of Smart Art objects (April 2014 – till date)
• Working on Office Art (graphics) components across office apps on Android platform. In this area, I currently own the rendering and editing functionality of Smart Art objects which are basically combination of predefined multiple shapes objects provided by default in Office Apps for better visualization of scenarios like hierarchy management, project structure etc…
• Enable build system for Android (Aug – 2013- Jan – 2014)
• Due to cross platform issues, we can’t directly make use of existing Microsoft office build system, I have worked on the build system integration for Android platform where we have enabled the usage of clang (compiler used for compiling c++ code for Android platform) compilation for building the existing Office code in windows build environment for Android applications.
• Fixing cross platform issues in existing office code base
• I have worked on fixing the cross platform issues (MSVC vs Clang) in existing office code base, I have created a wiki containing the common platform issues which I have encountered and also developed a tool which fixes the common errors automatically in the code without any user intervention.
• Improving Keyboard Shortcut support for PPT Next (Feb 2014 - March 2014)
• Worked in the addition of various keyboard shortcuts for PPT Immersive (PPT for windows 8). Along with this team was involved in bug fixing for Oart in PPT Next.
• Web-page Snapshot tool: (Sept 2012)
• When tester reports a rendering issue in a web-page he just share just a static image. Developer have to repro whole setup even though he just want to know what is the CSS applied. Lot of bugs are closed no repro if there are once in a blue moon bug.
• Lync web app (LWA): ( Mar 2012 - Aug 2012 )
• Worked in the final stabilization of LWA (Lyn Web App).

Dec 2010 – Jan 2012 · 1 yr 1 mo · bangalore

• I was part of team which was responsible for charging interface of content delivery solution provided by Movik Networks. Charging can be Online-Charging/ Pre-Paid or Offline-Charging / Post-Paid.
•  Online charging is implemented using Diameter protocol (Authentication, Authorization and Accounting protocol used in 3G and 4G networks)
•  Offline-Charging is implemented using BX interface. Charging Data Records (CDR) are generated using BX interface. Worked in redundancy support for CDR generation.

Jul 2007 – Oct 2010 · 3 yrs 3 mos

• Worked in development of MME (Mobile Management entity) node of LTE / 4G networks.
•  Worked in the development of Security module for Encryption and Integrity protection of the messages
•  Development of S6A Demeter protocol interface between MME and HSS (Home Subscriber Server). HSS contain all the authentication and authorization data.
•  Development of EGTP protocol interface parser module between MME and SGW(Service gateway.
•  Development of HSS S6A simulator.
•  Development of SGW EGTP simulator.
• Worked in the development of Diameter protocol. DIAMETER protocol that is used for exchanging Authentication, Authorization and Accounting (AAA) related information.
• Responsibilities:
•  High-Availability and Non-Volatile memory support for the Diameter RF Interface.
•  Generic Diameter Application Module (GDAM): Involve in the GDAM development. It is a generic module that implements all the common functionality of a Diameter interface. This functionality is session maintenance, encoding/ decoding etc.
•  GDAM Solaris Porting: Porting of Aricent GDAM base from Linux to Solaris platform.
•  Development of EAP interface over GDAM base.
•  Development of WM interface which is integration of EAP and NASREQ under one module.
•  C-Based API: Making the API C-Based such that customer application written in C programming language can include API of Diameter code written in C++ programming language.
•  gSOAP integration: this activity basically involves removal of XERCES XML parsing in DIAMETER and doing the same using gSOAP parser.
•  QNX Porting: Porting of Aricent DIAMETER on real-time operating system QNX (Qnix) Platform.
•  Code generation tool to generate various interface by just reading the RFC/ Specifications. By this tool all the Diameter interfaces are generated by just providing specification of message to the tool.

Jan 2007 – Jul 2007 · 6 mos

• Worked in the develpment and testing of RO/ RF Diameter protocol interface for online and offline changing.