Sarah Yasonik
Rails engineer at GitLab.
Contact me!
sarah@yasonik.com
(262) 227-7987
Work
GitLab Inc.
January 2022 - Team split!
Monitor:Monitor -> Monitor:Respond
August 2021 - Promotion!
Backend Engineer -> Senior Backend Engineer
October 2020 - Team merge!
Monitor:Health -> Monitor:Monitor
April 2019 - Team split!
Monitor -> Monitor:Health
January 2019 - Hired!
Backend Engineer, Monitor
As technical lead of our team, I facilitated 13 projects and led 7. I guided cross-team PMs, designers, and engineers in exploring new product areas and prototyping solutions.
While Acting Engineering Manager for 4 months, I transitioned the team through a reorganization, onboarded multiple new engineers, brought an IC through the promotion process, managed our team’s OKRs, and taught other engineers strategies for approaching technical planning themselves.
To prevent reconciliation errors and reduce risk exposure, I wrote a high-performance, constant time algorithm for generating recurring calendar events to reduce infrastructure load.
Increasing endpoint reliability to 99.95% from 99.8%, I refactored a high-volume endpoint for performance. Response times dropped from ~1s to ~100ms on average, and from ~20s+ to ~8s in the worst case scenario.
Major tools: Ruby/Rails, RSpec, Capybara, GraphQL, Vue, Prometheus, Grafana, Kibana, Sisense
FutureAdvisor
December 2018 - Left!
Travelling internationally!
May 2018 - Relocation!
San Francisco -> Remote
January 2018 - Promotion!
Software Engineer I -> Software Engineer II
October 2017 - Team change+!
Portfolio Intelligence -> Models & Algorithms Team (I'm scrum master now!)
May 2017 - Team change!
Core Product Team -> Portfolio Intelligence Team
August 2016 - Hired!
Software Engineer I, Core Product Team
Most recently, I'd been developing new services to dynamically and scalabily generate trade recommendations for client portfolios, while orchestrating the team's resources to deliver a well-documented API.
Major tools: Ruby/Rails, json-schema, Scala, Play, AWS SQS, S3
Previously, I acted as primary architect on the front end of an internal tool to manage trades placed on a day-to-day basis.
Major tools: React, create-react-app, css-modules, Redux
Starting out, I took a "where am I needed?" approach to our codebase, implementing new features to product specs, cleaning old junk up where possible, and thoroughly documenting the nasty bits.
Major tools: Ruby/Rails(backend), Backbone, Marionette, Epoxy, React, Redux, more Rails(front end)
Merus, Inc
April 2016 - Left!
Going back to school!
June 2015 - Hired!
Technical Support Specialist
I did a little of everything at Merus - resolved customer support issues, taught off-site product trainings, coordinated data migrations for new clients, performed data migrations.
Major tools: SQL, Ubuntu, Excel
Education
App Academy
San Francisco
May 2016
B.S. Materials Science & Engineering
The Ohio State University
2015
Personal Projects
WIP! Camellia 2.0 | GitLab
Tea app v2 - restarting Camellia.io from scratch with a narrowed vision, a new set of tools, and a partner with a thing for Ember
Major tools: Rails, GraphQL, Ember
Camellia.io | Github
Single page application meant for managing one's personal tea inventory, tracking teas they've tried, and reviewing teas.
Major tools: React, Ruby/Rails
Command-Line tool for teaching guitar chords | Github
Displays different chords on the screen based on a selected difficulty. Rewriting the project in different languages has been a helpful learning aid.
Major tools: Ruby, JavaScript, Python