Founding Technical Support Engineer

SigNoz is a global open source project with users in 30+ countries. We are building an open-source application monitoring which helps developers monitor their applications and troubleshoot problems, quickly.

We have crossed 21000+ Github stars, 6000+ members in the slack community and 150+ contributors.

Why us?

• Opportunity to work in a global dev infra product

• Backed by YC and some of the prominent VCs in the Bay Area

• We are completely remote. No offices

• Founding team member opportunity - build support function from scratch

What we are looking for
This is not your typical support role. If you're looking for a classic tier-1 support person who escalates everything to engineering, you should stop reading now. We're looking for someone who is:

• Technical enough to solve real problems - you need to debug OpenTelemetry instrumentation issues, troubleshoot ClickHouse queries, and help customers optimize their observability setup without constantly escalating to engineering.

• Someone who can build support infrastructure from the ground up - you will create our knowledge base, establish processes, and set up tooling for a world-class support experience.

• Passionate about engaging with opensource and developers - you'll be active in GitHub issues, Slack discussions, and technical forums.

Who would be a good fit

• 2+ years experience in technical support or Devops role supporting technical audiences (SREs, Platform Engineers, DevOps teams)

• Strong learning skills - you can quickly pick up new technologies and dive deep into complex technical problems

• Hands-on experience with observability tools - Grafana, Prometheus, Jaeger, DataDog, or similar platforms

• DevOps background - containerization (Docker, Kubernetes), infrastructure as code, and cloud platforms

• Programming ability - can read and debug code in at least one language (Go, Python, JavaScript preferred)

• OpenTelemetry knowledge - understanding of instrumentation, collectors, and distributed tracing concepts

• Customer-focused mindset - you're excited about helping technical users succeed and removing blockers to adoption

• Leadership potential - you want to eventually build and lead a support team as we scale

• Strong written communication - can explain complex technical concepts clearly to engineers

Who may not be a good fit

• Candidates who are fresh out of college

• People who need extensive training on observability concepts

• Candidates who prefer structured, process-heavy support environments

• People who want to avoid technical deep-dives or hands-on troubleshooting

• Those looking for a traditional escalation-heavy support model