Forward Deployed Engineer (Remote) (India time zones)

About the role SigNoz is a global open source project with users in 30+ countries. We are building an open-source observability platform which helps developers monitor their applications and troubleshoot problems, quickly. In less than a year of our launch, we have reached 22000+ 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 Work directly with engineering teams at high-growth companies We're looking for someone who is: Technical enough to architect observability solutions you'll work directly with engineering teams to design their OpenTelemetry instrumentation strategy, customize dashboards, and optimize for their specific use cases. Excellent at technical documentation you'll create custom integration guides, troubleshooting docs, and best practices documentation that engineering teams actually want to follow. Capable of hands-on implementation you'll directly contribute to customer codebases, help debug instrumentation issues, and ensure successful deployments rather than just providing guidance. Product-minded you'll identify patterns in customer deployments and work with our product teams to build better defaults, templates, and tooling. Who would be a good fit 2-6 years experience in technical roles DevOps, SRE, Platform Engineering, or Solutions Engineering backgrounds DevOps/Platform engineering background Containerization, Kubernetes, infrastructure as code, cloud platforms (AWS/GCP/Azure) Strong programming skills comfortable contributing to customer codebases in multiple languages (Go, Python, Node.js, Java) Excellent technical writing can create clear, actionable documentation that engineers actually use Systems thinking can understand complex distributed architectures and design monitoring strategies that scale Strong learning skills can quickly understand new customer environments and adapt solutions accordingly Who may not be a good fit People who prefer working in isolation rather than directly with customers People who struggle with technical writing or documentation Candidates who avoid hands-on coding or technical implementation Those who prefer following established processes rather than creating new solutions