SUMMARY:

• Background in Cloud Application and Infrastructure Development, Computer Security & Networks, Distributed Systems, Enterprise Development, API RESTful Server Side Services, UI Design with Web and Mobile Frontends, Mobile Application Development, System Administration and Scripting.
• Knowledgeable in Linux, Unix, and Windows operating systems, as well as the Android platform.
• Experienced in various languages, frameworks & scripts including Java, C++, C, C#, Ruby, Perl, PHP, SQL, Python, Batch, Bash, Powershell, CSS, Javascript/Typescript, Angular, React Native, NodeJS, Hibernate, Spring, RabbitMQ, Docker, Hypermedia, Hadoop, AWS, ect.
• Prior TS/SCI security clearance and Security+ .

PROFESSIONAL EXPERIENCE:

Senior Software Engineer

Confidential

Responsibilities:

• Entering at mid level and leaving as a senior engineer I for several years built and delivered software orientated towards creating global rapidly deployable, fully scalable, on - demand secure networks or applications utilizing cloud services or specific onsite hardware. I built a reputation for being able to quickly pick up and adapt to any new technology or framework needed and was given lead ownership of several projects during my tenor. The work environment being fully remote was based in Agile/SCRUM cycles with a lot of adaptive/extra effort when the time called for it as typical in smaller sized companies.

Senior Full Stack Engineer

Confidential

Responsibilities:

• The flagship product Fognigma is where the largest amount of time was spent engineering to create a dynamic web service infrastructure as code platform that gives on-demand, untraceable, invisible networks built across multiple cloud providers to provide a distributed secure space for business operations. Within this I developed major changes for every single aspect of the product ranging from the angular and react based frontends, php/java based public http(s) api, perl based engine for messaging and job processing, java based micro services for application and virtual machine spawning, Postgres SQL databases supporting the engine and application databases for the built networks, and other minor parts. I was knowledgeable to the extent of mentoring fresh engineers coming to work on all of the separate parts of the product as I was considered one of the few engineers with complete knowledge on the product.
• Designing and adapting from the ground up our propriety patented encryption messaging system based in C# and Java (Conclave) into an available opensource team based messaging application based in react including javascript and java logic (Mattermost) in mobile and desktop applications. Eventually brought in more engineers once the base POC product was finished. I created from the ground up and delivered a Java microservice spring api layer (dolosd) for communication between spawned virtual desktops in secure networks from the previously mentioned Fognigma product and custom dashboard admin web GUIs as an urgent customer need.
• Inherited a legacy C++ network gateway product utilizing manager and worker spawned virtual machines for firewall and traffic configuration. Was successful in addressing all customer feature requests, feedback, and bug reports. Was handed for a brief amount of time a C++ based service deployed using Docker containers (Wicket) that would establish the hardware as an entry or exit point in a virtual network. The service could also act as a gateway manager for other devices to connect to and have access to the virtual network. In the short amount of time was able to accomplish several features and improvements before handing it off to another engineer.

Software Engineer

Confidential - Colorado Springs, CO

Responsibilities:

• As the first entry in software engineering I developed enterprise applications and infrastructure for one of the most ambitious software projects ever created. Working with over 60 other engineers as well as other companies in charge of various other components, the project is responsible for being the next iteration of the US governments satellite situational assessment and reporting system, called JMS for short. JMS was based in a JEE architecture with Integration services for other systems as well as a CI/CD pipeline with supporting design and code review efforts. Development was based in Agile/ SCRUM cycles as well as a focus on documentation and knowledge transfer to the customer.
• I had sole ownership/ programming on one of the crucial infrastructure services JMS required for operational ability. Service was in charge of hosting a server that external satellite data sources could send to as well as receive. The service depending on what type of data received would internally route the information to the other services/components of JMS. This required delegating work to other engineers as needed by my discretion
• I co-lead programming on another crucial infrastructure service JMS required for operational ability. Service was in charge receiving from the above mentioned service satellite observation files that would be properly ingested into our databases. Service would also send satellite observation files to the above mentioned service to in turn route to external sources throughout the space domain community.
• I was used as a utility engineer/programmer for all other components of JMS for the exception of hardware system administration. I learned how to be useful and independent in a giant program, how to work with different engineers and their different styles, how to work in a project with numerous different technologies and learn them quickly, how to experiment and solve problems that someone doesn't have an answer for.

Software Engineer

Confidential

Responsibilities:

• A simple P2P (peer to peer) network overlay, which routes packets between nodes. In this system there is a node manager and any given number of nodes. Each node and node manager are separate computers running the software. The node manager is responsible for keeping track of new nodes that are entering or leaving in order to update each node's routing table. Each node has an efficiently sized routing table to keep the table small so that it can scale. Proper use of synchronization and shared resource locks were pivotal.
• A distributed content harvesting thread pool system. It's objective was to create a user defined number of web crawlers to scour a website's domain and follow links recursively to gather information. The web crawlers are in the form of threads with a complimentary thread pool manager. The thread pool manager is in charge of tracking job progress so that each thread is efficiently using its resources and keeping busy. Again, proper use of synchronization and resource locks were pivotal.
• I collaborated in a team of 3 to develop a MapReduce program based out of the Hadoop HDFS architecture. It's objective was to analyze the 1990's US census data to record and produce statistical output based on predetermined questions. With 100's of gigabytes of information to pass through it was vital to efficiently map records. This required me to come up with a custom data type that could be passed as the value required by Hadoop. After that, efficient use of combiners and reducers were needed to get the correct answers for each state.

Cook/Cashier

Confidential - Fort Collins, CO

Responsibilities:

• I gained valuable insight into customer service and people skills.

Intern

Confidential - Colorado Springs, CO

Responsibilities:

• This summer internship taught me many valuable skills in the technology industry related to computer science. Cloud computing and big data were the primary focuses of the experience.