Personal details

Daniel S. - Remote

Daniel S.

Timezone: Central Time (US & Canada) (UTC-5)

Summary

Architect: Collaborated with technical leads to design and implement numerous mission critical systems. Message bus, Real-time financial institution payments and settlement, as well as core accounting systems and reconciliation.

Software Developer: Over 13 years of experience with deep knowledge in multiple languages across multiple platforms. True full-stack engineer--Front-end, back-end, and cloud infrastructure.

Project Manager: 15 years of management experience. Worked with
multiple teams to streamline development processes, planning, project
execution, product/stakeholder coordination, and alignment with
strategic company goals.

Ambassador: Facilitated technical and product team collaboration
through frequent and consistent feedback. Championed agile ideology
to improve both execution speed as well as aligning expectations
across the organization. Planned and executed multiple company-wide
internal Hackathons.

Work Experience

Engineering Director
Hudl | Jan 2019 - Present
C#
React
I am the Engineering Director in charge of the projects surrounding Business Operations: Financial Data, accounting, Inter-business-unit operations, core data management, and business health reporting. I am still very hands on as far as the code, but I spend a lot of time helping teams find the right architectural solutions to complex problems with a large number of stakeholders.
Lead Software Engineer
Hudl | May 2017 - Jan 2019
C#
React
Lincoln, Nebraska I currently work at Hudl as the Lead Software Engineer in charge of the technical quality of projects surrounding billing and operations. Our team builds the tools and workflows that enable us to scale and improve Hudl's operations.

Personal Projects

Billing Performance and Resiliency
2017
C#
API
Back-End
Protect our core systems from 3rd party products' downtime, improve the performance of our system to aid in seemless user interactions. This project was essentially the addition of proper fault tolerance for 3rd party systems combined with a robust caching implementation. This included building a caching layer for our most called endpoints and a strong invalidation strategy tied to both internal actions as well as 3rd party webhooks. The final outcome was performance improvements from 5000x upward. It also got 99.98% of all calls to our cluster to under 1 second. In addition, we lowered the number of outgoing API calls to 3rd party provides by millions. When the last three downtime events occurred they went completely unnoticed by both internal and external users.