We are looking for a commission-focused B2B sales contractor to help us sell DataDelivery by National Drone Services to independent drone service providers. Our target customers are drone service providers who serve construction-related clients, including general contractors, developers, roofing contractors, civil contractors, paving/concrete contractors, infrastructure projects, property managers, and owners’ reps. DataDelivery helps these drone service providers package their drone projects into professional client portals instead of sending messy Google Drive, Dropbox, or file download links. The platform supports hosted project delivery, images, videos, orthomosaics, point clouds/models, reports, share links, and downloadable deliverables. The immediate goal is to find, contact, demo, and help close construction-focused drone service providers into our normal DataDelivery subscription plans. This is a lean startup sales pilot. We have a limited budget, so the role is designed around a small base plus meaningful performance bonuses. What you will do: * Research and build a list of qualified drone service providers serving construction, mapping, inspection, roofing, civil, infrastructure, property, or progress-documentation clients * Find decision-makers and contact information * Send personalized outreach through phone, email, LinkedIn, contact forms, and other appropriate channels * Follow up with prospects * Run product demos after training * Track all leads, outreach, responses, demos, objections, and outcomes * Help refine messaging based on prospect feedback * Close qualified prospects into paid DataDelivery accounts Target customer: Independent drone service providers who need a better way to deliver construction progress photos, maps, orthomosaics, point clouds, reports, and other project files to their clients. This is not a consumer product. This is niche B2B software for drone service providers. Ideal experience: * B2B outbound sales, SDR, appointment-setting, or closing experience * Comfortable selling SaaS, software, business services, or technical services * Strong written and spoken English * Able to run clear, professional demos * Organized and reliable with follow-up * Comfortable working with a founder in an early-stage startup environment * Bonus if you have experience with drones, construction, mapping, surveying, roofing, real estate, field services, or small business owners Compensation structure: * Small monthly base retainer * Bonus per qualified completed demo * Commission per paid DataDelivery subscriber * Additional retention bonus when customers remain active Proposed compensation: * $200/month base retainer * $20 per qualified completed demo * $15 commission for Starter signup + $10 retention bonus after 60 days * $50 commission for Basic signup + $25 retention bonus after 60 days * $125 commission for Premium signup + $75 retention bonus after 60 days * $250 commission for Enterprise signup + $150 retention bonus after 60 days Commissions are paid only after the customer completes their first paid subscription payment. Retention bonuses are paid only if the customer remains active for 60 days. A qualified demo means the prospect: * Is a commercial drone service provider * Serves construction, mapping, inspection, roofing, civil, infrastructure, property, or similar clients * Has a real need for client delivery, hosted files, maps, reports, or recurring project documentation * Attends a real product demo * Is not a hobbyist, real-estate-only photographer, or unrelated lead We are looking to start with a short paid trial before expanding the engagement. Initial trial milestone: * Research 100 qualified construction-focused drone service provider leads * Send personalized outreach to an agreed number of prospects * Track all activity in a shared sheet or CRM * Book and/or run qualified demos * Provide feedback on prospect objections, messaging, and sales opportunities Please include in your proposal: 1. Your B2B sales/outbound experience 2. Any experience selling SaaS, technical services, construction-related services, or niche B2B products 3. How you would find construction-focused drone service providers 4. A short sample cold email you would send to a drone service provider 5. Your comfort level running demos after training 6. Your preferred compensation structure 7. How many qualified prospects you believe you can contact per week without spamming We are not looking for someone to blast thousands of generic emails. We need someone who can research the right prospects, communicate professionally, run demos, follow up, and help close real paying customers.

Senior Mobile SaaS / Unity Entitlements Engineer for B2B Licensing Platform Project Overview: Simcoach Games develops behavioral health and educational games used by clinics, schools, clinicians, and families. We are looking for a senior technical resource to help us design and build lightweight access, licensing, and an entitlement layer for our Unity-based mobile games. Our current games are distributed through the Apple App Store and Google Play. We need to evolve from separate consumer and enterprise app versions toward a cleaner model where games can be downloaded easily, while access is controlled through parent purchases, clinic/school licenses, organization activation codes, or other entitlement rules. This is not a game development project. We are looking for someone with experience building mobile SaaS infrastructure, app-store purchase flows, backend entitlement systems, and simple admin tools. Scope of Work: The initial engagement will focus on one representative game and should produce a reusable pattern that can later be applied across our game portfolio. The expected scope includes: Recommend architecture for B2C and B2B access control across iOS and Android Design an entitlement model for organizations, users/devices, games, licenses, activation codes, expiration dates, and access rules Implement or integrate app-store purchase handling for parent/consumer unlocks Implement a clinic/school activation flow, such as organization codes or device activation Build a lightweight backend entitlement service Build a simple internal admin portal for Simcoach staff to create organizations, issue/revoke access, manage license status, and view activations Create a reusable Unity integration package or pattern that our internal developers can apply to other games Document the architecture and implementation clearly for future development Architecture must be compatible with future HIPAA compliance (encrypted data at rest and in transit, audit logging, BAA-ready cloud hosting). We will engage a HIPAA attorney separately, but the infrastructure should not create compliance debt. Advisory (Ongoing): Guide our team on App Store consolidation: merging duplicate listings, applying for Apple Unlisted App Distribution, configuring Apple Business/School Manager volume purchasing, and Google Play enterprise distribution. Recommend architecture for future integrations with ABA practice management platforms (CentralReach, Motivity, RethinkBH) via REST API/SSO. Ideal Experience: Strong mobile SaaS architecture experience Apple StoreKit and Google Play Billing experience, or experience with RevenueCat or similar tools Unity/C# integration experience Backend/API development experience using Firebase, Supabase, AWS, or similar platforms Experience with authentication, entitlements, activation codes, license management, and admin portals Familiarity with privacy-sensitive healthcare, behavioral health, or education products Ability to design pragmatic solutions for a small startup with limited engineering and support resources Helpful but Not Required: Experience with healthcare, digital therapeutics, behavioral health, edtech, or serious games Familiarity with HIPAA/FERPA-aware product design Experience with shared-device or clinic/school deployment models Experience supporting both direct-to-consumer and enterprise customers from the same mobile app What Success Looks Like: A successful engagement will give Simcoach a practical, scalable, and maintainable access model that reduces app-store confusion, avoids manual account administration, supports B2B clinic and school sales, and preserves a viable path for parent/consumer purchases. We are looking for a senior, pragmatic resource who can help us make the right architectural decisions, implement an MVP, and leave our internal team with a reusable foundation.

🔐 Cybersecurity Sales Representative – Commission-Based Job Type: Contract | Commission-Only Location: US-Based Freelancers Only About Us We are a boutique cybersecurity consulting firm delivering enterprise-grade managed security services, vCISO consulting, penetration testing, compliance advisory (SOC 2, ISO 27001, FedRAMP, HIPAA, NIST CSF), and 24/7 SOC operations. Led by a 25-year cybersecurity veteran and CCISO, we serve clients across finance, healthcare, government, and technology sectors in the US and internationally. The Opportunity We are looking for a driven, self-motivated Cybersecurity Sales Representative to help us grow our client base. This is a pure commission-based role — your earning potential is directly tied to your results. If you have an existing network in IT, security, or enterprise decision-maker circles, this is a high-value opportunity. What You'll Do Identify and generate qualified leads (SMBs, mid-market, and enterprise) Prospect and outreach to potential clients via LinkedIn, email, calls, and your personal network Present and position our service portfolio to prospects Schedule discovery calls with our technical leadership team Manage your pipeline and report progress weekly Help craft and send tailored proposals to potential clients Services You'll Be Selling Managed Cybersecurity & SOC (24/7) Virtual CISO (vCISO) Services Penetration Testing (Web, Mobile, Infrastructure) Compliance Consulting (SOC 2, ISO 27001, FedRAMP, HIPAA, NIST CSF) Threat Detection & Response (XDR) Cloud & Endpoint Security Third-Party Risk Management (TPRM) Cybersecurity Project Management What We're Looking For Proven B2B sales experience (cybersecurity, IT services, or SaaS preferred) Existing network of IT/security decision-makers (CISOs, CTOs, IT Directors) is a major plus Strong communication and proposal writing skills Self-starter who thrives without micromanagement Familiarity with cybersecurity concepts (you don't need to be technical, but you must speak the language) US-based only Compensation 💰 Commission-only — competitive percentage on closed deals Deal sizes typically range from $5,000 to $100,000+ Recurring revenue opportunities on managed services contracts Commission structure discussed during interview How to Apply Please submit a proposal that includes: Your relevant sales experience (B2B, tech/cybersecurity preferred) A brief description of your current network or lead generation approach Notable deals or clients you've closed Why you're a great fit for a commission-only role We do not respond to generic proposals. Tailored submissions only.

DESCRIPTION; I'm building a data infrastructure product for ontology-driven AI context: object types, properties, and relationships materialized ahead of query time, so AI systems retrieve connected context fast instead of rebuilding it from raw sources on every request. I need experienced eyes on the ingestion foundation before anything gets built on top of it. The deliverables are fixed (below); hours are flexible — propose what you think the work honestly takes. Rate: my budget is $50–75/hr. That's a hard ceiling — proposals above that range can't be afforded and won't be considered, regardless of quality __________________________________________________________________________ WHO SHOULD APPLY A data engineer / data infrastructure engineer who understands what an ontology and a knowledge graph are and why they matter for AI systems — connected entities and relationships as first-class context, not just tables. You don't need graph database experience; you need to get why pre-materialized, relationship-aware data beats rebuilding context from raw sources on every query. If that framing clicks for you, you're the right kind of applicant. __________________________________________________________________________ THE PRODUCT, HIGH LEVEL: The platform deploys on a client's own infrastructure — we never see their data. Clients connect their data sources, define an ontology (object types, properties, relationships), and the platform materializes it across tiered storage. Later phases add a binary serve layer, SSD/RAM caching, and GPU-parallel query execution so AI systems and data applications retrieve connected context at very low latency. Target customers: companies running AI on complex connected data (security operations, healthcare, financial services) where privacy demands private deployment and speed matters. Storage note: the current prototype uses Iceberg on GCS for development convenience, but the architecture is intentionally built for any S3-compatible storage (on-prem S3, private cloud VPC, MinIO, etc.). Portability is a design requirement, not an afterthought — the platform must never be tied to a single cloud provider. __________________________________________________________________________ WHAT EXISTS TODAY: A working Python prototype: FastAPI, PyIceberg, PyArrow, Postgres, Supabase (metadata + sync ledger), GCS as the Iceberg warehouse. Architecture and design docs are provided for orientation. The cold path is functional and tested: a 31-test production suite ran against live infrastructure at 1M–5M row scale — core correctness, concurrency, failure injection (kill mid-sync, storage outages, lease expiry), idempotency/replay, rollback, a 50-sync soak, and audit checks. All passing, with a written sign-off document you'll receive. That's exactly why I'm hiring you: tests confirm behavior I anticipated. You're here for what I didn't anticipate — structural weaknesses, hidden risks, and edge cases that a test suite written by the same mind that wrote the pipeline can't catch. I'm strong on product and systems design, not low-level data engineering. The codebase is AI-assisted, and I want a professional to find what that typically accumulates. This is a prototype built from the ground up — no live client today. The goal: ensure the ingestion foundation is genuinely solid (data coming in from source correctly, at scale, repeatedly) so a scoped MVP pilot and beta release won't break under real usage. You are validating the foundation before anything gets built on top. __________________________________________________________________________ YOUR SCOPE — THE COLD PATH, END TO END Data source → validation → identity merge → materialized ontology in Iceberg on S3-compatible storage. The data connectors are in scope — they ARE Milestone 1. The platform supports exactly three ways data comes in, and your job includes confirming each one is genuinely production-grade, not just demo-grade: Postgres — full refresh and incremental watermark sync S3-compatible object storage (CSV) — currently GCS via S3 interop, but must work against any S3-compatible store (on-prem, MinIO, private VPC) Manual CSV upload — primarily for testing/onboarding For each connector, production-grade means: real error handling (bad credentials, unreachable source, permission failures, malformed/garbage data, schema drift), clear failure messages that tell a user what broke, no silent partial ingests, and sane retry/recovery behavior. If a connector swallows errors, loses rows quietly, or fails confusingly — that's exactly the finding I'm paying for. No other connectors are planned for this milestone. Three connectors that work correctly under stress beats ten that mostly work. Focus areas across the pipeline: Connectors — production-readiness and error handling as described above Identity & matching — entities staying consistent across syncs (PK merge, fingerprint mode, composite keys) Sync semantics — full refresh vs incremental watermark sync, replay idempotency, delete behavior Relationships — FK→PK edge materialization, rebuild triggers, orphan handling, stable node identity Versioning & audit — Iceberg snapshots, rollback, schema change lineage, sync ledger completeness Reliability — failure modes, partial writes, lock/lease behavior, silent wrong-data risks Code structure — dead code, duplication, coupling, fragility; source-specific logic must stay contained in each connector and never leak into the shared pipeline Explicitly out of scope: GPU execution, query kernels, binary serve formats, caching layers, query-time serving, and any new connector types — all future phases. Your scope ends at correct, versioned, audited data in Iceberg. __________________________________________________________________________ DELIVERABLES (in priority order) Prioritized written assessment — what's pilot-ready as-is, what must be fixed before a real pilot customer (with specific recommendations), and what the existing test suite missed (edge cases, risks, gaps). Active code changes — implement fixes for the highest-priority issues you find, directly in the repo. You'll have full repo access. I'm open to architecture changes and refinements as long as they're clearly explained with reasoning. A change log that teaches — for every change: what you changed, why it mattered, what it fixes or prevents, and what to watch for going forward. This isn't paperwork — I'm making a local engineering hire for the next milestone, and your write-ups become the onboarding record. Everyone who touches this codebase after you should learn from what you found. Fixes go deepest-risk-first. What you get from me: repo access, architecture/design docs, the test suite + sign-off report, and async availability for questions. __________________________________________________________________________ ***REQUIRED EXPERIENCE: 1)Production Python data pipelines 2)Apache Iceberg, Delta Lake, or Hudi (or strong Parquet/data-lake work) 3)Postgres 4)Merge/upsert, idempotency, watermark/CDC patterns Building or hardening data connectors that real users depend on************* __________________________________________________________________________ WHERE THIS CAN GO: This starts as a fixed-scope review. Separately, I plan to make my first part-time/full-time engineering hire locally (Dallas) to build Milestone 2 and beyond — SSD caching, serve layers, containerization, and microservices as the platform scales. For the right freelancer, there's opportunity to stay engaged on recurring scoped work — reviewing the foundation as it evolves and working in conjunction with that future hire. Not required, not promised — but the door is open if the work is strong. __________________________________________________________________________ *********HOW TO APPLY — READ CAREFULLY***** Answer this one question in your proposal, briefly and in your own words: "You're building a pipeline that ingests from Postgres and S3-compatible storage and materializes a connected ontology (entities + relationships) into Iceberg. How do you design the sync process to be reliable and idempotent — especially around watermarking, commits, and failure handling between steps?" Include your proposed hour estimate for the deliverables above. Get creative — attachments and notes welcome. Note on AI-generated proposals: I use AI heavily myself — but if your proposal or screening answer is clearly AI-generated boilerplate, you will be automatically rejected without consideration. I'm hiring your judgment and experience, not your ability to paste a prompt. Short, direct, human answers. __________________________________________________________________________ A NOTE ON TECHNOLOGY BOUNDARIES: ***QUICK EXAMPLE*** FastAPI and Iceberg are what the platform uses today, not permanent decisions. As the product scales, we may want to run FastAPI alongside a second framework, replace it entirely, or eventually move away from Iceberg toward a custom storage format optimized for the GPU serve layer. Those should be engineering decisions made on merit, not decisions we're forced into because the current code makes swapping painful. What I need confirmed: is the codebase modular enough that a change like that stays contained? Core business logic (validate, merge, materialize, version) should never be tangled directly with infrastructure. API routes should be thin entry points that hand off to service logic, not where business logic lives. Iceberg writes should be isolated behind a single abstraction. If those boundaries are clean, replacing or extending a technology layer is a focused engineering effort. If they're not, it touches everything and becomes a mess under deadline pressure with a full team. Flag anywhere that boundary is broken. That's a priority finding. __________________________________________________________________________ FINAL REMARKS: NDA & IP protections This engagement requires signing an NDA and IP assignments agreement before work begins; standard protections given you'll have full repo access to a pre-launch product. Documents are provided on day one; nothing unusual in them. If that's a dealbreaker, please don't apply.

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.

About Sybal Corp: Sybal Corp is building the world's first governance-focused AI infrastructure platform through its Proof of Governance® (PoG™) platform. We serve defense, government, and highly regulated commercial organizations that require governance intelligence, oversight, and audit readiness. Position Overview: The Engineering Operations & Technical Program Management serves as the bridge between executive leadership and the engineering organization. This role is responsible for engineering accountability, project execution, technical oversight, roadmap delivery, and alignment between business objectives and technical implementation. This position oversees engineering execution, validates technical work, manages project delivery, and ensures developers, DevOps engineers, QA engineers, and AI/ML engineers remain accountable for timelines, quality, and outcomes. Primary Responsibilities: • Lead day-to-day engineering operations and project execution. • Manage engineering schedules, priorities, and sprint planning. • Review engineering deliverables for completeness and quality. • Evaluate technical designs and implementation approaches. • Translate business requirements into technical requirements. • Serve as the primary liaison between founders and engineering teams. • Hold engineers and contractors accountable for commitments and deadlines. • Manage offshore and domestic technical resources. • Coordinate work across Software Engineering, DevOps, QA, and AI/ML teams. • Track project risks, dependencies, and milestones. • Establish engineering KPIs and reporting processes. • Support technical due diligence discussions with investors and partners. Required Qualifications: • 8+ years of software engineering experience. • 3+ years leading engineering teams or technical projects. • Strong understanding of AWS, cloud architecture, APIs, DevOps, and modern software development practices. • Experience managing Agile/Scrum development teams. • Experience with Jira, GitHub, Azure DevOps, or similar tools. • Ability to evaluate code quality, technical designs, and engineering estimates. • Experience managing remote and distributed engineering teams. • Excellent communication skills. Preferred Qualifications • Startup leadership experience. • Experience with AI, AI Dev Automation (Claude, Open AI), Machine Learning, and NLP platforms. • Experience supporting government, defense, or regulated industries. • Experience with FedRAMP, CMMC, SOC 2, or NIST environments. • PMP, Scrum Master, or Agile certifications. What Success Looks Like: • Increased engineering accountability. • Improved visibility into project status and delivery timelines. • Better communication between leadership and engineering teams. • Improved release quality and predictability. • Reduced technical debt and project execution risk. • Scalable engineering processes supporting company growth.

We are looking for a strong software engineer who can build practical automation systems using AI, APIs, and modern development tools. This role is for someone who can take messy business workflows, understand the goal, and build working systems that save time, reduce manual work, and improve execution. You should be comfortable building automations, integrating tools, working with APIs, writing clean code, and using AI tools like OpenAI, Claude, or similar models to create useful business applications. What You’ll Work On You will help build and improve systems such as: AI-powered research and data extraction workflows CRM and sales process automations Email, spreadsheet, and database automations Internal tools and dashboards API integrations between business software Web scraping and data enrichment workflows when appropriate AI agents or assistants that help with repetitive business tasks Automation around deal screening, reporting, lead research, and document creation Ideal Candidate We are looking for someone who is practical, fast, and can figure things out without needing step-by-step instructions. You should have experience with: Python and/or JavaScript APIs and webhooks OpenAI, Claude, or other LLM APIs Automation tools like Zapier, Make, n8n, Airtable, Google Sheets, HubSpot, Salesforce, or similar Databases such as PostgreSQL, Supabase, Firebase, or similar Basic front-end or internal tool development Web scraping, data cleaning, and structured data workflows GitHub and clean documentation What Matters Most We do not need someone who only talks about AI. We need someone who can actually build. The right person should be able to: Understand a business process quickly Recommend the simplest technical solution Build fast prototypes Turn prototypes into reliable workflows Communicate clearly Document what was built Improve systems over time Nice to Have Experience with any of the following is a plus: Private equity, M&A, finance, or investment workflows Deal sourcing or lead generation systems CRM automation Data enrichment tools AI research agents Browser automation Cloudflare, AWS, Google Cloud, or similar infrastructure Engagement This will start as a part-time project-based role, with the potential to become ongoing if the work is strong. Estimated workload: 5 to 15 hours per week to start. To Apply Please include: Examples of automations or AI tools you have built The tech stack you usually work with A brief explanation of how you would approach automating a messy manual workflow Your hourly rate Your availability Please do not send a generic application. If your response looks copied and pasted, it will be ignored.

We need a senior architect to design and build a multi-model routing control plane, then lead a small senior team through the build. The control plane sits in front of a family of AI systems and decides, per request (text, image, video), the optimal path across cost, quality, latency, business value, and sovereignty (data residency, rights, and cultural fit): cache and reuse, a small or on-device model, an open-weight, fine-tuned, or sovereign model, or a higher-cost frontier fallback. It routes across compute too: CPU, GPU, inference accelerators, on-device, and edge. Core KPIs: the share of eligible workload kept off frontier accelerators and the resulting cost reduction on a representative workload, plus sovereignty compliance, with no quality regression. This is not a chatbot and not a wrapper over hosted APIs. You own the architecture, define the routing logic, and lead execution. You think in systems, not individual model calls. Context The router is one component of a larger AI platform. It must be model-agnostic: open-weight, fine-tuned, and proprietary models swap in and out behind a stable interface without rearchitecting. A separate team owns the models you route to. The engagement is a 60 to 90 day POC with a working router demo (text-first, with a defined path to image and video), followed by technical leadership through the build. What you'll own Control plane: intake and normalization, classification, routing taxonomy, model-selection logic, fallback hierarchy, cache and reuse rules, telemetry, and the eval feedback loop. Routing that is learned and calibrated, not just static rules: predict per-query difficulty and expected quality, and escalate on confidence thresholds. Comfort with cascades and speculative decoding is expected. Routing across cost, quality, latency, and policy. In constrained environments some requests must stay local regardless of cost. Model-agnostic interface: clean, stable contracts so models and execution paths swap without rework, and the separate model team can work independently of the routing layer. Cost optimization across compute: exact and semantic cache, prefix/KV cache reuse, output reuse, batching, small-model routing, CPU offload, and on-device/edge execution, with a clear fallback hierarchy. The goal is to move most eligible workload off frontier accelerators without degrading output. Generative caching and reuse: caching text is easy; image and video are not, since the same prompt should produce variation rather than an identical result. We need credible reuse at the asset or component level, not just for text. Eval loop: scores output quality by domain and flags weakness so the training team can target fixes instead of retraining broadly. Track quality vs intent, failure modes, cost per route, latency per route, cache hit rate, fallback rate, and regeneration rate. Execution and leadership: architecture blueprint, POC scope, milestones, infra assumptions, and risks leadership can review, plus hands-on architecture review and task breakdown. You'll lead a small senior team, and one of your first deliverables is recommending its exact composition (see screening questions). Ideal background Led or architected production AI infrastructure across several of: multi-model orchestration and LLM routing, multimodal, model serving, inference cost and GPU reduction, CPU and on-device inference, open-source and fine-tuned deployment, cascades and speculative decoding, semantic and prefix caching, eval pipelines, and AI observability. Deployed in at least one constrained environment: on-prem, self-hosted, air-gapped, or data-residency-restricted. You know what breaks when you can't lean on a single cloud. Can lead: set architecture, break down work, review the team's output, and keep the build on track. Tools matter less than the ability to architect the system correctly and lead execution. Not a fit: basic chatbot workflows, hosted APIs only, or prompt engineering alone. Deliverables Control plane blueprint, routing taxonomy, POC plan with milestones and success criteria, and an eval/feedback framework, with a working router demo as the 60 to 90 day target, then technical leadership of a small team through the build. Screening questions The most relevant AI routing, model-serving, or inference infrastructure system you personally designed or built: what was routed, which models or execution paths, and what role did you own? How would you design a router that chooses between cache/reuse, a smaller or local model, an open-weight or fine-tuned model, or a frontier fallback, across CPU and GPU? Where do learned routing, cascades, or speculative decoding fit? For generative image or video requests, how would you approach caching or reuse when the same prompt should still allow variation? Be specific. What metrics and eval loop would you use to prove the router cuts cost without degrading quality, and to help a separate training team find weaknesses? Beyond yourself, what team would you staff to hit these deliverables in 8 weeks? Give the roles, seniority, and headcount, how you'd split the work, and flag any deliverable that 8 weeks and a team of roughly 4 engineers can't realistically cover. To apply Answer the five questions, summarize your most relevant routing or inference-infrastructure work (repos, writeups, talks, or architecture you can describe), and give your high-level approach to a control plane that routes across cost, quality, and sovereignty while preserving quality. Note your availability, your rate, whether you've led a small engineering team before, and the team you'd staff to hit the deliverables in 8 weeks.

Forum Intelligence: Project Brief & Initial Rollout 1. Executive Summary & Objective Forum Intelligence is a beginning as a localized data retrieval, processing, and archiving system designed to scrape public municipal records and state legislative data for public oversight. The immediate objective is to build a functional, highly resilient prototype focused on the Tri-Cities region (Burbank, Glendale, and Pasadena, California). The system will autonomously ingest messy, unstructured municipal data (City Council meeting minutes, agendas, public notices, and legislative PDF text, recorded mp4), clean it, and make it fully searchable and queryable via a localized AI agentic framework. 2. Phase 1 Scope: The Tri-Cities Rollout Th engineer will be responsible for building two primary pillars: A. Resilient Scraper Bots • Target Ingestion: Monitor and pull data from Burbank, Glendale, and Pasadena municipal portals and California legislative feeds. • Data Types: Brittle HTML sites, heavily nested tables, public notices, legislative drafts, and massive unstructured PDF archives. • Requirements: The scraping architecture must be exceptionally robust, utilizing intelligent error handling, retry semantics, and pagination tracking to handle frequent municipal website layout changes without breaking the pipeline. B. Ingestion & Vector Pipeline • Parsing: Extracting clean text from poorly formatted documents and scanned PDFs. • Local RAG (Retrieval-Augmented Generation): Chunking and embedding the data locally into a vector database (e.g., pgvector, Chroma, or Milvus) to enable semantically accurate entity linking and contextual search. 3. Targeted Hardware Stack To ensure maximum data security, strict public oversight integrity, and predictable operational costs, Forum Intelligence is skipping commercial cloud APIs in favor of an on-premise, localized NVIDIA enterprise deployment. The production roadmap aligns precisely with the new computing patterns detailed in NVIDIA’s latest hardware roadmap: • Inference & Token Generation: Running local open-weight frontier models (e.g., Neotron 3 Ultra or Claude/Llama equivalents) optimized for reasoning and long-context tool use. • Compute & Orchestration: The backend infrastructure is architected around NVIDIA’s dedicated agentic architecture, utilizing high-instructions-per-clock (IPC) Vera CPUs paired with Vera Rubin GPUs. • Memory & Storage Processing: Utilizing NVIDIA’s unified memory fabric and data processing units (DPUs) for ultra-low latency context management, KV caching, and fast vector database retrieval. 4. Immediate Milestones for the Engineer 1. Architecture Design: Map out the database schema and local inference ingestion loop. 2. Tri-Cities Scraper Deployment: Write and deploy the initial automated bots for Burbank, Glendale, and Pasadena. 3. Local MVP Pipeline: Demonstrate a local RAG pipeline where a user can query the Tri-Cities scraped records and receive grounded answers with exact source attributions. The above was AI generated from months long conversations with Gemini. The goal is to prove the concept then roll out to LA County, state of CA, and then the country.

We are a growing technology consulting firm seeking a skilled Microsoft Power Platform Solutions Architect and Developer to deliver client-facing solutions that drive real business results. The right candidate has a portfolio of shipped applications they are proud of, a consulting mindset, and the ability to work directly with clients to turn business requirements into working software. If you have spent your career as a back-office developer waiting for tickets, this is not the role for you. If you have built things that made a measurable difference for real clients and can prove it, we want to talk. WHAT YOU WILL BE DOING • Design and build Power Platform solutions - Canvas Apps, Model-Driven Apps, Power Automate workflows, Power BI dashboards, and Dataverse implementations • Work directly with clients to gather requirements, clarify scope, and translate business needs into a clear technical solution without requiring heavy oversight. • Own your projects end-to-end: from the first client conversation through design, development, testing, deployment, and post-launch support. • Build SPFx components and SharePoint Online solutions as part of broader Microsoft 365 engagements. • Integrate Power Platform solutions with external systems and APIs, including SQL Server, Dataverse, SharePoint, and third-party platforms. • Deliver on time and communicate proactively • Produce clean technical documentation that supports handoff, training, and future enhancements. • Contribute to solution estimates and help scope new client engagements accurately. REQUIRED QUALIFICATIONS • 5+ years of hands-on Power Platform development: Canvas Apps, Model-Driven Apps, Power Automate, Power BI, and Dataverse. • Demonstrated consulting or contract delivery experience, you have worked across multiple clients, not just one employer. • A portfolio of shipped applications you can speak to: what the problem was, how you solved it, and what the outcome was for the client. • Strong SharePoint Online experience, including SPFx component development and Microsoft 365 integrations. • Proficiency in JavaScript, TypeScript, REST APIs, HTML, and CSS for custom UI and integration work. • Ability to work independently, manage your own time, and deliver without daily supervision. • Strong communication skills, you can run a client meeting, explain a technical decision in plain language, and push back professionally when scope creeps. • U.S. Citizenship required. PREFERRED QUALIFICATIONS • Experience leading client engagements as the primary architect and point of contact. • Azure fundamentals - Entra ID, App Services, Azure DevOps, and basic cloud infrastructure knowledge. • Copilot Studio or Azure OpenAI integration experience - AI-assisted app development is increasingly part of what clients expect. • Experience with Agile or sprint-based delivery in a consulting context. • Version control discipline - GitHub or Azure Repos. Deployments should be repeatable, not manual. • Federal government or regulated industry client experience is a plus, but not required.