Rob Schroder Email & Phone Number

San Francisco, Ca, Us

San Jose, California, Us

San Francisco Bay Area, Ca, Us

• Responsibilities: Engagez was a 10 person startup. This was a hands-on role, requiring multiplehats: site reliability engineer, performance engineer, technical program manager, and QAmanager (on-shore and off-shore). We achieved SOC2 compliance, reduced infrastructure costsby 50% through aggressive and ongoing testing and optimization of all layers of the stack. Ourmonitoring and visibility stack included: CloudWatch, prometheus, and NewRelic, Salt, andpython. Participated in a 24/7 on-call rotation.• Technologies: AWS, Kubernetes/EKS, Go, Python, PHP, Java, Apache, nginx, Solr, memcahce, redis, AuroraDB, Ubuntu, CentOS, Docker, Terraform

Santa Cruz, Ca, Us

New York, Ny, Us

• Responsibilities: Building the SRE team was a green field opportunity. Our mission was to buildout well instrumented, fault tolerant systems that performed and scaled. At OKL, the team wascomprised of a blend of DevOps, performance and scalability, application development,database, and systems engineering expertise. Our monitoring and visibility stack included:OpenTSD, Grafana, Icinga, Splunk, Boomerang, StatsD, and New Relic. We were embeddedwith development teams and made sure code was delivered in a timely and instrumentedfashion. All team members participated in a 24/7 on-call rotation. We improved to andmaintained 99.99% uptime. Team members worked from San Francisco, New York, London,and Argentina. Our team onducted postmortems that focused on resolution and prevention ofrepeat incidents, not on blame.• Technologies: Mix of AWS & On-prem, Nagios, Splunk, OpenTSDB, StatsD, Boomerang,CFEngine, SaltStack, Ruby, Rails, Resque, Java, Javascript, Redis, memcached, MySQL, CentOS,Android, iOS, Gatlin

New York, Ny, Us

• Responsibilities: Built the internal performance practice at Manilla from the ground up. Forsimulating load, we used open source tools such as jmeter and the grinder. For root causeanalysis, we used a combination of New Relic, ruby-prof, JProfiler, boomerang, and codeinstrumentation. For reporting, we used statsD and Graphite. Testing and root cause analysisefforts resulted in a thirty times reduction in hardware costs. Built a mature load testing,automation, profiling, and reporting infrastructure that allowed us to release software once perweek with confidence.• Technologies: Ruby, Rails, JRuby, Java, Javascript, Redis, memcached, MySQL, CentOS,Ubuntu, Android, iOS

Us

• Responsibilities: Built and managed a cross-client, geographically distributed team that wasresponsible for guiding our Fortune 1000 customers through the complete performanceassurance life cycle, from gathering performance requirements on through to capacity planning,test strategy definition, load simulation, root cause analysis, and maintenance driven regressiontesting. Responsible for managing all aspects of delivery, from sales support to scoping, resourceplanning, budgeting, and contract review and submission. Responsible for authoring marketingmaterials that explained practice methodology and execution. Responsible for managing clientaccounts. Turned customer’s business requirements into a cohesive set of tasks and testinggoals. Developed detailed schedules, project estimates, resource plans, status reports, andmetrics. Managed successful performance testing projects at over 25 clients, includingCitigroup, American Express, Marriott, Safeway, Expedia, Sun Microsystems, Walt Disney.• Technologies: Java, Javascript, WebSphere, Weblogic, Tomcat, Hibernate, Oracle, DB2, Solaris,Windows

Us

Technology Stack: Java, WebSphere, Weblogic, Tomcat, Oracle, DB2, ehcache, RedHat, Solaris, Windows• Played a lead role in establishing performance engineering methodologies and best practices.• Responsibilities included giving input on requirements, reviewing design, writing performancetest plans and strategy documents, isolating performance and scalability bottlenecks, andperforming the respective root cause analysis.• The Vignette application portal was capable of delivering thousands of transactions per secondwith sub-second response times

• Responsibilities: Played a lead role in establishing performance engineering methodologies andbest practices. Responsibilities included giving input on requirements, reviewing design, writingperformance test plans and strategy documents, isolating performance and scalabilitybottlenecks, and performing the respective root cause analysis. The Vignette application portalwas capable of delivering thousands of transactions per second with sub-second response times.The tools used to drive load were SilkPerformer and LoadRunner. For root cause analysis, weused OptimizeIt and native OS tools. Delivered eight versions of performant and scalableproduct.• Technologies: Java, WebSphere, Weblogic, Tomcat, Oracle, DB2, ehcache, RedHat, Solaris,Window

Armonk, New York, Ny, Us

• Responsibilities: My duties involved building the QA and load-testing lab for the first release ofIBM’S WebSphere Application Server. This lab consisted of several hundred machines that wereused for functional, system, load, and integration testing. I served as technical lead for thetesting effort surrounding the WebSphere servlet container. Developed the load-testing tool thatwas used for testing the first two versions of WebSphere.• Technology Stack: Solaris, AIX, Windows, HPUX, RedHat, OS/2, OS390, Oracle, DB2, Apache,Netscape, and IBM web servers.