Three quick stages before you hear back

Send Application
Skills Check
Recruiter Screening

There is no fee to apply, so treat every stage seriously. Be honest about what you can actually do, even if your experience feels limited, because recruiters respond to clear, genuine answers. Spending a little extra time on your responses can make the difference.

New openings, shared on LinkedIn first Follow us on LinkedIn
Home / Jobs / remote qa jobs / remote software engineer jobs

PROJECT-BASED OPPORTUNITY | $100/HR Remote Software, Platform & Data Engineer

Project-based remote opportunity for experienced Software, Platform, and Data Engineers with strong Python, Node.js, Azure, and OpenTelemetry skills.

A new project-based engineering opportunity is available for professionals who have experience building production-grade cloud systems, telemetry pipelines, data infrastructure, and privacy-focused engineering solutions.

This assignment is particularly relevant for engineers who enjoy working independently on technically demanding projects involving AI infrastructure, developer tooling, cloud platforms, observability, and data pipelines.

The project requires someone who can take an existing technical design and turn it into a working production pipeline with minimal supervision.

Important: This opportunity is expected to start next week, so qualified candidates who are interested should consider registering as soon as possible.

Project Details

This is a 3-month contractor assignment focused on building an end-to-end system for collecting, processing, securing, and reviewing AI coding-agent telemetry.

The engineer will work on a pipeline that captures agent traces from developer machines, sends telemetry to a centralized cloud environment, removes sensitive information, and makes the resulting data available through a secure read-only interface.

The project combines several areas of modern engineering, including:

  • Cloud infrastructure

  • Software engineering

  • Data engineering

  • Observability

  • OpenTelemetry

  • Azure PaaS

  • Data privacy

  • PII and secret detection

  • Developer tooling

  • AI/LLM infrastructure

This makes the role particularly interesting for engineers looking for project-based remote software engineering jobs rather than traditional long-term employment.

Registration / Application: APPLY

What Will You Build?

The main responsibility is to build the technical implementation of an agent trace collection and processing system.

The work covers the complete pipeline, starting from telemetry collection on developer machines and continuing through centralized ingestion, privacy processing, storage, and trace visualization.

1. Build the OpenTelemetry Capture Pipeline

The project requires setting up an OpenTelemetry-based capture path.

This includes configuring endpoint environments and shell environments such as .bashrc, establishing OTLP exports, and configuring collector pipelines.

You will work with components such as:

  • OpenTelemetry receivers

  • Processors

  • Exporters

  • OTLP

  • Spans and traces

  • Semantic conventions

  • Telemetry collection

Hands-on OpenTelemetry experience is therefore important for this project.

2. Develop the Azure Ingestion Layer

Collected telemetry needs to be securely processed in a centralized Azure environment.

The engineer will be responsible for implementing the ingestion architecture and connecting the different Azure services required by the pipeline.

Potential technologies involved include:

  • Azure Container Apps or AKS

  • Azure API Management

  • Azure Data Explorer / Kusto

  • Application Insights

  • Azure Blob Storage

  • Azure Data Lake Storage Gen2

  • Azure Key Vault

  • Microsoft Entra ID

The goal is to create a reliable cloud pipeline capable of handling telemetry while maintaining strong security and privacy controls.

3. Implement Privacy and Security Controls

Privacy is a core requirement of the project.

Before telemetry can be viewed by reviewers, sensitive information needs to be identified and removed.

The engineer will work on mechanisms for detecting and redacting information such as:

  • Personally identifiable information

  • Secrets

  • Credentials

  • Sensitive strings

  • Other potentially confidential content

Practical experience with techniques such as regex detection, entropy analysis, redaction, and tokenization can be highly valuable.

This is not simply a data-processing project. The pipeline must be designed so that sensitive information does not accidentally reach the review environment.

4. Build the Sanitized Data Layer

After sensitive information has been removed, the sanitized telemetry needs to be stored in a queryable format.

The system should maintain relationships between:

Task → Session → Trace

This correlation allows reviewers to understand the activity represented by each collected trace without exposing the original sensitive information.

5. Create a Read-Only Trace Viewer

The final stage involves connecting the sanitized data to a read-only trace viewer.

The viewer should allow authorized reviewers to inspect and query processed traces while maintaining the privacy boundaries established earlier in the pipeline.

This gives the engineer ownership of the project from endpoint collection all the way to the review interface.

Required Technical Skills

This project is aimed at experienced engineers rather than entry-level developers.

Candidates should ideally have:

  • A Bachelor's degree in Computer Science, Engineering, or a related discipline, or equivalent practical experience

  • At least 5 years of professional software, platform, or data engineering experience

  • At least 3 years of hands-on Azure experience or comparable major-cloud experience

  • At least 2 years working with observability or telemetry pipelines

  • Direct OpenTelemetry experience

  • Strong Python or Node.js skills

  • Bash scripting experience

  • Experience building production systems

  • Understanding of cloud security fundamentals

  • Knowledge of RBAC and private networking

  • Experience with data privacy and sensitive-data handling

Candidates should be comfortable taking a written technical design and independently turning it into a functioning system.

Azure Experience

Strong Azure knowledge is an important part of this project.

Experience with the following services can be especially relevant:

  • Azure Container Apps

  • Azure Kubernetes Service (AKS)

  • Azure API Management

  • Azure Data Explorer / Kusto

  • Application Insights

  • Azure Data Lake Storage Gen2

  • Azure Blob Storage

  • Azure Key Vault

  • Microsoft Entra ID

Engineers coming from another major cloud platform may also be considered if their experience can transfer effectively to Azure PaaS technologies.

OpenTelemetry Experience

OpenTelemetry is one of the most important technical requirements for this assignment.

Candidates should understand concepts such as:

  • OTLP

  • OpenTelemetry collectors

  • Receivers

  • Processors

  • Exporters

  • Spans

  • Traces

  • Semantic conventions

  • Telemetry pipelines

Experience with Grafana or other telemetry backends can also be an advantage.

Who Is This Project Best For?

This opportunity could be a strong match for:

Software Engineers who have experience building backend and cloud systems.

Platform Engineers who work with infrastructure, observability, cloud platforms, and developer tooling.

Data Engineers who have experience designing reliable data ingestion and processing pipelines.

Cloud Engineers with strong Azure experience and security awareness.

Observability Engineers who understand OpenTelemetry and telemetry architectures.

AI Infrastructure Engineers who have worked with LLM agents, developer tools, or GenAI observability.

It may also appeal to engineers who regularly work on remote software engineering projects and prefer focused contract assignments.

Nice-to-Have Experience

Additional experience that can strengthen an application includes:

  • Grafana

  • Telemetry backend configuration

  • LLM agent observability

  • Generative AI infrastructure

  • Cross-cloud identity federation

  • Azure AD / Entra ID

  • GCP IAM

  • Advanced cloud security

  • Developer productivity tooling

These skills are not necessarily the core requirement, but they can be useful when working across the project's infrastructure.

Compensation and Engagement

The project offers a compensation rate of:

$100 per hour

The engagement is structured as a contractor assignment.

Key details include:

  • Project duration: 3 months

  • Expected start: Next week

  • Minimum commitment: 20 hours per week

  • Daily commitment: At least 4 hours per day

  • Timezone overlap: 4 hours with PST

  • Work arrangement: Fully remote

  • Employment type: Contractor assignment

  • Benefits: No medical or paid leave

  • Location requirement: North America

Because the project has a relatively near-term start date, interested candidates should avoid waiting until the final days to register.

Evaluation Process

The initial evaluation is designed to be relatively short.

The process is approximately 30 minutes and includes one round covering:

  • Technical discussion

  • Cultural discussion

  • Relevant engineering experience

  • Ability to work independently on the project

Candidates should be prepared to discuss previous experience with cloud platforms, telemetry systems, data pipelines, security, and production engineering.

How to Apply

If your background matches the requirements above, you can register through the application link below.

Registration / Application: APPLY

Because the expected start date is next week, qualified engineers should consider submitting their application as soon as possible.

Looking for More Remote Opportunities?

If you are actively searching for remote technology positions, you can also explore remote QA jobs and other remote opportunities across software, testing, engineering, and technology-related fields.

The remote job market continues to include both traditional employment and project-based opportunities, making it worthwhile to monitor new assignments regularly.

Final Thoughts

This project stands out because it combines several highly relevant areas of modern engineering: Azure, OpenTelemetry, cloud security, data engineering, privacy, and AI infrastructure.

It is not designed as a basic coding assignment. The successful engineer will need to understand how multiple components work together and take ownership of an end-to-end production pipeline.

For engineers with strong Azure and OpenTelemetry experience who are comfortable working independently, this could be an interesting 3-month remote project-based opportunity.

With the project expected to begin next week, qualified candidates should consider registering early rather than waiting until the opportunity becomes more competitive.

#RemoteJobs #RemoteWork #ProjectBased #ProjectBasedJobs #SoftwareEngineer #DataEngineer #PlatformEngineer #AzureJobs #PythonJobs #NodeJS #OpenTelemetry #CloudEngineering #DevOps #AIJobs #TechJobs #WorkFromHome #RemoteEngineering