***No agency, please*** The contractor must be located within the United States. The expected volume of hours will be high, so please provide your most competitive rate. Requirements: • Experience in multiple Power Platform and/or D365 projects as a technical consultant. • Experience with Microsoft Dynamics 365 and/or Power Platform in the following areas: o Minimum 5-8+ years consulting/development experience in Microsoft technologies. o Experience in Data Modeling and mapping. o PowerApps, Azure Portal/Services, Dataverse. o Model driven forms, views, workflows and reports development. o Programming languages o Understanding of Synchronous and Asynchronous integration patterns o Role-based security design and customization o Development and change tracking using Visual Studio, Azure DevOps/GIT o Provide Dynamics 365 development effort estimates. o Create technical design documents o Ensure that code is testable and is tested. o Execute unit testing for the new functionality developed. o Ability to organize, prioritize, estimate and deliver tasks meeting deadlines o Confidence and willingness to expand technical prowess o Ability to adapt to constantly evolving technologies o Ability to meet deadlines and multi-task effectively o Experience working with a multicultural and/or multilingual team across several time zones o Power BI report development/data modeling

Candor Group Is adding a freelancer role to service our Fortune 500 accounts. The role is part time, “on demand” in that we plan 1-2 weeks ahead on work and the work may have 0,5,10 hours for those weeks. Availability during EST hours is required for some meetings, and support while some work can be done “off hours”. The role is not just technical but also business facing. ________________________________________ We are seeking a professional with experience in SharePoint Online, Power Apps, and Power Automate, combined with strong business analysis skills. This role will design, build, and support business solutions while working closely with stakeholders to translate requirements into scalable, user-friendly applications. ________________________________________ Key Responsibilities • Design, develop, and maintain solutions using SharePoint Online, Power Apps, and Power Automate • Gather, analyze, and document business requirements, workflows, and use cases • Translate business needs into technical designs and functional solutions • Build and customize SharePoint sites, lists, libraries, and permissions • Develop Power Apps applications • Create and maintain Power Automate workflows for process automation • Conduct testing, troubleshooting, and optimization of solutions • Collaborate with stakeholders, end users, and IT teams • Provide user training, documentation, and ongoing support ________________________________________ Required Skills & Qualifications • 3–5 years of experience with: o SharePoint Online (site design, lists, libraries, permissions) o Power Apps o Power Automate (flows, approvals, integrations) • Strong understanding of business process analysis and requirements gathering • Experience writing functional and technical documentation • Familiarity with: o Microsoft 365 ecosystem o Data sources (SharePoint, Excel, Dataverse) • Strong communication and stakeholder engagement skills ________________________________________ Desired / Preferred Skills • Experience with: o Power BI for reporting and dashboards(nice to have, not required) o SharePoint Framework (SPFx) or light customization o Dataverse and model-driven apps • Knowledge of: o Agile / Scrum methodologies o Governance and best practices for the technologies o SharePoint security and basic site administration. • Certifications (nice to have): o PL-100, PL-200, or related Microsoft certifications ________________________________________ Soft Skills • Strong analytical and problem-solving ability • Ability to bridge business and technical teams • Self-starter with attention to detail • Effective communicator and collaborator

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.

Seeking proven and Node.js development experience to build a production-ready REST API backend that will authenticate to Microsoft Power BI via Azure AD service principal, generate time-limited embed tokens for secure dashboard rendering, and retrieve real-time operational metrics from Power BI datasets using DAX queries. The system will integrate with the Anthropic Claude API using healthcare-specific system prompts, persist all analyses and audit logs in PostgreSQL with immutable compliance tracking, and deploy to Azure App Service with robust error handling, logging, and monitoring. The engagement includes full integration testing and a comprehensive security review prior to launch. ⚠️ All data in the Lovable frontend is currently generated by React components using hardcoded mock objects. There is no backend API, no database persistence, and no real data sources. This is the scope of work for your backend engineer. The primary objective for the data engineer is to deliver a secure, multi-tenant backend, replace all mocked page data with live API responses, embed Power BI dashboards with row-level security, and stand up a Claude-driven analytical agent that operates over a governed semantic model. SUCCESS CRITERIA 1. All 3 endpoints deployed and tested 2. Frontend Dashboard.tsx renders real Power BI embed 3. Frontend AIInsights.tsx displays Claude analysis 4. ActionPlanContext replaced with server-backed CRUD 5. PostgreSQL audit log captures all API calls 6. Security review passed 7. Load test: 50 concurrent users, less than 300ms p95 8. Power BI RLS verified between test orgs 9. Documentation + runbooks delivered 10. Zero unhandled errors in production 11. Launch in mid-June 2026

Summary As Exponentials is the first startup in the world to solve the AI backlash, we feel that it make sense and is realistic for us to choose our own investors rather than them choosing us. Here is the Exponentials investor demo (in progress) https://pull-discovery-core.base44.app/ Exponentials is seeking a senior virtual assistant or project manager. We find that our best hires have a natural culture fit. Are you an individual who sees solutions over problems? If so, how does that build a foundation for your work? How proactive are you, and what does that mean? Do you believe that world-class teams win in business and in life? What does it mean to be a part of and help lead a world-class team? Whare are your personal qualities and beliefs that contribute to this? Are you a fit to Exponentials as detailed below. What do you understand about Exponentials from the below that others miss? What is Exponentials trying to do, and why are you clearly the best candidate to do it? Exponentials investment thesis: 1. Exponentials is solving the AI backlash via the co-evolution of AI and humans in the service of human needs, and thus moving from the current extraction model of AI to a collaborative model. For Exponentials, this is moving past discovery silos to create unified discovery across (initially, $25 trillion TAM) Ecommerce, healthcare, education and media. This is accomplished through the combination of Search, LLM's and World models 2 AI can't be (optimally) successful if too many of its (potential) customers are fearful of or dislike AI 3 AI is feared and disliked (in addition to loved), as customers are smart enough to realize that AI is employing an extraction model on humans rather than a collaborative model with humans in the service of human needs 4 Major tech CEO's telling the public that they are wrong to have negative views about AI is insulting one's customer 5 If the AI industry wants to get into a war with the public it will be a stalemate at best. AI has enough perceived benefits already and the AI companies are powerful enough that they can impose their will on the public to a certain degree, but 6 It is inevitable that the AI companies who actually give the customers what they want and what truly benefits them, by flipping from the push to the pull model, will have a sustainable competitive advantage, with both inevitability and defensibility. 7 Famously, the future is already here. It is just not evenly distributed. And famously, there is nothing more powerful than an idea whose time has come. 8 We are not selling technology. We are not selling a model of AI. We are selling an empowered path for humanity that is inevitable and defensible because the AI backlash is real and not sustainable long term. What the research says about Exponentials Book Excerpt How to Avoid the AI Backlash Leading to the AI Bubble Hartfield, Solis & Elridge In 2026, artificial intelligence stands at a strange crossroads. On paper, it is the most powerful general-purpose technology humanity has ever built. In practice, a growing share of the public now experiences AI as something done to them rather than for them — and that emotional turn is reshaping the technology's future as surely as any breakthrough in model architecture. When AI is built on top of architectures that treat humans as targets for extraction — of attention, data, or money — it inevitably triggers backlash, and that backlash in turn increases the odds of a violent AI bubble. When AI is built as infrastructure for discovery that co-evolves with humans in the service of our actual needs, we get a different trajectory: compounding value, durable trust, and a stable foundation for long-term innovation. Exponentials, for example, is building a different kind of infrastructure: a universal personal discovery engine that integrates large language models, adaptive search, and world models to help people navigate complex needs across commerce, health, education, and media. Instead of pushing content to you based on what is most profitable to show, such a system starts from your articulated intent, your evolving context, and your long-term goals. Pull discovery uses the same core components that power today's AI wave — but arranges them differently. It treats you as an integrated being whose health, work, learning, and media consumption are interconnected, rather than as a series of separate "users" in separate verticals to be monetized independently. An AI-driven discovery engine built on pull, not push, gives us a way to answer, credibly, the question that will increasingly be asked by citizens, workers, and regulators: "Who is this for?" If we build the missing layer of AI for human needs — a discovery infrastructure that co-evolves with us, across the whole pyramid of human need — AI becomes a tool that communities defend rather than attack, that regulators shape rather than suppress, that individuals choose rather than endure. Book Excerpt The Co-Evolution of Artificial Intelligence and Humans Kai Mercer & Lena Voss We are not passengers in the age of AI. We are in the earliest stages of a co-evolutionary relationship — one in which humans and artificial intelligence are changing each other in continuous feedback loops. The question is not whether this co-evolution will happen. It is already happening. The question is what kind of co-evolution we will choose. For two decades, the dominant model has been "push discovery" — systems that decide what you should see based on what maximizes platform profit or engagement, not what serves your needs. These systems are powered by sophisticated AI. But they are not designed to serve human flourishing. The AI gets smarter at manipulation. Humans adapt by becoming more skeptical, more weary, more prone to decision fatigue. This is co-evolution in the wrong direction. Exponentials demonstrates a fundamentally different architecture — one built around understanding and serving human intent. The platform uses large language models to understand queries in context (not just keywords, but intent, constraints, and values), world models that maintain continuously updated representations of options, and hybrid search across structured and unstructured data. Critically, the person evolves too: getting better at articulating needs, learning to trust well-matched recommendations, navigating abundance efficiently rather than being overwhelmed by it. Critically, Exponentials proves this model is economically viable. Operating on subscriptions rather than advertising means the platform succeeds when you find what you need efficiently — not when you're kept scrolling indefinitely. When economic incentives align with human wellbeing rather than against it, co-evolution can move in a fundamentally different direction. The co-evolutionary trajectory is not determined by technological capability. It is determined by design philosophy, business model, and the values embedded in the system's optimization function. Exponentials proves the second path is viable — and that aligned AI, genuinely designed to serve human flourishing, can work at scale.

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.

Role Overview You are the Executive AI Enablement Lead at AIVC, the person whose job is to make the executives at AIVC’s client businesses true power users of Claude, Cowork, and code- and agent-driven workflows. AIVC partners with operator businesses to drive AI-led EBITDA growth, and part of that work is bringing each company’s most senior leaders up the AI curve. You’re the person who personally designs and runs that path on every engagement: assessing where a given client executive is today; curating the right materials, videos, and course content; running 1:1 coaching; building executive playbooks; and acting as their daily operator-in-the-loop until the new workflows stick. The first concrete instance is already lined up, a named client managing partner has explicitly asked for the fastest path to becoming a power user of Claude, Cowork, and Claude Code / Skills. From there you scale: same treatment to additional client executives across the portfolio, then a documented set of executive-grade playbooks and patterns that compound across every future engagement. You are bias-toward-results – a win is the client executive’s calendar-week looking different, not a beautifully written rubric nobody uses. What You’ll Own (Outcomes) • Within 30 days of pairing with the first client managing partner, they have a working daily routine in Claude, Cowork, and Code/Skills that’s already replacing or improving how they handle at least three recurring tasks • Within the first quarter of the engagement, the client executive is a true power user — running multi-step workflows, custom Skills/Projects, and agent-assisted tasks without needing coaching scaffolding for the basics • A documented set of executive playbooks (research, writing, analysis, synthesis, workflow automation, agent-assisted tasks) that compound across every client engagement, not one-offs • A curated, current library of learning materials, videos, example workflows, and Claude-native patterns — including a clear point of view on which external courses, tutors, or expert resources are worth plugging in • Observable change in how client executive cohorts use AI: from reactive chat to repeatable, structured, outcome-oriented workflows • A foundation of training assets and patterns that scales beyond executive coaching into broader client teams in year two • A reputation among AIVC’s clients as the trusted go-to for “how do I do this better in Claude” — measured by inbound demand and engagement expansion What You’ll Do (Responsibilities) • In the first weeks: build the first client managing partner’s tailored upskilling plan — assess current usage, identify the highest-leverage workflows for their day-to-day, curate the right mix of materials / videos / course content, and recommend any tutor or expert-guided support to fold in • Provide 1:1 coaching for client executives — managing partners, founders, C-suite leaders — on Claude, Cowork, and code- and agent-based workflows • Design tailored training plans per executive that go beyond basic onboarding into advanced usage, with explicit progression from chat → workflows → agents • Curate the best external materials (videos, courses, blog posts, example projects) and rewrap them into client-ready, AIVC-flavored learning paths • Teach practical, high-leverage use cases live: research, writing, analysis, synthesis, workflow automation, and agent-assisted tasks • Help client executives move from general chat usage into repeatable workflows — Claude Projects, Skills, scheduled Cowork tasks, MCP integrations, custom agents • Serve as a real-time tutor and expert resource for client executives — over Slack, in meetings, on-site, and in async written feedback • Run office hours, workshops, and informal Q&A sessions inside client teams to keep adoption sticky between coaching sessions What We’re Looking For (Required) • Deep hands-on expertise with Claude across every surface (Claude.ai, Claude Projects, Claude Code, Claude Skills, Claude API) — and an active habit of pushing the edges of each • Strong working fluency with Claude Cowork specifically, including scheduled tasks, connected apps / MCPs, and the broader workflow surface • Strong capability with code-enabled AI workflows: you can write Python and/or TypeScript, build agents, configure MCP integrations, and ship a working internal automation end-to-end without needing an engineer • Demonstrated ability to teach non-technical but highly demanding users — you’ve made executives, founders, or senior operators meaningfully better at something complicated, not just trained engineers • Strong workflow design instinct — you can translate messy business questions into clean prompts, workflows, and systems • Polished, discreet, and effective in high-touch client executive settings — high EQ, low ego, comfortable representing AIVC inside senior client environments and around senior decision-makers • Strong bias toward practical results over theoretical AI knowledge — the metric is the client executive’s behavior change, not the elegance of the explanation • Excellent written and verbal communication; you can write a playbook a client executive will actually read and use • Comfort with significant travel to client sites and embedded, on-site engagement work • 5+ years of professional experience across some mix of: applied AI / ML, technical training and enablement, developer relations, solutions engineering, executive coaching, management consulting, or chief of staff / senior operator roles to executives Helpful If You Have (Preferred) • Prior experience coaching or supporting C-level executives, founders, or managing partners as a client-facing professional — executive coach, principal solutions engineer to executive customers, chief of staff to a CXO, or partner-level consultant • Background that combines technical depth with people skills — developer relations, solutions engineering, technical training, or learning & development at a frontier AI or developer-tools company • Direct experience building executive-facing training programs or curricula that demonstrably moved adoption inside other organizations • Hands-on familiarity with the Anthropic product surface specifically: Claude Projects, Claude Skills, Claude Code, MCP server development, Claude API • Track record of getting non-technical users to genuinely adopt a technical tool — i.e., users who chose to keep using it after the training ended • Background in management consulting, professional services, executive coaching, or learning & development — especially in environments where the customer was a senior external client • An active personal portfolio of AI work (workflows, automations, blog posts, talks, open-source contributions) you can point to • Comfort building light tooling (a Notion playbook system, a Claude Skills catalog, a small dashboard) without needing engineering support • Familiarity with AIVC’s model — operator business engagements, EBITDA-led measurement, and the broader compounding intelligence layer — or eagerness to come up the curve quickly

DO NOT SEND AN AI GENERATED PROPOSAL. READ THROUGH THIS POST AND GIVE US YOUR HUMAN RESPONSE. Location: Remote Team size: Small (you’ll know everyone’s name) Stack: Java 21 / Guice / Gradle backend + React 19 / TanStack / MUI frontend **To apply** 1. Give us a few sentences for why you're a fit for the description below. 2. Include a Github/Gitlab/Gitea link to a recent PR you’re proud of (any language) 3. 5–10 minute Loom of you using Claude Code on a real task. **About the role** QAction is a large-scale Java enterprise document, records, and workflow platform — multi-project Gradle build, ~15 modules, customer-specific deployments (USDA, Ditco, Ascension, Mayo). The backend is being modernized behind an OpenAPI v2 surface (oasv2); the frontend is being rebuilt off GWT onto React 19 + TanStack Router/Query/Start with MUI v7. We need a developer who’s equally comfortable extending a v2 endpoint in a Guice-wired Java service as they are wiring up a TanStack Query call behind a Lexical editor or a virtualized data table — and who treats Claude Code as a peer on the keyboard, not a novelty. You’ll work directly with the product lead. No layers, no JIRA theater. Ship, review, iterate. **What you’ll do** Own vertical slices end-to-end: OpenAPI spec → Manager/ManagerImpl + EndpointImpl in QAction Java → React 19 / TanStack Query UI → JUnit + Playwright coverage. Extend the QAction Java backend: Guice (constructor injection only), Hazelcast-aware code paths, customer-deployment-aware module wiring, JUnit under oasv2. Build Modern UI features in the React 19 stack: TanStack Router/Query/Start, MUI v7 + Emotion, React Hook Form + Zod, Lexical, dnd-kit, OIDC auth (oidc-client-ts), TypeScript with the wrapper-component discipline already in place (Button, Icon, LabeledObject, ScrollShadows, etc. — never raw MUI in features). Move features off GWT onto the React 19 stack one slice at a time, without breaking the legacy app. Pair with Claude Code daily — write prompts that ship code, review agent diffs critically, and improve our skills/agents library when the workflow has friction. Keep integration tests honest: real DB + Solr + Keycloak at the seam, not mocks. Tech direction you’ll be living in **Backend** Java 21, Gradle multi-project (build single modules — ./gradlew QAction:build — never clean build) Guice DI, constructor injection, Manager/ManagerImpl naming (we don’t use “Service”) OpenAPI-first v2 endpoints in oasv2, canonical error model, paginated response classes as standalone beans in oasv2.beans Hazelcast clustering, Solr search, Postgres/MSSQL, Keycloak/OIDC FileNet integration, document import/migration tooling, RMT/remote services **Frontend** React 19 + TypeScript, Vite 7, TanStack Router + Query + Start + Table MUI v7 + Emotion, MUI X Date Pickers + Tree View Lexical (rich text), @dnd-kit + Atlaskit pragmatic-drag-and-drop, react-virtualized, react-pdf React Hook Form + Zod, oidc-client-ts + react-oidc-context, notistack, pino File naming kebab-case, @/ path imports, theme-first styling, wrapper components over raw MUI Adjacent surfaces in scopes over time **What we’re looking for** 8+ years shipping production app code across backend and frontend. You’ve owned services and UIs, not just one or the other. Java fluency — Guice or Spring DI, REST/OpenAPI design, JUnit. Bonus if you’ve worked in a 1M+ LOC enterprise Java codebase with customer-specific module deployments and didn’t flinch. Modern React fluency — React 18/19, TypeScript, TanStack Query (or React Query), a real opinion about effect dependency graphs, comfort with virtualized tables and rich-text editors. OpenAPI-first thinking. Specs are the source of truth, not documentation written after the fact. Claude Code power user. You write prompts that delegate well, you know when to use a subagent vs. inline, you’ve built or extended skills/hooks/MCP integrations. You can show us a recent session where Claude shipped something non-trivial under your direction. Small-team temperament. You’re allergic to ceremony. You read code before asking. You raise a small PR when it’s ready. **Nice to have** GWT (you won’t write new GWT, but you’ll need to read and migrate it). Workflow / BPMN, records management, e-signature, or ECM domain experience. Hazelcast, Solr, Keycloak operational familiarity. Lexical or another modern rich-text editor. Playwright (you’ll inherit a calibrated suite — we want you to improve it, not rewrite it). Docker compose stack bring-up across Postgres, MSSQL, Solr, Keycloak. Python services or Helm/Kubernetes deployment experience. **How we work** Small PRs. Every change ships through review. If it’s getting big, split it. Test-driven design. Tests come with the code, not after. JUnit on the Java side, Vitest + Playwright on the React side. Daily standups. 15 minutes, async-friendly, but we show up. Memory-backed Claude Code sessions — agents learn the codebase with you, not against you.

Seeking an experienced Microsoft Power Automate and API integration specialist to evaluate and design an automated bid follow-up workflow utilizing Autodesk BuildingConnected (Bid Board Pro). Current Workflow Our estimating team uses BuildingConnected Bid Board Pro to manage bid opportunities and follow-up dates. We would like to automate follow-up emails for opportunities with overdue follow-up dates while keeping BuildingConnected as the primary source of truth for follow-up scheduling. Desired Future Workflow BuildingConnected (Bid Board Pro) ↓ Identify opportunities with overdue follow-up dates ↓ Microsoft Power Automate sends customized follow-up emails- once per week ↓ Successful email send is logged ↓ Follow-up date is automatically advanced ↓ Updated follow-up date is written back to BuildingConnected (if API capabilities allow) Discovery Phase Objectives The selected consultant will: Review Autodesk BuildingConnected API capabilities. Determine whether opportunity follow-up dates can be read and updated programmatically. Review authentication requirements (OAuth, API credentials, permissions). Recommend the optimal architecture utilizing: Microsoft Power Automate BuildingConnected API SharePoint or Excel if required Identify limitations, risks, and alternative approaches. Provide a written implementation plan and budget estimate for full deployment. Deliverables API feasibility assessment Workflow architecture diagram Recommended implementation approach Estimated cost and timeline for full implementation Identification of any BuildingConnected API limitations Required Skills Microsoft Power Automate REST APIs OAuth Authentication JSON SharePoint Microsoft 365 Integrations Preferred Skills Autodesk Construction Cloud BuildingConnected API Construction software integrations Reference Documentation BuildingConnected API Overview: https://aps.autodesk.com/apis-and-services/buildingconnected-api BuildingConnected Opportunity Management: https://aps.autodesk.com/en/docs/buildingconnected/v2/tutorials/buildingconnected/manage-opportunities/ BuildingConnected API Reference: https://aps.autodesk.com/en/docs/buildingconnected/v2/reference/http/ Budget Fixed-price discovery engagement. Please provide an estimate and examples of similar API integration projects.

Job Description:We are looking for an experienced Microsoft Power Platform Developer to design, build, and deploy two internal business applications optimized for tablets and iPhones. Our company operates fully within the Microsoft environment, so native integration, security best practices, and clean architecture are critical. Project Scope: Application 1 (Factory Floor Quality Checklist): A tablet-optimized Canvas App for factory operators to record quality control data. It must feature large, touch-friendly UI elements, dropdowns, and camera integration for capturing and uploading defect photos directly to a SharePoint List database. Application 2 (Azure & IoT Sensor Dashboard): An iPhone and tablet-friendly app allowing users to input field data directly into an Azure Cloud environment (Azure SQL / Data Factory). Additionally, this app must pull, aggregate, and visually display incoming IoT sensor data from our Azure environment via clean, responsive dashboards (or an embedded Power BI frame). Required Technical Expertise:Proven track record building responsive Canvas Power Apps for mobile and tablet form factors.Deep understanding of SharePoint Online list architecture and standard data connectors.Strong experience with Premium Connectors, specifically connecting Power Apps to Azure SQL, Azure IoT Hubs, or custom Azure APIs. Experience with Power Automate for backend logic, data transformation, and automated notifications.Familiarity with data optimization to ensure high-frequency sensor data does not cause app latency.Strong focus on UI/UX tailored for fast-paced operational environments. Deliverables:Fully functioning Canvas Apps deployed to our environment. Architecture documentation detailing data connections and flows. Brief handoff session to outline maintenance steps. To Apply:Please share examples of past Canvas Apps you have built (specifically any manufacturing, inspection, or dashboard-related apps). In your proposal, briefly highlight your experience managing premium Azure data connections within Power Apps.