At SigNoz, we have lot of respect for founders or people who tried doing their own startups and gave a real shot to it.
It takes a certain type of person who can leave their cushy job and work on an idea to change the world
That drive is what changes the world. And we would like such folks to join our team and help us in changing a small part of the world.
We are growing fast and building some core developer infra products.
And we are not fooling around. :
24000+ Github stars
7000+ members in our slack
Top 15 open source project in cloud native space
Observability is a $24bn+ market and we want to make a dent here. We believe the future of observability is open source, and we want to make this vision come to life.
If you are interested in building for developers, have some experience in devops and platform engineering, and love working with customers and help make them successful, we would like to chat
Location
We are completely remote (no offices).
We’re looking for frontend engineers who are excited about:
Building data-intensive products that developers use for hours every day
Making complex, multi-module workflows feel simple and intuitive
Pushing React performance so the UI never gets in the way—especially during a production incident
SigNoz is an open-source observability platform that brings metrics, logs, and traces into one product.
Our frontend is built with React and TypeScript and helps engineering teams explore large volumes of telemetry data, investigate problems, and resolve incidents faster.
Today, SigNoz has:
31,500+ GitHub stars
8,000+ members in our Slack community
900+ customers
Users processing petabytes of telemetry data across the world
This role goes beyond implementing screens from specifications. You’ll own meaningful parts of the product experience from problem definition to production.
You will:
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 may be a good fit if:
You have strong experience building production applications with React and TypeScript
You think in systems and user journeys—not just individual screens
You care about product experience as much as code quality
You have worked on complex, data-heavy, or highly interactive applications
You understand React rendering behaviour and know how to find performance bottlenecks
You are comfortable using browser profiling and debugging tools
You can make thoughtful trade-offs between performance, maintainability, and delivery speed
You take ownership and can move work forward without detailed instructions
You communicate clearly and work well across engineering, design, and product
Experience with observability is helpful, but not required. Curiosity and the ability to understand complex technical domains matter more.
Rendering dashboards containing many charts and large datasets without slowing down the browser
Building fast and intuitive experiences for exploring millions of logs or traces
Visualizing complex distributed traces and service relationships
Creating consistent interactions across multiple product modules
Improving loading, filtering, navigation, and debugging workflows during live incidents
Evolving a large frontend codebase while the product and team continue to grow
We are remote-first and have no offices. Work from wherever you do your best work.
We are a small, experienced team, so individual contributions have visible impact.
Engineers have meaningful ownership over both technical decisions and the product experience.
We move quickly, talk directly with users, and continuously improve what we ship.
Observability is a large and growing market, but more importantly, it is a space full of difficult product and engineering problems.
If you enjoy React and TypeScript, care deeply about UX and performance, and want to build tools that engineers rely on every day, we’d love to hear from you.
","descriptionPlain":"We’re looking for frontend engineers who are excited about:\n\n - Building data-intensive products that developers use for hours every day\n\n - Making complex, multi-module workflows feel simple and intuitive\n\n - Pushing React performance so the UI never gets in the way—especially during a production incident\n\n\n\n\nABOUT SIGNOZ\n\nSigNoz is an open-source observability platform that brings metrics, logs, and traces into one product.\n\nOur frontend is built with React and TypeScript and helps engineering teams explore large volumes of telemetry data, investigate problems, and resolve incidents faster.\n\n\n\nToday, SigNoz has:\n\n - 31,500+ GitHub stars\n\n - 8,000+ members in our Slack community\n\n - 900+ customers\n\n - Users processing petabytes of telemetry data across the world\n\n\n\n\nWHAT YOU’LL DO\n\nThis role goes beyond implementing screens from specifications. You’ll own meaningful parts of the product experience from problem definition to production.\n\n\n\nYou will:\n\n - Design and build complex workflows across dashboards, traces, logs, metrics, alerts, and infrastructure monitoring\n\n - Own large frontend features and systems end-to-end\n\n - Turn technically complex observability concepts into clear, intuitive experiences\n\n - Architect for performance using techniques such as virtualization, progressive loading, smart caching, and selective rendering\n\n - Profile and improve slow interactions, large visualizations, and data-heavy views\n\n - Contribute to our frontend architecture, design system, and engineering standards\n\n - Work closely with design, product, founders, and backend engineers\n\n - Speak with users and ship improvements that help engineers investigate incidents faster\n\n - Help other engineers make better frontend and product decisions\n\n\n\n\n\n\nWHAT WE’RE LOOKING FOR\n\nYou may be a good fit if:\n\n - You have strong experience building production applications with React and TypeScript\n\n - You think in systems and user journeys—not just individual screens\n\n - You care about product experience as much as code quality\n\n - You have worked on complex, data-heavy, or highly interactive applications\n\n - You understand React rendering behaviour and know how to find performance bottlenecks\n\n - You are comfortable using browser profiling and debugging tools\n\n - You can make thoughtful trade-offs between performance, maintainability, and delivery speed\n\n - You take ownership and can move work forward without detailed instructions\n\n - You communicate clearly and work well across engineering, design, and product\n\nExperience with observability is helpful, but not required. Curiosity and the ability to understand complex technical domains matter more.\n\n\n\n\n\n\nPROBLEMS YOU MIGHT WORK ON\n\n - Rendering dashboards containing many charts and large datasets without slowing down the browser\n\n - Building fast and intuitive experiences for exploring millions of logs or traces\n\n - Visualizing complex distributed traces and service relationships\n\n - Creating consistent interactions across multiple product modules\n\n - Improving loading, filtering, navigation, and debugging workflows during live incidents\n\n - Evolving a large frontend codebase while the product and team continue to grow\n\n\n\n\n\n\nHOW WE WORK\n\n - We are remote-first and have no offices. Work from wherever you do your best work.\n\n - We are a small, experienced team, so individual contributions have visible impact.\n\n - Engineers have meaningful ownership over both technical decisions and the product experience.\n\n - We move quickly, talk directly with users, and continuously improve what we ship.\n\n\n\nObservability is a large and growing market, but more importantly, it is a space full of difficult product and engineering problems.\n\n\n\nIf you enjoy React and TypeScript, care deeply about UX and performance, and want to build tools that engineers rely on every day, we’d love to hear from you."},{"id":"f4273207-6f44-40cc-81b0-b1d8b288dc45","title":" AI GTM Engineer","department":"Growth","team":"Growth","employmentType":"FullTime","location":"India","secondaryLocations":[],"publishedAt":"2026-07-20T06:14:10.999+00:00","isListed":true,"isRemote":true,"workplaceType":"Remote","address":{"postalAddress":{"addressCountry":"India"}},"jobUrl":"https://jobs.ashbyhq.com/SigNoz/f4273207-6f44-40cc-81b0-b1d8b288dc45","applyUrl":"https://jobs.ashbyhq.com/SigNoz/f4273207-6f44-40cc-81b0-b1d8b288dc45/application","descriptionHtml":"We’re looking for an AI GTM Engineer to own the systems, data, and processes behind our marketing engine.
This is a hands-on role. You’ll work across Marketing, Sales, Product and Growth to make sure our campaigns run smoothly, our data is reliable, and we’re continuously improving conversion across the funnel.
You should be equally comfortable building a dashboard, fixing an email workflow, creating an account list, and figuring out why a conversion rate dropped.
What you'll build
Signal queues for sales. Define and ship signals such as ICP signups, usage spikes, expansion and win-back triggers, delivered to reps as ranked queues in HubSpot and Slack.
Data Pipelines: Build and maintain data pipelines for ingesting intent signals from various sources
Customer health and alerting. Build usage and billing-spike alerts so CS and Sales act on changes in paying accounts.
A trusted funnel. Build one source of truth for signup to SQL to closed-won in BigQuery, trusted by every GTM lead.
AI-native GTM workflows. Use LLMs and agents for enrichment, research, scoring and personalization, and measure how accurate they are.
CRM automation. Automate lead routing, lifecycle stages and data hygiene end to end, with zero manual lead assignment.
Build a self improving GTM system using LLMs and connectors to data source. Incorporate feedback mechanism so that the system improves over time
You'll also own
GTM tooling across HubSpot, Customer.io, Clay, Lemlist and n8n
Email journeys for prospects, product users and customers, including segmentation and experiments
Account lists, enrichment and measurement for ABM and outbound campaigns
Who would be a good fit
Experience in building data pipelines to get signals from different sources
Strong SQL. You're comfortable in BigQuery or a similar warehouse and build pipelines yourself.
You have 3+ yrs of experience either on engineering or GTM side or mix of two
You can work with APIs, especially CRM APIs like HubSpot's.
You define signals, not just implement them: you have a view on what makes an account worth calling, and you check that view against what actually closes.
You've worked closely with sales or growth teams, or you're eager to sit with reps and learn what they need.
Interest in understanding how GTM works and ideating ways to find new intent signals
You ship scrappily on your own, without needing a data team around you.
You can work async with some overlap with US hours.
Bonus points
Experience at a PLG, developer tools, infrastructure or open-source company
Hands-on experience with HubSpot, Clay, Customer.io or n8n
You've built entity resolution or enrichment pipelines (for example, domain or IP to company)
You've shipped LLM or agent workflows in production and measured their accuracy
You've used product usage data to drive sales or expansion
SigNoz is an open source observability platform built on OpenTelemetry: logs, metrics and traces in one tool. It's designed for an era where agents and humans run observability together. We are a YC company with 32K+ GitHub stars, and revenue grew 4x in 2025.
We have more buying signal than most companies our size. Thousands of teams run SigNoz self-hosted, hundreds of teams sign up for SigNoz Cloud every month, and we have product usage data for all of them. Very little of that signal gets acted on today. Your job is to turn it into pipeline.
You will work directly with the founders. We are looking for a builder: someone who sets up systems that keep working and scale well as we grow, not someone who runs one campaign after another by hand.
Decide which signals mean an account is worth reaching out to: ICP signups, usage spikes, trial activity, large self-hosted installs, teams hiring for observability or platform roles, and companies moving off an incumbent tool.
Turn each signal into a play. Decide who to contact, what to say, which channel (email, LinkedIn), what runs automated and what gets a personal touch, and when an account goes to an AE.
Write and run the sequences yourself at first. Track reply, meeting and pipeline rates for each play, and kill the plays that don't convert.
Work with our GTM Engineer, who builds the data and signal queues. You decide which signals matter and what we do with them. They make the signals reliable and automated.
Own the handoff to sales: what counts as a qualified meeting, response SLAs, and a weekly loop on lead quality.
Own the email journeys at every stage:
New signups, from onboarding through activation
Trials, through conversion to paid
Paying customers, toward expansion and annual plans
Self-hosted open source users, toward SigNoz Cloud or Enterprise
Build campaigns triggered by product usage: first data sent, usage milestones, trial expiry, usage drops and billing changes.
Write the way engineers like to be written to: plain, specific and useful. Run A/B tests, watch deliverability, and report what each journey adds to activation and revenue.
These aren't core skills for this role. If you understand them, that's a bonus, and you'll get to use them:
Run SigNoz on LinkedIn and X in formats native to each platform. Help the founders and DevRel get their best material in front of the right people.
Run paid experiments through an agency or freelancers first: Google on brand and competitor terms, and LinkedIn and Reddit retargeting. Scale only what pays back.
Agree pipeline targets with the founders, then own the number.
Build funnel reporting with the GTM Engineer so everyone knows what converts and what doesn't.
Work with Product Marketing and DevRel on messaging. Join the weekly pipeline review with sales.
This role starts hands-on. For the first few quarters you will run the programs yourself: writing sequences, building journeys and launching campaigns. We are not looking for someone who needs a team before anything happens.
Once your programs reliably produce pipeline, you build the team. The first hires will likely cover lifecycle, outbound/SDR, and social and content.
30 days: You know the product, the users and the data. You've audited our current email journeys and signals, and your first signal-based outbound play is live.
90 days: Three or more outbound plays are running with measured meeting rates. Onboarding and trial journeys have been rebuilt, and nurture for open source users is live. The funnel baseline is agreed and trusted.
12 months: Demand gen is a predictable, measured source of qualified pipeline. Signup-to-SQL conversion is clearly up, and you've made your first hires.
6+ years in demand gen, growth or lifecycle marketing at B2B software companies, selling to technical buyers in the US.
You've run outbound built on data and intent signals, not on bought lists. You can walk us through plays you designed and the meetings and pipeline they produced.
You've owned lifecycle email end to end on a self-serve or PLG product: segmentation, triggers, copy, testing and deliverability.
You write well, and engineers don't tune out when they read it.
You're comfortable with the math: attribution, conversion rates, CAC payback, and pipeline by channel.
You're a builder. You set up systems, automation and processes that keep running without you and scale as volume grows.
You measure yourself by pipeline and revenue, not MQLs.
You've worked hands-on with modern GTM tools (HubSpot, Customer.io, Clay, Lemlist or similar) and have opinions on where AI actually helps.
You can overlap with US mornings (India evenings) a few times a week.
A background in engineering, and you can understand technical terms
You've managed or mentored a small team
You've run paid campaigns on LinkedIn, Google or Reddit, directly or through an agency
You've grown a dev-facing social account
Real product pull. This isn't cold-start demand. Thousands of teams already use SigNoz.
Work directly with the founders, with a budget and a clear path to running the function.
A global dev-infra product, backed by YC and leading Bay Area VCs. Fully remote.
SigNoz is an open source observability platform built on OpenTelemetry: logs, metrics and traces in one tool. It's designed for an era where agents and humans run observability together. We are a YC company with 32K+ GitHub stars, used by engineering teams in many countries.
You own sales for India, APAC and Europe: from the first reply to a signed contract, a smooth migration and the first expansion.
This is not a hand-off role. You run discovery and the demo yourself, answer the technical questions you can. A forward deployed engineer helps on complex proofs of concept, but you run the deal.
Being based in India lets you cover APAC mornings and European afternoons.
Pipeline. Respond to inbound leads (demo requests, high-potential sign-ups, self-hosted users who need an enterprise license) within one business day, and get them on a call. Run outbound to target accounts, reaching several people per account.
Discovery and demo. Find out what triggered the search, the hard constraints (self-hosted or cloud, data residency, volume, budget), who decides and by when. Then pitch within those constraints.
Closing. Size deals from real usage, write the proposal, run a proof of concept with clear success criteria, and get through security reviews, DPAs and procurement.
The first 90 days of the customer. See the customer through onboarding and migration off their old tool
Forecast hygiene. Every call ends with a booked next step. HubSpot is up to date every week, with realistic close dates.
Voice of the customer. Bring patterns from deals back to product and marketing.
30 days: You can demo SigNoz end to end on your own (traces, logs search, dashboards, alerts, cloud vs self-hosted). You know our pricing well enough to size a deal. You've taken over all inbound for your regions.
90 days: You've closed your first deals and run discovery and demos without backup. Your pipeline is real, and the forecast matches what closes.
12 months: You consistently hit your number and have a repeatable playbook for India, APAC and Europe that the next AE can pick up.
4-8 years in customer-facing technical roles at a B2B devtools, cloud, data or observability company. Experience as a sales engineer, solutions architect or consultant, or technical account manager preferred
You've sold to technical roles. You can name deals you closed or were the technical lead on: their size, the competition, and what you did to win.
Ability to understand technical terms and concepts like Kubernetes
You write and speak clearly, in a few words.
Experience at an observability or data infrastructure company
You've been an early sales hire at a startup
A product engineers already choose. Most deals start with a team that is already using SigNoz or open source.
Own a region. You set the playbook for India, APAC and Europe.
Work directly with the founders. Fully remote, backed by YC and leading Bay Area VCs.
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs — all in one place. We’re built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products.
And we are not fooling around:
27,000+ GitHub stars
800+ customers
7,000+ members in our Slack community
We're looking for a Senior Product Manager to own the product for a developer-infrastructure platform used by engineers every single day. This is a hands-on IC role: you'll go deep on the product surface, talk to power users constantly, and ship things that make complex observability workflows feel obvious. Our users are demanding, technical, and detail-driven — so you'll need to be too.
Alerts: 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.
APM: 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.
Onboarding: 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.
Connected investigations: 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.
Observability UX: 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.
5–8+ years in product management, with proven product work shipped at a B2B company
A track record of building product-centric, user-experience-led products — you're not just a backlog manager; you obsess over the actual experience
Deep attention to detail and high standards for power users — you sweat the empty states, the keyboard shortcuts, the defaults, the 50th query of the day, not just the demo path
Ability to drive initiatives end-to-end: problem discovery → definition → design → implementation → rollout → iteration
Strong technical fluency — you can read API docs, reason about data and systems, and earn the respect of senior engineers
Excellent written communication — clear PRDs, crisp tradeoff write-ups, and decisions documented for an async team
Comfortable in a high-ownership, fast-moving, remote-first environment
Past experience in product team of a series B+ startup.
Experience in observability (monitoring / logging / tracing)
Familiarity with OpenTelemetry and/or ClickHouse, Kafka, Kubernetes, etc.
Has been, or wants to be, a founder in B2B/devtools
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 high-caliber team who just can't stop shipping
Remote-first, async-friendly culture
Opportunity to help define the future of open-source observability
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs — all in one place. We’re built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products.
And we are not fooling around:
27,000+ GitHub stars
800+ customers
7,000+ members in our Slack community
We are hiring a very small number of exceptional engineers. We are not trying to fill seats — we are trying to raise the average. If you join, the bar for everyone after you goes up.
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. If that's you, the rest of this will read as an invitation rather than a wishlist.
We're hiring for a specific profile, not a checklist of years. The signals that matter to us:
You operate in the top tier of engineers you've worked with. You're usually the person others go to when something is hard, ambiguous, or on fire. Your past managers and peers would describe you as one of the strongest engineers they've worked alongside.
You combine speed with craft. You ship quickly without leaving a mess behind you. You have strong instincts for what deserves polish and what just needs to work, and you rarely confuse the two.
You've done this during hyper-growth. At a previous company, you were a core engineer while it scaled fast — rapid user growth, scaling systems, scaling teams, or all three. You've felt what breaks at scale and you've fixed it in production, not in theory.
You take real ownership. You don't wait to be assigned problems; you find them, scope them, and close them. When something is broken, you treat it as yours regardless of whose code it is.
You have strong technical taste. Good judgment about abstractions, data models, and tradeoffs — and the humility to change your mind when the evidence does.
You don't need all of these, but several should resonate:
You've owned a system that went from \"works for a few thousand users\" to \"works for millions\" — and you remember exactly where it hurt.
You've shipped something significant in a window that surprised people, and it held up.
You have side projects, open-source contributions, or a track record that shows you build because you can't help it.
You've been an early or key engineer somewhere that grew up fast, and people there would fight to work with you again.
Experience in observability (monitoring / logging / tracing)
Familiarity with OpenTelemetry, ClickHouse, Kubernetes, etc.
Has been, or wants to be, a founder in B2B/devtools
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 high-caliber team who just can't stop shipping
Remote-first, async-friendly culture
Opportunity to help define the future of open-source observability
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs — all in one place. We’re built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products.
And we are not fooling around:
27,000+ GitHub stars
800+ customers
7,000+ members in our Slack community
We’re looking for a Staff Backend Engineer – Alerts who works with the Pulse team. The person will be responsible for building features around our alerting module and ensuring reliability when there are 1000s of alerts running.
You will be working with the high-caliber team to build the future of alerts at SigNoz. Here are the list of features that exist today https://signoz.io/docs/alerts/
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
5–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
Past experience in core teams of series B+ startups.
Experience in observability (monitoring / logging / tracing)
Familiarity with OpenTelemetry, ClickHouse, Kubernetes, etc.
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 high-caliber team who just can't stop shipping
Remote-first, async-friendly culture
Opportunity to help define the future of open-source observability
About SigNoz
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs — all in one place. We're built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products. And we are not fooling around:
27,000+ GitHub stars
800+ customers
7,000+ members in our Slack community
Role: Sr Product Designer
As a Senior Product Designer, you'll work closely with Product Manager and Engineers to create a platform that helps developers and SREs observe and understand their systems. From early discovery to delivering production-ready experiences, you'll play a crucial role in designing complex, data-rich interfaces that are user-friendly without oversimplifying user needs.
What we're looking for
You have experience designing data-rich interfaces
You love the challenge of translating complex technical topics into clear UX
You have exceptional craft and the drive to elevate the look-and-feel of even workhorse UI
You have experience creating component-based design patterns and working with established design systems, though you relish the chance to explore new approaches
Drive end-to-end product thinking across onboarding, instrumentation, troubleshooting, debugging, runtime analysis, and performance investigation workflows.
Use AI-assisted workflows and prototyping tools to rapidly explore ideas, validate concepts, and accelerate iteration throughout the design process.
Engage directly with customers to base work on real workflows
What will make you successful
You have 4-10 years of experience in digital product design.
Your portfolio demonstrates a strong track record of designing and shipping complex technical products and systems-oriented workflows.
You have experience designing for developer platforms, observability tools, infrastructure products, or other highly technical domains.
You are comfortable operating in ambiguous environments and influencing product direction through strong systems thinking and product judgment.
You are deeply thoughtful about edge cases, scalability, information architecture, and designing for technical depth without sacrificing usability.
Why you'll love working at SigNoz
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
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs, all in one place. We're built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products. And we are not fooling around:
31,000+ GitHub stars
900+ customers
8,000+ members in our Slack community
We're looking for a Sr Backend Engineer for Nerve, our AI pod. Nerve builds the AI layer of SigNoz: Noz (our AI teammate), the MCP server, AI Agents, and LLM observability. We're building toward agent-native observability, where the engineer and their agent are both first-class users.
Noz, our AI teammate: agent orchestration, tool calling, streaming over SSE, and session state, the hard parts of agent backends
SigNoz MCP server: the surface through which any LLM agent works with SigNoz, querying logs, metrics, and traces, and creating alerts, dashboards
LLM/GenAI observability: monitoring AI apps with OpenTelemetry, ours included
5-8 years building backend systems in production at product companies with strong engineering culture. You'll work across both Go and Python.
Strong with Go (concurrency, channels, performance) and with async Python (FastAPI, Pydantic, asyncio), and comfortable designing APIs and data models.
Curious about building with LLMs and agents. You don't need AI experience, strong backend engineers pick this up fast, and we'll ramp you up. What matters is the drive to make a non-deterministic system behave like a dependable one.
High ownership in a fast-moving, remote-first team: you drive initiatives from problem discovery → design → implementation → rollout, write clear docs, and explain trade-offs.
Shipped LLM features in production: agents, tool or function calling, evals, MCP, context and prompt engineering
Familiarity with OpenTelemetry and/or ClickHouse, Kafka, Kubernetes, etc.
Loves open source, ideally with prior contributions to OSS projects (any size)
You'll help define agent-native observability, a new category, not maintain a mature dashboard product.
If you've been wanting to move into AI engineering, this is a real path in: you bring the backend depth, we bring the AI problems.
Ship in the open, with a high-caliber team who just can't stop shipping.
Remote-first, async-friendly culture
SigNoz is an open-source observability platform that helps modern engineering teams monitor, debug, and optimize their applications with deep visibility into metrics, traces, and logs — all in one place. We're built natively on OpenTelemetry and offer both self-hosted and cloud options, so teams can run observability the way they want, without vendor lock-in.
We are growing fast and building core developer infra products.
And we are not fooling around:
32,000+ GitHub stars
1000+ customers
8,000+ members in our Slack community
We're looking for a Head of Finance to build and own the finance function end-to-end.
Today we're at meaningful revenue scale with a finance setup that got us here but won't get us to the next stage. Our books are accurate but slow. We can tell you our blended gross margin — we can't yet tell you which customer cohorts, plans, and workloads are actually profitable. That matters more for us than for most SaaS companies: we run petabyte-scale infrastructure, so compute and storage cost per customer is our margin story.
You'll report to the CEO, own everything from monthly close to the due-diligence data room, and partner closely with engineering on the cost side of the business.
This is a build role. Real revenue, incomplete infrastructure, and you'll be constructing systems while the numbers keep moving.
Controllership: monthly close in under 15 days, revenue recognition for usage-based and contracted plans, statutory audit, AR and collections
Multi-entity finance across our US and India entities — intercompany, transfer pricing, consolidation
Compliance: GST, TDS, ROC/MCA, FEMA and RBI filings, ESOP administration and perquisite tax
Gross margin engineering: partnering with the platform team on infra spend, cloud commitments, and cost per ingested GB
FP&A: annual operating plan, rolling forecast built from operating drivers, MIS that functional leaders act on
Cash and treasury: 13-week cash flow, runway, USD/INR exposure, banking and surplus deployment
Getting us off spreadsheets — ERP, billing ops, expense management, procurement approvals, internal controls
Building a small, high-leverage finance team as the load grows
CA with 8–12 years post-qualification
You have personally owned a monthly close and a statutory audit — owned, not supervised
You've built a financial model from operating drivers, been wrong in public about it, and can talk about what you learned
Working fluency in Indian startup compliance: GST, TDS, ROC, FEMA, ESOP taxation
Comfortable with messy, incomplete data and willing to ship a defensible answer before the data is perfect
Strong communication — can explain a margin problem to an engineer and a burn scenario to a board member in the same week
You'll argue with the CEO using data, and keep the relationship intact
Big 4 audit or TAS early, followed by real operating years in a funded startup
Currently #2 in finance at a Series B/C company and ready to run the function
Multi-entity experience, especially US–India structures
SaaS or usage-based billing revenue recognition
You've been through a fundraise from the inside, whatever your role in it
Roughly 40% of year one is unglamorous: GST reconciliations, audit queries, chasing collections. If you only want strategic finance, you'll be restless here for a while.
You'll find things that are wrong. We'd rather you find them than an auditor or an investor.
Build a finance function from scratch at a company with real revenue and real momentum
Huge scope and ownership — you'll own the number, the narrative, and the systems behind both
Work on a globally used open-source project that engineers actually love
Remote-first, async-friendly culture
A finance problem that's genuinely interesting: open-source distribution, usage-based economics, and infrastructure at petabyte scale
SigNoz is an open source observability platform built on OpenTelemetry: logs, metrics and traces in one tool. It's designed for an era where agents and humans run observability together. We are a YC company with 32K+ GitHub stars
Some of the most interesting AI and infrastructure teams in the Bay Area run on SigNoz, including Kernel and Sail Research. Their engineers have great stories about how they debug and scale production systems. Very few of those stories get told today
Your job is to fix that. You'll be the face of SigNoz in the Bay Area: on stage at meetups, on camera with customers, and in the room at events.
What you will own
Find Bay Area customers with a story worth telling: how they moved off an incumbent tool, scaled to billions of events, or debug AI agents in production.
Visit them, interview their engineers and film technical videos and case studies on site. You run the conversation and the technical depth.
Turn those relationships into references, quotes and talks that help sales close deals.
Speak regularly at Bay Area meetups: OpenTelemetry, cloud native and Kubernetes, AI engineering, SRE and platform engineering.
Host small, high-quality events: engineering dinners, roundtables and SigNoz meetups for the teams we want to work with.
Represent SigNoz at conferences like KubeCon and SRECON, AI meetups through talks, booths or side events.
Host and present webinars with customers and our engineers: deep dives, migrations and live debugging sessions. Our India team runs the logistics and promotion. You make the content worth showing up for.
Write or record technical content when the story needs a first-hand voice.
Join our Account Executive and Forward Deployed Engineer on customer visits when a technical talk or workshop will help.
Bring what you hear from customers and the community back to product and marketing.
This role starts hands-on: you plan your own calendar, run the events and give the talks yourself. Once the motion reliably produces stories, community and pipeline, you can build a small US DevRel and field team around it.
30 days: You've run SigNoz yourself on a real app and know the product, the customers and the team. You've mapped the Bay Area meetups worth being part of. Your first customer story is in production.
90 days: You've published three customer stories, spoken at four or more meetups, hosted the first SigNoz dinner or meetup, and run at least two webinars.
12 months: You publish customer stories and host events every month. Bay Area infra and AI engineers know SigNoz through you. Sales can point to deals that started at your events or were won with your stories.
3+ years as a software engineer, SRE, platform engineer, solutions engineer or developer advocate. You don't need a DevRel title. Many of the best people for this role are engineers who became the person their team sends to give the talk, write the post or meet the customer.
Bachelor's degree in Computer Science, Engineering or a related technical field.
You like explaining technical things to people, and you have some public proof: a talk, a blog post, a popular open source project, a meetup you organized, or customer-facing work. You're comfortable on camera
You understand production systems: Observability, OpenTelemetry, Kubernetes, cloud infrastructure or AI infrastructure. You can run a demo, answer hard questions and write code when needed. You don't need to be expert in this, but should be able to understand.
You're self-directed. You build your own plan and calendar, follow up with people without being reminded, and measure the results.
You enjoy meeting people. You come back from an event with names, follow-ups and a story idea.
You're based in the San Francisco Bay Area, or will move here, and can travel about 20% of the time.
You've given conference or meetup talks.
You've organized or grown a meetup or developer community.
You've done developer relations at a developer-tools or infrastructure startup.
You've contributed to open source
You're already part of the Bay Area AI engineering scene.
Real product pull. Thousands of teams use SigNoz, including some of the most interesting AI companies in the Bay Area.
Work directly with the CEO, who is also based in the Bay Area.
Build the US community function from the start, with budget and a clear path to leading it.
SigNoz is an open source observability platform built on OpenTelemetry: logs, metrics and traces in one tool. It's designed for an era where agents and humans run observability together. We are a YC company with 32K+ GitHub stars, and revenue grew 4x in 2025.
Most of our revenue is usage-based. That makes customer success especially important: retaining accounts and helping our larger accounts expand drive a big share of our growth.
This is our first dedicated customer success role. We're looking for a builder who can design the systems from scratch and set them up to scale as the team grows. You'll work directly with the founders.
Tier our paying accounts and decide what each tier gets: a named owner, a shared Slack channel, regular business reviews, or pooled coverage.
Build health scores from data we already have in our warehouse: ingestion volume, product usage, billing, support tickets and engagement.
Set up a review cadence for the top tier, and make sure each top account has several contacts on their side, not one champion.
Catch risk early. Usage drops, a champion leaving, a surprise bill and alerts going quiet are all signals. On a usage-based product, a billing spike can be as much of a churn risk as a usage drop.
Turn each signal into a play: who reaches out, what we offer (often help reducing their cost), and when it escalates.
Run a post-mortem on every meaningful churn or downgrade, and feed the lessons back into product, pricing and onboarding.
Run win-back campaigns for accounts we lost.
Move monthly usage-based customers onto annual commitments, and own those conversations, including the commercial terms.
Spot expansion opportunities: new teams, new signals (logs, traces, metrics), new environments. Work with sales on the bigger ones.
Own renewals for customers on annual plans.
Bring what customers need back to product and engineering, ranked by revenue impact.
Work with our technical support team on escalations so the most important accounts never wait.
Agree retention targets with the founders, then own the gross and net revenue retention numbers.
Run a weekly account review: at-risk accounts, saves, annual conversions in progress, expansion.
This role starts hands-on. You will personally own our top accounts and build the playbooks by running them yourself. We are not looking for someone who needs a team before anything happens.
Build the systems so they keep working as the number of accounts grows: clear tiers, health scores the team trusts, and playbooks a new CSM can pick up and run. Once they're working, you build and lead the customer success team.
30 days: You know the product and the data, and have met our top accounts. Account tiers and a first version of the health score are drafted.
90 days: The health score is live and the team trusts it. Business reviews are running for the top tier. Save plays exist for usage drops and billing spikes, and every meaningful churn gets a post-mortem. The first monthly-to-annual conversions have closed.
12 months: Gross and net revenue retention are measurably up, and a much larger share of revenue is on annual commitments. The systems you built are ready for the team to scale on.
6-10 years in B2B SaaS customer success, with at least part of that at a technical product sold to engineers.
You've owned a revenue retention number (GRR, NRR or renewals), not just CSAT or ticket metrics. You can walk us through accounts you saved and grew, and what you did.
You've worked with usage-based or consumption pricing, and you know how to talk to a customer whose bill just jumped.
You're a builder. You've set up CS systems from scratch (health scores, business reviews, playbooks) and made them work as the book of accounts grew. You didn't just inherit them.
You're technical enough to talk to SREs and platform engineers, read a usage dashboard, and write basic SQL, or you'll learn it fast.
You're commercial. You can negotiate an annual commitment and you're comfortable talking about money.
You've managed US-based customers directly: running their reviews, handling escalations and negotiating renewals. You can overlap with US mornings (India evenings) a few times a week.
You've led or mentored other CSMs. Formal management is a plus, not a requirement.
A background in engineering and can understand technical terms
You've set up a CS platform or built health scoring on raw data
You've moved customers from monthly to annual plans at scale
Customers who already love the product. Our customers chose us themselves. Your job is to keep that going as they grow, not to rescue bad deals.
Build the function from day one. You're the first dedicated CS hire, so you design how customer success works here and set it up to scale.
Work directly with the founders. You'll have the founders' backing, the data to work with, and a clear path to running the function.
A global dev-infra product, backed by YC and leading Bay Area VCs. Fully remote.