Karson Kalt

.dev

    Software engineer, UX advocate, people person.

    I create UI experiences for the web that enable organizations to build faster and scale effectively.

    Karson Kalt
    September 26
    Currently working on upgrading observability dashboards, filtering, query variables, and data visualization at JupiterOne.
    Past statuses

    About Me

    Growing up, I was always interested in design and technology. My favorite book was The Way Things Work by David Macaulay. I loved the illustrations and the way it explained how things worked in a simple and fun way. I built toy cars and buildings with K-NEX. With a math teacher for a mom and an industrial engineer for a dad, I naturally loved the space where logic-meets-design.

    As an engineer, I love building and designing apps for humans. Design to me is not "making it pretty", but surfacing the right information, to the right person, with the right controls, at the right time. Reframing this from an engineering perspective, great UX is about the human-API. We naturally process information adhering to a set of rules -- and the best interfaces are the ones that understand and respect those rules.

    Work History

    I began my professional career in 2014 working as a store manager for Target. After a few very challenging, but very rewarding roles, I re-evaluated my career path and attended a coding bootcamp at Flatiron School in 2020.

    In 2021 I joined JupiterOne as a Software Engineer focusing on UI in React. After becoming more comfortable with the codebase, I began to take on more responsibilities. A few projects I worked on include: rolling out a design system, upgrading our data viz library, implementing virtualization and data-grid features for query results, assisting transitioning to a microfrontend architecture , building natural language querying, and overhauling our multi-modal search experience.

    In 2024 I became a Senior Software Engineer at JupiterOne with the help of great mentors. Some recent projects I've worked on include introducing continuous threat and exposure management and adding smart classes to our query language and data model.

    My Resume LinkedIn

    My Stack

    Here is a short list of things that I use most often when starting a new project.

    • React for true web apps. I have mixed feelings about the framework but can't argue that there is a large community and ecosystem around it.
    • TypeScript. I believe in strong types, especially in an enterprise codebase. And with node now testing running TS, it's a no-brainer.
    • Node for backends and scripting. I love the ecosystem and the ability to share code between the client and server.
    • CSS of course for styling. Though I used to use them, I now don't think CSS preprocessors are needed with all of the new developments in CSS. Modern CSS supports design tokens, theming, and handles a lot of interactions that used to be handled by JS.
    • Vanilla JS and Browser APIs. When I can, I try to stick to native web standards do so much cool stuff. Web components, element anchoring, view transitions, nested CSS is super powerful, so I keep it simple if I can.
    • Next.js if I need SSR and infra out of the box. I don't love the pricing model, but getting something spun up quickly is a huge win.
    • Vite, it's my favorite build tool.
    • Vitest for unit testing. RIP Jest and Mocha, I won't miss you.
    • Cypress for E2E testing.
    • AWS for serverless infra and quick horizontal scaling.
    • Storybook and Chromatic for interaction testing, design system libraries, visual regression testing, and as a UI sandbox.
    My GitHub