<UL>
  <LI>Part of the team, which designed - the signal conditioning for weather 
  sensors, the A/D converter and microprocessor modules. 
  <LI>Added software features that allowed the calibration of the system at 
  site. </LI></UL><STRONG>T-TRONICS TEST EQUIPMENT<BR>Oct 1990 to Dec 1991 
</STRONG><BR>
<P>Level 1 and 2, customer support engineer for Integrated Circuit testing 
equipment and universal device programmers. Helped marketing team in organizing 
presentations and customer training. </P><STRONG>EDUCATION </STRONG>
<P>Bachelor of Engineering Electronics [equivalent to a BSEE in US], University 
of Pune, India 1990 </P>
<P align=right><A 
href="http://www.portnov.com/FreeResumeSample/EmbeddedSystemsResume.htm#Up">Up</A></P>
<HR>
<A name=2>
<H2 align=center>Resume 2</H2></A><B><FONT size=4>Kumar Verkar 
</FONT></B><BR><BR>
<P></P><STRONG>Objective: </STRONG>
<P>Seeking challenging position as senior Software Engineer/ Design Engineer in 
the field of design/development where there is a lot of scope to develop my 
knowledge, potential and skill. </P>
<P>REFERENCES Available upon request</P><STRONG>Educational Details : </STRONG>
<P>Masters in Technology M.Tech. in Computer Science from Computer Science 
Dept.--University of Pune India . <BR>Bachelor in Engineering B.E. in Electrical 
Engineering from Govt. Engineering College-Bilaspur India . 
</P><STRONG>Technical Proficiency : </STRONG>
<UL>
  <LI><EM>Technology/Protocol :</EM> DWDM, CWDM, SONET OC-192, OC-48 based 
  product , k-56 Modem v.90 
  <LI><EM>OS :</EM> VxWorks, WINDOWS NT, WINDOWS CE, DOS, UNIX, LINUX 
  <LI><EM>Languages :</EM> C, C++, VC++6.0, ASSEMBLY, FORTRAN, PASCAL 
  <LI><EM>TOOLS/ Platforms :</EM> VxWorks shell, DiskOnChipflash , LEX, YACC, 
  SOFTICE,STAR-TEAM PROFESSIONAL 3.0, DDK/SDK, WBT 
  <LI><EM>Hardware Platform :</EM> MPC8260, m68k, x86, Cyrix MediaGx 
</LI></UL><STRONG>Work Experience : </STRONG>
<P>Got more than five years of experience in the area of Systems Architecture, 
Design and Software development, mainly on--</P>
<OL>
  <LI>Optical networking/fiber optics based product DWDM, CDWM, SONET OC- 192/48 
  . 
  <LI>Device Driver VxWorks, WINDOWS NT, WINDOWS CE and proprietary RTOS mainly 
  for telecomm card. 
  <LI>Thin client WBT- Windows Based Terminal based on WIN CE. 
  <LI>Configuration management, performance monitoring, flash 
  handling/management, SNMP, TRAP/ALARM management, user interfaces and 
  applications. </LI></OL>
<P>Here are the companies I worked on: </P>
<OL>
  <LI>Working from June 2000 to till date in Merrento Networks as a Software 
  engineer in the Engineering group. Merrento Networks is an Optical networking 
  company which provides end to end Metro and Regional solutions by providing 
  DWDM solutions for various access/protocols Ethernet, ESCON, Fiber channel 
  etc. 
  <LI>Worked from August 1999 to May-2000 in Waxonet Communications as a 
  software engineer grade-II/design engineer in the system group. Waxonet is 
  optical networking sub-system company. This company is in development of 
  optical networking ASIC s using their proven CoreCell based ASIC development 
  methodology with focused on Access/Metro and Core market. 
  <LI>Worked from july-1998 to July 1999 in SwitchUp Networks as a software 
  Engineer in the system development group. SwitchUp Networks is a system 
  development Software Company. </LI></OL>Fields of work: 
<UL>
  <LI>Requirement and system design analysis. 
  <LI>Detail design high level and low level software design . 
  <LI>Implementation/development with close interaction with marketing and 
  system/architectural group. 
  <LI>Detail interface design and implementation with various modules/groups. 
  </LI></UL><STRONG>Project Profiles: </STRONG>
<P>1. Merrento Networks: <BR>1.1 CWDM MUX/DEMUX. <BR>1.2 Automatic power 
equalization using OPM Optical Performance Monitoring . <BR>1.3 SONET 
Performance Monitoring: <BR>a. SONET PM for OC-192 <BR>b. SONET PM for OC-48 
<BR>2. Waxonet Communications: <BR>2.1 Chip Modeling to verify the functionality 
and constraints. <BR>2.2 Development of NT based driver for the SONET/ATM based 
chip. <BR>3. SwitchUp Networks: <BR>Windows based Terminal thin client 
development for remote computing based on WINDOWS CE. </P>
<P><STRONG>1. Merrento Networks Project profiles:</STRONG> </P>
<P><STRONG>1.1 CWDM MUX/DEMUX 4-Channel :</STRONG> </P>
<P>This is the current project I am into-the idea is to provide a cheaper 
transport solution to the edge/access market/customers using CWDM technology. It 
supports protocol like Fiber Channel, ESCON, Ethernet, SONET/SDH OC-3/12/48 , 
and Fast Ethernet. </P><EM>Responsibility:</EM> Design and implementation. 
<P>Mainly worked on k-56 modem v.90. All the SFP Small Form Factor and GBIC 
Gigabit Interface Controller using I2C protocol, diagnostic routines, 
configuration management and flash handling. </P>Team size: Three <BR>Status: 
Completed. <BR>Platform: MPC8260, VxWorks 5.4, C, Tornado 2.0, Tornado shell 
Tools 
<P><STRONG>1.2 Automatic power equalization: </STRONG></P>
<P>The idea is to automate the power equalization problem during ADD/DROP, 
MUX/DEMUX and Amplification to eliminate/minimize the manual intervention. This 
can be achieved by distributed software, which monitors all the related data per 
channel and attenuates per channel. </P>My role was focused on Optical 
Performance Monitoring OPM . It involves: 
<OL>
  <LI>Accumulation, analysis, processing and storage of all the data and passing 
  this information to the Node controller periodically. 
  <LI>Configuration management, database management, PM processing conformity 
  with GR-253 , flash handling. 
  <LI>SNMP interface, TRAP/ALARM handling. 
  <LI>User interface and applications. </LI></OL>Platform: m68k, Legacy 
Proprietary RTOS, WMU3000, VOA. <BR>Team size: Three. 
<P></P><EM>Responsibility:</EM> 
<OL>
  <LI>Design and Implementation. 
  <LI>Close interaction with the NMS, Marketing group and system 
  design/architecture group to achieve/maintain the conformity of GR and various 
  requirements. </LI></OL>Status: Completed. 
<P><STRONG>1.3 SONET Performance Monitoring PM :</STRONG> </P>
<P>The goal was to develop transponder based on SONET OC192 and OC48 and also to 
do performance monitoring i.e. to monitor the health of the NE Network Element 
and to take appropriate actions and also to maintain static s/history of all the 
events/parameters, which will act like a STE Section Terminating Equipment in 
accordance with BELLACORE GR-253 requirement. </P><EM>Responsibility:</EM> 
<OL>
  <LI>Managing/leading the firmware part of the project. 
  <LI>Close interaction/active participation to maintain the Conformity between 
  MRD Marketing Requirement Doc , System design/architecture including GR-253 , 
  NMS and firmware. 
  <LI>Design and Implementation of the firmware. </LI></OL>
<P>The firmware functionality includes: </P>
<OL>
  <LI>SNMP interface, configuration management, flash management, driver for the 
  PM chip, database management. 
  <LI>PM management that includes data both analog and digital i.e. from SONET 
  header Accumulation, Analysis/processing, Storage and synchronization between 
  various PM activities. 
  <LI>Synchronization with NMS Network Management System for various activities 
  fault management, data collection etc. 
  <LI>GR-253 implementation for STE PM, TRAP/ALARM processing. 
  <LI>User interface and applications. </LI></OL>Platform : m68k, Legacy 
Proprietary RTOS, AMCC INDUS chip. <BR>Team size : One firmware part . 
<BR>Status : Complete. 
<P><STRONG>2. Projects in Waxonet Communications:</STRONG> </P>
<P><STRONG>2.1 Chip Modeling: Modeling of WindowMaker for OC-48 TM Traffic 
Manager :</STRONG> </P>
<P>The WindowMaker suppose to make a list of cells/packets to be transmitted to 
the scheduler which then sends those cells/packets by using TDM Time Division 
Multiplexing .Our target was to model/simulate it to check it s functionality 
and also to check the real-time constrain, if any, in terms of time/memory. </P>
<P>My responsibility was to design it model it in terms of c++ classes/functions 
using SystemC tool. </P>
<P>Actually we replaced all the modules of WindowMaker by a set of con-current 
processes c++ functions-supported by SystemC , all the processes interact by 
signals through ports supported by SystemC . </P>
<P>SystemC is a modeling tool provided free by a joint effort by major 
EDA-companies like-Synopsys, Frontier and Coware.</P>Platform : NT/VC++ 6.0, 
SystemC <BR>Language : C++ <BR>Team size : Two <BR>Duration : Three months. 
<BR>Responsibility : Design-part <BR>Status : Completed 
<P><STRONG>2.2 DEVELOPMENT OF NT DRIVER for SAR622:</STRONG> </P>
<P>SAR622 stands for Segmentation Assembly and Reassembly SAR at a speed of 622 
mbps. This is a PCI based memory mapped device, which takes ATM cells and 
assemble them in to packets and reassemble packets in to ATM cells. The idea is 
to validate the functionality of the SAR622. </P>My role was focused to develop 
the driver for SAR622, which basically does two main functions: 
<OL>
  <LI>Handle the device specific part Interrupt, initialization etc. 
  <LI>To give access to the higher layer software test engine etc. to validate 
  the functionality at a higher layer and make it more general in nature. 
</LI></OL>
<P>As far as device driver is concern this PCI card contains more than one 
device in the card SAR,TC and PCI to LOCAL BRIDGE , so there are three ISR s 
Interrupt Service Routine and DPC s Deferred Procedure Call to handle the 
interrupts for each three devices. This driver handles issues like sharing of 
ISR s for multiple card and multiple processors using spin lock . </P>
<P>Responsibility : Design, Implementation, Debugging and Testing of the driver. 
</P>H/W Platform : X86-based platform <BR>S/W Platform : Windows NT 4.0/DDK 
<BR>TOOLS : DDK, Softice for debugging , Numega Debugging tools like DriverAgent 
and DriverWorkbench <BR>Team size : One <BR>Duration : 6 months <BR>Status : 
Completed and working. 
<P><STRONG>3. DEVELOPMENT OF THE WINDOWS BASED TERMINAL WBT SwitchUp Networks 
</STRONG></P>
<P>This is a Windows Based Terminal development thin client project for remote 
computing. This is a diskless m/c,the m/c boots through flash memory and the 
loader loads the WinCE image from flash to system memory and then transfers the 
control to the WinCE O.S. </P>
<P>The localized protocol handles only mouse movement, keyboard, display etc. 
All other things are done in the server. The client interacts with the server by 
well-defined protocol like Citrix ICA, Microsoft RDP. </P>I worked mainly on the 
following specific projects: 
<OL>
  <LI>Flash Management, configuration management, and database management. 
  <LI>Drivers based on Windows NT and Windows CE . 
  <LI>Debugging and testing. 
  <LI>User interface and applications. 
  <LI>Porting of existing citrix ICA 3.0 thin client protocol driver 16-bit - 
  only the Display part on Cyrix MediaGx 32- bit client . </LI></OL>Server : 
Widows NT 4.0 Terminal Server Edition-Beta2 <BR>Client : Windows CE 2.10 
Diskless with Flash memory and Cyrix MediaGx processor <BR>H/W Platform : Cyrix 
MediaGx Advance Processor with DiskOnChip flash memory. <BR>Platform / : WBT 
Windows Based Terminal -Windows CE 2.10 , Citrix <BR>Tools Metaframe Server: 
Microsoft Terminal Server 4.0- Beta-2 with DOS client, Boot Developer Kit BDK of 
M-Systems , 32-bit client interface for DOS SDK for ICA DOS32 clients . 
<BR>Language : C, C++ , VC++. <BR>Duration : One Year <BR>Team size: Two. 
<P><STRONG>Projects during M.Tech. Course:</STRONG> </P>
<P>M.Tech. Project : </P>
<P>Title : Retargeting of GCC from 386 to Pentium </P>Platform : Unix/C 
<BR>Target : Retargeting the gcc GNU C AND C++ Compiler from 80386-unix to 
80586-linux platforms, so that it would support all the Pentium instructions and 
features of Pentium such as Super Scaler Architecture. 
<P>Description : Super Scale Architecture can be taken care of by analyzing 
whether the Two instructions are pairable i.e. independent or not. By changing 
the files related with m/c description and rtl appropriately we can support All 
the instructions of Pentium. Changes of Target Describing Macros Which describe 
all the features of target m/c, which does not fit in to the schemes of m/c 
description file can be done appropriately. </P>Team Size : One <BR>Duration : 6 
month 
<P><STRONG>Extra-Curricular Activities :</STRONG> </P>
<UL>
  <LI>Chairman of Jaycess Club Engg. College Branch during 1992-93. 
  <LI>Won Intra-University Chess Competition. </LI></UL>
<P align=right><A 
href="http://www.portnov.com/FreeResumeSample/EmbeddedSystemsResume.htm#Up">Up</A></P>
<HR>
<A name=3>
<H2 align=center>Resume 3</H2></A><B><FONT size=4>VLADIMIR CHERNOV 
</FONT></B><BR>164 Concord Dr. <BR>Sommerville, MA 01821 
<P></P><STRONG>OBJECTIVE </STRONG>
<P>An Embedded Software/Firmware Engineer position in an electronic system 
design company where I can contribute using proven ability to develop SW 
components for complex electronic systems. </P><STRONG>PROFESSIONAL SKILLS 
</STRONG>