Cover Letter of JS

My journey began with a love for mathematics — the elegance, the logic, the puzzles. I discovered Machine Learning and saw it as the most beautiful application of math — a vivid intersection of probability, linear algebra, calculus, and code.

Despite my passion, getting into data science wasn't easy. The competition was stiff, and the entry barriers high. So I pivoted to web development — a more accessible path that would end up reshaping my career.

That pivot launched me into the world of JavaScript. Over the past four years, I’ve worked extensively with React, Next.js, React Native, Node, and Express. I’ve built everything from frontends to APIs to real-time systems. It turned me into a builder.

But my love for systems and math never faded. As I ventured into DevOps — managing deployments, backups, observability, and monitoring — I began to see the internet for what it truly is: a collection of elegant, orchestrated Linux processes.

This deeper exploration rekindled my original fascination. Networking felt like math again — packets, routing, sockets, layers. Subtle yet immensely powerful. The internet, beneath the surface, is a masterpiece of engineering.

Though I moved away from formal ML roles, the mathematical thinking I honed there persists. It now feeds into how I model systems, understand observability metrics, debug infrastructure problems and critical life decisions.

From frontend to backend to infra, I’ve gained a 360-degree view of how things work. I’ve handled production issues, optimized systems, configured load balancers, and studied open-source infrastructure to understand the ‘why’ behind the tools.

While this isn't about a single employer, my roles across different teams — especially in DevOps and backend — have shaped my thinking. Understanding infrastructure isn’t just about uptime. It’s about performance, security, resilience, and clarity.

Everything clicked when I realized — it’s all just a system. The frontend, the backend, the protocols, the infrastructure — each a part of one grand machine. My engineering mindset evolved from writing code to understanding how everything interrelates.

Now I’m obsessed with the infrastructure layer: self-hosted systems, containers, failovers, cloud-native architecture, and observability. But I still build apps and write code — I just see the full picture now.

What excites me most is not choosing a niche, but seeing how it all connects. I find joy in solving real problems — whether through code, architecture, or understanding how a system behaves under stress.

I want to work in roles that embrace this holistic view — where I can connect the dots between frontend polish, backend logic, and infrastructure resilience. My goal is simple: build meaningful things while staying deeply curious.

So to sum it up, why you should hire me:

• I see web development, DevOps, and networking as one interconnected system.
• I build across the stack — from frontend UIs to real-time backend APIs.
• I treat infrastructure not as ops work, but as elegant system engineering.
• I enjoy working with protocols, routing, and observability tools like I once enjoyed solving math puzzles.
• I thrive when connecting seemingly unrelated disciplines to build robust, resilient systems.
• I believe the most powerful engineers understand not just code, but the machines and networks beneath it.
• I continuously seek to learn and build in a way that honors both the logic of math and the creativity of engineering.