Profile picture

Eli Sachs

Back End Developer
Pronouns he/him
Open Resume Email Directly

About me

Environmentalist, educator, 6th grade Spelling Bee champion, world traveler, music lover, collaborator, lifelong language learner, running enthusiast, aspiring paella chef, gardener and Peace Corps volunteer.

I'm an enthusiastic and resilient developer with a focus on backend engineering, Ruby on Rails and creating and consuming APIs. Prior to software development, I worked in the educational and environmental sectors teaching languages and ecology, managing development projects, and conducting trainings based on environmental, health and social issues.

I made the switch to software development born from the desires to grow personally, to have a larger impact through tech, and to further challenge myself professionally and creatively. I love the process of researching and writing quality code, and learning with others to discover and implement new ways to build and maintain something great.

My experiences working on teams, my passion for making a difference in the lives of others, and my love of puzzling and problem solving are just a small part of what I have to offer. If you would like to share experiences or connect, please reach out and let's arrange a time to meet.

@ easachs13@gmail.com @ github.com/easachs @ calendly.com/easachs/15

Preferred locations

  • Denver, CO
  • Boulder, CO
  • Broomfield, CO
  • Centennial, CO
Open to other locations and/or remote work

Previous industries

  • Education Management
  • Environmental Services
  • Primary/Secondary Education

Skills

  • AR
  • Atom
  • Continuous Integration
  • Git
  • GitHub
  • Heroku
  • PostgreSQL
  • Rails
  • RSpec
  • Ruby
  • SQL
  • User Authentication
  • Visual Studio

Currently learning

  • JavaScript

Projects

Skedaddle

Skedaddle

Project scope time 40 hours
Collaborators Profile picture for John Santosuosso Profile picture for Nick Jones Profile picture for Drew MacNicholas Profile picture for Wesley Garcia

Tools Used

  • AR
  • Bootstrap
  • Continuous Integration
  • Git
  • GitHub
  • Heroku
  • PostgreSQL
  • Rails
  • RSpec
  • Ruby
  • User Authentication

Skedaddle is a travel search application with a relational database, service-oriented architecture, and OAuth user authentication functionality. It exposes and consumes multiple API endpoints to create a custom itinerary with trails and restaurants.

This was a project idea that I pitched, and had the opportunity to work on with a team of four other developers over a two week period. Together we built out both front and back end services, practiced consuming and exposing APIs, and implemented Google's OAuth2 to allow users to register, log in, and search for and save itineraries. It was also a great exploration into the art of visual styling. Overall, it was an excellent learning experience, where we were able to practice and expand upon several elements of building a professional Rails application.

Launch the App Code Repository
Screenshot detail for project Skedaddle
Screenshot thumbnail #1 for project Skedaddle Screenshot thumbnail #2 for project Skedaddle Screenshot thumbnail #3 for project Skedaddle Screenshot thumbnail #4 for project Skedaddle

Heat Check

Heat Check

Project scope time 40 hours
Collaborators Profile picture for Ivy Nguyen Profile picture for Phillip Stewart Profile picture for Gauri Joshi Profile picture for David Daw Profile picture for Cleveland Ticoalu Profile picture for Ethan Nguyen

Tools Used

  • AR
  • Continuous Integration
  • Git
  • GitHub
  • GraphQL
  • Heroku
  • JavaScript
  • PostgreSQL
  • Rails
  • React
  • RSpec
  • Ruby
  • SQL
  • User Interface Design / UI
  • Visual Studio

Heat Check is a full stack web application with a Javascript/React frontend and Ruby on Rails backend that aims to help food aficionados find spicy restaurants and their spicy dishes, with ratings and reviews functionality.

This was a project that I worked on over a three week period with a team of six other developers, including a frontend team working with React. We used an agile workflow and communicated with a project manager to design and implement our backend service by finding restaurants through Yelp's Business API and scraping a menu from a restaurant's webpage with Nokogiri. That data was communicated to the frontend with GraphQL and deployed using CircleCI for CI/CD, both of which we learned to use over one week.

Launch the App Code Repository
Screenshot detail for project Heat Check
Screenshot thumbnail #1 for project Heat Check Screenshot thumbnail #2 for project Heat Check Screenshot thumbnail #3 for project Heat Check

Sweater Weather

Sweater Weather

Project scope time 20 hours
Collaborators

Tools Used

  • AR
  • Continuous Integration
  • Rails
  • RSpec
  • Ruby
  • User Authentication

Sweater Weather is a weather-forecast / book-lookup / roadtrip-planning application where users can register, and receive and use API keys to access search results. It consumed several APIs including Mapquest and OpenWeather in order to process and respond to JSON requests.

I really enjoyed working on this because it required exploring and combining several tools that I've learned over the last several months - from APIs, to user authentication and authorization, to robust unit and feature testing. I really love exploring and writing user functionality, and this app was my first foray into letting users create and use an API key.

Code Repository
Screenshot detail for project Sweater Weather
Screenshot thumbnail #1 for project Sweater Weather Screenshot thumbnail #2 for project Sweater Weather Screenshot thumbnail #3 for project Sweater Weather Screenshot thumbnail #4 for project Sweater Weather

Rails Engine

Rails Engine

Project scope time 15 hours
Collaborators

Tools Used

  • AR
  • Rails
  • RSpec
  • Ruby

Rails Engine is a Ruby on Rails/PostgreSQL database of merchants/items that exposes thirteen separate RESTful API endpoints. It includes search functionality, serialization, and, of course, full testing coverage.

This was a great learning experience for me, as it required building out purely back end API exposure, and required us to meet extensive testing criteria, which was completed in full. As such, I gained significant experience with error handling, as well as performing database queries.

Code Repository
Screenshot detail for project Rails Engine
Screenshot thumbnail #1 for project Rails Engine Screenshot thumbnail #2 for project Rails Engine Screenshot thumbnail #3 for project Rails Engine