CV: senior software engineer

Name of Degree

Name of University

Bachelor of Engineering in Computer Science

MS: Informatics 

MS: Space Science and Technology

(undergoing thesis work)

• Understanding and quick grasping of customer projects, got broader view of the whole system and environment in forehand.
• Individual requirements were documented by assigning ID's.
• Every stage of requirement collection further progressed on approval by the customer.
• Understanding the level of dependency involved with third party projects.
• Anticipated project stages and identify occur-able issues and problems in advance, maximum possible doubts were discussed with the customer, and documented accordingly.
• Made sure which requirements could be freeze-able and which could be modifiable at later stage.
• Every-stage of customer interaction was communicated and discussed with the respective managers
• SRS written and reviewed and approved by customer along with the project managers.

Project development: 

• Training to team members :-

Prepared presentation slides and seminars, prepared manuals and training materials. Identified new tools which increase work efficiency. Proposals for new methods for project managements and quality measures. 

• Helped system test team members to develop system test plan, review meetings, comments, approval of system test plan.

• Project estimation:-

Identify and divide project into subsystems /modules and divide further till clear-cut realization of every aspect is achieved in forehand. Mean value of estimated would be probable code size of all the team members is taken. PROBE criterion is followed to get the final estimation value based on code size. Based on this achievable time deadlines for sub-modules were planned.

• High level design

Modules were divided considering requirement Id's. Architecture, Data flow diagrams, algorithms, state diagrams and sequence diagrams for each function are specified. Dependency specification and external interfaces with/for third party systems are well defined. 

• Integration test plan, Low-level design, unit test plan preparation

Review, comments, modification as per review comments 

• Coding

Code review, code changes, follow coding standards, run tools to identify common errors, before coding, followed checklist for common errors, code review sessions to analyse every aspect of code with other team members, exchanged lessons learned from, previous projects and suggested better implementation methods and pointed reasons for such necessary changes,

noted down all code comments are carefully documented for future use

code modifications as per code  comments.

Root cause for any coding mistakes were analysed and detected, and the information is shared with all the team members as lesson learned.

Code review sessions improved the ability to identify bugs at earlier stage and improve implementation methods and get matured in programming 

• Project testing:

Unit testing and integration testing and performance testing were performed.

Tested against common errors checklist, follow test plans, testing tools used for better efficiency, written test scripts for regression testing.

Under all above stages metrics as effort and time taken for intermediate goals, review comments, final code size, defects vs code size, code size vs number of test cases. All test metrics are submitted to higher management as inputs for future decision making and for planning resource allocation and better understanding of team capabilities.

Also maintained the defect numbers far less than the max threshold specified by quality team, and system test team. 

• Project support and maintenance

Support for customer problems, debugging crashed environment, defect identification and resolution.

Name of the Thesis

• In depth study on already published research papers covering the related topic.
• Problem statement, thesis definition, task breakdown, timeline estimation and intermediate presentation delivery.
• Assembling the rover hardware, developing image processing software using Intel’s OpenCV library.
• Indoor surface testing and outdoor surface testing.

Name of the Project

Olite DB is used to store maps data.

• Traveled to HQ, attended the technology transfer meetings with the customers.
• Quickly grasped the customer systems, proposed solution criterion.
• Prepared training material for the team members in India.
• The prototype xyz board was brought up with CE Linux, and module by module olite porting was made, starting with resolving compilation errors, request for code changes were well documented.
• Unit testing for the modified code part, integration test and regression test were carried out. Finally performance test was done. Defects were resolved and metrics were documented, giving clear reasons for changes.

Name of the Project

Coco cola

Specific tasks include:

• Development and maintenance of framework that permits both interactively and automatic data processing
• Strong hands-on development expertise in the area of RTOS's (VxWorks, DOPRA) and embedded platforms.
• Having expertise and analytical ability in debugging software in an embedded environment.
• good understanding of writing low level software which interacts with the hardware directly
• Participated in optimisation, evaluation, and tests
• Interacted appropriately with customers and higher managers promptly on regular basis. Discussed every detail on project progress and problems faced and timeline for milestones.
• Contributed to the maintenance of the overall system, including configuration control and versioning
• Organised and helped system testing team to setup the environment
• Detailed knowledge of compiler and debugger internals, target connectivity technology, identify workarounds, and solve programming problems.
• Developed tools, documentation, and/or sample applications that enhanced the usability of the products.
• Entire software development life cycle from requirements analysis through to final hand-off and maintenance/support.
• Worked on multiple, overlapping projects.
• Defined and documented best practices and lessons learned

Name of the Project

Huawei

Features:

• Dynamically loading and linking, unloading and automatically reloading of DOPRA components (which are compiled as ELF files for the appropriate platform).
• Debugger module (GDBServer) DDM which can be used to debug a DDM.
• GDB application on the relevant platforms.
• Digital signing and verification framework (for verification of DDMs).
• DDMS related CLI commands
• interface for loading DDMS across a TFTP connection and on a local file system.
• support for Dynamic component (de)registration.

• Responsible for all phases of software development, including design, coding, integration, and debugging of major portions of software.
• Design and develop organized, easy to read and modify software code 
  • Remote Debugging, also used emulators, analyzers and similar tools 
  • Documentation of software designs and code.

      • Performed functionality and performance testing 
      • Prepared status reports 
      • End user documentation

Name of the Project

Huawei

-

Name of the Project

Huawei

Name of the Project

Huawei

At HUAWEI Technologies R&D center, Bangalore and China. 

Name of the Project

Huawei

•  Created portion of detailed technical design document and participated the design reviews.

•  reusable, reliable, and scalable solution was provided

•  Worked closely with QA to define and deliver the highest quality product

•  Provided technical guidance and assistance to other software engineers.

•  Enhanced and maintained existing capabilities.

•  Adhered to release/project schedules and milestones.

Name of the Project

Huawei

involved with all stages of the development process

Identified project risks and submitted mitigation plan to the management. Planned realistic implementation schedules,

Made sure the functionalities are compatible and inter operable with industry standard software. Performance, scalability, reliability are given more importance. Adhered to development goals and principles.  
• Estimate engineering effort, plan implementation.

Name of the Project

Huawei

Support to operations and trouble shooting

Name of the Project

E2000-E Porting to HP

Thales. France

About the Project

Responsibilities include porting existing software from Compaq true 64 to HP-UX, then worked on to get the product up and running.

This includes working with engineers from other teams across the company on best practices and shared approaches. Also worked closely with Quality Assurance (QA) engineers to ensure quality throughout the development cycle and porting activity. Wrote development specifications, incorporate specification feedback from QA, engineering team. Developed task lists based on completed specifications. Porting activity including recompiling, solving shared library issues, compiling issues, platform related issues and endian issues, code modifications, made requests for changes, carried out all the test cases.

Working closely with the QA team to ensure high quality and a consistent cross-platform experience.

• With effective communication and ability to clearly articulate complex problems and solutions in terms that others can understand all the phases carried out smoothly.
• Strong sense of accountability in meeting commitments and achieving results.
• Completed the project on time, being self motivated found solutions to critical problems during porting

Responsibilities included were architecture, design and development of software, to include requirements analysis, software design, coding, software integration, testing, debug, and maintenance.

Worked closely with team-mates to solve problems, transfer knowledge, and complete the project successfully on time.

Name of the Project

Writing drivers for Player (robotics platform based on client-server architecture). Implementing client side MobRob protocol.

Developing user Interface using Java3D, live video from rover is augmented with laser scanner data for displaying depth information as well as all the other sensor information for navigation. 

Hardware:

Building the rover, assembling hardware parts, interfacing steering and drive motors and encoders, Gyroscope, GPS receiver to C167 micro-controller running MobRob OS. Interfacing PC104 with camera, laser scanner, Inclinometer and C167 controller.

Name of the Project

Software:

Ground station monitoring software for the display of sensor data received onboard the Cansat. Onboard software i.e., device drivers for sensors interfaced to the microcontroller. 

Hardware: Assembling and interfacing sensors with microcontroller.