⭐ JOB AD: Full Stack Java Developer (Hybrid – NJ Office Required for Initial Paid Assessment) Location: Mountain Lakes, NJ (Initial in‑office assessment required) Type: Contract → Long‑Term / Hybrid Compensation: Competitive, based on experience and performance We are expanding our engineering team as we scale our Revenue Generation Engine (RGE) and Autonomous OS — advanced AI-driven systems powering multiple client platforms. We are seeking a Full Stack Java Developer who is comfortable working across modern backend and frontend stacks, and who can execute clean, efficient, and secure development workflows. This role begins with a paid, in‑office technical assessment at our private NJ development office. This is standard procedure due to the sensitive nature of our systems and the proprietary architecture we maintain. ⭐ What You’ll Do (Initial Assessment Project) The first assignment is a small, well‑defined technical task designed to evaluate your baseline competency with standard development tools and workflows: - Setting up and running a project locally - Working with GitHub repositories - Re-establishing deployment pipelines (e.g., Netlify or similar) - Ensuring clean builds and proper CI/CD functionality These are foundational skills expected of any experienced developer. Successful completion unlocks access to larger, ongoing AI and enterprise projects. ⭐ What We’re Looking For - Strong experience with Java, Spring Boot, REST APIs, Microservices - Solid understanding of React/Angular, modern front-end workflows - Comfort with GitHub, CI/CD, cloud deployments (Netlify, AWS, GCP, Azure) - Ability to work efficiently, follow structured processes, and deliver clean execution - Professionalism, reliability, and strong communication - Ability to work on-site for the initial assessment (required) - Availability for hybrid or remote work afterward (project-dependent) ⭐ Why Work With Us - We are scaling rapidly and onboarding multiple developers - You will work directly with our architecture and AI systems team - Opportunity to grow into long-term, high-impact roles - Exposure to cutting-edge AI automation and enterprise-level systems - Competitive compensation with performance-based advancement - A culture focused on speed, precision, and innovation ⭐ How to Apply Please send: - Your resume or LinkedIn profile - Your standard rate (hourly or fixed) - Your availability for the in‑office paid assessment in Mountain Lakes, NJ Office We are moving quickly and evaluating candidates on a rolling basis.

DataSci Technologies, Inc. is an enterprise software C-Corp. We own our domain (datascitechnologies.com) and have finalized our independent institutional asset valuation. We are seeking an elite, Expert-level Full-Stack Product Architect / Fractional CTO to build the V1 / MVP layout of our proprietary predictive AI platform, the DST Codex, from the ground up. The Product & Target Audience: The DST Codex is a secure, high-end portal built specifically for institutional asset management firms and real estate conglomerates managing $250M to $10B+ in AUM [1.1]. The platform maps out, quantifies, and visualizes hidden operational risk metrics—known as "Shadow Variables"—to protect institutional capital. The user interface must look like a premium, dark-mode institutional banking terminal. Required Technical Scope (Full Lifecycle Build):Infrastructure & Security: Secure database architecture setup using AWS or Google Cloud Platform with enterprise-grade encryption. Front-End & Interface: Building a pristine, highly aesthetic, dark-mode responsive dashboard layout (React, Vue, or enterprise visual frameworks like WeWeb/Bubble). The Core Visualization Layer: Engineering interactive, custom open-source data tracking charts (utilizing D3.js or high-performance visualization packages) to map out predictive risk telemetry. User Auth: Airtight, password-protected multi-tenant user authentication and client login portals. Project Structure: We are a capital-efficient C-Corp moving at high velocity. We are looking for an experienced product builder who can act as a long-term technical partner. Please share your portfolio of completed SaaS platforms/dashboards, outline your architectural recommendations, and state your standard fixed-price or monthly fractional structures for a 60-day development milestone sprint.

We are a digital marketing agency focused primarily on the homebuilding and residential construction industry, and we’re looking for an experienced WordPress developer to temporarily fill in for our in-house developer during paternity leave for approximately two months. This is not a “babysit a template site” role. Most of our websites are fully custom WordPress builds using custom themes, Advanced Custom Fields (ACF), custom post types, API integrations, and performance-focused development practices. You’ll work closely with our internal design and marketing teams to handle both front-end and back-end development tasks across multiple client websites. Example Websites: https://westhomes.com/ https://stonemanorhomes.com/ https://frenchbrothers.com/ What You’ll Be Doing * Developing and maintaining custom WordPress websites * Building responsive front-end layouts from supplied designs * Working within existing custom WordPress themes and frameworks * Creating and modifying Advanced Custom Fields (ACF) structures and flexible content systems * Updating templates, page builders, and custom functionality * Troubleshooting bugs, styling issues, and plugin conflicts * Optimizing websites for speed, performance, and SEO best practices * Assisting with deployment, staging environments, and version control workflows * Working with third-party and custom API integrations that feed dynamic website data * Collaborating with our internal project managers and designers in a fast-paced agency environment Required Skills & Experience * Expert experience with Git * Strong experience with custom WordPress development * Advanced experience with: * Advanced Custom Fields (ACF) * Custom post types * Custom theme development * PHP * JavaScript/jQuery * HTML5/CSS3 * Responsive/mobile-first development * Experience working with API integrations and external data feeds * Ability to work inside existing codebases and adapt quickly * Understanding of website performance optimization and technical SEO fundamentals * Experience debugging and troubleshooting production websites * Strong communication and reliability — we move quickly and need someone responsive Nice to Have * Experience in agency environments * Experience with builders/homebuilder websites or real estate-related sites * Familiarity with hosting environments, server migrations, and DNS management * Experience with animation libraries or interactive front-end effects Project Structure This role will be hourly, but we plan to structure it similarly to a retainer arrangement with a guaranteed minimum of 30 hours per month during the contract period. There is also potential for ongoing overflow work after the temporary coverage period if it’s a good fit. To Apply Please send: * Examples of custom WordPress websites you’ve developed * Your experience with ACF and custom theme development * Examples of API integrations or complex functionality you’ve worked on * Your availability over the next 2–3 months * Your hourly rate We are looking for someone dependable, detail-oriented, and capable of jumping into an existing development environment quickly without extensive hand-holding.

Overview: I have a marketing site for my construction/remodeling business built in Lovable (Vite + React single-page app). The problem: it's client-side rendered, so search engines and AI crawlers (GPTBot, Perplexity, ClaudeBot) and social link previews receive an empty HTML shell with no content. Google has only indexed 6 of my 89 pages because of this. I need the site served as fully prerendered static HTML so every route returns real content in the raw HTML — no JavaScript required to see it. Scope of work: Export my existing Lovable project to GitHub (I'll authorize access). Add a build-time prerendering step (react-snap or equivalent) that generates a static HTML file per route — including all service pages and the ~58 service-area pages. Deploy to Netlify or Cloudflare Pages (your recommendation) with the prerender step running automatically on each build. Point my existing domain (www.mastersconstructiongroup.com) to the new host via DNS. I'll provide registrar access or make the changes you specify. Critical requirement: I must be able to keep editing the site in Lovable after the move. Set up the GitHub → host pipeline so that when I publish edits from Lovable, they automatically flow through and redeploy the prerendered site. I do NOT want to edit code for routine content changes. Please confirm you can preserve this workflow. Acceptance criteria (how I'll confirm it's done): Running curl (no JavaScript) on the homepage and at least 3 interior pages returns the page's real title, H1, and body content in the raw HTML. The LocalBusiness / GeneralContractor JSON-LD schema is present in the raw HTML. I can make a content edit in Lovable, publish, and see it live on the domain without developer involvement. Helpful notes: The Lovable export is already partly prepared for this: main.tsx uses hydrateRoot(), internal links render as real anchor tags, and react-helmet is wired up for per-page head tags. There's also a react-snap config recipe I can share with you. This should be a small, well-defined job. Please include in your proposal: a fixed-price quote, estimated turnaround, and a one-line confirmation that you can keep my Lovable editing workflow intact after the move.

SHOPIFY CUSTOM APP MIGRATION — LIFT-AND-SHIFT, NO DEVELOPMENT I'm looking for an experienced developer to perform a clean lift-and-shift migration of two existing custom Shopify apps from my current development agency's hosting infrastructure onto hosting that I own and control. This is purely a migration job. No new features, no code changes, no enhancements. The apps work as intended in their current state — I simply need them moved. THE TWO APPS BEING MIGRATED 1. A custom currency recorder app used for dual-currency (KYD / USD) transaction reconciliation in our Shopify store. 2. A custom Shopify POS UI extension that integrates with our in-store loyalty program (Jericommerce). Both apps are currently live and in operational use. They cannot go dark, even briefly, during the migration. WHAT I NEED FROM YOU - Coordinate with my current developers to obtain the source code, environment variables, deployment configurations, and any other materials needed to redeploy the apps on new infrastructure. - Recommend a target hosting environment that makes the most sense long-term for this kind of workload (e.g. Render, Heroku, AWS, DigitalOcean) and explain why. - Stand up the new hosting environment under accounts that I own. - Deploy the apps onto the new hosting in a staging state, run them in parallel with the existing deployment, and confirm they are functioning identically to the current production version. - Confirm with me, in writing, that the migrated apps are fully functional before any cutover takes place. I will not authorize the cutover until you have demonstrated the new deployment works as expected. - Execute the cutover — switching webhook endpoints, DNS, Shopify app URLs, or any other relevant routing — in a way that produces zero downtime or operational disruption. - Verify all Shopify connections (webhooks, OAuth, app proxies, POS UI extension registration, etc.) are correctly wired to the new hosting after cutover. - Document the new deployment so I have a clear record of where each app lives, how it is accessed, how the environment is configured, and how to maintain it going forward. WHAT I AM NOT LOOKING FOR - No new features. - No code refactoring. - No "improvements" to the apps. - No exploratory audit or rebuild. - The apps work. They just need to live somewhere else. If you see something in the codebase you'd genuinely recommend addressing, flag it to me separately — but do not change it as part of this engagement. Migration first, anything else later, only if I ask. WHO YOU'LL BE COORDINATING WITH This migration involves three parties: 1. You (the migration contractor). 2. My current development team (who will provide source code and deployment details). 3. Me (overseeing the engagement and approving the cutover). You will need to be comfortable coordinating with my current developers professionally to obtain what you need from them. The relationship is winding down, but the handover should be cordial and efficient. I will introduce you to them directly once we have an agreed scope and timeline. WHAT I'M LOOKING FOR IN A CONTRACTOR - Strong experience with Shopify custom apps (private apps, public apps, app extensions, POS UI extensions). - Strong experience with cloud hosting and deployment (Render, Heroku, AWS, DigitalOcean, or equivalent). - Experience with zero-downtime migrations and parallel-deployment cutover patterns. - Comfortable working with code you did not write and deploying it without making changes. - Direct, honest communication style. I do not need to be managed or shielded — I just need clear updates and reliable execution. - IP ownership: all deployment configuration, hosting accounts, environment variables, and documentation produced under this engagement belong to me. QUOTE AND PROPOSAL Please provide: - A fixed-price quote for the full migration as described above. - Your recommended hosting environment and rationale. - An estimated timeline from kickoff to cutover. - A brief description of your relevant prior experience (Shopify app migrations, hosting transitions, or similar). - Any clarifying questions you have before quoting. Looking forward to hearing from you.

We are looking for an expert backend developer and automation engineer to extend an existing, production-grade Model Context Protocol (MCP) server and overhaul its orchestration layer. The headline correction for this project: the existing Lawfather MCP is to be retained and extended, not rebuilt. It already exposes deterministic, parameterized Playwright tools for every required county portal (District Clerk, HCSO, HCDAO) and a client database. Those backend tools are the reliable layer and are not the source of the instability this project exists to fix. The instability lives entirely in the orchestration layer — the model-driven layer that decides when and how to call the tools. The fix is to move deterministic control out of model-followed prose and into code, and to host the agent on an always-on machine with persistent memory. Core Project Principles • Extend, Don't Rebuild: Retain and extend the existing MCP; do not re-implement portal scrapers from scratch. • Code Over Prompts: Deterministic logic lives strictly in tool code, never in instructions the model must remember each session. • No Caller Loops: Batch operations must run to completion server-side. No operation may require the caller (model) to loop. • Agnostic Architecture: The system must remain model-agnostic and host-agnostic. No single provider — Anthropic, OpenAI, Z.ai/GLM, or Nous — may be a hard dependency. • Privilege First: Client data stays on owned hardware; the model is never the gatekeeper of which case a file belongs to. Existing Tool Inventory (To Be Inherited As-Is) The following tools already exist on the production MCP (containerized on a local Synology NAS) and are in daily use. Re-deriving their behavior is completely out of scope: • hcdc_get_docket: Court settings by date range + bar number (District Clerk). • hcdc_check_filings: Per case: standard defense filings present vs. missing. • hcdc_download_filings: Images-tab documents: bulk OR selective by filters; dest_subfolder; dry_run. Note: The parameterized download tools already cover most retrieval requests. "All filings," "this filing," "all subpoenas," "all resets," and "everything filed that day" are argument combinations on this tool, not separate features. • hcso_locate: Defendant custody location (facility / floor / pod) by SPN. • hcdao_grab_file: Download a single named file from the DA portal Files tab. • hcdao_download_discovery: Batch / delta discovery download from the DA portal. • hcdao_download_media_alert: Batch-download files listed in a 'New Media Available' portal email. • hcdao_case_summary: Scrape the Case Jacket quick summary / DAO narrative. • hcdao_plea_offer: Scrape current plea offer + full offer history. • hcdao_assigned_ada: Assigned ADA name / email / phone on a case. • lookup_client / list_clients: Resolve / list clients from the shared client database. Scoped Work (Paid Deliverables) 1. County Case Resolver (New Tool): Find a case from partial identifiers — any subset of (name, SPN, DOB, court, cause). Searches county systems (not just the local client DB). MUST return a ranked candidate list for the user to choose from; MUST NEVER auto-select. Wrong-defendant selection is a privilege failure, not a cosmetic bug. 2. Latest-Version Retrieval: Add scope=latest to hcdao_grab_file so 'most recent' selects the newest among supplements instead of the first match. 3. Async Transcribe Tool (Skill to Tool Promotion): Build a deterministic MCP tool using Gemini 3.1 Pro Preview for transcription, followed by a second pass that sends the transcript back with case context for cleanup (speaker mapping, defense-moment preamble). Long-running: implement as an async job (submit to job id to poll to fetch), NOT a synchronous call. 4. OCR Tool (Skill to Tool Promotion): Implement a readability check on ingest. If a document is not cleanly readable, FLAG it and ASK before sending to Gemini 3.1 Pro Preview for OCR. OCR must be gated and confirmed, never automatic. 5. Server-Side Batch Jobs: Move all chunk, loop, delta, and throttle logic OFF the caller and INTO the tool code. One call runs the batch to completion. 6. Queued HCDAO Fixes: For hcdao_download_discovery, add a portal_ids filter for targeted single-file pulls and a custom output-path / Drive-folder destination feature. Known Portal Quirks to Handle from Day One • hcdc_get_docket returns a broader date range than requested; results must be filtered to the requested window. • hcdao_download_discovery delta detection is blind to files organized into dated subfolders and must be explicitly handled. • Court DG7 does not surface through standard bar-number docket lookup and requires separate handling. • The Playwright Node.js driver subprocess can die silently while database tools respond; you must health-check the driver proactively. Orchestration, Host Layer, & Deployment Topology • Target Host: Hermes Agent (Nous Research) running as the persistent shell, providing persistent memory, the scheduler, and messaging surfaces. The MCP server will plug directly into it. • Agnostic LLM Routing: Default the agent/dispatch role to the most reliable tool-calling model (currently Claude Opus). Route bulk, non-critical generations (draft summaries, transcript cleanup) to a cheaper model (e.g., GLM-5.2). No provider may be hard-wired. Per-tool pins are allowed strictly for transcription/OCR tasks (pinned to Gemini 3.1 Pro Preview). • Memory Fencing: Hermes's persistent memory and learning loops must remain enabled to accumulate facts and user preferences. However, the agent must be strictly fenced from self-editing or rewriting its own mechanical execution paths (portals, downloads, filings), which must remain frozen in MCP tool code. • Hardware Deployment Infrastructure: • Always-on Brain: M1 Pro MacBook Pro (16 GB, mains-powered, lid open) running the Hermes gateway, Messages.app, and a BlueBubbles iMessage bridge. Must be fully automated via launchd services to handle headless crash recovery, auto-login, and sleep prevention (pmset autorestart / caffeinate). • Tools and Storage: Synology NAS (10.0.0.149) hosting the Lawfather MCP container, local client folders, and Drive sync. • Private Network: Tailscale mesh across all devices for secure remote access without open inbound ports. Acceptance Criteria for Sign-Off • No batch operation requires the caller to iterate. • The case resolver returns ranked candidates and never auto-selects. • Transcription runs seamlessly as an async two-stage job surviving multi-hour files without timing out. • OCR never fires automatically on low-readability files without gated confirmation. • Zero regressions on the existing MCP tool inventory. • The Resiliency Test: The full stack successfully restarts completely unattended after a host reboot or simulated power loss, and is reachable via iMessage/SMS immediately after. • Self-editing is fenced on mechanical download/filing paths. Hard Guardrails • Privilege: Downloads route strictly to the correct client folder; a wrong-case match is treated as a severe defect, not a warning. Privileged audio/discovery data stays on owned hardware where the chosen model allows. • Determinism: Repeatable steps live entirely in tool code, never in prompts. • Agnosticism: Model and host layers must remain fully swappable without modifying the core MCP tools. Before quoting "done," you will be expected to confirm live portal behaviors regarding District Clerk document labels, DA portal stable identifiers, and county search surfaces. How to Apply Please submit a proposal detailing your specific experience with MCP architectures, Playwright browser automation, and macOS/Docker DevOps automation. Anti-Bot Filtering: To prove you read this entire scope, please start your application with the phrase "PROTECT THE LAW" in all caps. Automated or generic copy-paste applications will be instantly rejected.

Frontend: React Native (Expo SDK 54), TypeScript Backend: Firebase — Firestore, Cloud Functions (Node, v1), Firebase Auth, Firebase Storage Architecture: Multi-tenant data model (multiple client organizations sharing one Firestore database, isolated by security rules) Auth: Email/password via Firebase Auth, role-based access (general contractor / subcontractor roles) Firebase / React Native SaaS (Contract, with potential for ongoing work)

We're seeking an experienced developer or agency to create a premium, modern website for a subscription-based platform. The project involves integrating AI technologies with Next.js to enhance user experience. The ideal candidate will have a strong background in web development and a keen eye for design.

Expectations include setting up development, staging and production environments in AWS, creating and managing the CI/CD pipeline and support for front end development and integration with the API.

We are looking to do a new build of our patch bay label designer tool. Customers are currently able to pick their model of patch bay, add text labels, colorize, and group. They can then checkout and it creates print ready artwork for our team to produce. The UI is a bit clunky and there are some features we want to add such as an admin tool to add and edit labels. You can see the current tool here: https://create.traceaudio.com/