Understanding a process is one part of the work. Understanding the technology behind it helps me figure out what can be changed, what needs to connect, and what it will take to build a useful solution.
These are tools I've used at work, in my projects, and through my education. My experience varies across them, so I've described how I've used each rather than assigning proficiency ratings.
Process automation
At Amazon, I used Excel and VBA to build tools around the way the work actually happened. That included a productivity-tracking prototype and inbound and outbound automation that brought together tasks spread across several systems.
Operational analysis
I used Tableau reports created by management to understand productivity, look for patterns, and support capacity planning. My part was interpreting what the data meant for the operation and where it pointed to something worth investigating.
Working with data
My software development and IT coursework includes SQL and relational databases. That gives me a foundation for understanding how information is stored, how records connect, and how to query the data a system depends on.
Application logic and backend development
I use Python and Django in application projects, including our current stock trading capstone. My work includes market simulation, price history, and bringing features together so they follow the same rules.
Interactive applications and APIs
I've used JavaScript for interactive websites and applications, and Node.js and Express for backend coursework. That work includes API integration, authentication, and connecting applications to databases.
Structure, layout, and accessibility
I use HTML and CSS to build interfaces people can navigate and use across different screen sizes. That includes page structure, forms, responsive layouts, and accessibility considerations.
Component-based interfaces
I've used React with Vite for web projects and prototypes. Breaking an interface into components helps me work through how information moves through the application and how the pieces fit together.
Application data and relationships
My coursework and projects include SQL Server, MongoDB, and SQLite. I've worked with database queries, application models, and the connections between stored data and application behavior.
Configuration and deployment
My IT coursework includes Windows Server, Active Directory, and Microsoft Endpoint Configuration Manager. In a lab environment, I've configured software deployments, explored security policies, and worked with reporting and system configuration.
API integration
I've used Cloudflare Workers as a server-side connection between web applications and external APIs. That lets the application make requests without putting API credentials in the browser.
Turning scope into coordinated work
For our capstone, I work through requirements, document the system design, and break the work into assignments. I use Trello to help track progress and coordinate features that depend on one another.
Collaboration and change review
I use branches and pull requests to keep changes reviewable. As capstone lead, I review teammates' work, discuss follow-ups, and coordinate integration so separately developed features work together.
Following the problem through the system
I use browser tools and application tests to investigate behavior and check changes. I want to understand where a problem starts, what it affects, and whether the fix holds up when the pieces come together.
