×
James W. Gibson Jr.

James W. Gibson Jr.

Enterprise Software Architect

Englewood, Colorado, US, 80113
(443) 907-3453

Background


About

About

From profit models to enterprise cloud architecture I have your business covered. I am a user of almost all things node, cannabis tech engineer, admin of denverdevs.org, geospatial geek, and thought leader

Work Experience

Work Experience

  • Director of Engineering & ProductFlowhub

    Nov, 2016 - Aug, 20178 months

    Bringing enterprise stability to an agile startup. During my tenure, I was responsible for managing a team of 12, comprised of both engineers and product owners. I directly oversaw product decisions as well as mentoring a team of junior and mid level engineers. On the product side, I oversaw four iOS applications, three Electron-based applications, two web applications, and a centralized API. This suite of solutions was the bedrock of Flowhub's network and tracked millions of dollars of transactions daily. On the engineering side, I successfully led an effort to consolidate disparate tech stacks into a JS-based stack (excluding iOS apps of course).

  • Platform ArchitectFlowhub

    Oct, 2016 - Nov, 20161 month

    Brand new to the cannatech industry I was tasked with assessing the health and stability of a monolith application built on top of Meteor/Mongo. One of my very first tasks was to provide a partner company with a alpha api reaching into a multi-pod architecture database and application front end. I was also responsible for identifying areas of risk and weaknesses in the existing application.

  • Senior Software EngineerApto

    Oct, 2014 - Oct, 20162 years

    While working as a lead, I collaborated closely with small, cross-functional teams of designers, developers and stakeholders to build new features and applications. I served as technical architect and lead engineer for a project that is resulting in at minimum a tenfold ROI. I also was responsible for continuously searching out new ideas and technologies to learn and share with my team members. I managed the following productivity tools: JIRA, GitHub, Jenkins, Slack. I helped train new developers and review code from team members, while managing product promotions onto the Force.com platform.

  • Geospatial DeveloperGISInc

    Jul, 2012 - Oct, 20142 years 3 months

    NSGEM: Primarily engaged with DOD contracts, building geospatial views into enterprise data; GeoMetri: Developed and managed the migration from v0 to v1 of prototyped API's in a team of three

Skills

Skills

  • node.js
    expressknex.jsstreamsapi development
  • Front End Development
    angularwebpacksocket.ioelectronpolymerflex/actionscript
  • Back End Development
    node.js.netjavaapexpostgres
  • Dev Ops
    jenkinseslintdockerkubernetesvimdebianubuntugcpaws
Education

Education

  • BS in Information Systems , Minor in Geographical Information Sciences, Salisbury University - Perdue School of Business

    Jan, 2009 - Jun, 2012

Volunteer Work

Volunteer Work

  • Workshop Leader, DevMeetings

    Jul, 2017 - Jul, 2017

    Led a community workshop focused on the Angular Heroes Tutorial

  • Guest Lecturer, Learn to Code: Colorado

    Feb, 2016 - Feb, 2016

    Lecture Description: "Ever wanted to build something that used someone else's data? Well many websites actually make their data available through Application Programming Interfaces or API's for short, sometimes for free! During this meetup I'd like to introduce you to a few tips and tricks on how to gain access to API's for your own projects. We will be utilizing a popular weather forecast site to request an API key, using that key to interact with the API, and then stepping through some javascript to see the data in action."

Publications

Publications

References

References

  • Teagan Glenn

    James, almost singlehandedly, set up Apto's build and development environments. He took it upon himself to set up a build server (Jenkins), lock down the GitHub repo, implement ESLint, JavaScript unit testing (Chai), validation checks against not only the build environments but the production environment with every commit. We have had contractors come in and comment on how well set up our development process is, and we have James to thank for that!