SUMMARY

• Confidential is a Senior Systems Engineer with skills in Java, Spring, SOAP, REST Oracle, and Java Security among others.
• During his long tenure with Walgreens, Confidential has provided development of multiple applications and systems. Confidential is passionate about working with code, adept at innovative design of complex, large scale applications, and the knowledgeable use of abstractions, cohesion and minimized module coupling for flexibility and scalability
• Confidential values creativity, loves learning and being part of a collaborative team, and cultivates curiosity to create new technical possibilities. Confidential is a self - starter, an excellent communicator, Confidential embraces ambiguity, and favors iterative, Agile methodologies.

PROFESSIONAL EXPERIENCE

Confidential

Technical Architect

Responsible for:

• Evaluated overall structure and design of applications
• Technical connection between project managers and development teams
• Analyzed business processes, trouble-shooting of software issues, found maintainable solutions
• Project Example: 1WORLDSYNC GS1
• Rigid record formatting had this project running over budget, waiting for final GS1 attribute selection, attempting to redefine existing record layouts to consume new GS1 XML attributes into an existing database.
• Created new approach to work alongside current system that consumes GS1 XML, keying and persisting the raw XML text for each UPC, then available for look-up, parsing, and attribute selection by this and other systems.
• Rigid formatting became a non-issue.
• Used StAX Parser to segment raw XML and acquire database keys for persistence of the keyed raw XML

Business Systems Analyst

Confidential

Responsibilities:

• Liaison between IT and Business, advised Stakeholders
• Developed needs assessments and cost benefit analysis
• Leveraged business and technical expertise with leadership to drive system development
• Project Example: Walgreens Supplier Food Safety Questionnaire
• 900 suppliers presented with an initial set of questions which then prompted a myriad of legal compliance questions, 140 in total.
• Complex web pages were in initial development. Any modifications would require time consuming recoding and redeployment.
• Redesigned the process using a spreadsheet and question selection macro that suppliers download, complete, and upload for compliance approval.
• Results included perpetual, significant time and cost savings due to a spreadsheet that is easily modifiable by business users eliminating the need for new deployment.
• Project Example: Daily Item Ad Changes to eCommerce System
• Leveraged prior years’ experience streaming Result sets into XML
• Created high level interfaces which provided a clear definition for the offshore team to code to
• Several different queries for each item
• Required jUnits for all work
• Went in significantly under budget and without any issues

Senior Application Architect

Confidential

Responsibilities:

• POC/Proof of Concept Rapid Prototyping
• Rescued, re-engineered, redesigned at risk back end systems
• Project Example: Predictix On Demand Promotional Forecasting (SaaS)
• Designed, coded, and deployed large scale forecasting HTTP client data transport (Google Protobuf) application, all self-directed.
• Heavy use of Java type generics, jUnit testing during development
• Achieved easy reuse of higher level processing for the various generic types
• Worked within existing data architecture, coded in just 3 weeks with an issue-free deployment.
• Success of project was the result of an Agile approach, test driven development, critical high and low level abstract thinking, as well as the intelligent use of object-oriented patterns and principles.
• Project Example: Ad Planning Swing Application
• Worked with consulting company, advising development of Swing app, data modeling, data transport to Swing clients
• Database migration (DB2 to MySQL) for testing by offshore team
• Project Example: Seasonal Buy Add-ons to DM Group
• SOAP Web Services data transport of Seasonal ordering data to Client database
• Class generation from XML schemes refs
• Invocation of new Seasonal data views to gain perspective on overall seasonal ordering
• Project Example: Worked on two file upload processes.
• Spring Framework
• Better analytical systems produced Excel spreadsheets with better ordering data, the important part was the validation of the spreadsheet data to avoid erroneous content fed into downline systems
• Used FitNesse for validation verification with Business involvement. Users could set up verification scenarios themselves, then invoke the validation processing themselves to create new validation scenarios
• Using FitNesse also encouraged high design and code quality
• The same processing had to be invoked by FitNesse and within the web environments

Systems Engineer

Confidential

Responsibilities:

• Created new internal web-based systems
• Initial development of the chain wide Basic Department Management System
• High profile 150 District Promotional Ordering Planning Application, Self-Directed
• Project Example: District Manager Swing Remote Client
• 150 District managers needed to work without network connection, Interactive Jtables
• XML, JAXP SAX (Large volume ResultSet streaming into XML), SAX parsing into objects, Using XML achieved a 90+ compression ratio
• Consolidated multiple views with popups into two views, no popups, tremendous time savings and better ordering
• Multithreaded batch processing, (a JDBC connection/thread)
• Client download of new content zip files produced by batch processing (Servlets)
• Swing client updates applied immediately to server
• Initiation of batch jobs through servlets (on request)
• File management (archiving) with shell scripts invoked by Java servlets
• Java WebStart application download
• Used for 14 yrs 2.5M per year savings in DM’s time + better ordering (eased District managers work)
• Project Example: Optimizer Container Management
• System algorithmically arrived at lowest cost container configuration, consolidation and de-consolidation choices for ocean freight shipping. Acceptance testing proved to be extremely difficult due to large complex data structures and business operation / class diffusion.
• Prioritized, implemented, and scaled dependency inversion choices to aid and isolate testing of conditional logic (paired programming).
• Data scenarios more easily set up for automated testing (jUnit, FitNesse Acceptance Testing Framework, Spring Framework).
• Visitor pattern used for marshaling and unmarshaling of content at testing inflection points using xStream, then compared with XMLUnit
• As opposed to manually eyeballing end result DB tables
• Were able to run tests in seconds on sections of processing, again and again, quickly
• People began trusting that the fixes were actually correct, easily confirmed, without unanticipated consequences

TECHNICAL SKILLS

• Java
• J-Unit
• Test Driven Development
• Spring
• Tomcat
• Jetty IBM WebSphere
• Web Services (SOAP)
• Jersey REST
• XSL (XPATH)
• Jetty HTTP Client
• Google Protobuf
• JAXP (SAX2) Streaming
• XML, Schema DEF
• ActiveMQ
• HTML
• JavaScript
• SQL, JDBC
• Oracle
• Agile
• Java Security (Keytool)
• SHAnnn Authentication
• UNIX (Bash, KornShell)
• Linux
• Windows
• UML
• Eclipse
• Netbeans