etherealiska

Joined as a supporting frontend engineer and quickly became the team lead through consistent delivery and technical ownership. Improved performance, fixed critical bugs, and shipped new features using TypeScript, React, and Tailwind CSS. Overhauled the frontend codebase by implementing a new design system from Figma, extending unprovided pages with custom UI, integrating backend APIs, and reducing technical debt to ensure maintainability and scalability. Led the deprecation of a legacy backend in favor of a fully blockchain-based architecture, building infrastructure to interface with decentralized networks (Ethereum, Arbitrum, Base) and deliver low-cost, high-availability data — outperforming providers like Alchemy and Infura. Designed, implemented, and deployed a full intent-based trading API using Node.js, including database schema design and AWS-hosted infrastructure. Integrated this system into the frontend for seamless user interaction. Built and managed Kubernetes and Docker-based infrastructure across AWS, enabling highly available services that support blockchain operations and frontend data needs. Architected and deployed a scalable system of blockchain subgraphs, using AWS RDS and custom schema design to support efficient and reliable data querying for the frontend. Architected and managed Kubernetes and Docker-based deployments across AWS, optimizing resource usage and scaling policies — resulting in a 70% reduction in infrastructure costs.

Lead every aspect of software development from architecture to implementation, while assisting with some aspects of product development and design. Decided which technology would be most appropriate for the task at hand in, for the frontend, backend, api, database and server deployment. As well as determining how to align the cloud infrastructure to satisfy the security concerns of prospective clients. Personally implemented each aspect of the technology product, which includes React / Typescript (frontend), NodeJS (backend), Loopback (api), Mongo (database). And for deployments Docker, AWS ECS, AWS Cloudformation, AWS VPC (networking / infrastructure). Worked closely with CTO of major company, to ensure that the architecture and implementation was sound, secure and cost effective.

Worked completely remotely to build a time tracking and invoicing web application using the Javascript framework Angular, Material, C# (Asp.net core), RabbitMQ, Postgres and Kubernetes (K8s), none of which were used previously in a professional setting. Began contributing substantial amounts of code within a week of starting, by spawning the idea (and then creating) a locally deployed K8s stack, that mirrors the stack deployed on the dev server. The idea being that there is no need for local testing to be different than what's on the server if K8s can run everywhere. This process involved spawning 6-9 different services in their own repos (web server, API, saga service, message consumers), building the appropriate images based on the local code, and making sure they can all communicate (networking). This process was automated via C# scripting. The next step in contributions were to begin developing back end features like generating reports on time spent and money earned via excel and pdf using the C# backend. This involved learning how the Rabbit messaging system work to pass data around multiple services, and researching and choosing the best option to generate pdfs, and writing all in a somewhat unfamiliar language. Within a year, contributions to the full software development cycle were being made on a regular basis. From creating a new interface to account for users with different roles in different companies, to that is compliant with federal regulations, and designing a system for reliable tests in a micro-service architecture. Other tasks include: Building angular components according to the designer's specifications. Fixing bugs from former developers. Building front end features like connecting to various invoicing applications (like QuickBooks) via OAuth. Getting very very familiar with Observables, and Redux. Using 3rd party APIs and communicating with their developers to retrieve and post data relevant to specific users. Architecting solutions for features that don't have the necessary backend structure.

Continued many/all of the same duties required in previous position at Xamarin. The team was kept largely the same after an acquisition. Used cloud engineering resources to transform manual build infrastructure to automated infrastructure. Learned the build system of a product in order to build it from scratch and use automated build resources instead of physical hosts in order to ensure reproducible build environments. Worked extensively with different teams building different products with varying build systems, and organize a transition from one CI to another. While also accounting for every aspect of the release pipeline that will be changing or needed to be preserved during the transition. Experimented with docker and got a working system that furthers the attempt for fast starting reproducible builds. Also used docker to enhance the server monitoring system. Updated all the code for the previously mentioned monitoring system, using ES6 and an updated build system using Yarn to manage dependencies. Switched from using a files/git as the datastore to using a postgres database with docker. Also switching from a Ruby Gem to automate/parallelize connecting to multiple servers, and implemented a more reliable method using pure Net::SSH in ruby. This all took place while continuing the daily duties of diagnosing random problems that arise in CI due to machine misconfiguration in physical hosts, developers using the tools incorrectly, needing to add functionality for the developers, fixing bugs in the various CI system plugins.

Responsibilities included: Creating software and websites used to keep track of installations and status of machines. Operating systems mainly consisted of Mac and partially consisted of Windows. Automate configuration of those machines. Maintain the in-house continuous integration system, and maintain the Jenkins CI system. Daily responsibilities were standard Ops tasks (installing required software, clearing space, etc.). Spent a large amount of time writing software to easily view build times, disk space, and trends in order to actually gauge how well the entire release cycle is performing. Maintaining and adding features to 3 different CI systems (1 open-source, and 2 different Jenkins Instances) was also required.

Responsibilities were given on an as needed basis as a part of the DevOps team. Ranging from modifying git repository workflow to be easily integrated with other technology, creating multiple chef cookbooks for production, fixing broken software, and modifying and monitoring a site using php. Had to assume the role of another teammate for two weeks, without much knowledge of the specifics of his technology at a last minutes notice. Worked with QA and Performance teams during this time, and figured out how to locate and fix errors from anywhere in the stack, while being responsible for a successful deployment to production. Learned all new technologies in a timely fashion. Linux administration, Ruby, PHP, Chef, and Git.

Began as a part-time worker/consultant for this startup learning basic html and using Python for data mining. Had no previous knowledge of python and was hired on the basis of learning what was necessary in the given amount of time. Was hired full time in May 2012 for demonstrating competence in the field, and willingness to learn. Was introduced to web development (Javascript/CSS/Ruby on Rails) in September 2012. Figured out how to make complete overhauls and create websites from scratch. Was the only web developer on this skill application from that point forward.

Worked closely with Prof. Jackie Liederman PhD, to help design and implement the components of a word learning experiment for credits towards a Neuroscience degree. First experience working with a team to achieve a common goal, and designing an interface in order to obtain measurable data. Was later assigned to figure out how to program the experiment using an unknown language (e-prime). Was hired to finish the project in the subsequent semester.

Input and organized information into the database in order to eliminate paper usage, Worked alongside officers and other interns on specific projects. Toured the court system, Special investigations unit, Autopsy and other, in order to learn more about each aspect of the legal system.

Was chosen to live in the sophomore dormitory as a senior, monitored study hours, met with and coordinated information with dormitory teachers, organized events for all students on campus.