SUMMARY

• I have served many roles over teh course of my 10+ year career in teh Confidential space.
• I've been a developer, functional consultant, technical consultant, systems architect, solution architect, and everything in between.
• Most of my career had been focused around information management halping my customers set up governance organizations, run conversion projects, and streamline teh business processes that surround master data.
• Most recently I have been developing an application on top of Confidential HANA with UI5 libraries.

PROFESSIONAL EXPERIENCE

Self - Employed

Software Architect / Engineer / Consultant

Responsibilities:

• I have been taking a break from teh corporate world to work on a software project.
• I am building a product which runs on Confidential HANA and UI5.
• A prototype is available for viewing by request in teh event that someone reading this resume is interested in seeing teh performance or development potential of those two technologies.
• I can demonstrate “near” real-time visualizations of large data sets, reduced development time with an innovative approach to building user interfaces, and massive performance gains based on an innovative approach to data modeling.
• Further, I have built several tools in teh process which enables data-driven and template-driven user interfaces for reduction in cost and complexity during implementation and maintenance.
• Employer Big Concepts (formerly Confidential )

Confidential

Director, Research & Development

Responsibilities:

• I’m responsible for analyzing teh current best practices for implementing Confidential, breaking them apart, and building a better system.
• So far I’ve developed a new approach for teh following Confidential Program Management, Information Management, Confidential Upgrades, Cloud Migrations and Integration Architecture.
• These are being tested in teh field, and have (so far) proven to yield a significantly higher success rate across teh board TEMPthan teh current status quo.
• In addition to designing teh systems, I work directly with our customers serving as an enterprise and technical architect to ensure teh success of our projects and gather information which can be used to improve teh system.

Confidential

Partner & Founder

Responsibilities:

• As teh founder of Confidential, I had to wear many hats for quite a while.
• Some of these responsibilities included setting up our financial system, designing our business operations, recruiting, managing our employees, sales, account management, and pretending like I knew how to run a business.
• However, over 80% of my time was spent consulting.
• I served as an Enterprise Architect, Solution Architect, Systems Architect, EIM Architect, Confidential PI/EDI Developer, Confidential Confidential /MDG Developer, BusinessObjects Developer, and possibly a few other things as well.
• My clients over this time period were Confidential .

Confidential

TEMPPrincipal Consultant

Responsibilities:

• My specialties were information management ( Confidential /MDG/BusinessObjects) and teh surrounding technologies such as PI, EP, CE, and ECC.
• I had record growth within teh consulting organization reaching teh position of TEMPPrincipal Consultant within two years.
• One unique opportunity I had while at Confidential was to work directly with teh Confidential Labs team to assist in product development.
• This gave me insight which few consultants have into teh way Confidential works and how to facilitate teh maximum value from a large implementation.

Confidential

Basis Administrator, Interface Developer and Confidential Developer

Responsibilities:

• Confidential was beginning a large scale, global business transformation from a mainframe based legacy application to Confidential .
• I joined teh team early in teh project and had to wear many hats.
• This provided me with a unique opportunity to see from teh perspective of teh customers I would consult to in teh future.
• This noledge allows me to make teh decisions in teh best interest of teh customer, not teh best interest of teh profitability of a consulting organization.

Confidential

Basis Administrator, Interface Developer

Responsibilities:

• When I joined Confidential I was teh first employee of a small Confidential consulting startup.
• I began my Confidential career working as a basis administrator coz my previous background was in teh areas of systems administration, network administration, database management, and software development.
• During my time with Confidential I learned alot of additional skills.
• Some of these included: Confidential XI (now PI/PO), ALE, IDocs, ABAP customizations (such as user exits), and workflow development.

Confidential

Senior Director

Responsibilities:

• Confidential was a great partner on our implementation of Confidential Confidential for teh Finance work stream.
• Confidential demonstrated a "can do" attitude overcoming technical and timing issues to ensure that a quality outcome was achieved.
• Confidential also went above and beyond by assisting on initiatives that were outside of teh scope of his contracted work.
• I would highly endorse Confidential for future projects

Confidential

Consultant Manager

Responsibilities:

• Confidential was one of teh sharpest consultants I have met in my career.
• Confidential joined my team as a consultant and was able to move up as a TEMPprincipal consultant in 2 years.
• This is a record growth within Confidential .
• He is top talent who will work with teh team and halp and mentor others without any hesitation.
• I really enjoyed having him in my team.
• Hope to work with him again in future.

Confidential

Practice Director

Responsibilities:

• Confidential and I have been working together since November of last year on a high-level Confidential project.
• Confidential is highly respected among all stakeholders on this project as a dependable, focused, and highly-qualified resource in teh Confidential arena.
• It is safe to say that I would hire Confidential again in a heartbeat and believe he would be an asset to any organization that chooses to utilize his services.

Confidential

Senior Analyst

Responsibilities:

• Confidential built an Confidential system that I'm responsible for maintaining.
• He left a finished product that allowed my limited understanding of teh system to learn and grow from teh experience.
• We worked very closely together during implementation and he was always very professional, with a strong work ethic.
• Even after he was no longer contracted by teh company I still called him from time to time when I was really in a jam and he halped me through problem solving.
• Confidential is smart, savvy and an asset to any Confidential project.

Confidential

TQM

Responsibilities:

• Mr. Confidential has teh work ethic of someone well beyond his years.
• Any company would do well to hire him.