SigNoz

• Design and build complex workflows across dashboards, traces, logs, metrics, alerts, and infrastructure monitoring • Own large frontend features and systems end-to-end • Turn technically complex observability concepts into clear, intuitive experiences • Architect for performance using techniques such as virtualization, progressive loading, smart caching, and selective rendering • Profile and improve slow interactions, large visualizations, and data-heavy views • Contribute to our frontend architecture, design system, and engineering standards • Work closely with design, product, founders, and backend engineers • Speak with users and ship improvements that help engineers investigate incidents faster • Help other engineers make better frontend and product decisions

• You will be working with the high-caliber team in some of the below areas. • Noz, AI teammate: agent orchestration, tool execution, and the APIs that stream results back into the product • SigNoz MCP server that exposes observability data to LLM agents, so any agent can query a user's logs, metrics, and traces • The hard parts of agent backends: long-running execution, security, streaming over SSE, tool calling, and session state across DBs • LLM/GenAI observability, so teams (including us) can monitor their own AI apps with OpenTelemetry

• Work closely with Product Manager and Engineers to design a platform for developers • Translate complex technical topics into clear UX • Engage directly with customers to base work on real workflows • Use AI-assisted workflows and prototyping tools for rapid iterations

• Own the reliability, scalability, and operability of the SigNoz cloud platform • Keep a petabyte-scale observability system fast and dependable • Scale the ingest path — making it robust to bursts while maintaining data freshness • Operate and tune ClickHouse and the data layer for performance and cost • Manage Kubernetes infrastructure: cluster operations, upgrades, multi-tenancy • Help make the observability of SigNoz itself world-class • Work with a high-caliber team across various responsibilities including SLOs/SLIs, incident response, and tooling

• Own the alerting experience end-to-end — rule creation, thresholds, anomaly detection, routing, and notifications — making it powerful for SREs while cutting alert fatigue through smarter grouping and signal-to-noise tuning, so on-call engineers trust what fires and land straight in the relevant data. • Shape the application performance monitoring experience — service maps, latency/error/throughput views, and span analysis — and drive the "something's slow" → "here's the exact bottleneck" workflow that gets engineers to root cause fast. • Own the path from sign-up to first real value — instrumentation, first telemetry, first useful dashboard — reducing time-to-first-insight across language SDKs, collectors, and common frameworks, while respecting power users who want to skip the hand-holding. • Define how alerts, APM, metrics, traces, and logs come together into a single coherent investigation rather than disconnected tabs, closing the loop from signal to root cause. • Sweat the details that matter to power users — query speed, sensible defaults, empty states, keyboard-driven workflows, the 50th query of the day — and make exploring high-cardinality, petabyte-scale data feel obvious rather than overwhelming.

• We are hiring a very small number of exceptional engineers. • This role is for people who ship fast and ship well, and who have already proven they can do that when the stakes and the pace were highest. • Signals that you might be a great fit include owning a system that scaled from a few thousand to millions of users, shipping significant work in surprising windows, having side projects, or being an early or key engineer somewhere that grew fast.

• Build alert features with robustness and scalability in mind • Build integration with JIRA, incident.io, etc • Design and implement APIs, services, and core backend components in Go • Reliability of alerts

Role Description We’re looking for a Staff Backend Engineer – Platform. The platform team at SigNoz handles infra, billing tech, automations, auth, RBAC, caching, scalability of SaaS, staging environments, etc. The team is responsible for handling petabyte-scale data with performance. You will be working with the high-caliber team in some of the below areas: - BillingOps, RevenueOps, Caching, Agent collectors, SaaS operations - Create a marketplace of integrations: patterns, templates, examples, and tooling to help the community plug SigNoz into their stack - Design and implement APIs, services, and core backend components in Go - SaaS auto-scalability - Making the ingest path robust to bursts while maintaining data freshness Qualifications - 7–10 years of experience in Golang - Strong understanding of concurrency, locks, channels, and performance in Go - Experience building distributed systems while writing clean and scalable code - Loves open source – ideally with prior contributions to OSS projects (any size) - Ability to drive initiatives end-to-end: from problem discovery → design → implementation → rollout - Comfortable working in a high-ownership, fast-moving, remote-first environment - Strong communication skills – can write clear tech docs and explain trade-offs Requirements - Past experience in platform teams of series B+ startups (nice-to-have) - Experience in observability (monitoring / logging / tracing) (nice-to-have) - Familiarity with OpenTelemetry and/or ClickHouse, Kafka, Kubernetes, etc. (nice-to-have) - Has been, or wants to be, a founder in B2B/devtools (nice-to-have) Benefits - Work on a globally used open-source project that engineers actually love - Huge scope and ownership – your work directly shapes how teams adopt SigNoz - Collaborate with a high-caliber team who just can't stop shipping - Remote-first, async-friendly culture - Opportunity to help define the future of open-source observability

• Design and implement APIs, services, and core backend components in Go • Making the ingest path robust to bursts while maintaining data freshness • Create a marketplace of integrations: patterns, templates, examples, and tooling to help the community plug SigNoz into their stack • BillingOps, RevenueOps, Caching, Agent collectors, SaaS operations • SaaS auto-scalability

• Define and continuously sharpen how SigNoz is positioned against competitors. Build the messaging hierarchy, from technical ICP (DevOps, SRE, Platform) to economic buyer (VP Eng, CTO) • Write and oversee technical content that actually ships, battle cards, comparison pages, solution briefs, and launch narratives. You write the first draft • Own the GTM motion for every major release - from naming and narrative to launch sequencing across docs, community, social, and sales. Partner closely with product and engineering on roadmap context. • Turn happy customers into a growth engine. Own case studies, reference programs, and customer stories. Identify advocates, build co-marketing opportunities • Run continuous win/loss analysis and customer interviews. Translate what you learn into sharper segmentation, better talk tracks, nurture campaigns and tighter landing page copy. • Equip the sales and CS teams with everything they need to win - battle cards, objection-handling guides, demo narratives, and persona-specific one-pagers. Own the feedback loop between field conversations and marketing output so what you build actually gets used. • Own SigNoz Website as a marketing asset. Drive copy, messaging hierarchy, and page structure in partnership with design and engineering. Run experiments to improve trial signups, docs-to-product conversion, and self-serve activation. Every page should have a job. • Track and improve the full funnel - from awareness and first touch through trial. Partner with growth and product to identify drop-off points, define MQL/PQL criteria, and build campaigns that move the right metrics. • Maintain a live view of the observability landscape. Track pricing changes, feature drops, activation, and expansion. Build and maintain battle cards that sales and CE can actually use in the field.