SOFTWARE ENGINEER · PRODUCT BUILDER · SYSTEMS ARCHITECT
Thomas Azarian — Full-Stack Software EngineerI build software from the ground up.
From custom frameworks to production SaaS platforms.
I'm a Full-Stack Software Engineer focused on designing and building complete software systems — from architecture and developer tooling to production applications, APIs, automation and data infrastructure.
import { createApplication } from "my-framework";
const app = createApplication({
name: "production-service",
modules: [authModule, dataModule, apiModule],
});
app.start();About
Not just a developer. A builder.
I don't just use frameworks. I build them. My work spans the full depth of a software system — the architecture that holds it together, the tooling that makes it maintainable, and the product that ships to real users.
Read more about how I build software- 01Complete SaaS products
- 02Custom frameworks
- 03Developer tooling
- 04APIs
- 05Automation systems
- 06Data pipelines
- 07AI integrations
- 08Financial technology
- 09Complex dashboards
- 10Web applications
- 11Backend systems
Selected work
Products built end to end.
A sample of systems designed and shipped from architecture to production — not just interfaces on top of someone else's backend.
Custom software
Built my own framework.
Rather than only assembling applications from other people's libraries, I designed and built a software framework of my own — the kind of foundational, opinionated layer that most engineers only ever consume.
import { createApplication } from "my-framework";
const app = createApplication({
name: "example-service",
modules: [authModule, dataModule, apiModule],
config: {
env: process.env.NODE_ENV,
strict: true,
},
});
app.use(loggingMiddleware);
app.use(rateLimiter({ windowMs: 60_000, max: 100 }));
app.start();From zero
Things I've built from scratch.
Not integrations. Not templates. Systems designed, architected and implemented from the first line of code.
Technical map
The stack is only the beginning.
A broad technical toolkit built up across products, not a list of claimed mastery.
Principles
How I think about software.
Build
If the right tool doesn't exist, build it.
Understand
Don't just use abstractions. Understand what's underneath them.
Ship
A technically perfect system that never reaches production has no value.
Iterate
Build → measure → improve → repeat.
In practice
Different problems. Same engineering discipline.
A quick look at the shape of code across the systems I build — frameworks, SaaS logic, APIs, data pipelines and automation.
import { createApplication } from "my-framework";
const app = createApplication({
name: "example-service",
modules: [authModule, dataModule, apiModule],
});
app.use(loggingMiddleware);
app.start();$ npm run build
✓ Architecture validated
✓ TypeScript compiled
✓ Production bundle generated
✓ Build completed
Experience
Software engineering, applied.
Across research, open source and independent development.
June 2026 — Present
Quantitative Research Dev · WorldQuant
Quantitative research and development, applying software engineering to systematic research workflows.
February 2026 — June 2026
Software Developer · Google Summer of Code
Contributed as a software developer on an open-source project as part of Google's global mentorship program.
Open source
Open source, experiments & code.
Live data pulled directly from GitHub — repositories, languages and recent activity. Nothing here is fabricated.