Developer Observability · India
Some of you may wonder, what does SigNoz mean? As engineers we are obsessed with the idea of signal vs noise. How do devops engineers find signals which they can act on from the various sources of noise they encounter from their observability systems? This is one idea we obsess over and seems important enough to continually strive towards. And, hence the name Sig.Noz ( Signal vs Noise) 🤓 After spending a lot of time in college reading philosophy, I got interested in technology. Biometric & image recognition was especially interesting to me. Led product teams in startups & MNCs like Microsoft, before stumbling into the domain of observability. Reducing noise in developers' and devops engineers' life is my current passion :) Playing Badminton professionally was my dream at one time. But that seemed too tough, so I started coding. I have delved in all sorts of technologies including crypto when it was exciting. Always interested in solving interesting problems with technology. Microservices & Distributed systems is what I am most interested in these days. Move from symptoms to evidence across APM, logs, traces, infra, LLM telemetry, alerts, and dashboards. Use the SigNoz MCP server to bring telemetry into coding agents, or use Noz, your AI teammate inside SigNoz Cloud, to investigate incidents, tune alerts, and build dashboards with the same production context your team sees. I can help you understand and be the all-seeing eye over your entire infrastructure. What do you need? Move from a latency spike to the related logs, traces, metrics, and spans without stitching together separate tools. Use open standards instead of vendor SDKs, so instrumentation stays portable as your stack changes. Use query builder, PromQL, and ClickHouse SQL on a fast columnar datastore built for high-cardinality observability data. One OpenTelemetry-native source gives agents a known schema for traces, logs, metrics, and services, so they can debug with less translation. For fast-scaling teams that need observability to scale with them. For larger orgs that need data residency, compliance, and support. Visualization: noisy telemetry signals converging into a single clear signal with detected events. Add teammates freely, monitor autoscaling infrastructure, and estimate telemetry costs before you commit. Autoscale infrastructure without turning every node, container, or host into a billing surprise. Bring engineering, support, and on-call teams into SigNoz Cloud without seat limits or seat math. Send any mix of logs, traces, and metrics. Pay for telemetry volume, not custom metri
Some of you may wonder, what does SigNoz mean? As engineers we are obsessed with the idea of signal vs noise. How do devops engineers find signals which they can act on from the various sources of noise they encounter from their observability systems? This is one idea we obsess over and seems important enough to continually strive towards. And, hence the name Sig.Noz ( Signal vs Noise) 🤓 After spending a lot of time in college reading philosophy, I got interested in technology. Biometric & image recognition was especially interesting to me. Led product teams in startups & MNCs like Microsoft, before stumbling into the domain of observability. Reducing noise in developers' and devops engineers' life is my current passion :) Playing Badminton professionally was my dream at one time. But that seemed too tough, so I started coding. I have delved in all sorts of technologies including crypto when it was exciting. Always interested in solving interesting problems with technology. Microservices & Distributed systems is what I am most interested in these days. Move from symptoms to evidence across APM, logs, traces, infra, LLM telemetry, alerts, and dashboards. Use the SigNoz MCP server to bring telemetry into coding agents, or use Noz, your AI teammate inside SigNoz Cloud, to investigate incidents, tune alerts, and build dashboards with the same production context your team sees. I can help you understand and be the all-seeing eye over your entire infrastructure. What do you need? Move from a latency spike to the related logs, traces, metrics, and spans without stitching together separate tools. Use open standards instead of vendor SDKs, so instrumentation stays portable as your stack changes. Use query builder, PromQL, and ClickHouse SQL on a fast columnar datastore built for high-cardinality observability data. One OpenTelemetry-native source gives agents a known schema for traces, logs, metrics, and services, so they can debug with less translation. For fast-scaling teams that need observability to scale with them. For larger orgs that need data residency, compliance, and support. Visualization: noisy telemetry signals converging into a single clear signal with detected events. Add teammates freely, monitor autoscaling infrastructure, and estimate telemetry costs before you commit. Autoscale infrastructure without turning every node, container, or host into a billing surprise. Bring engineering, support, and on-call teams into SigNoz Cloud without seat limits or seat math. Send any mix of logs, traces, and metrics. Pay for telemetry volume, not custom metri
Aptitude (logical, verbal, quantitative) and basic domain knowledge
Role-specific knowledge, academic background, past projects or experience
Introduction, motivation, career goals, teamwork, strengths and weaknesses