JD Skinner

Senior Software Engineer at BlockFi
  • Claim this Profile
Contact Information
us****@****om
(386) 825-5501
Location
Salt Lake City, Utah, United States, US

Topline Score

Topline score feature will be out soon.

Bio

Generated by
Topline AI

5.0

/5.0
/ Based on 1 ratings
  • (1)
  • (0)
  • (0)
  • (0)
  • (0)

Filter reviews by:

LinkedIn User

It's hard to overstate how critical JD has been to the success of the credit card product. His expansive technical acumen, combined with his natural, easy-going leadership style has made him a cornerstone member of our team. JD never shies away from a challenge, making time to mentor other engineers, or even lend support to our client service team. I'd trust JD to lead any product team and I'm glad I can call him a friend.

You need to have a working account to view this content.
You need to have a working account to view this content.

Experience

    • United States
    • Financial Services
    • 100 - 200 Employee
    • Senior Software Engineer
      • Aug 2020 - Present

    • United States
    • Financial Services
    • 100 - 200 Employee
    • Senior Software Engineer
      • Dec 2019 - May 2020

      The engineering organization at Divvy is akin to the Spotify model; small, focused teams working to solve a particular problem, or own a feature-set. Divvy is hosted on AWS, and GitLab pipelines were used to monitor continuous integration of code. Kubernetes was used to automate deployments and scaling. I was on the Budget squad, which was one of the oldest parts of the Divvy codebase, and one of the most complex. Within a short time at Divvy, I was asked to take lead on a new feature; the Budget People Picker. Adding new members to a budget was a sore spot for a lot of our customers. Sending funds was clunky and harder than it needed to be. I worked on the GraphQL API via Absinthe that allowed the front end to streamline the process so that users could be added to a budget, and funds could be sent to everyone in a budget at the same time. Another feature I took leadership of was the Selected/Default Budget. I updated the pipeline that processes new transactions as they come in which verifies that the user has enough funds for the purchase that they are making, categorizes it correctly, and sends a notification based on the type of transaction that occurred. This changed the flow of transaction processing (a core business function) and allowed for the removal of a cron job that would potentially change a users selected budget every 15 minutes, which was confusing and unintuitive to our users. Show less

    • United States
    • Financial Services
    • 100 - 200 Employee
    • Senior Software Engineer
      • Oct 2019 - Dec 2019

      Even though I had never used elixir professionally before, I was hired at Nav as an Elixir developer on the Marketplace team. Within 2 weeks, I was working on my first integration with a new loan partner. The goal of this integration was to pull loan products from the loan provider, parse the data into a standardized format that we then turn into Loan offer products for our users. Two weeks later, that integration was ready for Production. Nav is also hosted on AWS, with GitLab hosting the version control and pipelines with Kubernetes for deployment orchestration.Nav used a more Agile/Scrum-like style. While at Nav, I attended a Scrum Alliance Scrum Master training and became a certified Scrum Master. I took that training and lead my team’s Scrum ceremonies. This leadership experience helped me transition into an intermediary role when my Product Manager left the company. His departure opened a massive hole in our team and communication with other teams started to suffer greatly. I stepped in to ensure communication didn't break down. I met regularly with Business Development to ensure issues reported by our loan partners were properly investigated and resolved. I met with Design to ensure my team had what they needed in order to complete the work we had said would be done. I increased clarity and communication within my own team, ensuring that we were solving the right problems for the right reason. I also continued work on more integrations, and API improvements that would facilitate progress on a major new initiative. Show less

    • Software Engineer
      • Oct 2018 - Oct 2019

    • United States
    • Information Technology & Services
    • 1 - 100 Employee
    • Software Engineer
      • May 2017 - Oct 2018

      I joined a very small team at Kuali, where I quickly took over as lead on their Business Continuity Planning product, Kuali Ready, which was targeted at Universities. Kuali: Ready was written in Ruby on Rails and hosted on AWS. In my first months at Kuali, while familiarizing myself with the codebase, I worked on creating the AWS pipeline and scaling infrastructure. The first major feature I worked on was a dashboard for our users, showing up to date information on the state of their University's state of readiness. I also updated the very old and limited PDF generation utility which allowed us to improve the design and functionality of PDFs generated by Kuali: Ready, which our customers could use to keep hard copies of their business continuity plans, and print out for use when conducting tests of their plans. Show less

    • Printing Services
    • 1 - 100 Employee
    • Software Engineer
      • Aug 2012 - Jun 2017

      Franklin Anywhere is a very full featured print shop management tool written in Ruby on Rails and deployed to Heroku. It offers print shops everything they would need to run a print shop of nearly any size. In my time there, I worked on all aspects of the product, and one of the more mentionable aspects was the Image Size Picker. When laying out a print job, there are various things that need to be taken into consideration (parent sheet size, press sheet size, image size, grain direction, bleeds) that are involved in calculating how much stock will be required to run a job. I implemented this feature from top to bottom, including a visual representation of the selected layout. This made it very easy for the person estimating a job to see that the job was being estimated as desired. Show less

Education

  • University of Utah
    Bachelor of Arts - BA, Japanese Language and Literature
    2005 - 2008
  • University of Utah College of Social and Behavioral Science
    Bachelor of Science - BS, Psychology
    2005 - 2008

Community

You need to have a working account to view this content. Click here to join now