Andrew Malitzis

Development Manager at IBM
  • Claim this Profile
Contact Information
us****@****om
(386) 825-5501
Location
Old Bethpage, New York, United States, US

Topline Score

Topline score feature will be out soon.

Bio

Generated by
Topline AI

5.0

/5.0
/ Based on 2 ratings
  • (2)
  • (0)
  • (0)
  • (0)
  • (0)

Filter reviews by:

Donald Mead

I have had the great fortune to work with Andrew at two different companies over the last 15 years. Andrew is one of the sharpest engineers I know. He is forward-thinking and thorough, with a broad knowledge and experience developing solutions around storage, security, networking, and web services. But even with his excellent technical capabilities, he is always humble. His colleagues constantly comment how enjoyable he is to work with. It has been my honor to work with Andrew in the past and hopefully someday I will be privilege to work with him again.

Alex Chen

Andrew is a self-motivated manager equipped with innovated design and development skills. His hand-on experience and project development vision has established himself as a role model for the team. Two major projects that Andrew has achieved should be emphasized. 1. With his contribution, we have successfully secured the business opportunity with Microsoft to standarize our security products within Microsoft globally. 2. Through his effort, the successful lauch of our first Chinese Localized Security Product KILL98 has set the milestone in China and become the #1 product in China. It is always my pleasure to work with Andrew and I won't hesitate to endorse him for his professionalism and enthusiam.

You need to have a working account to view this content.
You need to have a working account to view this content.

Experience

    • China
    • Software Development
    • 700 & Above Employee
    • Development Manager
      • Apr 2021 - Present

      I immediately transitioned from Architect to the Manager (of ECX/SCDM) as part of the IBM acquisition. I focused my effort on keeping prior committed release dates during the IBM transition which involved transitioning the entire product environment (Code Repo, Buiild process, Build env, QA env, JIRA, managers, IBM process complaince, IBM security, etc...). The entire SCDM environment was up-lifted, shifted and changed and moved to IBM BUT the SCDM/ECX team still released ALL of its prior commitments ON-TIME! (This took 27/7 hour effort from the ECX/SCDM teams to make this the "seemless" transition that IBM dreamed of and it all happened over the brief 4 months transition we had). In addition to moving SCDM forward, I am now also tasked to work on IBM advanced security products/efforts which we hope can lead the western world back to a truly secure internet. Show less

    • United States
    • Software Development
    • 1 - 100 Employee
    • Software Architect
      • Jan 2018 - May 2021

      Returned to Catalogic to take on the Software Architect role for its Copy Data Management (CDM/ECX) product. This was a natural move for me as I was one of the initial architects for the Catalog Software CDM product. Due to business and resource changes at Catalogic Software (and IBM), I was also asked to take on the managerial role for the Catalogic ECX/SCDM product as vital ECX/SCDM resources were transferred over to the more business critical Catalogic/IBM SPP product effort. Returned to Catalogic to take on the Software Architect role for its Copy Data Management (CDM/ECX) product. This was a natural move for me as I was one of the initial architects for the Catalog Software CDM product. Due to business and resource changes at Catalogic Software (and IBM), I was also asked to take on the managerial role for the Catalogic ECX/SCDM product as vital ECX/SCDM resources were transferred over to the more business critical Catalogic/IBM SPP product effort.

    • United States
    • IT Services and IT Consulting
    • 1 - 100 Employee
    • Director of Engineering
      • Apr 2016 - Jan 2018

      Joined this startup in 2016 to help pioneer intelligent software defined analytics to be applied against a rapidly converging marketplace of storage within cloud, compute, and networking environments. Designed a self-describing HATEOS JSON/REST API leveraging the Eve framework backed by MongoDB and implemented in Python. This API was first used to manage ProphetStor Storage. It was then extended to manage third party platforms such as OpenStack, VMware, Kubernetes and CEPH via the implementation of providers for those third party platforms. Designed and implemented an OpenStack provider to manage OpenStack from our platform/API. This provider also captured a rich set of OpenStack data for analytics. Designed and implemented a VMware provider to manage VMware from our platform/API. This provider also captured a rich set of VMware data for analytics. Designed a Kubernetes provider to manage Kubernetes and containerized workloads from our platform/API. This provider also captured a rich set of Kubernetes data for analytics. Designed and implemented a Kubernetes storage provider in GO that offered up ProphetStor storage for use in Kubernetes (Storage Class with dynamic PVC support). Designed a comprehensive Time Machine capability to browse the captured storage/third party data and exposed it from the REST API. This allowed consumers of our API to roll forward or backward in time and retrieve fully associated statics across the captured data. Leveraged Elastic Search for query/search and Time Machine capability Incorporated an analytics layer that leveraged the Time Machine to produce many interesting time based analytics. The analytics was also used to detect resource sprawl. Planned for the use of the Time Machine as a means to feed statistical data to an AI Prediction module. The AI Prediction module is currently in development by another team. VMware TAP relationship – VMware VTSP certified and managed the ProphetStor-VMware TAP relationship. Show less

    • United States
    • Software Development
    • 1 - 100 Employee
    • Senior Manager
      • Jan 2014 - Mar 2016

      Automated SLA based storage defined Copy Data Management leveraging existing vendor storage (NetApp, IBM, EMC) to fulfill a dense matrix of Recovery, Migration, DR, DevOps and wasteful storage reclamation use cases. Creating mirror or replica copies of data should be done for a purpose. Location and service levels of the copies should be used to determine their use. Remote copies lend to DR use cases as they protect against site failures such as power outages. Local copies with higher SLA's lend to local recovery use cases such as item level recovery of email. Other copies on remote storage across cloud boundaries lend to DevOps so long as those copies have been data masked. Yet other copies may be found to be wasteful and can be removed. In all cases, the copies must be of high quality with high fidelity cataloging. Automating Migration, Recovery, DR or DevOps use cases within or across site boundaries is not trivial. The software must have access to an in-depth high fidelity knowledge base when it is asked to automatically reconstruct the target Compute, Storage, Network, Security, and application level wiring within fenced or remote sites. This knowledge comes from the catalog. In fact, I would postulate that the whole concept of a useful software defined process must depend upon access to high fidelity and deeply cross associated knowledge. Catalogic Software achieves this with a densely cross associated high fidelity catalog. And of coarse, the value of the Migrated, DR or DevOps copies of workloads depend opon the quality of the data copies they are constructed upon (are they application consistent with high IOPS/low latency) as well as the quality of the target resources used for Compute, Network and Security (can they handle the workloads securely). Show less

    • United States
    • Software Development
    • 100 - 200 Employee
    • Director of Engineering
      • 2005 - 2014

      Automated Any2Any BI Service level BCDR and Cloud Iaas solutions. Automated BI service level DR goes well beyond simple machine P2V2V2P BMR (driver injection) as you need to handle BI service level recovery (multi-machine groupings with correct start up order), auto layer 2 - layer 3 network re-mapping of workloads from source to different DR networks, auto-security remapping to DR security, auto-rehome of workloads to operate in completely different DR environment (ie. remap storage/network/security/virtual to completely different DR components), auto remap of snapshot agents to operate against DR protection installation to maintain SLA while in DR (while in DR, snapshots occur against DR installation of SAN and agents), auto role reversal of SAN infrastructure on failback to maintain latest data from DR operation. Architected to address multi-tenancy concerns and the Service Provider (cloud) use case which involves a client <=> provider "Chinese Wall". Completely handle VMware SRM use case including auto-mapping of VM<=>Datastore<=>Storage groupings (Protection Groups) since role reversal of the underlying storage means role reversal of colections of datastores and VMs. Auto-detection of incorrect storage configurations for proper BI service level recovery (SAN storage is almost always incorrectly configured to properly handle DR for the BI services they protect). Recovery software runs at both source and DR sites to ensure no-single point of failure (in real DR, entire source site is down!). Daily scheduled test runs of BI service level recovery jobs (DNS, AD, clustered Exchange/SQL/ SharePoint farms) of large groups of workloads to fenced off networks to ensure that the BI services like Exchange/SharePoint do come up in minutes (validates the protection and recovery together). Also created, designed, developed and managed several other products/projects including the award winning RecoverTrac, Multi-site clusters, Exchange, SharePoint and VSS Recovery. Show less

    • Finland
    • Telecommunications
    • 700 & Above Employee
    • Senior Engineering Manager
      • 1997 - 2005

      Core switch and edge device Network Management. Managed several development teams: Solaris based NM Software; Windows and Solaris based NM Software; Embedded device software for SNMP using GNU environment. Team sizes managed ranged up to 10 developers and 10 QA. Architect involved with the design/development of a new XML/embedded Java MVC framework that allowed complete modularization of device management under a single container. This "new approach" was tasked to allow the concurrent development of management software for a diverse range of network devices across geographically dispersed teams. Bell Labs core developed new compilers and debuggers to go above GNU/GDB to facilitate rapid development. The closest analogy for this framework approach would be the current day Spring IO frameworks. Also involved with several RFCs surrounding SNMP (DSL) and SIP. Show less

    • Software Development
    • 1 - 100 Employee
    • Director Antivirus Software
      • 1993 - 1997

      Enterprise Scale Antivirus and Security. Created, designed, developed, managed, lead, ... the award winning InocuLAN and Cheyenne Antivirus Products. Team included 10+ developers, 10+ QA and 5+ support engineers. The main design goal for InocuLAN was to tackle enterprise scale Anti-virus protection. This included automated remote installation of AV client agents to corporate servers and desktops under a single protection policy. Virus updates were stage-able to ensure stability before automated roll-out via multi-spoke and hub routing to the AV client agents. The closest current day architecture would be Symantec's End-Point protection suite except that InocuLAN automated new signature updates under the hood while Symantec still requires manual update procedures. Show less

    • Senior Software Engineer
      • 1992 - 1993

      Designed and developed Network Management and embedded driver software for edge switches and routers. Part of a small team that developed a management platform similar to HP OpenView . The software supported device discovery via interrogation of router routing tables (RIP) that directed ping sweeps and network sniffing algorithms that monitored various protocols (ARP, RARP, ICMP, SNMP, UDP, TCP, SMTP, DDCMP, etc.); the catalog and display of physical and logical views, the propagation of status via bubble up methodologies, and the exposure of our API via a COM server. Show less

Education

  • Columbia Engineering
    BS, Computer Engineering
    1981 - 1987

Community

You need to have a working account to view this content. Click here to join now