Senior Software Engineer
RallySoftware - Developer Experience / CI & CD
Rally Software - Full Stack Microservices
October 2014 to August 2016
Rally Software - Front End
October 2012 to October 2014
University of Arizona - College of Soil, Water, and Environmental Sciences
Bioinformatics Research Specialist
February 2011 to July 2012
Tucson, Arizona Area
University of Arizona College of Social and Behavioral Sciences
Web Application Developer
June 2009 to October 2011
Tucson, Arizona Area
Senior Software Engineer @ Workday Jenkins, Cloud Infrastructure, and Internal Tools. Boulder, COSoftware Engineer @ RallySoftware - Developer Experience / CI & CD Design, implement, and maintain fully reproducible continuous integration and delivery infrastructure, heavily relying on advanced usage of Docker and Jenkins.I am a member of a small (2-3 people) extremely dynamic team who reacts quickly to support our customers (Rally's engineering organization) with whatever they need when writing, testing, building, and deploying their software.We heavily rely on Jenkins and Docker to achieve full automation of all of this tech. There is no manual configuration required to redeploy nearly any of our infrastructure. We run 15-20 Jenkins instances, each in a Docker container. Data such as job history is in a separate container and backed up to s3. All of our Jenkins slaves are also Docker containers, giving us an incredibly reliable, fast, and scalable system. We run more than 100,000 containers a month across more than 14,000 builds.Teams are (somewhat) responsible for creating and maintaining the jobs (all written in either Job DSL or Jenkins Pipeline) but we heavily contribute expertise and knowledge sharing to make sure the job is done right.Accomplishments:- Created infrastructure by which any user can spin up their own 'test' version of a CI instance to test out changes to jobs. Includes automatic creating of URL routes to access the system by the name they choose, and custom job DSL to exclude certain parts of the job from test systems, such as various job triggers (e.g., cron, push triggers, pull request triggers), and deployments- Created custom job DSL to create jobs for building docker images, reducing LOC by an order of magnitude while standardizing the interface and adding features- Wrote custom init scripts for ~10 Jenkins plugins- Forked an abandoned but heavily used Jenkins plugin w/ a critical bug that surfaced, fixed the issue, and redeployed all CI systems w/ the changes before it caused any serious downtime- Dockerized many of our internal services, even when no one knew how they worked Boulder, COSoftware Engineer @ Rally Software - Full Stack Microservices Moved to a team working on our emerging microservices architecture. We were responsible for development and maintenance of our real-time object change message system that pushed all user changes for all object types to the rest of our services. This consisted of a service to extract changed artifacts from our database, a service that would create a 'diff' of the artifact (built on top of Datomic, a time-series database, itself backed by Riak), and a service that is a rules engine that provides extreme flexibility to trigger actions based on specific criteria. All tied together with Kafka queues.Some of the possible actions are: sending emails when a certain fields on a work item, or type of work item, changes, sending realtime notifications to users though the UI, and providing specific change messages to downstream services (e.g., our authentication uses this to update its database of user accounts).I saw that the system was too complex to be reliable (we suffered weekly outages when I joined) so I lobbied to simplify the system. By careful redesign, we were able to generate the OCMs inside our application rather than externally (which forced us to duplicate our entire production dataset), allowing us to kill 2 of the services. We went from outages weekly to very rarely.I also spearheaded the redesign of our HTTP REST API. v1 of our API allowed (and forced) users to directly create rules in the rules engine, which led to unmaintainable complexity and performance issues. We redesigned the API from scratch, exposing only the necessary endpoints to enable our use cases. This improved the experience for external devs using our endpoints, prevented performance problems, and allowed us to refactor much more easily.During this time I used React/Redux to expose this functionality in our app.I also created a tool ('Stacker') that greatly simplifies the process of starting all of this technology locally for development that is still heavily in use. From October 2014 to August 2016 (1 year 11 months) Boulder COSoftware Engineer @ Rally Software - Front End 2013 - 2015Worked on front-end technologies using Ext-JS. Worked to create solid, reusable, composable components. Accomplishments: - became knowledgable of the best practices and internals of Ext-JS- created a 'Rally Labs' feature that was highly rated called Tag Popover that allowed a user to click a tag anywhere in the application, showing an editable datatable of all work items that contain that tag (there is currently nowhere in the app to see that information, even today) From October 2012 to October 2014 (2 years 1 month) Boulder, COBioinformatics Research Specialist @ University of Arizona - College of Soil, Water, and Environmental Sciences Process metagenomic samples from Kartchner Caverns (Southern Arizona) as per the scientists’ requests. Learned and applied unfamiliar technologies on the fly to our research. Wrote custom scripts, applications as needed.Primary languages: Ruby, PHP, JS, Python, Perl, Bash From February 2011 to July 2012 (1 year 6 months) Tucson, Arizona AreaWeb Application Developer @ University of Arizona College of Social and Behavioral Sciences Design, implementation, & maintentaince of web-based applications used by the college: SBS Snapshots Newsletter application, Women’s Plaza of Honor RSVP System, Mass mail program. Updated legacy systems to improve per- formance, remove bugs, add features. Maintained 30-35 departmental web- sites.Primary languages: PHP, JS, HTML, CSS, SQL, Bash From June 2009 to October 2011 (2 years 5 months) Tucson, Arizona Area
What company does Brandon Fryslie work for?
Brandon Fryslie works for Workday
What is Brandon Fryslie's role at Workday?
Brandon Fryslie is Senior Software Engineer
What industry does Brandon Fryslie work in?
Brandon Fryslie works in the Information Technology and Services industry.
Extraversion (E), Intuition (N), Feeling (F), Judging (J)
1 year(s), 11 month(s)
There's 86% chance that Brandon Fryslie is seeking for new opportunities
Enjoy unlimited access and discover candidates outside of LinkedIn
One billion email addresses and counting
Everything you need to engage with more prospects.
ContactOut is used by
76% of Fortune 500 companies