1. SHWETA BIJAY
Phone :( 425) 440-1137
Email:shwetak345@yahoo.com
EDUCATION
BE (Electrical), Sardar Patel College of Engineering, University of Mumbai, 1993-97
COMPUTING SKILLS
Programming: C#, Python, FORTRAN, PASCAL, Visual FoxPro
Tools / Technologies: ASP.NET, ADO.NET, Web Services, OData, Entity Framework, Source Depot, Perforce,
TFS, Product Studio, Bugzilla, JIRA, Eclipse, Visual Studio, SCVMM, Microsoft Test Manager,
XML, JSON, Postman
Database: Microsoft SQL, MS Access
OS: Windows
EXPERIENCE
TestEngineerIII F5 Networks April 2015 - current
Bellevue, WA
I worked on various projects during this period, few key projects are mentioned below:
1) Project Name: VMWare NSX Cloud Connector
Cloud connector to provision active-standby pair of BIG-IP VEs (virtual editions / virtual machines) in
VMWare/NSX environment. Their management consolecalled iWorkflow allows to manage these connectors. One
can configure cluster of iWorkflows (iWorkflow HA (high availability feature)). Team follows Scrum model.
Role:
I performed functional test. My role was to test iWorkflow HA functionality around NSX. I created a test plan and
wrote test automation to validate core scenarios around iWorkflow HA functionality. During testing, I found some
good bugs that demanded design updates.
Tools and Technologies: Python, Perforce, Eclipse, Postman, REST (Representational state transfer)
2) Project Name: Onboarding Events during Big-IP VE provisioning
These events were fired during Big-IP provisioning. The purpose of these events is to allow customers to perform
custom configurations via eventhandlers during Big-IP VE provisioning in active-standby or standalone mode
Role:
I performed functional test. My role was to test the functionality. Again, during testing I found some good bugs, 3
of which got release noted (documented as Open Issues which we publish to the customers).
Tools and Technologies: Python, Perforce, Eclipse, Postman, REST (Representational state transfer)
3) Project Name: Diagnostics and Alerting
As the name suggests, the purpose of this component was to log diagnostics metrics example disk I/O, CPU,
memory usage for iWorkflow machine at configured interval and raise alerts
Role:
I performed functional test. My role was to test the functionality. Again, during testing I found few complex bugs.
For these, I helped developers with diagnosis.
Tools and Technologies: Python, Perforce, Eclipse, Postman, REST (Representational state transfer)
SoftwareDesignEngineerTestII Microsoft Sep 2009-Dec 2014
SoftwareDesignEngineerTest Microsoft Oct2007-Aug 2009
Redmond, WA
I worked on various projects during this period, few key projects are mentioned below:
1) Project Name: MSDial

2. MSDial was a collection of web services that exposed APIs to manage servers in various data centers. MSDial
provided metadata info of servers, history of servers (For e.g. when server was procured, moved, repurposed,
disposed) and ticketing system for maintenance and monitoring of servers. Team followed Waterfall model for
MSDial Project.
Role:
I performed integration and stress/perf test.
For integration test, I created a test plan and wrote test automation to validate core integration scenarios. I found
spec issues while driving discussions around these scenarios. I drove discussions for defining lab requirements
with labs team and other key stakeholders. I also triaged bugs with the team and managed schedule of the project.
For stress/perf test, I wrote automation and executed component level stress and perf test for base CRUD (Create,
Read, Update, Delete) APIs exposed by the service. I analyzed the results and generated reports. I also mentored
vendors for stress/perf test.
Tools and Technologies: C#, SQL, Source Depot, Stress/Perf test tool I wrote for the team, Perfmon executable
(Performance Monitor), Product Studio, REST (Representational state transfer)
2) Project Name: Surface Area Manager
Surface Area Manager was a web service that exposed APIs for scheduling deployment of approved firewall rules
on servers, monitoring existing firewall rules on servers against expected list of rules and raising alerts for any
discrepancies. Team followed Scrum model for Surface Area Manager Project.
Role:
I performed functional testing for web service APIs. I also wrote test plan and test framework to support the tests.
Tools and Technologies: C#, SQL, TFS (Team Foundation Server), OData Web API
3) Project Name: QA (Quality Assurance) / Infrastructure tools:
This project comprised of developing tools to help with QA.
My role in this project was to design and develop tools. I designed and developed three tools that are mentioned
below:
a) Stress/Perf test tool:
This tool enabled automated stress/perf run against daily builds. It also supported scheduling ad-hoc runs. For
e.g. schedule 48 hour stress run over the weekend to check for any memory or handle leaks.
The tool comprised of following main components:
i) Library: This component via its configuration enabled invoking test APIs (which in turn invoked Service
APIs) in specified percentage for specified duration of time. It used ThreadPool to queue concurrent
requests to service APIs. It created perflog file to log perf numbers and other key metrics (memory,
handle, %CPU consumption) for the run using Microsoft internal tool called PerfAnalyzer. Post
stress/perf run, the tool analyzed results and generated report which was communicated via email.
ii) Lab: Expanded bed lab comprising of OneBox server and multiple clients were created using
SCVMM and Microsoft Test Manager.
iii) Workflow: TFS build definitions helped schedule daily runs and for daily run define workflow steps
(apply clean snapshot of environment, deploy dev and test bits and execute stress or perf run).
Role:
 Designed, developed and tested the tool. Got sign-off on the design from key stakeholders
 Made presentation to test team. This included a demo about the tool showcasing its features. I also
discussed good practices for developing test framework to support stress/perf test during the
presentation
 Defined standardized set of performance counters to be implemented by component devs
 Partnered with PMs to define performance metrics
 Drove discussions for defining lab requirements for stress/perf testing with labs team
 Created and shared stress/perf test plan template with the team
 Created and configured expanded bed environment comprising of OneBox server and multiple clients
using SCVMM, Microsoft Test Manager, TFS build definitions
Tools and Technologies: C#, SQL, SCVMM, Microsoft Test Manager, TFS, PerfAnalyzer
b) Custom Test Harness:
This test harness was an executable that enabled executing test cases decorated with custom attributes.
Role:
 Designed, developed and tested the tool. Got sign-off on the design from key stakeholders

3.  Made presentation to the test team. This included a demo about the tool showcasing its features
Tools and Technologies: C#
c) SmokeTest Tool:
This tool was an executable that was integrated with deployment service. It helped execute Smoke tests
immediately after deployment against each logical DC in all supported environments (Test: OneBox, expanded,
Prod). It provided smoke test results to deployment service so deployment service could decide at runtime
whether to proceed or not. This tool leveraged custom test harness to identify test cases that were decorated with
SmokeTest attribute.
Role:
 Designed, developed and tested the tool. Got sign-off on the design from deployment service devs
 Made presentation to the test team. This included a demo about the tool showcasing its features
 Helped feature testers adopt the tool
Tools and Technologies: C#
SoftwareDesignEngineerTest LanceSoft Inc Dec 2006-Oct 2007
Redmond, WA
During this period, I worked for Microsoft as a vendor.
1) Project Name: TeamStats
This was a QA(Quality Assurance) tool that generated report on bug metrics by querying Product Studio database.
Role:
I worked on TeamStats project with EBIS team of Microsoft. I extended the tool by adding report through charts.
Tools and Technologies: C#, ASP.NET, Product Studio, SQL, Xceed Control
2) Project Name: SSRS (SQL Server Reporting Services):
SSRS supports reporting on variety of data sources.
Role:
I worked on this project with SQL team of Microsoft. I worked on Web UI automation of Report Viewer Control
using existing test framework that leveraged WebAuto tool (UI automation tool developed by the SQL team).
Tools and Technologies: C#, Product Studio, WebAuto, SSRS
DeputyManager(R&D) Reliance Energy Ltd April 2002-April 2006
Sr Engineer(R&D) Reliance Energy Ltd Jan 1998-March 2002
Trainee Reliance Energy Ltd July 1997 – Dec 1997
Mumbai, India
At Reliance (largest Electric Supply Utility in India), I worked on projects that involved research, prototyping and
pilot studies. Following are few key projects:
1) Project Name: Impact of Harmonics and Remedy:
This project was about measuring level of harmonics and designing and testing Passive Filter to prevent
harmonic content from polluting the power supply.
Role:
I worked with Engineering team to shortlist few distribution stations that fed power supply to harmonic
generating load e.g. industries that used UPS (Uninterruptable Power Supply). I measured harmonic content at
these distribution stations. Based on analysis of measured harmonic data, I designed Passive Filter using thesis
report submitted by one of the PhD student. I negotiated with vendors to get Passive filter manufactured and
installed. After installation, I measured reduction in harmonic content to validate the design. I created a software
application to calculate filter specifications.
Tools and Technologies: Visual FoxPro
2) Project Name: AMR (Automatic Meter Reading) System:
This project was about introducing AMR system for different class of customers (residential, commercial and
industrial).

4. Role:
I analyzed various modes of communication and compared them with their pros and cons. Modes of
communication included PLCC (power line carrier communication), RF (Radio Frequency), and GSM (Global
System for mobile communications). I created spec, performed cost/benefit analysis for different technologies,
reviewed and shortlisted vendors. I also performed a pilot project on the site with one of the identified vendors
for PLCC and submitted report to the management with recommendations.
Tools and Technologies: N/A
COURSEWORK
MCAD (70-316): C#
MCAD (70– 315): ASP.NET