diff --git a/bridges/otelzap/example_test.go b/bridges/otelzap/example_test.go
new file mode 100644
index 00000000000..d1076da5cff
--- /dev/null
+++ b/bridges/otelzap/example_test.go
@@ -0,0 +1,37 @@
+// Copyright The OpenTelemetry Authors
+// SPDX-License-Identifier: Apache-2.0
+
+package otelzap_test
+
+import (
+	"os"
+
+	"go.opentelemetry.io/contrib/bridges/otelzap"
+	"go.opentelemetry.io/otel/log/noop"
+
+	"go.uber.org/zap"
+	"go.uber.org/zap/zapcore"
+)
+
+func Example() {
+	// Use a working LoggerProvider implementation instead e.g. using go.opentelemetry.io/otel/sdk/log.
+	provider := noop.NewLoggerProvider()
+
+	// Initialize a zap logger with the otelzap bridge core.
+	// This method actually doesn't log anything on your STDOUT, as everything
+	// is shipped to a configured otel endpoint.
+	// nolint: ineffassign
+	logger := zap.New(otelzap.NewCore("my/pkg/name", otelzap.WithLoggerProvider(provider)))
+
+	// Alternatively, if you want to log also on stdout, you can initialize a new zap.Core
+	// that has multiple outputs using the method zap.NewTee(). With the following code,
+	// logs will be written to stdout and also exported to the OTEL endpoint through the bridge.
+	core := zapcore.NewTee(
+		zapcore.NewCore(zapcore.NewJSONEncoder(zap.NewProductionEncoderConfig()), zapcore.AddSync(os.Stdout), zapcore.InfoLevel),
+		otelzap.NewCore("my/pkg/name", otelzap.WithLoggerProvider(provider)),
+	)
+	logger = zap.New(core)
+
+	// You can now use your logger in your code.
+	logger.Info("something really cool")
+}