Joel Meyer
Los Angeles, CA
United States
Work Objective:
I desire to be involved in interesting projects that challenge me and allow me to interact with others while growing my technical and leadership abilities.
Education:
University of Illinois at Urbana-Champaign
College of Engineering
Computer Science
Bachelors, with honors
2002
Work History
Google
Software Engineer
02/2007 - current
As a member of the AdWords front-end team I have focused on improving the Keyword Tool by adding features (search volume data, results view customization, scrollable results table), increasing discoverability of existing features (through a UI refresh), improving performance (by integrating with a new back-end, rewriting the javascript, and adding JS pre-processing), and increasing test coverage (by providing a simple framework that allows a single set of Selenium tests to run against the four UIs in which the Keyword Tool is exposed).
In addition to my work on Keyword Tool I have served as a 'build cop' for the AdWords front-end continuous build, working to quickly identify changes that break the continuous build and notify the responsible party.
I am also currently involved in developing the next version of Keyword Tool.
Latham & Watkins
Web Programmer
07/2006 - 02/2007
At L&W I worked on a team developing a collaboration site for legal professionals using ASP.Net 2.0.
Xanga.com
Software Engineer
05/2005 - 07/2006
I worked extensively on the ‘Upgraded Profiles’ feature which brought social-networking to Xanga. This work was done using ASP.Net 2.0 and leveraged the Atlas framework to provide a responsive, rich-client-like interaction within the browser that allowed users to categorize, filter, sort, and manage their connections. This project was unique in the way it moved much of the application logic into the browser and used the MVC pattern to bring order to the large amount of Javascript that powered the pages.
Prior to this I implemented a URL rewriting solution in ASP.Net 1.1 in order to provide cleaner URLs for user pages and make user content more easily indexed by search engines.
I have also worked with the Amazon ECS web-service and AJAX to create an interface that allows users to search for books/music/etc and post links to their sites.
IBM
Software Engineer, WebSphere Performance
06/2002 - 05/2005
I worked on the WebSphere Application Server (WAS) Performance tools team. From 2003 to 2005 I was primarily responsible for the design and development of Tivoli Performance Viewer (TPV).
In WAS version 6.0 TPV was migrated from a Java thick client to an integrated part of the (web based) admin console. This involved a complete redesign and rewrite of TPV. My
responsibilities included the conceptual design document, the system design document, as well as a much of the implementation work. I also worked with internal testers and beta testers to
find and address defects prior to release.
I also served as a first responder when the build broke. In this capacity I was responsible for isolating the problem and either providing a patch or calling out the developer responsible.
Before that I did development for the WebSphere Performance Advisors, and before that I did performance benchmarking on WebSphere version 5.
SAIC
Intern
05/2001 - 05/2002
While working at SAIC I did development in C++/OpenGL for a modeling application in which I was responsible for implementing terrain rendering algorithms. While there I first implemented the Real Time Optimally Adapting Meshes (ROAM) algorithm described by Mark Duchaineau et al and the algorithm described by Peter Lindstrom and Valerio Pascucci in their paper "Visualization of Large Terrains Made Easy".
NCSA
Intern
12/2000 - 05/2001
While working at the NCSA I wrote a small GUI Java program to control a camera for video conferencing. The camera was controlled via the serial port and I used JNI on Linux to
interact with the serial port (Java didn't support serial communication at the time).
Tellabs
Intern
06/2000 - 08/2000
When I was a summer intern at Tellabs I wrote a Perl program that allowed the hardware engineers to search and analyze the log files produced by the equipment they were working
on. The GUI was written using Perl/Tk. Users could pick an event type and a color they wished to display it in, or they could enter a regular expression and highlight the
results.
Languages/Platforms:
Java/J2EE - I currently use Java at Google and all my time at IBM was spent programming Java. The code I write is performant as well as readable and well documented. I'm also familiar with Java related technologies like JMX, XML parsing in Java, JSPs/Servlets, Struts & Tiles, Webwork, etc. I've used Eclipse extensively and I've also used various tools to look at heapdumps and analyze memory leaks.
C#/.Net - I've done a significant amount of ASP.Net development using C# on both the 1.1 and 2.0 .Net CLRs at Xanga.com and at Latham & Watkins. I've also used the Microsoft ATLAS framework extensively. For development I use Visual Studio 2005 and Visual Studio 2003.
Python - While at Google I've had the opportunity to learn Python and know it well enough to accomplish my goals with the help of a reference. I've also played around with Google App Engine and the Django framework.
C++ - I haven't used C++ since I worked at SAIC, but I was fairly proficient at the time. I also took several computer graphics courses in C++/OpenGL.
Perl - I've written thousands of lines of Perl but I haven't used it in the last couple years. And it wouldn't bother me if I never did again.
Ruby/Rails - Currently learning.
JavaScript/CSS/AJAX/XHTML - I've used these plenty.
Platforms:
Windows (NT/2000/XP/2003)
Linux (SuSE/Gentoo/Ubuntu)
Mac OS X
Unix (AIX, HP-UX, Solaris)