Gautam Mishra

Advanced Software Developer

At Fidelity, I worked on backend systems responsible for generating and serving firm-wide authorization data. This involved building batch pipelines, owning shared authorization libraries used by multiple teams, and supporting APIs that had strict correctness and availability requirements.

I also worked closely with downstream consumers to define data and API contracts, coordinate rollouts, and resolve integration issues as systems evolved. Along the way, I built internal tooling to reduce operational overhead and improve day-to-day workflows for the team.

Senior Backend Developer

At IBM’s Weather Company, I worked on backend systems responsible for ingesting and distributing large-scale weather and lightning datasets. The systems processed multi-terabyte data volumes daily and served millions of data products to enterprise clients with strict latency requirements.

My work focused on data ingestion, system reliability, and operational readiness, including multi-region redundancy, CI/CD improvements, and backend service migrations. I spent a lot of time thinking about trade-offs between performance, cost, and long-term maintainabilit.

Senior Software Engineer

At Klaviyo, I worked on data platforms that powered customer engagement workflows at scale. This included contributing to the early architecture of the company’s data lake, building high-throughput stream processing systems, and supporting analytical use cases that depended on accurate, timely event data.

I also worked on internal tooling and data models that helped teams reason about data correctness and system behavior as scale increased.

Software Engineer

During my earlier time at IBM, I worked on backend systems supporting large-scale weather and lightning data products used by enterprise customers. This role was formative in shaping how I think about building production systems that need to be reliable, observable, and correct under load.

I was involved in designing and operating data ingestion pipelines, improving service performance, and addressing operational issues as they arose in production. Over time, I gained hands-on experience with distributed systems, backend service development, and the realities of running data-heavy workloads at scale.

This period helped me develop a strong appreciation for disciplined engineering practices, thoughtful system design, and the importance of understanding how software behaves beyond local development environments.

Java Developer

I began my career as a Java developer working on backend systems for consumer-facing applications. In this role, I was exposed to the fundamentals of building secure, scalable services, including payment workflows, messaging systems, and early platform features that directly impacted end users.

I worked on implementing security protocols, improving message delivery reliability, and building backend components that supported high-volume user interactions. I also started identifying gaps in existing systems and introducing improvements where possible, which helped me develop an early sense of ownership and responsibility for the quality of the systems I worked on.

This role laid the foundation for my later focus on backend architecture and data-driven systems, and it shaped how I approach engineering problems with an emphasis on correctness, reliability, and real-world impact.