My responsibilities included middleware code development and unit testing for Overtures 6500 platform designed to provide metro edge connectivity. • As an individual contributor I developed an interface for reporting alarms for the EoC (Ethernet over copper) cards utilizing a database to log and clear the alarms. • Developed code for gathering performance metrics of various events reporting the data to a log file• Developed configuration verification functions to query database data within a pending configuration using SQLite before allowing configurations to be committed to a specified line card in the system.• Resolution of various PRs found by system test. I was responsible for recreating and troubleshooting the issues and developing a fix, which was then resolved by system test.Code development was done in an embedded Linux user space using C, C++, SQLite and SVN for software build control and versioning. JIRA used for reporting bugs found during testing.

• Development of a Message Flow Control feature (MFC) which is a middleware mechanism that allows an applications to register a service at a set capacity on a server. Advertise service availability to clients and regulate traffic to the server based on if capacity of the server is exceeded via broadcast messages putting a service in flow control for a specified time frame. • Development of Group Broadcast feature which is a middleware mechanism that allows our Eagle applications to generate high speed, low latency, highly reliable delivery of messages to other card applications registered with logical groups. The meanings of these groups are registered by the application and only cards registered for that group will receive the messages.• Development of an Ethernet application that allows for inter-shelf communication between an active and stand-by Shelf Manager Controller utilizing Freescale’s PowerQuicc II 8250 processor running the MQX RTOS. The application was designed to establish a connection between active and stand-by ShMCs, gather pertinent shelf status from the tasks running on the active card and transmit that data via an Ethernet packet to the stand-by ShMC. • Experience with developing code that utilizes MCC (Multi-Core communication) in an environment where VxWorks is run in AMP mode.• Development of a bare bones Intel 82571 device driver used as a bridge interface sitting on a PCI-e bus to enable TX/RX of IMT packets encapsulated in an Ethernet frame to and from an FPGA for further processing. • Code development in C with the VxWorks RTOS environment utilizing Clearcase for build control and versioning.