Dylan Clemann
Software Engineer
I build D|
About me
After graduating from the University of Central Florida in 2018 with a degree in Computer Science, I spent a few years as a Software Engineer at LSQ in Orlando, Florida, where I helped build a variety of web applications, working on Frontend, Backend, and everything that comes in between.
In 2022, I joined Amazon as a Software Development Engineer. At Amazon, I work on large-scale Distributed Backend Systems, where high availability and performance are of the utmost importance.
In my spare time, I'm probably working on personal development projects, learning new recipes, or planning my next snowboarding trip.
> Professional Experience
At Amazon, I am a member of the Fuse team, which enables integrations with third-party resellers to sell Prime and other subscription services on Amazon's behalf.
My day-to-day involves technical design and implementation of a variety of event-based distributed backend systems, powering the customer subscription lifecycle. Due to the large-scale nature of these services, high-availability, performance, and redundancy are major focuses for any project.
(Intern Aug 2018 - Jan 2019)
At LSQ, I was part of a Scrum team that built and maintained a variety of projects, including customer facing web applications, internal business tools, and backend server applications.
Writing enterprise level code with robust test coverage was part of my daily life, as well as participating in architecture and design decisions, reviewing code submitted by peers, and maintaining documentation.
Working with AWS to automate the development and deployment lifecycle was also a large focus of mine, leveraging many of the technologies AWS offers, such as CodePipeline, Lambda, and CloudFormation, just to name a few.
During my internship at FIS, I worked with a team of interns to design and develop a business data visualization web dashboard. Our team underwent the entire development lifecycle, from requirement gathering, design, and deployment.
Some of my main focuses were integrating the dashboard into the existing internal .NET MVC Web application, using SQL to query data for the PowerBI visualizations that were embedded on the web page, and integrating with PowerBI’s Javascript API to build custom data filter capabilities.
As an Intern at the University of Central Florida’s Office of Research, I was tasked with designing and developing the IT department’s new public facing website.
After gathering requirements from various department heads, I created high fidelity designs and mock ups using Photoshop. Once approved, I implemented the new site using plain old HTML, CSS, and Javascript.
At the time of writing this (Dec 2022), the website I designed and built is still in use: https://it.research.ucf.edu/
> Personal Projects
A Simple Web-app for creating, storing, and sharing recipes. Allows users to create meal plans from those recipes.
This project was built over a couple days of after work hacking, so the code is somewhat sloppy. My goal was to see how fast I could get a to a useable product with the current TS/React ecosystem. I used Github Copilot extensively.
The project was bootstrapped with the [T3 Stack](https://create.t3.gg/)
View on Github
This website is my personal homepage, showcasing my professional life as a software engineer.
I've rebuilt this site countless times. This iteration, it's completely statically generated, using Next.js as the React framework, with Contentful as the Headless CMS. It is hosted on Vercel, which is extremely convenient as it has CI/CD out of the box. This was also my first time using TailwindCSS.
A web app for tracking personal expenses and spending, with strong categorization features and charts for tracking spending over time. I built this because none of the budgeting apps available had all the features I was looking for (a common theme across my personal projects...).
This project lives in an NX Monorepo, with both the NextJS frontend and NestJS backend codebases side by side (as well as another project). I wanted to experiment with a monorepo structure for sharing libraries across applications and using CircleCI to deploy these applications independently.
Next Steps: Integrate with Plaid or a similar service for automatic expense importing, Mobile views, Sharing/Splitting expenses with others, and enhance Security
I built OneCart because I could never quite find a grocery list app that had all the features I needed. The main feature I was looking for was the ability for everybody in our household to update a shared list.
OneCart uses Firestore, which enables real-time updates on all devices. Two people that live together can both create an account, then join the same household, and the list of items is connected to that household for all members to see and update.
OneCart is built using Angular and Ionic 5, which is then built for iOS and Android, as well as a PWA. Authentication and storage use Google Firebase.
The app used to be published to the Apple AppStore, but I stopped paying the fee to keep it up there, as it was mainly an experiment for me to understand the process of getting an app approved for the store.
