SUMMARY:

• I am a senior DevOps style, hands - on, Confidential Specialist. Senior means I've coded in Java since the first production release, of “Java One”, the jdk1.0.2 released. That's twenty years development experience, continually through every subsequent release up to and including the current 1.8 release. I've downloaded the early release version of 1.9 to preview features. I'm pretty rigorous about java.: -)
• DevOps means I've not only coded applications, but also administered relational databases and performed infrastructure installation throughout my career. It means that I moved from traditional manual admin to scripted and automated admin, in which I develop the “infrastructure as code” scripts necessary to properly install and administer the production environment. Most DBAs still are traditional manual administrators, but I have experience and know how to do Confidential in scripted, automated, DevOps style, via bash-scripts in a continuous-integration continuous-deployment pipeline environment.
• Confidential means I stay cutting-edge: in exploring the NoSql world to achieve web-scale performance, I latched onto Confidential since the first Apache release, version 0.3 on . I've worked on every subsequent version up to and including the current 3.0.9 release, for a total of 7 years experience. I was attracted to Confidential because it's open source written in Java. I've built it from source and can run it in debug mode from my IDE. When I say I've worked with it, it means I've worn every C* hat there is: administrator, cluster designer, multi-datacenter troubleshooter, AWS-elastic scalability Proof-of-Concept implementer, Java application developer using Confidential as a back-end database, and so forth.
• I've worked with the Apache Open source distribution, where the admin had to be implemented separately, such as by using tablesnap/tablerestore for backup, reaper for repair management, jmx and linux performance monitoring scripts and nagios or graphite to gain insight into the cluster. I've written the scripts necessary to administer the cluster as a unit.
• I've also worked with the Datastax distribution, where OpsCenter provides these services. I'm a Datastax certified Developer.
• I'm a Datastax certified Administrator.
• I've even gone throught Datastax training, when I was hired by Blackbird in Silicon Valley to produce a training program and pipeline for DBAs in Confidential .
• Naturally, I'm also well experienced in Hadoop, Spark, Kafka, SOLR, elastic search and all the other packages that form part of the Big-Data ecosystem, both integrated with C* via the Datastax distribution, and also installed as separate Open Source packages.
• I'm well qualified in Confidential .

PROFESSIONAL EXPERIENCE:

Confidential

Senior Digital Architect

Responsibilities:

• responsible for 105 nodes.
• Interviewed key workers to determine risks to production systems.
• Mentored staff on proper backup procedures.
• Investigated performance problems
• Remediated data corruption.
• Revised data model and code for performance tuning. wrote DevOps scripts to manage cluster as a unit
• Corrected backup/recovery procedures, to make them work.
• Implemented Hadoop ecosystem (including Hive/Pig) to interoperate with existing stack.

Confidential

Digital Architect

Responsibilities:

• As leader of the database layer & Confidential specialist -- charged with reviewing and remediating any or all of over 300 nodes of Confidential .
• Supported Predix Industrial Internet of Things platform.
• Troubleshot multidatacenter communications problem. From a very complex configuration and difficult circumstances, I was able in only 9 business days to find the problem. It wasn't Confidential, by the way C* is awesome
• Advised on DevOps, production standards, operationalization issues and CI pipeline development.
• Supported DSE/Hadoop.
• Worked production tickets.

Confidential

Developer/architect

Responsibilities:

• Reports internationalization, localization, and restructuring.
• Barcode implementation for Order Entry, Billing, and distribution system.
• Oracle schema alteration to support new requirements.
• Bug fix and code restructuring for proper application architecture.
• This was good solid coding experience for 8 months, which is rare for an architect, but crucial for keeping skills up to date. I implemented use of PDFBox for reports. I fixed necessary changes in the legacy Swing GUI. And I added new DAO components to meet requirements.

Confidential

Digital Architect/Engineer

Responsibilities:

• I worked on the Confidential clustering project, to establish a high-availability, several hundred node data “grid,” with over 100 million users.
• I collected end-user's requirements, modeled the data appropriately for Confidential, worked with infrastructure on performance requirements, features, and support issues (such as whether to use TTL, triggers, investigating log errors, warnings, and issues, etc.)
• I helped establish a proactive monitoring procedure, where logs were consolidated to Splunk and then examined regularly. As one example, we developed a procedure for monitoring anti-entropy repair.
• I worked with infrastructure and engineering to do proof of concept on implementing hadoop queries within C*.
• I mentored java developers on Confidential development, and functioned as the developer's C* DBA.
• I coded java programs that complied with the internal framework.
• This large enterprise had me (as Enterprise Architect) interview staff and hardware vendors and investigate software and hardware configurations to develop a systems integration and customer satisfaction strategy.
• Developed a portfolio of related projects, including: database integration systems federation security
• Ship card integration: to reduce 3 cards (cabin-card, gambling card, and room card) to a single, or “OmniCard.” I had to integrate the card with all existing systems, and insert hooks to make that happen. I succeeded in proving out the concept in a dedicated lab, which I designed and constructed for them, and coded the Proof of Concept driver code to make that happen, using the card vendors proprietary SDK. This illustrates the value of a hand-on architect.

Confidential

Application Architect

Responsibilities:

• This Entertainment & Media Company needed their order and billing system modified to accept payments from Confidential, and Confidential .
• I researched the APIs, secured them with the required OAUTH method, and wrote java code to make that happen in the context of their package.
• I altered the schema of their MySql database to accommodate the new payment and delivery system.

Confidential, NYC

Responsibilities:

• Digital Transformation: I oversaw the first move of this enterprise into the cloud.
• Information Layer: Database federation project, data warehouse implementation, POS implementation.

Confidential

Enterprise Architect

Responsibilities:

• Spearheaded, Designed, & Engineered the first performance engineering lab at Fox.
• Oversaw the elimination of java performance problems for Royalties applications.
• Infrastructure upgrade of Weblogic.
• NoSql transformation: POC on use of Coherence, Confidential, and Mongo. ver 30 Move Groups identified, scheduled, and analyzed with technical staff and users.
• Move methodology determined, risk assessment, consolidation
• Digital transformation: migration of servers into virtualization and some into cloud.

Confidential

Lead Architect/Server Developer

Responsibilities:

• I refined the product vision by analysis with key users and staff.
• I developed the User Experience through defining Scenarios.
• With the product backlog filled, I researched Social media and mobile issues and synthesized them as I defined the architecture for a C2C and C2B mobile/social app with a web-interface aimed at B2C.
• I abstracted the MVP, coded the back end for a RESTfull access to the underlying datastore, and installed and administered the development and production infrastructure.
• I lead the developer team of 11. Our backend was Confidential (NoSql), for scalability.
• We had fun. But we lost funding.

Confidential

Digital Architect

Responsibilities:

• I performed a virtualization and private cloud project which included a Confidential NoSql cluster to support 100 Million ops/sec.
• I benchmark-tested it for performance using YCSB, and spun up 100 nodes on the cluster to test transaction speed.
• We established that we could accomplish linear growth, and thus our replacement strategy was sound.
• This project was to replace a for a critical legacy system expecting on the order of 130 million users.

Environment: C*

Confidential

Architect/Developer

Responsibilities:

• I developed a natural language parser using a modified Tomita algorithm.
• I coded the back end using SOA and JMS connectors to the rules-engine and rules-base components.

Confidential

Enterprise Architect

Responsibilities:

• My role was supporting the Infrastructure migration.
• I back-filled architectural documentation based upon owner and developer interviews and investigations for hundreds of systems, and coordinated with the infrastructure teams to get them migrated to the new datacenter.
• I worked closely with storage, networking, security, Web Services, Integration, and Database groups to accomplish this.

Confidential

Systems Architect

Responsibilities:

• When this naughty Government Sponsored Entity got caught cooking the books, I was brought in to provide a rules-engine based effort to re-cook those books, by reposting every trade from the bond model to the sub ledger and general ledger.
• Every single transaction passed through my rules-engine, and I worked closely with Confidential to ensure the quality of the rules-firings, by writing inconsistency spotters and reconciliation modules, to feed into their spreadsheets.

Confidential

Enterprise Architect

Responsibilities:

• I established the architecture for Single-Signon across legacy mainframe and Server farm, to be rolled out across the entire enterprise: we split it up into Web and Federated SSO, because we had external and internal parties who needed signon.
• My Responsibilities included drafting the architectural documentation, business-case development, budget writing, securing project financial approval from senior management, writing project plan and tracking progress.
• I led vendor selection and negotiation including RFQ, RFPs, SOWs, and invoice-approval. It’s kind of strange for an architect to do project management, but different experiences are good all around. They push you out of your comfort zone.

Confidential

Enterprise Architect

Responsibilities:

• I planned and executed Capital Markets datacenter relocation from NYC to NJ.
• My analysis covered over 20 groups and trading desks across fixed income and equities.
• I assessed and analyzed risk on over 500 applications, wrote formal move documentation and plans, secured approval from senior management and technical staff.
• I presented the risk to all senior business sponsors and performed assessment of actual impact to business.
• My project was a great success, being on-time, and having not a single user outage.
• We only had to revise 3 plans, after presentation of risk to senior traders.