Looking for Node JS Developer

@shrec

I’m an experienced Node.js developer with hands-on expertise using open-source OpenTelemetry to collect and export metrics, traces, and logs in cloud-native environments. I can build a complete POC using Node.js with OpenTelemetry, Dockerized services, AWS Lambda and Fargate, and route signals to Observe with proper exporters and pipelines. The focus will be a clean, production-realistic setup that clearly demonstrates signal collection, transformation, and export flow. I work independently, document clearly, and can deliver a working, testable POC end to end.

@neerajdhameliya

Hello, ◆◆◆◆◆ Portfolio & Past Work: ◆◆◆◆◆ https://www.freelancer.com/u/neerajdhameliya As an experienced Node.js developer, I specialize in creating clear, working OpenTelemetry POCs that demonstrate real-world signal flow and AWS integration. Here’s my approach: ◆ OpenTelemetry & Node.js Instrumentation: Implement end-to-end OpenTelemetry setup for metrics, traces, and logs in Node.js, including custom exporters and collectors aligned with Observe ingestion requirements. ◆ AWS & Containerized POC Delivery: Build a Dockerized POC using AWS Lambda and Fargate to process and forward telemetry signals, with clear architecture, validation, and handover documentation. Please feel free to message me to discuss your POC scope, signal flow design, and delivery timeline. Best regards, Niral D

@Microlent

This is a proper OpenTelemetry POC and I’m comfortable owning it end to end. I’ve worked hands-on with Node.js + OpenTelemetry, instrumenting metrics, traces, and logs and exporting them through custom pipelines. I understand the differences and constraints when running telemetry in AWS Lambda vs Fargate, including cold starts, batching, exporters, and async flushing. For this POC, I’d set up clean Node.js instrumentation, route logs through AWS Lambda, export all signals into Observe Inc, and package everything with Docker so the setup is repeatable and easy to validate. The focus would be correctness and visibility, not just “something that runs.” If needed, I can also document the signal flow clearly so your team understands how metrics, traces, and logs move through the system. Let’s open the chat and confirm the exact Observe exporter configuration and AWS architecture you prefer. I’m happy to walk you through a similar OpenTelemetry pipeline I’ve built and outline how I’d structure this POC. If you want this done by someone who’s actually shipped OpenTelemetry in Node, not experimented with it, we’ll be a strong fit. Let’s open the chat and get started. Best, Jenifer

@PentabayC

Hi there I read your requirement carefully and this POC is very clear to me – collecting OpenTelemetry metrics, traces, and logs in Node.js, sending logs to AWS Lambda, and exporting signals to Observe, with Docker and Fargate involved. I have hands-on experience working as a sole Node.js developer with OpenTelemetry, AWS Lambda/Fargate, containerized services, and setting up end-to-end signal pipelines for observability platforms. I can build a clean POC showing metrics, traces, and logs flowing correctly from Node.js → Lambda → Observe, with proper Docker setup and documentation. I’ve worked on similar enterprise observability setups and know how to handle exporters, pipelines, and AWS deployment without overcomplicating things. Regards Vijay

@hitech10

Hello, I have reviewed your requirement and can support the development of a POC using OpenTelemetry with Node.js to collect and export metrics, traces, and logs through AWS infrastructure to Observe. This will be a production-aligned proof of concept demonstrating end-to-end observability. Development to Deployment Road-Map (FMCG Domain Solutions): Requirement analysis & POC scope definition → system architecture design → ER-style signal flow mapping (services, traces, logs, metrics) → Node.js app instrumentation with OpenTelemetry → Docker containerization → deployment on AWS Fargate → log forwarding to AWS Lambda → signal transformation & export to Observe → validation of metrics, traces, and logs → performance testing → documentation & handover. POC Coverage: OpenTelemetry setup for Node.js Metrics, traces, and logs collection AWS Lambda & Fargate integration Observe signal export & validation Dockerized deployment pipeline I am very interested for long term collaboration. Best regards, Prakash.S

@mahig47

Hello! As per your project post, you are looking to build a Node.js proof-of-concept that collects telemetry signals metrics, traces, and logs and forwards them through AWS Lambda to Observe, with Docker containerization involved. The purpose of this project is to validate end-to-end observability using OpenTelemetry in a scalable cloud-native setup. My focus will be on setting up a Node.js POC that instrumentally collects signals using OpenTelemetry, forwards logs and traces through AWS Lambda and optionally Fargate, and ensures proper export to Observe. I will containerize the application for easy deployment and testing, and demonstrate the flow of metrics, traces, and logs through the system in a reproducible way. I specialize in Node.js development with experience in OpenTelemetry instrumentation, AWS Lambda/Fargate deployment, and containerized microservices. My approach emphasizes modular code, reliable signal capture, and clean integration with observability platforms like Observe, so the POC is robust and clearly demonstrates the telemetry pipeline. Let’s connect to finalize the architecture, define the telemetry scope, and map out a clear plan for delivering a working Node.js OpenTelemetry POC. Best regards, Nikita Gupta.

@malkesh3m

⭐ Hello there, My availability is immediate. I read your project post on React/Node Developer. I have extensive knowledge in MERN Stack (MongoDB/MySQL, Express JS, React, and NodeJS), as well as RESTful API integration. I am an experience full-stack developers with skill sets in - React, JavaScript, jQuery, TypeScript, NextJS, React Native - NodeJS, ExpressJS - MongoDB, MySQL, PostgreSQL, SQLServer, SQLite - Redux, Thunk, GIT - JavaScript, HTML, CSS, Tailwind CSS - AWS, Azure, Digital Ocean, GoDaddy, Web Server Hosting Please send a message So we can quickly discuss your project and proceed further. I am looking forward to hearing from you. Thanks

@Julian29

Hello, I have over 10 years of experience in backend and Node.js projects, and I am confident I can handle this POC from start to finish. I am ready to dedicate 40 hours per week full-time to ensure the project is completed efficiently and to the highest standard. *** Node.js & OpenTelemetry: Collect metrics, traces, and logs for full observability. *** AWS Lambda & Fargate: Route logs and signals seamlessly for processing and export. *** Docker & Containerization: Build scalable, portable environments for reliable deployment. With my experience, I can manage the full workflow—from signal collection to containerized deployment—ensuring everything runs smoothly and is production-ready. I am focused, reliable, and fully available for full-time work. Julian

@jackson325

Hello, I understand you're seeking a skilled Node.js developer to create a proof of concept (POC) project that integrates OpenTelemetry for collecting metrics, traces, and logs, forwarding them to AWS Lambda, and exporting to Observe. I have substantial experience in this area, having successfully developed similar projects that leveraged OpenTelemetry and AWS services. My background includes deploying solutions in Docker containers, ensuring smooth operational workflows. ✅My Plan: - Analyze the requirements to confirm all needed features. - Set up a Node.js environment integrated with OpenTelemetry. - Implement log collection and forwarding to AWS Lambda. - Deploy on AWS Fargate for scalable architectures. - Use Docker for containerization of the application. Could you provide details on your timeline for this POC? Additionally, what specific metrics or traces are most critical for your assessment? Best regards, Hongqiang Chen

@amazeez1100

Hello, ss an experienced and dedicated full-stack developer, my main focus has been on Node.js for the past 6 years. I believe that my experience in designing and developing complex projects from scratch can be invaluable to creating your POC with opensource opentelemetry. I'm excited about this opportunity and eager to ensure your project is nothing short of stellar!

@nikhilgarg96

As a seasoned full-stack developer, I'm confident that I have the skills and experience you need for this project. Notably, my deep understanding of Node.js and AWS Lambda, along with my proficiency in RESTful APIs, aligns perfectly with your requirements. I've also had the chance to use opentelemetry in previous projects. Most recently, I worked with Docker containers for efficient deployments and possess the knowledge to leverage it in your project effectively. During my career, I've been involved in creating POCs from scratch that offered efficient collection of vital signals such as metrics and logs, by deploying them to AWS Lambda before exporting them to observe. My diverse range of projects has enhanced my problem-solving skills greatly, equipping me to tackle potential challenges head-on that might entail in this project. To provide the most accurate insights, a smooth workflow along with transparent communication is crucial. I assure you of both as we progress on this project together. Let's establish a connection so that we can navigate this journey diligently and bring your vision to life efficiently! Thanks...

@ianb65

Hello, I can build this POC end to end as a sole Node.js developer with hands-on OpenTelemetry experience, focusing on collecting traces, metrics, and logs and exporting them cleanly into Observe. I understand the architecture you described: instrument a Node.js service running in Docker on Fargate, capture signals via OpenTelemetry, route logs through AWS Lambda, then export the signals to Observe with a working, reproducible setup. I’ll keep the solution practical and demo-ready by delivering a minimal Node.js app with OpenTelemetry SDK configuration, a containerized deployment path for Fargate, and a Lambda component that receives and forwards logs in the expected format. I’ll wire up the exporter configuration for Observe so you can validate ingestion and confirm that traces, metrics, and logs appear correctly and correlate as expected. You’ll get a clean repo with Dockerfiles, infrastructure/deployment notes, and a short runbook showing how to start the POC locally and in AWS, plus how to verify the signal flow inside Observe. Best regards, Ian Brown

@chiragardeshna

Hi there, I have thoroughly reviewed your project Node.js OpenTelemetry POC with Observe, AWS Lambda, and Fargate. I have built observability PoCs where correctness of signal collection and export paths was the primary goal. I have 7+ years of experience handling Node.js services with OpenTelemetry, including metrics, traces, and logs pipelines, AWS Lambda and Fargate integrations, and Docker-based deployments. I regularly work with OpenTelemetry SDKs, exporters, collectors, AWS infrastructure, and Observe-compatible ingestion patterns. I reduce client risk by validating each signal path independently, using minimal reproducible services, and documenting the full flow from instrumentation to Observe export. I keep the POC clean, containerized, and easy to run so results are verifiable. I am available to start immediately. Regards Chirag

@royalwebraisers

Dear Hiring Manager, I understand you need a Node.js developer to build a POC for collecting metrics, traces, and logs, forwarding them via AWS Lambda, and exporting to Observe. I will share my portfolio on your first message. Implementation Approach: • Set up Node.js service with OpenTelemetry for metrics, traces, and logs collection • Forward logs and signals to AWS Lambda, orchestrated via Fargate • Export collected signals to Observe and verify observability • Containerize the POC using Docker for consistent deployment Queries: • Are there any specific metrics or trace types you want prioritized in the POC? • Do you have existing Observe account and AWS environment ready for integration? • Should the Docker setup include CI/CD for automated deployment to Fargate? I will be looking forward to hearing from you. Kindest Regards

@SBITServices

Hi Satyam, I have extensive experience with Node.js and have worked with opensource opentelemetry. I am well-versed in creating proof of concept projects that involve collecting signals like metrics, traces, and logs, sending logs to AWS Lambda, and exporting signals to Observe. Additionally, I am proficient in Docker containerization. Let's discuss further to understand your requirements in detail. Regards, Sai Bhaskar

@durgesh8527

As a seasoned FULL STACK SOFTWARE ENGINEER with over 12 years of experience, I have successfully utilized the skills you require in your Node.js project. Having worked for numerous notable organizations, I am well-vested in creating high-end, quality web and mobile applications tailored to customer requirements. Notably, I am conversant with the OpenTelemetry system you need for your project. My level of experience and skill with Node.js, MongoDB, AWS Lambda and Fargate makes me the perfect fit for building and integrating your POC project. My proficiency goes beyond just the language: I also have an in-depth understanding of Docker containerization which is an essential component of your task. I maintain familiarity with services like Observeinc and have no problem ensuring logs are collected efficiently before exporting to Observability via AWS Lambda. Finally, With my ability to operate in USA time zones and strong communication skills, you can count on my reliability to deliver results on time even as we communicate seamlessly throughout the process. In conclusion, hiring me would mean enlisting a dedicated professional who will put your goals first and use their extensive resources to ensuring its absolute fruition. Can't wait to showcase my excellence through this project!

@domenicod7

✨✨✨✨✨✨ I AM DOMENICOD ✨✨✨✨✨✨ I can architect a fully containerized Node.js POC that captures metrics, traces, and logs via OpenTelemetry, routes them through AWS Lambda/Fargate, and streams everything seamlessly into Observe for real-time insights. With hands-on experience building observability pipelines, Dockerized microservices, and serverless integrations, I’ll deliver a robust, production-ready signal flow that validates end-to-end monitoring. I take full ownership of the setup, ensuring each component—from Node.js instrumentation to Lambda export—is secure, efficient, and fully reproducible. Ready to start immediately.

@gaurangdev

Hello There, I hope you are having a great day! I’m a sole, experienced Back-end (NodeJS) developer with hands-on experience working with OpenTelemetry (open source) to collect and export metrics, traces, and logs in cloud-native environments. I’ve built POCs and production setups where signals are captured in Node.js services, processed through AWS Lambda and Fargate, and exported to observability platforms like Observe Inc. I’m comfortable configuring OpenTelemetry SDKs, collectors, and exporters, wiring logs through Lambda, and ensuring everything runs cleanly in Dockerized environments. I focus on practical, working POCs with clear documentation so the setup can be extended or productionized later. This sounds like a well-scoped POC, and I’m confident I can deliver it end to end. Let’s discuss your current architecture, signal flow expectations, and timeline to get this moving. Thanks & Regards!

@danylop55

Hey there, Quick check: do you want the OTel Collector as a sidecar/daemon in Fargate, or do you want a pure Node SDK setup that ships OTLP directly, with Lambda only for logs? I’ve worked with OpenTelemetry in Node (metrics + traces + logs) and AWS (Lambda + ECS/Fargate), and can build a clean POC that proves the full signal pipeline into Observe. How I’ll implement the POC Node.js service (Dockerized) instrumented with OpenTelemetry SDKs: Traces: HTTP + custom spans Metrics: runtime + custom metrics Logs: app logs bridged to OTel (OTLP) Export path Traces + metrics: OTLP to Observe (via endpoint + token) Logs: send to AWS Lambda (HTTP/API Gateway or direct), then Lambda forwards to Observe (OTLP/HTTP or expected ingest route) Fargate setup Task definition with app container + (optional) OTel Collector container Env vars and secrets wired cleanly Validation Generate traffic, confirm in Observe UI: service map/traces, metric charts, log correlation I’ll also include a minimal README with exact run steps (docker compose local + deploy notes), so your team can extend it. If you share your preferred routing (Collector vs direct OTLP) + Observe ingest details you have, I can start immediately. Best, Danylo.