Intro
Jagger Brulato
Full-stack engineer across product, platform, and language tooling.
I like work that makes me understand the whole system: the product surface, the backend, the tooling around it, and the operational reality once it is live.
- I have shipped frontend product work, backend services, internal platforms, dashboards, mobile apps, and developer-facing tooling.
- I do my best work when I can move across layers instead of treating the UI, the backend, and operations like separate worlds.
- The side projects here are a good sample too: interpreters, simulations, games, and backend utilities.
Focus
The work I’m most drawn to usually makes something simpler, clearer, or easier to use.
That can mean product features, platform work, developer tooling, or just making a system easier for the next person to work in.
Own the whole path
I like being able to follow a problem from the interface all the way down to the backend and operational details.
Bring systems thinking into product work
A lot of what I’ve learned from systems and platform work shows up in how I build product software too.
Build things other engineers use
Some of the most satisfying work for me is tooling, visibility, onboarding, and internal abstractions.
Experience
This is the fastest way to get a feel for the kinds of work I’ve done.
It spans product engineering, platform work, and leading teams while still staying close to the code.
Red Ventures
Platform Engineer
Built internal platform capabilities that made it easier for engineering teams to launch, operate, and understand applications without rebuilding the same infrastructure each time.
- Designed, prototyped, and developed flexible internal applications for common platform use cases so new services could be launched through a streamlined platform experience instead of bespoke setup work.
- Built frontend product surfaces for platform tooling in TypeScript and React, alongside the infrastructure and runtime work behind those flows.
- Used Golang to generate and deploy Terraform through a custom Terraform provider and runtime, turning infrastructure setup into a more repeatable platform workflow.
- Built internal dashboards and monitoring surfaces that gave engineers visibility into cost, availability, and process health, feeding back into architecture and operational decisions.
- Worked at the seam between platform reliability and developer experience, keeping systems healthy while also making them easier for other engineers to use.
GolangTypeScriptCustom providersReactPlatform automationTerraformDashboardsObservabilityPlatform engineeringWeb
Lowe’s
Software Engineer
Worked as a full-time software engineer after interning there earlier, contributing in a large enterprise environment with real production delivery expectations.
- Built and maintained enterprise retail systems using Java, Spring, Spring Boot, and Kafka in a mature production environment with established delivery processes.
- Maintained a suite of 20+ microservices, updating Docker images and runtimes, upgrading Alpine base versions, and addressing security vulnerabilities across the service fleet.
- Worked across existing systems, stakeholders, and release workflows rather than building in isolation, which meant shipping changes that fit into a much larger operational environment.
- Built on earlier experience with Lowe's merchandising and pricing systems, adding more depth in large-scale backend delivery and enterprise software coordination.
JavaSpringSpring BootKafkaProduction deliveryDistributed systemsEnterprise softwareMerchandising systemsRetail systems
Software Engineer
Built distributed data systems at Google, spanning self-service pipeline generation, shared data infrastructure, and internal reporting systems in a high-scale production environment.
- Built complex distributed data systems using Apache Beam, where arbitrary graph pipeline definitions were generated at runtime and executed through a self-service internal tool.
- Worked with Bazel, Pub/Sub, Spanner, BigQuery, Cloud SQL, PostgreSQL, and other databases, sources, and sinks to support flexible pipeline execution across varied data environments.
- Built custom reporting and data pipelines around Google's internal shared data layer for mergers and acquisitions, automating manual report creation and exposing M&A data more broadly across the company.
JavaApache BeamBazelBigQueryCloud SQLPostgreSQLPub/SubSpannerSelf-service toolingData pipelinesDistributed systems
Cornell Design & Tech Initiative
Developer Lead
Oversaw development across DTI applications and the technology around their maintenance and deployment while still staying hands-on with implementation and developer support.
- Oversaw development across DTI apps on multiple platforms, including native iOS in Swift, native Android in Java and Kotlin, and cross-platform work in Flutter.
- Supported teams building applications in React, React Native, and Angular, with backends primarily in Node and supporting services built with Firebase and GraphQL.
- Balanced leadership responsibilities with hands-on implementation, helping developers get unstuck while keeping architectural decisions practical and close to the code.
DartJavaKotlinSwiftAngularFlutterGraphQLNext.jsNodeReactReact NativeSvelteVue.jsFirebaseLeadershipAndroidiOSMobileWeb
SWE Intern
Created an open-source scheduler and roster organizer for Alvin Ailey Dance Company in NYC, building a multi-user full-stack experience shaped closely with clients and stakeholders.
- Held weekly meetings with clients and stakeholders to design and refine the product around the company's real scheduling and operational needs.
- Built custom user interfaces in Angular and TypeScript, along with the data structures behind workflows like drag-and-drop roster editing, administration tools, and dancer self-service time-off requests.
- Built the backend in Java with Spring Boot and PostgreSQL, alongside features such as mobile notifications, automatic roster backup rotations, and collaboration-friendly scheduling flows.
JavaTypeScriptAngularSpring BootPostgreSQLFull-stackOpen sourceStakeholder collaborationMobileMulti-user systemsScheduling softwareWeb
Cornell Design & Tech Initiative
Technical Project Manager
Led the Cue app subteam while also doing full-stack product work across the interface, backend APIs, and deployment setup that kept the project moving.
- Led a team building native iOS and Android applications in Swift, Java, and Kotlin, alongside the backend systems that powered them.
- Worked across backends in Python with Django and Node with Express, with data and service infrastructure using MongoDB, Firebase, Firestore, and GraphQL.
- Helped make technical decisions, coordinate developers, and keep the product moving from early implementation toward something real and usable.
JavaKotlinPythonSwiftDjangoExpressGraphQLFirebaseFirestoreMongoDBProject leadershipTechnical directionAndroidDesktopiOSMobileWeb
Cornell Design & Tech Initiative
Full Stack Developer
Worked as a full-stack developer on a Cornell DTI project team, building user interfaces and backend systems across multiple platforms.
- Built native iOS and Android application features in Swift, Java, and Kotlin, along with supporting web interfaces and other client surfaces used by the team.
- Worked across backends in Python with Django and Node with Express, with MongoDB, Firebase, Firestore, and GraphQL supporting product data and APIs.
- Contributed across both frontend and backend responsibilities, which established the multi-platform full-stack workflow that later carried into team leadership work.
JavaKotlinPythonSwiftDjangoExpressGraphQLFirebaseFirestoreMongoDBFull-stackAndroidDesktopiOSMobileWeb
Lowe’s
Software Engineering Intern
Worked on Lowe's Central Price Master, contributing across frontend, backend microservices, and the surrounding delivery tooling.
- Implemented frontend work in Angular and TypeScript for a large internal pricing system, including a data filtering view for a data aggregator microservice that I owned end to end.
- Built and maintained several Spring Boot microservices in Java supporting merchandising and pricing workflows.
- Worked with the surrounding delivery and infrastructure tooling including Jenkins, Jira, Bitbucket, GCP, Google Container Registry, and Docker, so the internship covered far more than writing feature code.
JavaTypeScriptAngularSpring BootBitbucketDockerGCPGCRJenkinsJiraWeb
Incite Analytics
Full Stack Developer
Worked at a cardiovascular health startup, building product functionality that helped track and detect heart problems in patients across mobile clients and backend systems.
- Built user-facing mobile interfaces in Swift for iOS and Java for Android for the company's client applications.
- Worked on backend systems and Django-based database management supporting cardiovascular health workflows and patient-facing product behavior.
- Worked in a smaller startup environment where communication between product behavior, mobile implementation, and backend data concerns mattered just as much as the code itself.
JavaPythonSwiftDjangoDatabase managementFull-stackAndroidHealth techiOSMobile
Velocitor
Software Engineer Intern
Built cross-platform mobile software in C# and Xamarin for large-client operational applications, while also contributing platform-specific code on both Android and iOS.
- Used C# with Xamarin and binding libraries to support simultaneous cross-platform development.
- Wrote platform-specific code in Java for Android and Objective-C for iOS alongside the shared mobile application layer.
- Worked on applications for inventory management, live driver tracking, and bus scheduling, so the software was tied directly to real operational use cases.
C#JavaObjective-CXamarinAndroidInventory systemsiOSMobileScheduling software
Projects
These projects fill in the rest of the picture.
They’re the ones that say the most about what I like building when nobody is assigning it to me.
JaggerScript
A small typed scripting language with its own parser, interpreter, and browser playground.
This is one of the clearest examples of how I like to work: own the language, the runtime, and the interface around it.
TypeScriptLanguage designBrowser toolingInterpreterPEG parserRuntime systems
Genetic Algorithms in TypeScript
An interactive simulation where a genetic algorithm learns the launch velocity needed to hit a target under changing physics.
Change gravity and wind, rerun the population, and watch the algorithm adapt in real time.
TypeScriptmatter-jsData visualizationGenetic algorithmsInteractive simulationPhysics modeling
TSXLight Renderer
A proof-of-concept TSX rendering engine for web and Electron apps, built around a custom JSX factory, server-managed component trees, and socket-triggered callbacks.
This is the kind of lower-level experiment I enjoy because it forces me to think about rendering, state persistence, per-user sessions, and page transitions from first principles.
TypeScriptElectron + ExpressSSR + socketsCustom JSX factoryRealtime UIRendering architecture
Rengine
A small rendering and game engine experiment with scenes, entities, transform hierarchies, animation loops, and switchable canvas or React output.
What I like about this one is that the interesting work sits below the demo: engine boundaries, update loops, renderer abstraction, and entity composition you can reason about directly.
TypeScriptCanvas renderingEngine architectureEntity systemsGame loopsScene graphs
JetStream
A production-oriented weather app that uses Open-Meteo data, a React/Vite dashboard, a NestJS backend-for-frontend, and an installable PWA shell.
The useful work is in the quality-of-life details: saved preferences, live and deterministic test modes, direct or backend data paths, rich weather instruments, and service-worker caching that make it feel like a real app.
TypeScriptReactNestJSOpen-MeteoPWAService workersViteVitest
Portfolio Site
This site: a React/Vite portfolio built around a 3D section backdrop, project deep links, resume delivery, embedded demos, and daily games.
It is the connective tissue for the rest of the work here, combining frontend polish, routing, responsive project cards, test coverage, and subproject integrations into one deployable portfolio.
TypeScriptReactReact RouterPlaywrightResponsive UIThree.jsViteVitest
new-react-typing-effect
A reusable typing animation component published as a TypeScript React package, with customizable cursor rendering, text rendering, and pacing controls.
It is a smaller project, but it still shows a practical skill I value: designing a clean component API, shipping types with the library, and making customization flexible instead of bolted on.
TypeScript libraryReactNPM PackagingComponent API designAnimation componentsDeveloper experience
IDOL
An internal tools platform for Cornell DTI that bundles org operations, scheduling workflows, member data, and the team website into one TypeScript monorepo.
It is a strong example of the full-stack work I like most: shared types, real product surface area, business logic-heavy APIs, and software a 100+ person organization actually depends on.
TypeScript monorepoExpress + NetlifyFirebaseNext.jsBusiness logic APIsInternal tools
Jordle
A six-letter daily word game with archives, persistent daily state, and a much larger curated word set behind it.
I wanted at least one project on the site that people might come back to every day.
TypeScriptReactLocal persistenceArchive systemsDaily puzzlesGame UIWord games
Jolor
A daily color-guessing game where the name is the clue and you have to dial in the actual color yourself.
It let me build a daily game that is much more visual than Jordle while still needing careful state, feedback, archive handling, and a clean interface.
TypeScriptReactArchive systemsColor systemsDaily puzzlesGame UIVisual feedback
Jinx
A daily minefield puzzle that keeps the rules simple: reveal safe cells, flag mines, and read the numbers carefully.
This one let me build a cleaner version of that classic board logic while keeping the state, archive, and hint systems tight.
TypeScriptReactLocal persistenceBoard stateDaily puzzlesGrid logicHint systems
Judoku
A smaller daily sudoku built around a 6x6 grid, notes mode, and a faster solve than a full-sized board.
I wanted a number puzzle that still feels satisfying, but fits better on a phone and does not ask for a giant time commitment.
TypeScriptReactState managementConstraint puzzlesDaily puzzlesMobile-first UINotes mode
Jigsaw
A daily tile-swap picture puzzle where each board is a scrambled image you have to piece back together.
It added something visual to the games section and gave me a fun excuse to build image slicing, archive handling, and a simple interaction loop around it.
TypeScriptReactInteraction designArchive systemsDaily puzzlesImage puzzlesImage slicing
Domes
A two-player strategy game inspired by Santorini, built around movement, tempo, and board control.
It sits right in the overlap I like most: clear game rules, interaction design, and state that has to stay coherent turn after turn.
TypeScriptReactState machinesBoard strategyGame UIRules enginesTurn-based gameplay
Chains
A monadic pattern for wrapping a value, composing transformations over it, and layering side behaviors like history or undo on top.
It is the kind of abstraction work I enjoy most: simple at the call site, but strong enough to support richer behavior underneath.
TypeScriptAPI designComposable abstractionsFunctional patternsHistory / undoMonads
materialize()
A Firestore utility for turning reference-heavy data into something easier to read and use.
It is a small utility, but it captures a kind of backend work I genuinely enjoy: taking something awkward and making it simple enough to use everywhere.
TypeScriptBackend utilitiesFirestoreData shapingData accessReference materialization
How I work
The stack matters less to me than how the pieces connect.
I care a lot about good boundaries, good defaults, and making software easier to work in over time.
Working with a team
I usually end up doing some mix of implementation, technical direction, and unblocking other people at the same time.
Technical leadershipDeveloper onboardingCross-functional communicationSystem designExecution under ambiguity
Systems and platform work
A lot of the backend work I enjoy sits around reliability, observability, internal platforms, and the infrastructure that makes product teams faster.
Distributed systemsPlatform engineeringCloud computingObservabilityPerformance-minded design
Range
I like being able to move between layers instead of getting stuck in only one of them.
Frontend engineeringBackend APIsMobile developmentProgramming language toolingTypeScript, Java, Python, C#
Contact
If this looks like the kind of background you need, reach out.
I’m especially interested in work where product thinking and technical ownership both matter.