We have a .NET 8 Web API running on Azure App Service with Azure SQL and Azure Service Bus. Right now, our order flow performs a dual write: it saves the order to SQL and then publishes an `OrderCreated` event to Service Bus. The issue is that a couple of times each week, the SQL transaction succeeds but the Service Bus publish times out. The order is stored successfully, but downstream systems never receive the event. We usually catch it later through a reconciliation report and replay it manually, which isn't a long-term solution. We know the right fix is the Transactional Outbox pattern, but we haven't had the bandwidth to implement it properly. We're looking for someone who can build it for this one workflow so we can use it as the reference implementation for the rest of our events. We're looking for: - An Outbox table that's written in the same EF Core transaction as the Order - A `BackgroundService` dispatcher that polls the outbox and publishes messages with at-least-once delivery semantics - Exponential backoff for retries - Service Bus `MessageId` mapped to the outbox row's primary key so we can take advantage of duplicate detection - Poison message handling that parks a row after a configurable number of failed attempts and emits a metric so we can alert on it - A short write-up explaining the delivery and ordering guarantees of the implementation, along with the guarantees it does not provide, so downstream teams understand the tradeoffs We're intentionally not looking for Hangfire. We'd like this implemented as a plain hosted `BackgroundService` so we can understand the underlying pattern and extend it ourselves over time. To make sure you've read the project description, please answer this in the first two sentences of your proposal: Would you implement the dispatcher as a polling worker or using SQL CDC + Debezium, and why? We skip generic, copy-and-paste proposals.

Role summary Power BI Developer to build an integrated KPI dashboard that pulls data from multiple departmental Excel and other source files, creates department-level reporting, and develops cross-functional views that combine data across teams. The role is intended as a short-term, fast-moving engagement with an ASAP start and remote flexibility. Key responsibilities Build Power BI dashboards from disparate data sources, especially Excel-based departmental KPI reports. Create Level 1 dashboards for individual departments and their core metrics. Create Level 2 dashboards that combine data across departments for derivative reporting and business insights. Design a repeatable process to ingest and refresh recurring Excel inputs. Work quickly to stand up an initial dashboard in a few weeks. Collaborate with stakeholders to translate reporting needs into usable visual dashboards. Required skills 5+ years Strong hands-on Power BI development experience. Experience integrating multiple data sources into a unified dashboard. Ability to work with messy or decentralized Excel-based reporting inputs. Experience building KPI dashboards and cross-functional reporting views. Ability to deliver quickly with minimal ramp-up. Preferred skills Experience with dashboard automation and scheduled refresh workflows. Experience supporting public sector or multi-department reporting environments. Ability to advise on scalable dashboard structure beyond the initial prototype.

We're looking for an experienced C#/.NET developer to help us improve and maintain a production app that's already being used by customers. The system has been around for a while, and as we've grown, we've started running into some real problems. This isn't a greenfield project. We need someone who's comfortable getting into existing code, figuring out how things work, and making them better without breaking stuff. Our backend runs on .NET 8 and we're moving toward .NET 10. We use Entity Framework Core for most data access, but we also write raw SQL for the heavier queries. The database is SQL Server, about 200 GB with roughly 500 daily active users. We have REST APIs, though there's still some legacy WebForms hanging around. The frontend is React with TypeScript, handled by another team, but you'll work with API contracts. We're on Azure App Service with Azure SQL and Key Vault, and we use Azure DevOps for CI/CD and Git for source control. The team is small, one PM, two backend devs, and one frontend dev, working in two-week sprints with code reviews and planning meetings. You'll be doing a bit of everything. Fixing slow endpoints, optimizing queries, improving background jobs. Investigating customer issues, cleaning up old code, adding new features safely. We also need help automating manual stuff like data exports and report generation. You'll join code reviews, sprint planning, and technical discussions. We're looking for someone with at least five years of C# and .NET experience, including .NET Core or .NET 5+. You should know SQL Server well, be comfortable with REST APIs, and know how to work with existing production code without causing outages. Good English is a must, and we care more about getting things done than about perfection. Nice to have: Azure, React, Hangfire, or Docker. When you apply, just send a short summary of your experience, a couple of examples of similar work you've done, when you can start, and your hourly rate. This is a long-term thing. We want someone who can stick around and grow with us. Hours are flexible, though some overlap with CT timezone would be helpful.

We need a data warehouse architect to design and recommend a solution that integrates with SageX3 and supports Power BI reporting. The work includes evaluating the right data warehouse approach, defining the architecture, and planning how to connect ERP data into a reporting environment. You should be able to advise on the best structure for reliable reporting, data flow, and long-term scalability. Experience with ERP systems and business intelligence reporting is important for this project.

Seeking a Power BI developer to build the first phase of an operations dashboard for a small services company. We report on four locations. Data comes from a read-only SQL database from our field operating system. We provide the schema, server, and credentials. No API work, no Excel imports. Phase 1 scope: connect to the database, build a ticket-level fact table with a date table and supporting dimensions, write roughly a dozen DAX measures, and deliver one weekly operations table showing month-to-date on top with each week below, broken out by location. Publish to the Power BI service with a working scheduled refresh. The data model should carry every ticket-level field from the schema, not just the fields this page displays, because we plan to add pages later. Requirements: strong Power Query and M with native SQL query folding, solid DAX, incremental refresh, and experience publishing with scheduled refresh. Fixed price with a written acceptance checklist. The measures must reconcile to our existing spreadsheet on the same inputs before payment releases. Done means the numbers tie, not that the page looks right. This is the first milestone of a larger project. Good work leads directly to more.

We're experiencing intermittent stalls in a .NET/Kestrel application running in Kubernetes pods. We need an experienced .NET performance engineer to help diagnose the root cause and recommend/implement a fix. The problem: Pods intermittently stall under load — requests stop being processed We suspect a threading issue (possible thread pool starvation), but haven't confirmed root cause We've captured thread pool diagnostics showing a growing pending work item queue prior to a stall We've taken memory dumps during/after incidents but haven't been able to extract clear signal from them Stack: .NET (ASP.NET Core / Kestrel), Redis, SQL Server, Elasticsearch, running containerized (Kubernetes) What we need help with: Review our existing dumps, logs, and thread pool/GC counters to identify likely root cause Advise on and help set up better diagnostic capture for the next incident (dotnet-trace, dotnet-counters, PerfView, or equivalent) since our current dumps aren't giving us enough Identify sync-over-async patterns, blocking calls, or connection/keep-alive issues in Kestrel that could cause thread starvation Assess whether Redis or SQL calls (connection pool exhaustion, blocking calls, timeouts) could be contributing to thread pool pressure Recommend concrete code/config changes to prevent recurrence Ideally: pair with our team live during/after the next incident to capture and interpret data in real time Ideal experience: Deep expertise in .NET thread pool internals, async/await patterns, and Server GC behavior Hands-on experience diagnosing incidents using WinDbg/dotnet-dump, dotnet-trace, dotnet-counters, or PerfView Experience with ASP.NET Core/Kestrel hosting internals — connection limits, keep-alive, middleware pipeline Familiarity with Redis and SQL Server client libraries and how misuse (blocking calls, pool exhaustion) can cause thread starvation Experience with containerized/Kubernetes .NET deployments a plus Comfortable working from partial/incomplete diagnostic data and telling us what additional data to capture next Engagement type: Starting with a paid diagnostic review of existing logs/dumps (fixed scope) to assess feasibility Potential for ongoing engagement if we need help capturing and interpreting data during a live incident, or implementing fixes To apply, please briefly describe: A similar thread pool starvation or Kestrel stall issue you've diagnosed, and how you found the root cause What tools/data you'd want us to capture next time this happens, given that our current memory dumps haven't been useful Your experience with Redis/SQL Server client misuse causing thread pool pressure

1k per month flat fee 20 hours Must have 15 years experience Master of Computer Science Key Skills: • Python and/or TypeScript / Node.js • AWS cloud infrastructure • Terraform / Infrastructure as Code (IaC) • PostgreSQL / SQL • REST APIs and third-party integrations • Docker, GitHub and CI/CD • Redis, queues and scalable backend architecture • Authentication, security and data privacy • Stripe payment integrations • Snowflake • Datadog / Cloudflare • Production debugging, monitoring and performance optimization Strong coding abilities

We need an experienced consultant to help provision and configure Azure AI Search and Azure OpenAI (with SQL) for our enterprise client, who is a Microsoft shop. The work includes working with enterprise client to ensure up the environment is set up properly, integrating search and AI capabilities, and ensuring the solution is ready for use. You should be able to guide implementation decisions, troubleshoot issues, and deliver a reliable foundation for future AI-driven projects. Experience with similar cloud-based AI implementations is required. Working inside HIPPA environment highly desired. Must pass a background / security check.

We are seeking an experienced marketing data engineer / automation developer to build an automated cross-channel marketing analytics and reporting system. Project Objective Our goal is to consolidate data from multiple marketing and analytics platforms into a centralized data repository, automate recurring reporting, and create a dashboard that allows our team to evaluate marketing performance across channels. We are also interested in incorporating AI-driven workflows that can analyze the consolidated data and surface useful observations or recommendations. Phase 1 Data Sources The initial project will integrate six sources: -Google Analytics 4 -Google Ads -Microsoft Advertising -LinkedIn Ads -LinkedIn Page Analytics -SEMrush Note: A potential future phase may add additional sources including YouTube, Wistia and BusinessWire. Desired Functionality The completed system should: -Automatically retrieve data from the supported platforms through their APIs. -Normalize and consolidate marketing data from the different sources. -Store the resulting data in a centralized data warehouse or repository. -Automate recurring data collection and reporting workflows. -Provide a dashboard for viewing marketing performance across channels. -Allow us to compare paid-media performance across Google, Microsoft and LinkedIn. -Incorporate website and owned-social performance from GA4 and LinkedIn. -Incorporate competitor insights from SEMrush. -Include data-quality monitoring to identify missing or incomplete fields. -Support automated notifications or reports through Slack or Microsoft Teams. -Explore the use of AI/LLM workflows to analyze results and provide actionable marketing recommendations. Technology Our current proposed architecture includes: -n8n or similar for workflow/API orchestration -SQL -A centralized data warehouse such as Google BigQuery or Snowflake -Sigma for dashboarding and visualization -Claude/Anthropic and MCP for AI-assisted analysis and recommendations -JavaScript as needed for custom integrations We are open to recommendations regarding the architecture if you have experience building similar systems and believe an alternative would be more reliable, maintainable or cost-effective. Required Experience We are particularly interested in candidates with experience in: -n8n or comparable workflow automation platforms -REST APIs and API integrations -SQL and data modeling -ETL/ELT and automated data pipelines -BigQuery, Snowflake or comparable cloud data warehouses -Marketing analytics and advertising data -Google Analytics 4 and advertising-platform APIs -JavaScript for custom API/workflow development -Experience with LinkedIn APIs, Microsoft Advertising, SEMrush, Sigma, Claude/Anthropic, MCP or other LLM-based agentic workflows is strongly preferred. Ownership & Maintainability All technology accounts, workflows, code, API connections and data repositories created for this project must be owned by our company. An important objective is maintainability. The completed system should be documented sufficiently so that its ongoing management can be transferred to another internal or external technical resource in the future. When Responding Please include: -Examples of similar marketing data integration or automated reporting systems you have built. -The APIs and marketing platforms you have previously integrated. -Your experience with n8n, SQL and cloud data warehouses. -Your experience incorporating AI/LLMs into automated data-analysis workflows. -Your recommended architecture for this project and any changes you would suggest to the technology stack described above. -Your estimated hours, timeline and cost for completing Phase 1. -Any ongoing software, API or infrastructure costs we should anticipate. -Your approach to documentation and handoff at the end of the project. We are specifically looking for someone who has built production-quality data integrations and automated reporting systems, rather than someone whose experience is limited primarily to creating dashboards.

We are migrating away from Epicor Prophet 21 (P21) and need an experienced P21 consultant to help extract our historical ERP data into a portable, offline archive format. The goal is to preserve business records and reporting capability after the P21 environment is decommissioned. We are not looking for a full ERP migration at this stage. Instead, we need an organized export of key business data into commonly accessible formats such as CSV, Excel, SQL database dumps, or similar. Scope of Work The consultant will: Review our Epicor P21 environment and available export options Identify key data entities and relationships Export historical data into a structured format suitable for long-term retention Document the exported datasets and field mappings Provide recommendations for maintaining usability of the archive after P21 is retired Data Areas of Interest We expect the archive to include, at minimum: Customers and contacts Vendor records Products and inventory Sales orders Purchase orders Invoices and accounts receivable Accounts payable records Pricing data Transaction history Notes and attachments (if available) Custom fields and user-defined data Please describe any limitations or special considerations regarding attachments, audit trails, or customizations. Deliverables Exported data in CSV, Excel, SQL, or other agreed-upon format Data dictionary or field mapping documentation Summary of relationships between major tables/entities Recommendations for accessing and reporting on archived data in the future Required Experience Significant experience with Epicor Prophet 21 (P21) Experience performing data exports, migrations, or archival projects Knowledge of P21 database structure and reporting tools Ability to work with on-premises and/or hosted P21 deployments Strong documentation skills When Applying Please include: Your experience with Epicor Prophet 21. Examples of similar ERP archival or migration projects. Recommended archive format(s) and why. Any risks or challenges you anticipate with exporting historical P21 data. Project Type Fixed Price or Hourly (please provide your recommendation based on the scope). We are primarily looking for a consultant who can help ensure we retain complete and usable historical data after Epicor P21 is no longer available to our organization.