Personal details
Samuel T.
Summary
I'm a full-stack software engineer with a background in Mechatronics (BS), Management of Industrial Processes (MS) and a heavy bias towards functional, declarative, and otherwise powerful problem-solving tools. I have a proven track of pragmatic business solutions, and am looking for a team that shares my passion for the craft as a whole.
Over the past 7 years I’ve been responsible for the design and implementation of solutions involving client-side code (React with Reagent and Typescript with Rambda/Redux), server-side code (Clojure, Node and JavaEE), and a good deal of Ops (AWS, CDK, Terraform, Docker, Swarm, Github Actions), and a bit of firmware (PIC).
Work Experience
At Stedi I acted as a Serverless Engineer, working on platform-centric verticals such as client authorization and identity systems.
- Designed, built and operated multiple serverless systems, heavily leveraging AWS for minimal overhead, cost and operational burden:
â—‹ An authentication and authorization system fronting all requests to Stedi
â—‹ A membership system, bringing AWS-enforced tenant isolation to all services
â—‹ A partnership system, enabling bounded cross-tenant information sharing - Wrote and maintained a set of libraries encapsulating best-practices across all our services and 40+ repos via CDK and Projen. It handled both runtime concerns, such as rolling deployments, standardized alarms and baked-in observability; and development processes, such as github-actions deployment pipelines, automated dependency upgrades and AWS-breakglass team notifications.
- Championed the use of hermetic and reproducible environments across the company’s projects, spanning Node, Rust and Go toolsets, through the use of Nix.
- Documented and streamlined a complex Smithy-driven automated SDK generation process for all our services.
- Continuously promoted both functional and git best practices through detailed code reviews and pairing sessions, leveraging the peer’s background.
At Roomkey I acted as a Full Stack Engineer, working across projects and teams.
Between adding new features to the Clojure back-end API and the Clojurescript browser extension, my responsibilities include bringing CLJS to the main product, providing guidance and tooling to ensure that the team is able to leverage their existing skills during the process.
- Lead the efforts to seamlessly and gradually port the company’s main application to Clojurescript. Implemented a transitional hybrid Webpack-CLJS environment
- Revamped the existing JS Redux/React architecture, applying best practices and functional principles to solve long-standing navigation bugs.
- Ported the CLJS browser extension to a different browser in a short time, leveraging the environment commonalities and abstractions.
- Fully spec-ified the main application data flow, uncovering inconsistencies in third-party data being used in production.
- Continuously promoted both functional and clojure best practices through detailed code reviews and pairing sessions, leveraging the peer’s background.