Find Your Next TypeScript Project

We're a 4-person team building a research assistant tool for legal and compliance teams. Our frontend is done and looks great - Next.js 14 (App Router), TypeScript, Tailwind, deployed on Vercel. Both of our engineers are frontend-focused. We've been faking the backend with mock data and a couple of thin API routes, and we've hit the wall.

We need someone to own the backend properly.

What we need built:
- FastAPI service to replace our current Next.js API routes
- Streaming endpoints for our chat interface (SSE) - right now responses appear all at once after 20+ seconds and it feels broken
- Auth: currently using Clerk on the frontend, need proper token verification and per-org data isolation on the backend
- Background job processing - users upload documents (PDF/DOCX, sometimes 200+ pages) that need parsing and embedding without blocking the request. We assume Celery + Redis but we're open
- Postgres schema design and migrations. We have a rough schema that we know isn't right
- Vector search over uploaded documents. We're on Supabase/pgvector currently, happy to move if there's a good reason
- Deployment setup (we're thinking Railway or Fly.io) and basic monitoring so we know when something breaks

About the AI side:
We're calling the OpenAI API directly and it mostly works, but retrieval quality is inconsistent and we don't have a good way to tell whether a change made things better or worse. If you have opinions here we'd like to hear them, but the backend infrastructure is the priority.

What we're looking for:
- Strong Python and FastAPI, with production systems you can point to
- Comfortable with async Python - a lot of this is I/O bound
- Experience with background job queues at real volume
- You've worked with a frontend team before and can define a clean API contract instead of us guessing
- Enough familiarity with Next.js/TypeScript to read our code and tell us when the problem is on our side
- Clear communicator. We're async across three time zones

Nice to have:
- RAG/vector search experience
- Experience with Clerk or similar auth providers
- You've dealt with LLM streaming and cancellation before

How we work:
Async-first, Slack. We'll give you full repo access and a Loom walkthrough of the product on day one.

To apply:
Tell us about a backend you built that a frontend team consumed - what the API contract looked like and what you'd do differently now. Please skip the generic proposals, we'll know.

Screening questions:
1. Describe your experience with FastAPI and async Python.
2. Have you implemented SSE or WebSocket streaming in production? What went wrong the first time?
3. What's your approach to background job processing for long-running tasks?
4. What is your availability over the next 3 months?

OrthoTitans is hiring a Senior Full-Stack Software Engineer to help build Bravura, a modern orthodontic practice-management and EHR platform replacing outdated industry software. This is a remote, 40-hour-per-week contract role; senior candidates are preferred, though strong mid-level developers will be considered. You will build complete features using Angular, TypeScript, Tailwind CSS, C#, ASP.NET Core, PostgreSQL, and, when needed, Three.js/WebGL. The platform follows Domain-Driven Design, Clean Architecture, REST APIs, role-based authorization, multi-tenant SaaS patterns, and repository/service patterns. Responsibilities include turning detailed requirements and high-fidelity mockups into responsive, accessible interfaces; implementing APIs, domain logic, schemas, queries, permissions, validation, error handling, and persistent data; replacing mock data; testing work; reviewing code; and releasing frequently. Candidates should be comfortable with GitHub feature branches, pull requests, Jira, sprints, CI/CD, rapid iteration, and end-to-end ownership. Reliable overlap with Addis Ababa and California Pacific Time is required. Compensation is discussed with qualified applicants.

# Senior Full-Stack Developer — Trading Systems

We are looking for an experienced full-stack developer to help build, improve, and scale Prime Automation, a production trading automation platform supporting cryptocurrency, futures, equities, copy trading, and AI-powered strategies.

You will work across the full application stack on trading-bot configuration, webhook ingestion, order execution, account synchronization, risk controls, performance reporting, and integrations with exchanges, brokers, and market-data providers.

This is a long-term, full-time role with meaningful product ownership. We need someone who can deliver product features while also improving system reliability, testing, architecture, security, and engineering standards.

## Responsibilities

- Develop end-to-end product features using Node.js, React, and Next.js.
- Build and maintain scalable backend services, REST APIs, and application workflows.
- Create responsive interfaces for configuring bots, managing accounts, monitoring positions, and reviewing trading performance.
- Integrate cryptocurrency exchanges, brokers, market-data providers, payment systems, and other third-party services.
- Build reliable and idempotent trade-execution workflows.
- Handle multiple entries and exits, partial fills, stop losses, take profits, and position reconciliation.
- Maintain accurate trade history, PnL, account balances, and bot performance reporting.
- Develop reliable systems for processing webhooks, scheduled tasks, queues, and background jobs.
- Prevent duplicate, delayed, or missed events from causing incorrect trading behavior.
- Improve application performance, availability, security, and scalability.
- Design and maintain database models using MySQL and Redis.
- Diagnose production incidents using logs, monitoring, metrics, and error-tracking tools.
- Write unit, integration, and regression tests for complex application workflows.
- Participate in technical planning, architecture decisions, code reviews, and product discussions.
- Maintain clear technical documentation and improve development and deployment processes.
- Review AI-generated code critically and validate it through testing and code review.
- Collaborate with the team through GitHub, Discord, Asana, and other modern development tools.

## Required Technical Skills

- At least three years of professional Node.js development experience.
- Strong professional experience with React and Next.js.
- Strong JavaScript experience and practical TypeScript experience.
- Experience designing, developing, and maintaining REST APIs.
- Experience working with relational databases such as MySQL.
- Familiarity with Redis or similar caching and data-storage technologies.
- Strong understanding of asynchronous programming and event-driven workflows.
- Understanding of retries, idempotency, concurrency, race conditions, and failure recovery.
- Experience debugging production services, database queries, background jobs, and third-party API failures.
- Experience using Git within a collaborative development environment.
- Ability to write clean, maintainable, and well-tested code.
- Strong debugging, investigation, and problem-solving skills.
- Understanding of authentication, authorization, application security, and secure API development.
- Ability to take ownership of a feature from requirements through implementation, testing, deployment, and production verification.

## Nice to Have

- Experience developing financial technology, trading, cryptocurrency, brokerage, or market-data applications.
- Experience integrating cryptocurrency exchanges or trading APIs.
- Familiarity with futures, equities, leverage, margin, order types, and position management.
- Experience with WebSockets, streaming data, webhooks, queues, and background-processing systems.
- Experience handling partial fills, order reconciliation, PnL calculations, and broker state synchronization.
- Experience building dashboards, analytics tools, or data-visualization interfaces.
- Familiarity with cloud infrastructure, Docker, CI and CD pipelines, monitoring, and production deployments.
- Experience with DigitalOcean, Vercel, PM2, Sentry, or similar technologies.
- Experience improving applications that operate continuously or process time-sensitive transactions.
- WordPress development experience for occasional agency or client projects.
- An interest in financial markets, algorithmic trading, or trading automation.

## What We Value

- Ownership and accountability.
- Careful engineering for financially sensitive workflows.
- Clear and proactive communication.
- Practical decision-making and attention to edge cases.
- Willingness to investigate root causes rather than apply temporary patches.
- Ability to balance feature delivery with reliability and maintainability.
- Constructive participation in code reviews and technical discussions.

## Working Arrangement

- Full-time availability of approximately 40 hours per week.
- Individual applicants only. No agencies or outsourced development teams.
- Fluent written and spoken English.
- Reliable communication and ability to meet agreed deadlines.
- Working hours within three hours of Central European Time.
- Availability for recurring team meetings and consistent communication during shared working hours.
- Long-term interest in growing with the product and the company.

## Application

Please include:

- A short introduction describing your relevant experience.
- Examples of full-stack applications you have built or maintained.
- Details of any trading, financial technology, exchange, broker, or market-data integrations you have worked on.
- An example of a difficult production issue you investigated and resolved.
- Your availability, location, and preferred working hours.

Senior Zoho One Architect & Developer — Full Operating Spine for Life-Science E-Commerce Company

Company and Project Overview

LuvionBio is a research-use-only life-science reagent company with approximately 150 SKUs, multiple suppliers, batch-specific analytical testing, wholesale and direct e-commerce customers, and approximately 800 orders per month.

We have Zoho One and want to build it into the central operating spine of the company not simply configure a collection of disconnected Zoho apps.

We need a senior Zoho solutions architect, developer, or small named implementation team capable of:

* Designing the complete architecture
* Establishing one authoritative owner for every major data object
* Configuring the Zoho applications
* Migrating and reconciling financial and operational data
* Building reliable integrations and automations
* Implementing batch-level inventory and quality workflows
* Creating executive and operational reporting
* Securing, documenting, testing, and handing off the complete system

This is not a basic CRM setup or a collection of simple Zoho Flow automations.

Current Environment

Our current and planned environment includes:

* Zoho One
* Zoho Books and Zoho Inventory
* Zoho CRM
* Zoho Marketing Automation 2.0 and an existing Campaigns setup
* Zoho Desk and SalesIQ
* Zoho Creator
* Zoho WorkDrive
* Zoho Analytics
* Zoho Flow, Forms, Sign, Vault, and related applications
* QuickBooks Online Advanced as the current accounting system
* WordPress and WooCommerce as the current e-commerce platform
* A future Next.js and Medusa commerce platform
* Microsoft 365 for business email, identity, and collaboration
* Postmark for transactional email
* AfterShip for shipment tracking and post-purchase workflows
* Partnero for affiliate management
* Gusto for payroll
* Additional payment, shipping, warehouse, and marketing systems

Primary Objectives

The finished system must:

* Establish one source of truth for every major business object
* Eliminate unnecessary duplicate entry
* Connect commerce, finance, inventory, purchasing, quality, sales, service, marketing, and analytics
* Support batch/lot-level traceability
* Provide reliable financial and inventory reporting
* Be auditable, secure, documented, and recoverable
* Support the current WooCommerce store without becoming dependent on WooCommerce
* Be ready for the planned Next.js and Medusa migration
* Support future brands or subsidiaries without requiring the architecture to be rebuilt
* Remain manageable by LuvionBio after implementation

## Target System Ownership

The final ownership matrix must be validated during discovery, but our intended architecture is:

* **Zoho Books:** General ledger, banking, AP, AR, invoices, financial payment records, tax configuration, expenses, financial close, and financial reporting

* **Zoho Inventory:** Canonical SKU identity, physical inventory, warehouses, batches/lots, purchasing, receiving, inventory movements, fulfillment records, returns, reorder controls, inventory valuation, and COGS inputs

* **Zoho CRM:** Leads, contacts, accounts, research-access status, wholesale pipeline, relationship history, segmentation, sales activity, and customer approval data

* **WooCommerce/Medusa:** Storefront presentation, catalog merchandising, cart, checkout, discounts, payment capture, and originating e-commerce order events

* **Zoho Creator:** Quality control, supplier qualification, sample tracking, batch testing, lot release, deviations, and custom operational workflows

* **Zoho Desk:** we are currently using FreshDesk Omni, but open to making a change.

* **Zoho Marketing Automation 2.0:** Marketing audiences, journeys, behavioral segmentation, lead scoring, and lifecycle automation

* **Postmark:** Transactional and system-generated email

* **Zoho Analytics:** Cross-functional reporting and executive dashboards

* **Zoho Vault:** Workforce credentials, integration secrets, and controlled access to sensitive system credentials

Where two systems contain the same information, the architect must document which system owns it, which system receives a copy, permitted update directions, conflict handling, and deletion behavior.

## Scope of Work

### Phase 1: Discovery and Architecture Blueprint

Perform a comprehensive audit of the existing environment, including:

* Zoho One organization and application associations
* Current Zoho Books and Inventory organizations
* QuickBooks Online data and configuration
* CRM configuration and data
* Campaigns configuration and marketing contacts
* Current WooCommerce structure, products, customers, orders, discounts, taxes, refunds, and payment states
* Existing integrations, APIs, plugins, webhooks, Flow automations, and Deluge functions
* WorkDrive documents and existing folder structure
* Microsoft 365, Postmark, AfterShip, Partnero, Gusto, and other relevant systems
* User accounts, licenses, roles, permissions, and administrator access
* Duplicate records, inconsistent SKUs, missing IDs, and other data-quality problems

Required architecture deliverables:

* Current-state architecture diagram
* Target-state architecture diagram
* Application responsibility matrix
* Object-level source-of-truth matrix
* Canonical ID strategy
* Master data model and data dictionary
* Integration and event map
* Field-mapping workbook
* Migration and cutover plan
* Security and permissions plan
* Testing and acceptance plan
* Risk, dependency, and issue register
* Phased implementation estimate

No production build should begin until this blueprint is approved.

### Phase 2: Zoho Books and Inventory Backbone

Configure Zoho Books as the only active accounting general ledger after cutover. We do not want QuickBooks and Zoho Books maintained as parallel accounting systems.

Books requirements include:

* Company and fiscal settings
* Chart of accounts designed for e-commerce and life-science operations
* Departments, channels, warehouses, locations, or reporting dimensions where appropriate
* Banking and credit-card connections
* Payment clearing and reconciliation workflows
* Accounts payable and accounts receivable
* Purchase transactions, bills, invoices, sales receipts, refunds, credit notes, and adjustments
* Sales tax configuration
* Approval rules and financial controls
* Inventory accounting, landed costs, valuation, and COGS
* Payroll journal workflow from Gusto
* Month-end close and reconciliation procedures
* CPA/bookkeeper roles with controlled access
* Structure capable of supporting future related entities without mixing legal-entity books

Inventory requirements include:

* Approximately 150 SKUs with multiple strengths, vial sizes, and product variations
* Consistent item and SKU naming standards
* Vendor and manufacturer records
* Purchase orders and approval workflows
* Partial shipments and partial receipts
* Inbound tracking
* Multiple warehouses or inventory locations
* Batch/lot tracking
* Manufacture and expiration dates where applicable
* Quarantined, released, rejected, damaged, and expired inventory states
* Inventory transfers and adjustments
* Returns and replacements
* Kits or composite items where appropriate
* Barcode support
* Low-stock alerts and reorder points
* Purchase and demand-planning reports
* Inventory-aging and slow-moving inventory reporting
* Batch-level transaction history
* Prevention of unreleased inventory being allocated or sold

Migration requirements include:

* Preserve existing Zoho organization history
* Back up all source data before cutover
* Migrate approved QuickBooks data into the selected Zoho Books organization
* Migrate customers, vendors, items, balances, open AR/AP, and approved historical transactions
* Migrate or reconstruct inventory quantities and valuation by SKU, warehouse, and batch
* Reconcile the trial balance, balance sheet, P&L, AR aging, AP aging, bank balances, inventory quantities, and inventory valuation
* Obtain written signoff before deactivating any previous system

### Phase 3: CRM and Customer Architecture

Configure CRM for both e-commerce customer context and higher-touch B2B/wholesale sales.

CRM requirements include:

* Leads, contacts, accounts, deals, and appropriate custom modules
* One unified customer identity across website, CRM, Books, Inventory, Desk, and marketing
* Research-access application and approval status
* Application review, approval, rejection, expiration, and renewal workflows
* Wholesale and institutional sales pipeline
* Customer types and research-organization segmentation
* Sales ownership, tasks, reminders, and follow-up sequences
* Customer order, invoice, payment, support, and marketing context
* Duplicate-detection and merge rules
* Data-validation rules
* Required-field and stage controls
* CRM Blueprints for important business processes
* Consent status, marketing eligibility, and suppression fields
* Customer lifetime value, total sales, last order, order frequency, and product-category summaries
* Controlled synchronization with Books and Inventory
* Role-based views for management, sales, finance, support, warehouse, and marketing

### Phase 4: Quality, Batch Release, and Document Control

Build a custom quality-management workflow using Zoho Creator, WorkDrive, and related Zoho applications.

The workflow should support:

* Supplier and vendor qualification
* Purchase order and supplier-batch association
* Batch and lot records
* Sample intake and chain of custody
* Quarantine status
* Analytical test requests
* HPLC, mass spectrometry, endotoxin, net peptide content, potency, stability, and other applicable test records
* Target specifications and pass/fail rules
* Test result review
* Quality approval
* Lot release, rejection, hold, or investigation
* Deviations and corrective-action records where appropriate
* Complete audit history
* Electronic approval or signature where required
* Automated notification to relevant employees
* Controlled release of inventory in Zoho Inventory
* Prevention of fulfillment from unreleased lots

WorkDrive requirements include:

* Standardized company folder architecture
* Automatic folder creation for suppliers, POs, batches, lots, products, and quality records
* Standard naming conventions
* Version control
* Permission groups
* COA and SDS storage
* Supplier and manufacturing documents
* Batch and testing records
* Links between Creator, Inventory, CRM, and WorkDrive records
* Controlled mechanism for publishing approved COAs to the public website or customer portal
* Ability to identify the exact COA and batch associated with a customer order

### Phase 5: Desk, SalesIQ, and Customer Service

Configure Zoho Desk as the central support platform.

Requirements include:

* Configure the company’s primary customer-support inbox
* Ticket categories and subcategories
* Assignment and escalation rules
* Priority definitions
* Service-level targets
* Internal notes and collaboration
* Approved response templates and macros
* Refund, replacement, shipping, account-access, and quality-issue workflows
* Links to CRM customers, orders, shipments, invoices, payments, and batches
* Knowledge-base architecture
* Reporting by ticket type, product, customer, agent, and resolution time
* SalesIQ chat and visitor routing
* Conversion of qualified inquiries into CRM records
* Appropriate research-use-only disclaimers and escalation rules
* Controls preventing unsupported treatment, dosing, or human-use guidance

### Phase 6: Marketing Automation and Customer Lifecycle

Zoho Marketing Automation 2.0 is intended to become the primary marketing platform.

The contractor must:

* Audit the current Campaigns configuration
* Document the transition from Campaigns to Marketing Automation
* Preserve reusable templates, contacts, consent data, suppression lists, and engagement history where possible
* Avoid connecting CRM directly to both Campaigns and Marketing Automation
* Establish CRM-to-Marketing Automation field ownership and sync rules
* Keep transactional order email in Postmark
* Implement website tracking and event capture
* Create accurate customer and prospect segmentation
* Implement a subscription preference center
* Preserve opt-in source, date, consent language, and suppression history
* Prevent unsubscribed or ineligible contacts from being re-added through other integrations

Initial lifecycle journeys should include:

* Research-access application follow-up
* Access approval and welcome
* First-order onboarding
* Cart or checkout abandonment
* Post-purchase education and service
* Customer reactivation
* Wholesale lead nurture
* VIP and loyalty segmentation
* Product-interest segmentation
* Customer-service recovery
* Appropriate promotional and educational journeys

All marketing workflows must remain consistent with a research-use-only business and must not present products as intended for human or veterinary use.

### Phase 7: WooCommerce and Future Medusa Integration

The internal Zoho spine should be stabilized before the production commerce integration is activated.

The current WooCommerce integration must account for:

* Customers and applications
* Products and SKUs
* Inventory availability
* Orders and line items
* Coupons and discounts
* Taxes
* Shipping charges
* Payment status
* Refunds and partial refunds
* Cancellations
* Chargebacks
* Fulfillment and tracking
* Customer consent
* Affiliate attribution
* Order and customer updates
* Historical data import

The architecture must not depend on a temporary WooCommerce-only plugin. It must provide a documented path to replace WooCommerce with Next.js and Medusa.

For the future Medusa environment, we expect a durable server-side integration layer using supported APIs and webhooks. The integration must include:

* Stable canonical IDs
* Idempotent event processing
* Duplicate prevention
* Retry handling
* Rate-limit handling
* Queuing where appropriate
* Dead-letter or failed-event handling
* Structured logs
* Monitoring and alerts
* Scheduled reconciliation
* Manual replay tools
* Environment-specific credentials
* Test and production separation
* Documented recovery procedures

The contractor must clearly explain when native Zoho integration, Zoho Flow, Deluge, or custom middleware is being used and why.

All custom code must be stored in a LuvionBio-controlled GitHub repository. Credentials and connections may not remain in a freelancer-owned account.

### Phase 8: Other Integrations

Audit and implement the approved connections involving:

* Microsoft 365
* Postmark
* AfterShip
* Partnero
* Gusto
* Payment and banking systems
* Shipping and tracking systems
* Website forms and research-access gate
* Zoho Forms, Sign, Bookings, and WorkDrive
* Any required SMS consent or communication data

Existing third-party systems should not be replaced without written approval.

### Phase 9: Zoho Analytics and Executive Reporting

Build reliable dashboards and scheduled reporting for:

**Executive**

* Revenue
* Gross margin
* AOV
* Repeat purchase rate
* Customer lifetime value
* Discounts
* Refunds
* Channel performance
* Cash position
* AR and AP
* Integration health

**Sales and Customers**

* Revenue and margin by customer
* Wholesale pipeline
* New versus returning customers
* Customer cohorts
* Customer segments
* Sales-representative performance

**Products and Inventory**

* Revenue and margin by SKU
* Inventory on hand, committed, available, and quarantined
* Inventory valuation
* Stockouts and reorder risk
* Aging and expiration exposure
* Demand and purchase planning
* Returns and product issues

**Suppliers and Quality**

* Supplier performance
* Purchase-order cycle time
* Late and partial receipts
* Batch pass/fail rates
* Testing turnaround time
* Quality exceptions
* Cost and margin by supplier or batch

**Marketing and Service**

* Journey performance
* Attribution
* Conversion
* Engagement
* Unsubscribe and complaint rates
* Ticket volume
* Resolution time
* Customer-service issues by product and batch

All dashboards must use documented definitions so that the same metric does not produce conflicting values in different systems.

### Phase 10: Security, Governance, and Administration

Implement:

* Least-privilege access
* Custom roles and permission groups
* Separation of finance, warehouse, quality, marketing, service, and administrator access
* MFA and security-key support for privileged users
* At least two controlled super-administrator accounts
* Emergency-access procedures
* Dedicated service accounts for integrations
* Minimum necessary API scopes
* Credential management through an approved company-controlled vault
* Audit logs
* User onboarding and termination procedures
* Sandbox and production-change procedures
* Backup and export schedule
* Integration inventory
* Data-retention standards
* Incident-response and recovery runbooks
* Periodic access reviews

No shared administrator credentials should be used.

## Required Deliverables

The engagement is not complete until LuvionBio receives:

* Approved architecture blueprint
* Source-of-truth and ownership matrix
* Data dictionary and field-mapping workbook
* Fully configured Zoho applications
* Migrated and reconciled data
* Production integrations
* Integration source code
* Integration monitoring and alerts
* Analytics dashboards
* User-role and permission matrix
* Configuration workbook
* Automation inventory
* API and connection inventory
* UAT scripts and results
* Cutover and rollback plan
* Administrator runbook
* End-user SOPs
* Recorded training sessions
* Administrator training
* Department-level user training
* Known-issues register
* At least 30 days of post-launch stabilization support

All source code, configurations, documentation, intellectual property, accounts, and credentials created for this project must be owned and controlled by LuvionBio.

## Acceptance Criteria

At minimum:

* Financial balances reconcile to approved source-system balances
* Inventory quantities and valuation reconcile to the approved cutover schedule
* No production data is deleted without written approval
* Duplicate customer, order, invoice, or payment records are prevented
* The complete order lifecycle passes UAT, including refund, cancellation, replacement, and failed-payment scenarios
* Duplicate webhooks do not create duplicate transactions
* Failed integrations generate actionable alerts
* Failed events can be safely replayed
* Every integration has documented ownership and recovery procedures
* A batch can be traced from supplier and PO through testing, release, inventory, order, shipment, and customer
* Unreleased inventory cannot be inadvertently fulfilled
* Marketing consent and suppression rules are tested
* User permissions pass role-based testing
* Company administrators can operate the system without continued dependence on the contractor
* All documentation, source code, and credentials have been transferred before final payment

## Required Experience

Applicants should have substantial experience with:

* End-to-end Zoho One architecture
* Zoho Books and Inventory implementation
* QuickBooks Online to Zoho Books migration
* Zoho CRM customization and Blueprint
* Zoho Creator and Deluge
* Zoho WorkDrive document automation
* Zoho Desk and SalesIQ
* Zoho Marketing Automation 2.0
* Zoho Analytics
* Zoho APIs, OAuth, webhooks, and Flow
* Node.js or TypeScript integration development
* WooCommerce APIs
* Medusa or comparable headless-commerce platforms
* Batch/lot-controlled inventory
* E-commerce accounting and reconciliation
* Security, logging, testing, documentation, and production deployment

Experience with life sciences, laboratory products, regulated products, manufacturing, or quality-controlled inventory is strongly preferred.

## Engagement Structure

We prefer:

1. A paid fixed-price discovery and architecture milestone
2. Written approval of the blueprint
3. Phased implementation milestones
4. Weekly demonstrations and status reporting
5. Formal UAT and financial reconciliation
6. Production cutover
7. Thirty-day stabilization period

Please do not submit a single unsupported price for the entire implementation without explaining assumptions, dependencies, exclusions, and team composition.

## Application Instructions

Begin your proposal with the word **SPINE**.

Include:

* Two examples of similarly complex Zoho One implementations
* Your specific role in each project
* Experience migrating QuickBooks Online to Zoho Books
* Experience with Zoho Inventory batch tracking
* Experience building Creator-based approval or quality workflows
* Experience integrating WooCommerce or Medusa through APIs and webhooks
* Your recommended approach to Zoho Flow versus custom middleware
* The names and roles of everyone who would work on the project
* Your proposed price and timeline for the discovery phase
* Preliminary implementation phases
* The three largest risks you see in this project
* Your availability for meetings during US Eastern Time

Generic proposals describing only CRM setup, lead automation, or simple Zoho Flow connections will not be considered.

## Out of Scope Unless Separately Approved

* Redesigning the public website
* Building the core Next.js or Medusa storefront
* Replacing Microsoft 365
* Replacing Postmark, AfterShip, Partnero, or Gusto
* Telehealth, patient, clinical, or PHI workflows
* Medical or pharmaceutical regulatory consulting
* Ongoing bookkeeping
* Ongoing marketing campaign content creation
* Unsupported human-use or veterinary-use workflows

I am building a large-scale CRM platform and I'm looking for multiple experienced React/TypeScript developers to work on individual modules in parallel.

The project already has an established architecture, coding standards, and development workflow. Rather than building an application from scratch, your responsibility will be implementing and improving isolated CRM modules within an existing codebase.

Tech Stack
React
TypeScript
Vite
Node.js (Express)
PostgreSQL
Git (Feature Branch Workflow)
How We Work

The CRM consists of approximately 40 independent modules.

Development is organized into short sprints.

Each sprint contains a group of modules that are assigned independently to different developers. Depending on the sprint, you may be responsible for 5–10 modules, allowing multiple developers to work simultaneously without blocking each other.

Every task is delivered through:

a feature branch
pull request
code review
merge into the main development branch

Developers who deliver high-quality work consistently will be invited to future sprints as the project continues to grow.

Example Modules
Customer Management
Opportunity / Pipeline Tracking
Task & Activity Management
Notes
Calendar
CRM Dashboard
Reporting
Notifications
Contact History
Settings
What You'll Do
Build new CRM modules
Improve existing architecture when necessary
Write clean, maintainable TypeScript
Add unit/integration tests where appropriate
Follow the existing project structure and coding standards
Nice to Have

Experience with any of the following is a plus:

Authentication & Authorization
WebSockets / Real-time updates
Data Analytics
Performance Optimization
PostgreSQL optimization
GraphQL
Cypress or Jest
TanStack Query
Zustand / Redux
When Applying

Please include:

A GitHub repository or similar React/TypeScript project
Your experience with large React applications
Weekly availability
Time zone
Your preferred sprint size
Your hourly or fixed-price rate

This is not a one-time project. Developers who perform well will receive additional modules in future sprints, making this an ongoing collaboration.

Skills: PHP, Website Design, HTML, Node.js, PostgreSQL, Frontend Development, GraphQL, REST API, Vite

Job Overview

We're looking for an experienced Next.js developer to help identify, troubleshoot, and fix bugs in an existing web application built with Next.js, React, TypeScript, Tailwind CSS, and Supabase.

This is initially a bug-fixing task, but if everything goes well, there may be opportunities for ongoing work and new feature development.

What You'll Be Working On

You may be asked to:

Fix frontend bugs and unexpected UI behavior
Debug authentication and session issues
Resolve Supabase integration problems
Fix API and database-related issues
Improve application performance
Resolve responsive design inconsistencies
Fix hydration, rendering, or routing issues
Troubleshoot deployment or production-only bugs
Refactor problematic code where necessary
Required Skills

We're looking for someone with strong experience in:

React.js
Next.js (App Router)
TypeScript
JavaScript (ES6+)
Tailwind CSS
Supabase
Authentication
REST APIs
Git/GitHub
Vercel deployments

Bonus if you also have experience with:

PostgreSQL
Row Level Security (RLS)
Server Actions
Middleware
Performance optimization
SEO
Accessibility
What We Expect

The ideal developer:

Can quickly identify the root cause of issues
Writes clean, maintainable code
Doesn't introduce new bugs while fixing existing ones
Communicates clearly during debugging
Suggests better solutions when appropriate
Can work independently
Application Requirements

Please include:

Your experience with Next.js.
Your experience with Supabase.
Links to 2–3 relevant projects.
Your GitHub profile (if available).
Your availability this week.
Your hourly rate.
Screening Questions
Describe a difficult Next.js bug you've solved.
How do you usually debug production issues?
Have you fixed authentication or Supabase-related bugs before?
How quickly can you start?
To Apply

Start your proposal with the word "Supabase" so we know you've read the entire job description.

We're looking for someone who can jump in quickly, diagnose problems efficiently, and deliver reliable fixes. If the collaboration goes well, we'll have additional work involving new features and ongoing maintenance.

Project Overview
We provide a multilingual Voice AI infrastructure with enterprise APIs for automatic speech recognition, text-to-speech, speech translation, voice cloning and real-time streaming. Our speech infrastructure already exists. We're looking for an experienced AI Voice Agent developer to build the application layer that sits on top of our APIs.
This is not a machine learning or speech model development project. Your responsibility is to build a scalable Voice AI application that consumes our APIs.

Important
You must use our APIs for all speech capabilities. Do not build or substitute speech recognition, text-to-speech, translation or voice cloning, and do not replace our APIs with ElevenLabs, OpenAI Speech, Azure Speech, Google Speech, Retell AI or Vapi. The objective is to make our infrastructure the underlying speech engine for every voice application you build.

What You'll Build
This is a single project covering the full scope below, not phased or billed by calendar week. We'll agree milestone checkpoints and payments with the freelancer we hire, based on their proposed delivery plan.
A reusable, configurable Voice AI platform supporting multiple enterprise use cases, including AI customer support agents, AI receptionists, banking and telecom voice assistants, healthcare voice agents, internal enterprise assistants, appointment booking, lead qualification, call routing and FAQ agents. The platform should be configurable so new voice agents can be created without rebuilding the application.

Voice Agent Framework
Multi-turn conversations with conversation memory and session management, interruption handling (barge-in), voice activity detection and end-of-turn detection, low-latency streaming, and configurable prompts and agent personalities.

AI Agent Capabilities
Function calling and tool execution, retrieval-augmented generation, external API integration, and MCP-based tool integration so agents can consume external MCP servers. This includes business workflow automation and multi-agent orchestration where appropriate.

Enterprise Integrations
Modular, configurable connectors for CRM platforms, calendar systems, email providers, REST APIs, webhooks and internal business systems.

MCP Integrations
We expose our voice infrastructure through an MCP (Model Context Protocol) server. You'll extend and productionise this so AI assistants and AI-powered IDEs can use our speech capabilities directly, targeting Claude (claude.ai connectors, Claude Desktop, Claude Code), Cursor, Windsurf, ChatGPT and the OpenAI ecosystem, GitHub Copilot and other MCP-compatible clients.

This means building a remote MCP server over Streamable HTTP with OAuth 2.1 authentication mapped to our API credentials, MCP tools covering ASR, TTS, translation, voice cloning, voice selection and account usage, one-click install links and configuration files for each target client, per-client setup guides, and usage metering, rate limiting and audit logging consistent with the main API, with MCP usage reported in the analytics dashboard. As with the rest of this project, all MCP tools must route through our APIs.

Telephony
Twilio Programmable Voice, LiveKit and SIP, with inbound and outbound calls, DTMF and WebRTC support, and telephony-grade (8 kHz) audio. The telephony layer should stay independent of the conversation engine.

Multilingual Voice
Automatic language detection, dynamic language switching and code-switching, with translation and voice cloning routed through our APIs.

Administration Portal
The ability to create and configure voice agents, prompts, voices and languages, manage API credentials, integrations, users and permissions, and view audit logs and configure rate limits.

Analytics Dashboard
Reporting on active and completed calls, call duration and response latency, speech recognition confidence where available, transcripts and call outcomes, language usage, API consumption, MCP tool usage, error rates, and searchable conversation history.

Technical Requirements
Preferred technologies are Python, FastAPI, TypeScript, React or Next.js, WebSockets, MCP and Docker. The architecture should clearly separate the transport layer (browser, Twilio, LiveKit, SIP), speech APIs, conversation engine, business logic, integrations, MCP server and analytics, so the same voice agent can run across web, mobile and telephony channels without changes to the core application logic.

Deliverables
Complete source code, technical documentation, a deployment guide and Docker configuration, API integration documentation, MCP client setup guides, an installation guide and architecture diagrams.

In Your Proposal, Please Include
Examples of Voice AI applications you've built
Experience integrating custom ASR and TTS APIs, not only managed platforms

Any MCP servers or MCP client integrations you've built
Your proposed architecture, delivery plan and milestones

Estimated timeline and project cost
Any recommendations or technical considerations based on your experience
Successful delivery may lead to a long-term engagement building enterprise Voice AI products on top of our platform.

Chrome Extension Developer Needed to Review, Fix & Enhance Existing Extension

We are looking for an experienced Chrome Extension Developer to work on an existing Chrome Extension and its backend integration. The majority of the development has already been completed, and we need an expert who can quickly understand the current codebase, review the existing scripts, identify issues, implement improvements, and ensure everything is functioning properly.

Responsibilities
Review and understand the existing Chrome Extension codebase.
Analyze the extension's architecture, scripts, and backend integrations.
Troubleshoot and resolve bugs or functionality issues.
Optimize extension performance and reliability.
Ensure compatibility with the latest Chrome Extension Manifest standards.
Improve code quality, maintainability, and security.
Test the extension thoroughly and provide documentation where needed.
Assist with deployment and publishing updates if required.
Required Skills
Strong experience with Chrome Extension development.
JavaScript, TypeScript, HTML, and CSS.
Chrome Extension APIs and Manifest V3.
Backend API integration and authentication.
Debugging and performance optimization.
Git and version control.
Experience working with existing codebases.
Project Details
Existing Chrome Extension source code will be provided.
Backend code and API documentation will be shared.
Initial task is to review the current implementation and provide recommendations.
Additional work may include bug fixes, feature enhancements, and deployment support.
To Apply

Please include:

Examples of Chrome Extensions you have developed.
Experience with Manifest V3.
Experience integrating extensions with backend APIs.
Similar projects where you worked on an existing codebase.
Your estimated time to review and understand an existing Chrome Extension project.

We are looking for a developer who can start immediately and provide clear communication throughout the project.

BACKGROUND
The previous Upwork contract was closed by the platform before milestone payment was released. This continuation agreement reinstates the remaining two milestones under a new Upwork contract. All prior work completed under the original contract is acknowledged by both parties. This agreement covers only the remaining outstanding deliverables.
The scope below reflects a simplified launch version agreed upon by both parties, designed to keep the app financially sustainable from day one without adding scope beyond the original agreement.

Milestone 1 — Payments & App Launch — $2,600

App configured so that API costs per active user do not exceed subscription revenue. Free tier with 3-session monthly cap enforced server-side. Core tier at $4.99/month with unlimited sessions. Limitation popup when free user hits cap. Push notifications, streak tracking, memory across entries, and EQ Points all functioning correctly. Terms of Service screen in app. Client has access to usage and subscription data. App live on App Store. Payment released after client confirms everything is working as expected.

Milestone 2 — Backup & Bug Fixes — $760

Database backups active. Full QA completed before submission. 30-day bug guarantee begins on public launch date. All bugs reported within 30 days fixed per original contract terms. Payment released 30 days after public launch.

Intellectual Property
All work product, code, and deliverables become the sole property of the client (Miriam Macip / Commander Mimi) upon payment of the relevant milestone
Developer retains no rights to the Daily MIMI app, codebase, or brand upon completion
Client is entitled to full access to all source code, repositories, and credentials upon final payment

Credentials & Handover
Upon release of Milestone 2 payment, developer provides full handover of:
All source code via repository access (GitHub or equivalent)
App Store Connect access
All API keys and service credentials
RevenueCat account access
Any backend service accounts created for this project

Experienced Base44 / React AI Developer Needed to Complete AI SaaS Platform

Guardian Allies Collective LLC is seeking an experienced Base44/React AI Developer to help complete and prepare EvalIQ, our AI-powered SaaS platform for school psychologists, for commercial launch.

EvalIQ is an advanced web application that uses artificial intelligence to help practitioners create high-quality psychoeducational evaluation reports. The platform is already substantially developed, and we are looking for a developer who can quickly understand the existing application, resolve launch-critical issues, and help stabilize the platform for production.

This is not a project to build a website from scratch. We need someone who enjoys troubleshooting, improving existing applications, and solving complex technical problems.

Responsibilities

You will work directly with the Founder and be responsible for:

Reviewing the existing Base44 application architecture
Diagnosing and resolving production issues
Troubleshooting custom domain, DNS, SSL, and deployment problems
Improving authentication and session management
Resolving auto-save and data persistence issues
Improving AI-assisted workflows
Troubleshooting file uploads and report generation
Improving application performance and stability
Reviewing Base44 functions, entities, and workflows
Documenting technical changes and recommendations
Preparing the application for commercial launch
Required Skills
Base44 experience (strongly preferred)
React
TypeScript
JavaScript
REST API integration
AI/LLM integration (OpenAI, Anthropic, Gemini, etc.)
Authentication and session management
SaaS application development
Custom domains, DNS, and SSL troubleshooting
Strong debugging and problem-solving skills

Experience with educational technology, healthcare software, document-generation systems, or AI-powered applications is a plus.

Initial Engagement

This is an hourly contract (10–15 hours per week) for an initial 4-week engagement, with the possibility of continued work based on performance and future product needs.

Paid Technical Assessment

Finalists will be invited to complete a paid technical assessment before the full engagement begins. The assessment will focus on diagnosing a limited set of technical issues and providing recommendations. This helps ensure a strong technical fit while respecting your time.

How to Apply

Please begin your proposal with the word:

EVALIQ

Then include:

A brief summary of your Base44 or similar AI SaaS experience
Links to relevant projects (if available)
Your experience with React and AI integrations
Your availability over the next four weeks
Your hourly rate
Your earliest possible start date

We are looking for a collaborative developer who enjoys solving meaningful technical challenges and wants to help launch a product that supports professionals serving students and schools.

If you have extensive experience with React, TypeScript, AI-powered SaaS applications, and can quickly learn new low-code/no-code development environments, we encourage you to apply even if your direct Base44 experience is limited. Please explain your transferable experience in your proposal.

Hi there,

I'm looking for a quote on a fixed-scope security review.

We're on early-stage production planning platform (UK). Pre-launch, no real user data in the system yet. I want a security review completed before that changes.

Stack: Next.js (App Router), TypeScript, Prisma, Auth.js, Postgres-ready, deploying to Railway/Vercel with UK/EU data residency.

What the product does: a production manager creates a schedule, then shares audience-specific views via a link. Recipients don't log in. Different audiences (5/6 x different views) see different fields from the same record. Personal data includes names, phone numbers, addresses, travel bookings and emergency contacts.

What I'd like reviewed:
1. Share-token design: hashed tokens, revocation, expiry
2. Server-side authorisation and fail-closed field filtering (does anyone see a field they shouldn't?)
3. Auth implementation: magic links and passkeys
4. Field-level encryption of sensitive data
5. File storage and signed URL handling
6. Audit logging
7. UK GDPR posture: data minimisation, retention, subject access

Deliverable: written findings with severity ratings, plus a prioritised remediation list I can hand to my developer.

Please quote:
- Fixed price and turnaround for the review as scoped
- Your day rate if I need follow-up verification after fixes
- Two examples of similar reviews you've done
- Any relevant certifications

Happy to share the repo under NDA. Thanks.

We're a bootstrapped SaaS product with paying customers. We need a backend developer to build and deliver a clean, production-ready REST API. Frontend is React and already handled — you own the backend only.

Scope of work

Build REST API endpoints with Node.js + Express
Design and implement MongoDB schemas (Mongoose)
JWT authentication + role-based access control
File upload handling and third-party API integration
Input validation, error handling, and basic rate limiting
Deploy to our environment (Vercel / Railway / VPS) and hand over docs

Requirements

3+ years hands-on Node.js/Express in production
Strong MongoDB data modeling (not just CRUD tutorials)
Clean, documented, testable code — we will review it
Git workflow, clear commit history
Daily async updates in English, overlap with CET hours preferred

Nice to have

TypeScript
Docker
CI/CD experience

Budget & timeline

Fixed price: $500 USD
Timeline: 2 weeks
Milestone 1 ($150): schema design + auth complete
Milestone 2 ($200): core endpoints delivered and tested
Milestone 3 ($150): deployment, docs, handover

To apply, answer these 3 questions

Link one Node.js/Express repo or API you built what was the hardest part?
How would you structure MongoDB collections for a users → orders → items relationship?
What's your approach to securing a JWT-based API?

Applications without answers to all three will be ignored. Start with the word "BACKEND" so we know you read this.

Je lance à Montréal un projet propulsé par l’intelligence artificielle qui, selon moi, connaîtra une forte croissance cette année. Je cherche un·e collaborateur·trice francophone pour prendre en charge le développement logiciel de A à Z.

Voici ce que j’ai en tête :
• Frontend : bâtir une interface moderne en JavaScript/TypeScript (React, Next.js ou outil équivalent) avec une UX fluide et responsive.
• Backend : concevoir l’API et l’architecture serveur (Node.js, Express, GraphQL ou REST) en veillant aux performances et à la sécurité.
• Intelligence artificielle : intégrer des modules d’IA (par exemple TensorFlow.js ou appels à des services externes) jai propuler sripe pour linstant afin d’automatiser des fonctionnalités clés.
• Système de paiement : mettre en place une passerelle fiable (Stripe ou autre) pour les transactions récurrentes et uniques.

Je m’occuperai du volet produit, de la vision et du financement initial ; j’ai besoin d’une personne capable de transformer ces idées en code robuste, de suggérer des choix technologiques pertinents et de livrer rapidement des incréments fonctionnels. Une présence à Montréal est importante pour des sessions de travail en personne, surtout au démarrage.

Si tu maîtrises JavaScript/TypeScript et que tu aimes relever des défis où l’IA occupe une place centrale, j’aimerais qu’on discute de la roadmap, du mode de collaboration et des prochains livrables.

Skills: JavaScript, Website Design, HTML5, Node.js, Stripe, GraphQL, API Development, Next.js

I have an existing SaaS-style dashboard built with Next.js and need several feature upgrades so the application delivers deeper business insight without compromising performance. The codebase is clean, TypeScript-ready, and already uses React Query and TailwindCSS; your updates should slot in smoothly.

Core objectives
• Add interactive chart components that render smoothly on both desktop and mobile. I’m open to Recharts, Chart.js, or another modern library as long as it plays well with SSR in Next.js.
• Implement flexible data-filtering hooks (dates, categories, users, etc.) so stakeholders can slice information in real time and see the charts refresh instantly.
• Surface key KPIs—sales, retention, traffic and others we define together—on a compact panel with trend indicators.
• Provide export options: CSV and PDF downloads triggered from a single, reusable button component.
• Refine the overall dashboard UX: sensible loading states, lazy-loaded modules, and Lighthouse-friendly performance.

Acceptance criteria
1. All new UI matches the current Tailwind design tokens.
2. Charts and filters work with live API data, not mock fixtures.
3. KPI panel renders in under 200 ms on first paint and stays below 100 KB added bundle size.
4. Exports contain exactly what the user sees on screen and pass a quick manual QA.
5. PR includes clear README notes plus Jest/React Testing Library coverage for the new logic.

If this sounds like your wheelhouse, let’s talk tech details and timelines so I can get the new reporting suite into production without disrupting existing users.

Skills: PHP, JavaScript, HTML5, Laravel, Next.js

I need a focused internal web application for Evergreen Flooring (Kansas City area). This is NOT a full CRM or public product; it is only for a small internal team of about 7 people (3 account reps, 1 measurement specialist, and 3 quality control staff).

Goal
Help our office staff schedule property visits on a calendar and automatically generate the most efficient daily driving route that finishes by 4:30 p.m., including real travel times, on-site work time, buffers, and return to the office.

Core features needed
• Familiar calendar (Month / Week / Day views) that feels like a normal calendar app
• Ability for office staff to add property visits (address, visit type, estimated duration, optional time window, priority, contact info, notes)
• Capacity indicators so we can see when a day is Available, Nearly Full, Full, or Over Capacity
• “Generate Route” button on any selected day that produces an efficient stop order
• Full daily timeline (departure, drive times, arrival, waiting, service time, departure, return to office)
• Clear plain-language warnings if the route would finish after 4:30 p.m. or if a time window cannot be met
• Ability to manually reorder stops and immediately see the updated timeline
• Simple roles: Scheduler (office staff), Field (measurement & QC), and Admin
• Secure login

Technical preference
• Next.js (App Router) + TypeScript + Tailwind
• Supabase (Postgres + Auth), you already have strong experience here
• Leaflet for the map
• Routing logic behind an adapter (we can start with a solid mock mode and later add a real mapping provider)

What is deliberately out of scope
No invoicing, payroll, inventory, customer portal, automated messaging, or CRM features. Keep it simple and focused only on scheduling + route optimization.

I have a detailed project proposal ready that includes the exact requirements, user roles, success criteria, and suggested phasing. I can share it immediately with the right person.

Looking for someone who can move quickly, communicate clearly, and deliver a clean, reliable internal tool that our non-technical staff will actually enjoy using.

# Project Overview Document

## Project Title

**AI-Powered End-to-End UI Test Automation Framework using Playwright**

## Project Overview

We are looking for an experienced freelancer to develop an AI-powered automated testing framework that performs end-to-end testing directly through the application's User Interface (UI). The objective is to build a system that mimics how a real user interacts with the application, rather than relying on backend APIs or predefined test scripts.

The solution should combine **Playwright** with **Large Language Models (LLMs)/AI** to intelligently understand the application, navigate through different workflows, identify UI elements, perform validations, and generate meaningful test results with minimal human intervention.

The framework should be scalable, modular, maintainable, and optimized for low operational cost.

---

# Project Objectives

The primary objectives of this project are:

* Automate complete UI testing using Playwright.
* Enable AI to perform testing similarly to a human tester.
* Reduce manual scripting effort.
* Allow the AI to understand application screens and determine the appropriate testing flow.
* Minimize AI token consumption to reduce ongoing operational costs.
* Produce reliable and repeatable test execution with detailed reporting.

---

# Scope of Work

The freelancer will design and develop a framework capable of:

## 1. UI-Based Testing

The framework should execute tests only through the User Interface.

Examples:

* Login
* Navigation
* Forms
* Search
* Filters
* Tables
* Buttons
* Dropdowns
* Dialogs
* Validation messages
* Error scenarios

The AI should behave like a human user interacting with the application.

---

## 2. Playwright Automation

Use Playwright as the primary browser automation engine.

The framework should support:

* Chromium
* Microsoft Edge
* Chrome

Future support for Firefox/WebKit is desirable.

---

## 3. AI-Driven Testing

Instead of hardcoded scripts for every scenario, the AI should:

* Understand the page context.
* Decide the next action.
* Identify controls intelligently.
* Read labels and UI text.
* Handle dynamic pages.
* Recover from minor UI changes.
* Adapt to changing workflows where possible.

The goal is to reduce maintenance compared to traditional automation frameworks.

---

## 4. Human-Like Interaction

The AI should execute actions similar to how a manual tester would.

Examples include:

* Reading page content before interacting.
* Waiting intelligently instead of using fixed delays.
* Understanding validation messages.
* Filling forms logically.
* Navigating multi-step workflows.
* Handling popups and confirmations.
* Verifying success and error messages.

---

# AI Token Optimization (Very Important)

One of the primary requirements of this project is **cost optimization**.

The solution must be architected to minimize LLM/API token usage while maintaining good testing quality.

The freelancer should propose and implement techniques such as:

* Reusing previously generated context.
* Sending only relevant page information to the LLM.
* Avoiding unnecessary DOM dumps.
* Compressing UI context before sending it to the AI.
* Caching repeated prompts.
* Reusing locator knowledge where possible.
* Using deterministic Playwright actions whenever AI reasoning is not required.
* Using AI only for decision-making instead of every interaction.
* Maintaining memory of previous page structures.
* Reducing repeated prompts across test cases.

The overall architecture should focus on reducing operational cost over time.

---

# Intelligent Framework Design

The framework should separate deterministic automation from AI reasoning.

For example:

Playwright should handle:

* Clicking buttons
* Typing text
* Waiting for elements
* Assertions
* Screenshots
* Browser control

AI should handle:

* Understanding user stories
* Determining next actions
* Identifying business workflows
* Handling unexpected UI changes
* Making decisions when multiple paths are available

This hybrid architecture is preferred over invoking the AI for every UI interaction.

---

# Framework Characteristics

The framework should be:

* Modular
* Extensible
* Maintainable
* Reusable
* Easy to configure
* Well documented
* Easy for new testers or developers to use

---

# Reporting

The framework should generate comprehensive execution reports including:

* Test execution summary
* Passed tests
* Failed tests
* Screenshots for failures
* Error messages
* Execution time
* Logs
* AI reasoning logs (optional/configurable)
* Browser console errors (optional)

---

# Non-Functional Requirements

The solution should prioritize:

* Performance
* Reliability
* Scalability
* Low maintenance
* Low AI operating cost
* Readability of code
* Clean architecture
* Proper documentation

---

# Preferred Technology Stack

* Playwright
* TypeScript (preferred) or JavaScript
* Node.js
* OpenAI or other compatible LLM APIs (architecture should be provider-agnostic where possible)
* Git
* GitHub

---

# Deliverables

The freelancer should provide:

* Complete source code
* Framework setup instructions
* Documentation
* Installation guide
* Configuration guide
* Sample automated test cases
* AI integration documentation
* Token optimization strategy documentation
* Architecture diagram
* Instructions for extending the framework with new test scenarios

---

# Expected Outcome

At the end of the project, we expect a production-ready AI-assisted UI automation framework capable of executing end-to-end test scenarios through the application's UI with minimal manual scripting. The framework should intelligently leverage AI for reasoning while relying on Playwright for deterministic browser interactions, resulting in a robust, maintainable, and cost-efficient testing solution.

A key success criterion is that the architecture demonstrates efficient AI usage, minimizing token consumption and operational costs without compromising testing quality or reliability.

Skills: JavaScript, Test Automation, Node.js, Typescript, LLM Integration

We are looking for an experienced AI Automation Specialist to help us improve efficiency across our Shopify store by building practical, reliable automations. Our goal is to reduce repetitive work, enhance the customer experience, and create scalable workflows that support our growing business.

The role will involve automating areas such as customer support, email marketing, order management, product content creation, review follow ups, inventory alerts, social media workflows, reporting, and AI powered knowledge resources.

We are looking for someone with experience using automation platforms such as Make.com, n8n, Zapier, or similar, along with AI models and APIs from OpenAI, Claude, or Gemini. Experience integrating Shopify with tools like Airtable, Google Sheets, Notion, CRM platforms, and email marketing systems is highly valued. Familiarity with JavaScript or Python is a plus.

We value professionals who can identify opportunities to improve processes, recommend efficient automation strategies, and build workflows that are reliable, easy to maintain, and well documented.

As part of this project, you will design and implement AI driven automations, document each workflow, perform testing and troubleshooting, and suggest additional improvements that can support future growth.

When submitting your proposal, please include a brief introduction, examples of relevant automation projects, the tools you use most frequently, a project you are particularly proud of and the results it achieved, and your estimated timeline for delivering the initial workflow.

We are open to both hourly and fixed price proposals and are looking forward to building a long term working relationship with the right specialist.

Full-Stack SaaS Platform with Next.js, Supabase, and OpenAI Integration

I have a SaaS platform and need an experienced developer to improve some funtionalities.

Scope:

Build the application in Next.js with a clean, responsive interface.
Set up Supabase for the database, authentication, and row-level security (multi-tenant, role-based access).
Integrate an OpenAI-powered feature an AI assistant that generates and summarizes content for users based on their data.
Build admin dashboards with CRUD management, search, and filtering.
Implement secure API routes with proper error handling and rate limiting.
Deploy to production with a clean handover and documentation.

Ideal skills:

Strong Next.js and React with TypeScript.
Supabase (Postgres, auth, row-level security).
OpenAI / LLM API integration, including streaming responses.
Experience building multi-tenant SaaS with role-based access.

Deliverables:

Fully working SaaS platform with the AI feature live.
Admin dashboard and documentation for managing the system.

Looking for someone who can own this from architecture through deployment.

Skills: PHP, JavaScript, CSS, HTML, AngularJS, Full Stack Development, Next.js, OpenAI, Supabase

We're a lower middle market private equity firm looking for an experienced developer to build a custom integration between Claude AI and our CRM (DealCloud by Intapp). The goal is to eliminate manual data entry and replace a static deal-tracking system with a live, synced web application.

What We Need Built (3 Phases):

Phase 1 — MCP Server + Web Portal (~6 weeks)
Build a custom Model Context Protocol (MCP) server that connects Claude AI (web, desktop, and Cowork interfaces) to DealCloud's API.
Build a web portal ("Caymus AI Portal") with Microsoft 365 SSO authentication.
Implement role-based access control (RBAC) and audit logging using Supabase.

Phase 2 — DealFlow Migration & Data Sync (~6 weeks)
Migrate our existing static deal-tracking spreadsheet/app into the web portal.
Build bi-directional data sync between the web portal and DealCloud so target lists, coverage tiers (we use 6 tiers), and deal assignments stay current in both places automatically.
Auto-generate weekly target lists by tier and territory for two BD associates.

Phase 3 — PDF Data Extraction & CRM Automation (~4 weeks)
Build custom extraction tools within Claude that can ingest Confidential Information Memorandums (CIMs) and deal teasers (PDFs, typically 30–80 pages).
Automatically parse key deal data points (revenue, EBITDA, geography, sector, employee count, deal structure) from unstructured PDF content.
Push extracted data directly into the correct DealCloud fields with minimal manual review.

Technical Environment:
CRM: DealCloud by Intapp (REST API)
AI Client: Claude AI via MCP (Model Context Protocol)
Auth: Microsoft 365 / Azure AD SSO
Backend/DB: Supabase (or comparable — open to recommendations)
Current deal tracking: Static spreadsheet-based system

What We're Looking For:
Proven experience building MCP servers or similar AI-to-SaaS integrations.
Experience with DealCloud's API is a major plus (it's niche — if you haven't worked with it, experience with similar financial services CRMs like Salesforce Financial Services Cloud, Dynamo, or Affinity is relevant).
Strong full-stack skills (backend API development + frontend web portal).
Experience with Microsoft 365 / Azure AD authentication.
Understanding of RBAC, audit logging, and data governance requirements (we're a regulated financial services firm).
Experience with PDF parsing and unstructured data extraction is a plus for Phase 3.

How This Engagement Would Work:
We'd prefer to start with Phase 1 and evaluate before committing to Phases 2–3.
Open to fixed-price per phase or hourly — include your preferred structure in your proposal.
Must be comfortable signing an NDA (you'll have access to deal pipeline data).

In Your Proposal, Please Include:
Relevant experience with MCP, CRM integrations, or AI-to-SaaS tool building.
Whether you've worked with DealCloud specifically (or which financial CRMs you have worked with).
Your proposed approach and rough timeline for Phase 1.
Your pricing structure (fixed per phase, hourly rate, or monthly retainer).
1–2 examples of similar integrations you've built.

Hi, I’d like you to review an existing project called Trade Compass. The platform is approximately 85–90% complete, and I’m looking for someone who can review the existing codebase, identify issues, and help bring it to production quality.

The platform is built with Next.js, React, TypeScript, Node.js, PostgreSQL, and is deployed using Railway and Vercel. It integrates with SnapTrade for brokerage connections and currently supports Webull.

Current Issues

1. Master Trader Dashboard

* The master trader account is connected to Webull, but the dashboard displays a balance of $0.00.
* The dashboard should display the live portfolio value, buying power, cash balance, open positions, and open orders pulled from the brokerage API.

2. Brokerage Synchronization

* I need someone to review the SnapTrade/Webull integration to ensure brokerage accounts stay synchronized correctly.
* Verify that balances, positions, and account information update consistently.

3. Admin Dashboard
Several admin actions are currently only UI placeholders and need backend implementation, including:

* Delete User
* Suspend/Reactivate User
* Disconnect Broker
* Reconnect Broker
* Force Broker Sync
* Reset Password
* Assign/Remove Master Trader
* Pause/Resume Copy Trading

4. Broker Display
The Connected Brokers page currently shows multiple Webull accounts but doesn’t clearly identify which user owns each brokerage account.
Each broker connection should display:

* User Name
* Broker Name
* Account Type
* Last 4 digits of the account
* Balance
* Buying Power
* Connection Status
* Last Sync Time

5. User & Follower Management
Review the user management flow to ensure:

* Followers are correctly assigned to master traders.
* Copy trading relationships remain accurate.
* User status updates properly throughout the platform.

6. Error Handling
Replace placeholder or generic messages with meaningful production-ready error handling and improve logging to make debugging easier.

7. General Code Review
I’m looking for someone who can:

* Review the overall architecture.
* Identify performance bottlenecks.
* Clean up technical debt where appropriate.
* Improve backend reliability.
* Ensure the application is production-ready.
Intergrate Other brokers

Skills: JavaScript, NoSQL Couch & Mongo, Node.js, PostgreSQL, Software Development, AngularJS, Web Development, Trading, Next.js

SageMed builds software that turns scientific data into the documentation life sciences companies depend on: scientific validity reports, clinical evaluation reports, claims substantiation, market and competitive research, and more. Our platform, SageMed Bridge, does this work as a set of modules over a shared evidence and traceability layer. The work it replaces takes specialist teams months, and the output has to survive a notified body, a regulator or a legal reviewer reading it line by line.

We're looking for a senior full stack engineer to join the small team building Bridge end to end: the Next.js interface specialists work in, the services behind it, the pipelines that ingest and process evidence, and the agentic AI workflows underneath.

What you'll work on:
You could be building the one module one quarter and something entirely different the next. The modules may vary, the underlying problem does not.

User-facing product. Next.js and TypeScript. Review, appraisal, evidence-to-claim mapping, and document output that specialists live in for hours at a time.
Backend services and data pipelines. Ingesting scientific data from bibliographic databases, structured sources and PDFs, deduplication, structured extraction, versioned storage of every artifact we produce.

Agentic workflows. The retrieval, appraisal, analysis and drafting agents, and the evaluation harness that tells us whether a change made them better or worse.
The traceability layer. Every sentence in a generated report resolves to a real source. Every human decision is recorded with who, when and why. Every run is reproducible against a pinned model and configuration.

Making it defensible. Secure and auditable enough to pass procurement and supplier qualification at large regulated manufacturers.

What we're looking for:
Strong TypeScript with React and Next.js, plus genuine backend depth ([our stack: e.g. Node/Python, Postgres, cloud]).
You've shipped LLM-backed features that had to be correct, not just plausible, and you can describe how you measured that. Eval harnesses, regression suites, grounding checks, failure analysis.
Security-by-default habits: authorisation and tenant isolation, secrets handling, dependency and supply chain hygiene, least-privilege cloud IAM, and a healthy suspicion of untrusted input, including the arbitrary PDFs we feed to agents.
Comfort owning a problem from design through production with limited scaffolding.

Useful, not required:
GDPR in practice: data residency, DPAs, subprocessor management, records of processing.
SOC 2 or ISO 27001 from the building side rather than the auditing side.
A regulated background of any flavour: IVDR/MDR, ISO 13485, GxP and 21 CFR Part 11, clinical research, or similar. Life sciences domain knowledge is a real advantage.
Retrieval and search at depth: hybrid retrieval, ranking, relevance evaluation.
Document engineering: PDF and table extraction, structured output, deterministic document generation.

Why this role is worth your time:
You're close to the product and close to real users. Regulatory, clinical and commercial specialists, not a persona in a deck.
Correctness is legally consequential here. A fabricated citation isn't a bad user experience, it's a finding. That constraint makes the engineering more interesting, not less.
You pick the right tool for the job. There's little historical architecture to work around, and you'll have real influence over what replaces it as the team grows.
Polished interfaces and solid services behind them, built by the same person.
Real autonomy at an early stage, with the ownership that comes with it.

DATAONE Merchant Services is seeking a senior product engineering lead—or a small senior team with one clearly accountable lead—to take over and complete the next phase of our internal operating platform and agent-assisted products.

We have already invested heavily in product definition, architecture, governance, workflow design, engineering handoff materials, and prototype code. We are not looking to start over, and we are not looking for someone who simply builds generic software with AI.

The right partner will first study what exists, demonstrate a clear understanding of our payment-processing business and intended user experience, identify gaps or unnecessary complexity, and recommend a practical implementation plan. Only after that paid review will we select the person or team for the larger build.

What we are building

The immediate program includes:

1. **DATAONE HQ**
- The internal operating platform for leadership, finance, operations, sales, partnerships, and marketing.
- Role-based command centers, shared identity and permissions, approvals, operational workflows, evidence, handoffs, reporting, and auditability.
- A powerful backend with an interface that remains clear and easy for a small team to use.

2. **CoPilotOS**
- A guided sales and referral-partner enablement experience.
- Helps users understand opportunities, prepare for conversations, follow approved workflows, retrieve approved knowledge, and complete work with appropriate human controls.
- It is not intended to become an uncontrolled autonomous sales agent, the company CRM, or the system of record.

3. **Hermes**
- An internal advisory, reasoning, and orchestration layer.
- Supports governed workflows, recommendations, summaries, task coordination, and human approval.
- Our current Hermes work is a controlled lab and design baseline—not proof of a finished production runtime.

4. **Buzz**
- Evaluate Buzz as a potential human-and-agent collaboration/workspace layer.
- Determine where it provides real value, where it overlaps with Hermes or DATAONE HQ, and whether it should be adopted, isolated as a supporting component, or deferred.
- We do not want two competing production agent platforms. The engagement must produce a clear recommendation and boundary before implementation.

5. **MIN — later phase**
- MIN is a separate merchant intelligence product/data capability.
- Full MIN implementation is intentionally deferred. Current work should preserve clean interfaces and avoid architectural choices that block its later introduction.

Initial engagement: paid architecture and product review

Before committing to a larger implementation contract, selected finalists will complete a bounded paid review using sanitized documents and controlled, read-only repository access.

The review must:

- explain the system back to us in plain English;
- identify the intended users, their highest-value jobs, and the key business outcomes;
- assess what is clearly defined, unclear, conflicting, overbuilt, missing, or not yet ready;
- evaluate the existing code, product-definition package, architecture, data boundaries, security controls, tests, and implementation backlog;
- distinguish documentation and design intent from actual working runtime behavior;
- recommend what should be retained, simplified, revised, purchased, or built;
- propose the correct roles for DATAONE HQ, CoPilotOS, Hermes, and Buzz;
- show how MIN can be introduced later without premature implementation now;
- identify system-of-record and field-authority decisions that must be made before integrations;
- produce a realistic sequence, team plan, budget range, dependencies, risks, and acceptance criteria;
- identify what should explicitly **not** be built in the first release.

We welcome thoughtful disagreement. We do not want automatic agreement with our current plan; we want recommendations supported by product reasoning, repository evidence, security considerations, and delivery experience.

Required product-engineering capabilities

You should be able to own both the product and engineering conversation:

- translate business goals and user workflows into a coherent product architecture;
- interview stakeholders and separate real user needs from feature requests;
- define MVP boundaries, user journeys, service boundaries, acceptance criteria, and measurable outcomes;
- make build-versus-buy and sequencing decisions;
- simplify complex backend capability into an intuitive role-based experience;
- maintain design-system and UX consistency while working closely with design;
- plan incremental releases rather than defaulting to a rewrite;
- demonstrate working software frequently and incorporate user feedback;
- leave behind maintainable code, tests, runbooks, decision records, and a clear handoff.

Required technical experience

Strong hands-on experience in most of the following:

- TypeScript/JavaScript, React, and Next.js;
- Python and FastAPI or comparable production backend frameworks;
- PostgreSQL, schema design, migrations, queues, caching, and event-driven workflows;
- secure APIs and third-party integrations;
- authentication, role-based access control, tenant isolation, approval workflows, and audit trails;
- Docker, CI/CD, cloud infrastructure, observability, testing, and production operations;
- API contracts, data lineage, idempotency, error recovery, and evidence-backed workflow state;
- security and privacy practices appropriate for financial-services software.

Our current implementation evidence includes a Next.js/TypeScript frontend and a Python/FastAPI backend using PostgreSQL, Redis, Docker, authentication controls, CI checks, and agent/workflow components. Candidates should be comfortable assessing and continuing this stack, while recommending changes only when the benefit is clear.

Required agentic-systems experience

You must have built and operated more than a chatbot or simple LLM wrapper. Relevant experience includes:

- tool-using agents and constrained workflow orchestration;
- human-in-the-loop review, approval, pause/resume, and escalation;
- model routing and provider abstraction;
- retrieval and governed knowledge systems;
- structured outputs, contracts, evaluations, regression testing, and failure handling;
- agent identity, permissions, memory boundaries, provenance, and auditability;
- MCP, ACP, or comparable agent/tool protocols;
- sandboxing, secrets management, cost controls, tracing, and observability;
- clear separation between advisory output and authorized external action.

Please be prepared to show what you personally designed and implemented, what failed, and how the system was evaluated and controlled.

Payment-processing and fintech experience

Direct payment-processing knowledge is strongly preferred. You should understand—or be able to demonstrate credible experience with:

- merchant acquiring and the roles of merchants, processors, gateways, acquirers, ISOs/agents, and referral partners;
- merchant lead-to-onboarding and account-lifecycle workflows;
- pricing, statements, residuals, portfolio economics, and partner attribution;
- underwriting boundaries and the distinction between sales support and approval authority;
- KYC/KYB, AML, PCI scope, restricted financial data, and least-privilege access;
- disputes, chargebacks, risk signals, and operational escalation;
- CRM and system-of-record authority, including safe integration patterns.

Industry vocabulary alone is not enough. We need someone who understands how product and data decisions affect a merchant-services business.

Expected working style

- Senior and hands-on; the named lead must remain actively involved.
- Evidence-based and direct about uncertainty.
- Comfortable inheriting a partially defined system without demanding a wholesale rewrite.
- Able to communicate technical decisions clearly to a non-engineering founder.
- Willing to work within human approval, security, compliance, and data-governance boundaries.
- Uses DATAONE-controlled repositories, accounts, documentation, and deployment environments.
- Provides weekly demonstrations and written evidence of completed acceptance criteria.

Out of scope for the initial phase

- full MIN implementation;
- processing transactions or moving funds;
- autonomous underwriting, merchant approval, pricing approval, or compliance decisions;
- use of live merchant PII, banking data, processor credentials, or production secrets during discovery;
- uncontrolled CRM, email, advertising, social, or external-system writes;
- a full platform rewrite without an evidence-backed and approved reason;
- launching both Hermes and Buzz as overlapping production systems.

What to include in your application

1. Identify the person who will be the accountable product engineering lead and describe their weekly involvement.
2. Share two relevant systems you personally helped build. For each, explain the users, business outcome, architecture, your contribution, production status, and a lesson learned.
3. Describe one agentic system you operated beyond a demo. Explain its tools, permissions, human approvals, evaluations, observability, failure recovery, and cost controls.
4. Explain your direct experience in merchant services, payments, fintech, or another regulated financial workflow.
5. In a few paragraphs, explain how you would decide the boundaries between an internal operating platform, a sales copilot, an advisory agent/orchestrator, and a human-agent workspace.
6. Describe how you would validate an inherited architecture before proposing implementation.
7. State what information you need to provide a credible timeline and cost range.
8. Provide your availability, location/time zone, proposed team, rate structure, and two client references.

Please do not send a generic agency deck. Applications that do not identify the actual lead and directly answer the questions above will not move forward.

Selection process

1. Written application and evidence review.
2. Structured interview with the named lead.
3. Reference and portfolio verification.
4. NDA and access to a sanitized document package.
5. **Paid, fixed-scope discovery and architecture review.**
6. Review presentation and questions.
7. Separate decision on an implementation statement of work.

The paid review is not a guarantee of the implementation contract.

Location: Remote (targeting UTC+13)
Schedule: Friday, Sunday, Tuesday (6hr active shifts 06:00 - 12:00 UTC) | Rest days for synthesis
Stack: TypeScript, Node 20+, PostgreSQL, Railway, Zod, Vitest, GitHub Actions

About the Role
We're building a vertical SaaS factory that configures and deploys dedicated customer instances autonomously. Our engineering runs as a continuous 24-hour relay across 4 global hubs on active days (Fri/Sun/Tue), with deep rest and architectural thinking on the days between.

You'll own a 6-hour shift: 3 hours of uninterrupted solo building, followed by 3 hours of live handoff with the incoming engineer. Your code ships as verified PRs with structured Brick Reports. CI validates. Agents orchestrate. You stay in code.

What You'll Do
-Build platform infrastructure in TypeScript (strict types, Zod schemas, Express routes, PostgreSQL)
-Own bricks end-to-end: read the spec, build it, verify it (typecheck + tests + CI), open the PR
-Execute Blind Trust handoffs: pull the current state fresh, form your own understanding, then sync with the outgoing engineer
-Post Strategic Anchors at shift-end: crystallize the deep architectural question your work surfaced
-Work within a spec-driven process (/populus:start routes your scope, engineering standards are auto-loaded)

What You Are
-TypeScript-native: You don't write any. You think in Zod schemas and strict interfaces. Types are documentation.
-Autonomous: You don't need a manager to unblock you. You read specs, build, and verify without hand-holding.
-Async-first: You communicate through code quality, PR descriptions, and structured brick reports, not Slack threads.
-UTC-comfortable: You schedule your work life around a UTC anchor, not your local wall clock.
-Infrastructure-fluent: Railway, PostgreSQL, GitHub Actions, 1Password (op://), Cloudflare are your daily tools.

What We Offer
-Deep work, not meetings. 3 hours of uninterrupted solo time every active day.
-3 active days per week. The rest is for thinking, reading, and living.
-A system that doesn't depend on you being available 24/7. The relay means you log off clean.
-Claude Code as your pair programmer. AI-augmented engineering is the default.
-A real product with real customers. Not a research project.

Lead Agentic Ai Developer

About Avarlo

Avarlo builds and manages custom AI systems for businesses.

We are urgently hiring an experienced AI Agent Developer with strong hands-on experience using Claude, Claude Code, the Anthropic API, Claude Agent SDK, and/or OpenClaw.

This person will build internal agents for Avarlo and custom agent systems for our clients. You will also help deploy, maintain, troubleshoot, and improve these systems over time.

This is not a basic chatbot or prompt-writing role. We need someone who can build secure, dependable agents that use tools, connect to business software, and complete multi-step workflows.

Responsibilities

* Build Claude-powered and OpenClaw agents
* Create internal Avarlo agents and client-facing systems
* Design single-agent and multi-agent workflows
* Build tools, skills, MCP servers, and integrations
* Connect agents to APIs, CRMs, databases, calendars, email, documents, and messaging platforms
* Create memory, retrieval, and context-management systems
* Add human approval and escalation steps
* Deploy, host, monitor, and maintain agent infrastructure
* Test reliability, security, accuracy, and performance
* Troubleshoot failures and optimize active systems
* Document builds so they can be maintained and scaled

You should be able to understand a business process, recommend the right architecture, and build the solution with limited supervision.

Example Projects

Initial projects may include:

* Sales research and lead-intelligence agents
* Client-onboarding agents
*Training Ai Voice Agents
* Internal operations assistants
* Project-management and fulfillment agents
* Proposal and reporting agents
* Agents that monitor client systems
* Multi-agent internal workflows

Client systems may support research, document processing, CRM updates, customer service, administrative work, reporting, and other multi-step business processes.

Required Experience

Strong experience with several of the following:

* Claude, Claude Code, Anthropic API, or Claude Agent SDK
* OpenClaw
* MCP servers and tools
* Multi-agent orchestration
* Tool calling and structured outputs
* Agent memory and retrieval systems
* APIs, webhooks, OAuth, and authentication
* Python, TypeScript, or JavaScript
* Docker, GitHub, databases, and cloud deployment
* Logging, monitoring, testing, and evaluations

The ideal candidate has built and deployed agents used in real business environments.

Security and Reliability

You should understand how to:

* Secure API keys and client credentials
* Separate client data and environments
* Apply least-privilege permissions
* Protect against prompt injection
* Add approval steps for sensitive actions
* Create logs, monitoring, and recovery procedures
* Test agents before production launch

We are looking for someone who understands the difference between a prototype and a reliable production system.

Long-Term Opportunity

We expect to begin with a paid technical trial.

Successful work may lead to:

* Consistent weekly projects
* Ownership of Avarlo’s technical fulfillment
* Ongoing client maintenance
* Development of reusable agent systems
* Input into technical strategy
* A long-term technical leadership role

How to Apply

Begin your proposal with:

**AVARLO AGENTS**

Please answer:

1. What have you personally built using Claude or OpenClaw?
2. Describe one production agent you built that used tools and completed multi-step tasks.
3. Have you built MCP servers, agent skills, or multi-agent systems?
4. Which programming languages and infrastructure tools do you use?
5. How do you secure client data, credentials, and agent permissions?
6. How do you test and monitor agents after deployment?
7. Please share relevant case studies, videos, GitHub repositories, or documentation.
8. What is your weekly availability and hourly rate?
9. Are you interested in a long-term role with Avarlo?

Generic proposals without specific technical examples will not be considered.

We are looking to hire immediately.

I need a hands-on .NET/React developer to take over maintenance of an existing production web app (React/TypeScript, .NET 6/ASP.NET Core, PostgreSQL, AWS) during a startup pilot — fixing bugs and keeping the platform stable, with clear, itemized pricing. Must be available during Eastern (US) business hours and able to ramp up quickly on someone else's codebase.

Location: Remote (targeting UTC-5, Colombia/Peru)
Schedule: Friday, Sunday, Tuesday (6hr active shifts 06:00 - 12:00 UTC) | Rest days for synthesis
Stack: TypeScript, Node 20+, PostgreSQL, Railway, Zod, Vitest, GitHub Actions

About the Role
We're building a vertical SaaS factory that configures and deploys dedicated customer instances autonomously. Our engineering runs as a continuous 24-hour relay across 4 global hubs on active days (Fri/Sun/Tue), with deep rest and architectural thinking on the days between.

You'll own a 6-hour shift: 3 hours of uninterrupted solo building, followed by 3 hours of live handoff with the incoming engineer. Your code ships as verified PRs with structured Brick Reports. CI validates. Agents orchestrate. You stay in code.

What You'll Do
-Build platform infrastructure in TypeScript (strict types, Zod schemas, Express routes, PostgreSQL)
-Own bricks end-to-end: read the spec, build it, verify it (typecheck + tests + CI), open the PR
-Execute Blind Trust handoffs: pull the current state fresh, form your own understanding, then sync with the outgoing engineer
-Post Strategic Anchors at shift-end: crystallize the deep architectural question your work surfaced
-Work within a spec-driven process (/populus:start routes your scope, engineering standards are auto-loaded)

What You Are
-TypeScript-native: You don't write any. You think in Zod schemas and strict interfaces. Types are documentation.
-Autonomous: You don't need a manager to unblock you. You read specs, build, and verify without hand-holding.
-Async-first: You communicate through code quality, PR descriptions, and structured brick reports, not Slack threads.
-UTC-comfortable: You schedule your work life around a UTC anchor, not your local wall clock.
-Infrastructure-fluent: Railway, PostgreSQL, GitHub Actions, 1Password (op://), Cloudflare are your daily tools.

What We Offer
-Deep work, not meetings. 3 hours of uninterrupted solo time every active day.
-3 active days per week. The rest is for thinking, reading, and living.
-A system that doesn't depend on you being available 24/7. The relay means you log off clean.
Claude Code as your pair programmer. AI-augmented engineering is the default.
-A real product with real customers. Not a research project.

Job Title
Full-Stack Developer for TEDOS AI Platform: Maintenance, Bug Fixes, and New Feature Development

Job Description
TEDOS is an AI-powered business operating system that helps coaches, consultants, experts, agencies, and high-ticket businesses build complete client acquisition systems. The platform creates funnels, messaging, offers, scripts, emails, CRM workflows, automations, and client dashboards.

The original TEDOS system is already built. We are now looking for a reliable full-stack developer to help maintain the platform, fix bugs, improve existing features, support customer issues, and develop new features based on direct founder direction.
The founder is the master designer, product architect, and strategic lead. You will not be responsible for inventing the product vision. Your role is to execute cleanly, solve technical problems, improve the product, and help keep TEDOS stable as we continue scaling.
Responsibilities
• Maintain and improve the existing TEDOS application.
• Fix bugs reported by customers or internal users.
• Develop new product features based on founder direction.
• Improve existing AI workflows, funnel-building logic, dashboards, and user flows.
• Work with APIs and integrations such as GoHighLevel, Close CRM, HubSpot, Zoom, OpenAI, Stripe/payment systems, and webhooks.
• Help troubleshoot customer issues quickly and professionally.
• Improve frontend layout, responsiveness, UI polish, and user experience.
• Test all updates before they are pushed live.
• Keep code clean, organized, and documented.
• Communicate progress daily.
New Feature Development
You will also help build new TEDOS features as the product expands. New feature work may include:
• New TEDOS product modules
• Funnel builder improvements
• AI content generation flows
• Client dashboards
• Sales dashboards
• CRM integrations
• Admin tools
• Reporting and analytics
• Onboarding flows
• Customer support tools
• Workflow automation
Required Skills
• Strong JavaScript / TypeScript
• React, Next.js, or similar frontend framework
• Node.js and/or Python backend experience
• API integration experience
• HTML/CSS with strong attention to clean UI implementation
• Experience with SaaS apps, dashboards, CRM tools, or automation platforms
• Git/GitHub workflow
• Ability to debug existing code without breaking other parts of the system
• Good written English
• Reliable daily communication
Nice To Have
• GoHighLevel API experience
• Close CRM API experience
• OpenAI API experience
• Stripe or payment integration experience
• SaaS customer support experience
• Funnel builder or landing page builder experience
• Experience working directly with a founder
• UI/UX implementation skills
Who This Role Is For
This role is for a developer who is reliable, detail-oriented, and good at execution. You should be comfortable maintaining an existing product, fixing problems, and building new features from clear direction.
Who This Role Is Not For
This is not for someone who wants to redesign the entire product without direction, disappear for days, overcomplicate tasks, or ship untested work.
Location
Remote. Preference for developers in India or the Philippines.
Hours
Part-time to start, with potential to grow into full-time.
Pay
Please include your hourly rate. Compensation depends on experience and quality.
How To Apply
Please send:
1 Your resume or portfolio.
2 Links to 2-3 SaaS apps, dashboards, automation tools, or AI products you helped build.
3 Your hourly rate.
4 Your weekly availability.
5 A short answer: “How do you debug a customer-reported issue in a live SaaS app?”

Hoi Mosh

Hoffe es geht Dir gut. Wir haben auf der neuen Robinhood Blockchain (EVM) ein Launchpad für Memecoins gebaut. Allerdings muss da noch ein Profi drüber für den Audit und ein Paar andere Sachen. Falls Du Zeit und Lust hast, könnten wir gerne die Details besprechen. Wäre dringend 😅

PS: Wir bauen und launchen ständig Sachen, einen guten Dev in der Schweiz zu haben, wäre generell ein riesen Vorteil für uns. Unser anderes Projekt haben wir auf Base gebaut, das braucht auch noch einen Audit.

Liebi Grüess
Armin

Project Overview

AI Bookkeeper is an AI-powered bookkeeping and accounting SaaS platform designed for small businesses and accounting firms. The goal of this project is to build a modern, high-performance, and SEO-optimized marketing website that clearly communicates the product’s value and supports future scalability.

We are seeking an experienced freelance Next.js developer to design and develop a fully custom-coded website for AI Bookkeeper. The website must be fast, responsive, secure, and built with best practices for modern SaaS platforms.

The main marketing website will be fully custom built, while a headless CMS will be used only for managing blog content and other frequently updated sections.

Website Structure

The project will include multiple domains and subdomains to support different parts of the platform:

- "aibookkeeper.com" — Main marketing website
- "app.aibookkeeper.com" — Customer application portal
- "stage.aibookkeeper.com" — Staging and testing environment
- "developer.aibookkeeper.com" — Future developer and API documentation portal
- "api.aibookkeeper.com" — Backend API subdomain

The initial focus of this engagement is the public marketing website, blog integration, subdomain routing setup, deployment configuration, and foundational application routing structure.

Scope of Work

1. Fully Coded Marketing Website

The website must be developed using modern technologies including:

- Next.js (latest version)
- TypeScript
- React
- Tailwind CSS (or equivalent responsive styling framework)
- Modular and reusable component architecture

The solution must be fully custom-coded and must not rely on WordPress, Webflow, Wix, Elementor, or any similar no-code/low-code page builders. UI libraries may be used where appropriate, but the final design must be unique, professional, and tailored for a U.S.-based accounting SaaS product.

2. Main Website Pages

The initial set of pages will include:

- Home
- Features
- How It Works
- Pricing
- QuickBooks Integration
- For Small Businesses
- For Accountants and Bookkeepers
- Security
- About Us
- Contact Us
- Book a Demo
- Blog
- Privacy Policy
- Terms & Conditions

Final content structure and design references will be provided separately.

3. Blog CMS Integration

The blog must be fully designed and developed as part of the website, with a headless CMS integrated only for content management.

The CMS should support:

- Blog title
- Blog content
- Featured image
- Author
- Category
- Publication date
- SEO title
- Meta description
- URL slug

Preferred CMS options include:

- Sanity CMS
- Headless WordPress
- Other approved headless CMS solutions

The marketing team should be able to manage blog content independently without affecting the website’s design or codebase.

4. Subdomain-Based Routing

The system must support proper routing across multiple subdomains:

- "aibookkeeper.com" — Marketing website
- "app.aibookkeeper.com" — Customer portal
- "stage.aibookkeeper.com" — Staging environment

Implementation should use Next.js Middleware or proxy-based routing depending on the architecture and Next.js version.

Key requirements:

- Accurate hostname detection
- Support for local development
- No rewrite or redirect loops
- Preservation of visible subdomain URLs
- Proper handling of static assets and API routes
- Compatibility with Vercel, Cloudflare, or similar reverse proxies

5. Hosting and Deployment

The preferred infrastructure setup includes:

- Vercel for the Next.js frontend
- Google Cloud for application/backend services
- Cloudflare for DNS, security, and performance optimization

The developer will be responsible for:

- Connecting GitHub repository
- Setting up CI/CD pipelines
- Configuring production and preview deployments
- Domain and subdomain configuration
- Environment variable setup
- DNS record configuration
- Staging and production environment separation
- Basic deployment documentation

6. SEO Requirements

The website must be fully optimized for search engines, including:

- Server-side rendering or static generation where appropriate
- Editable meta titles and descriptions
- Open Graph and social sharing metadata
- Canonical URLs
- XML sitemap generation
- Robots.txt configuration
- Schema markup implementation
- Proper heading hierarchy
- Clean and semantic URLs
- Image alt attributes
- Fast load performance
- Mobile-first responsive design

Important pages must not rely solely on client-side rendering for SEO-critical content.

7. Performance Requirements

The website must be optimized for:

- Fast page load times
- Core Web Vitals compliance
- Image optimization
- Font optimization
- JavaScript bundle reduction
- Code splitting
- Lazy loading
- Caching strategies
- Mobile performance

8. Security Requirements

The implementation must follow industry-standard security practices:

- Secure environment variable handling
- No hardcoded secrets or API keys
- Input validation for all forms
- Spam protection (contact/demo forms)
- Secure HTTP headers
- Dependency vulnerability checks
- Restricted staging access where required

9. Forms and Integrations

The website may include:

- Contact form
- Book a demo form
- Newsletter subscription
- Login redirect to application
- Email notification system
- Future CRM integration support

All forms must be properly implemented and connected to approved endpoints or services.

Expected Deliverables

The freelancer will deliver:

1. Complete Next.js source code
2. Fully responsive website (desktop, tablet, mobile)
3. Reusable component architecture
4. Blog CMS integration
5. Subdomain routing implementation
6. GitHub repository setup
7. Vercel deployment configuration
8. Custom domain setup
9. Staging and production environments
10. SEO implementation
11. Technical documentation
12. Deployment guide
13. CMS usage guide
14. Full project handover (code, access, credentials)
15. Post-launch bug fixing support (as agreed)

Required Skills

The ideal candidate should have strong experience in:

- Next.js (App Router preferred)
- React
- TypeScript
- SSR / SSG / ISR strategies
- Tailwind CSS
- Middleware and routing logic
- Headless CMS integration
- GitHub workflows
- Vercel deployment
- DNS and subdomain configuration
- Responsive UI/UX development
- Technical SEO
- Performance optimization

Experience with Google Cloud and Cloudflare is a plus.

Preferred Experience

Preference will be given to developers who have built:

- SaaS platforms
- Fintech or accounting tools
- AI-based products
- Multi-subdomain architectures
- Headless CMS-driven websites
- U.S.-focused B2B marketing websites

Important Project Conditions

- The website must be fully custom-coded
- No WordPress, Webflow, Wix, or similar builders for the main site
- CMS is strictly for content management only
- Design and UI must remain code-controlled
- All intellectual property will belong to AI Bookkeeper
- Strict confidentiality is required
- Code reuse in other projects is not permitted
- All third-party tools must be disclosed before use

Application Requirements

Applicants should provide:

1. Relevant Next.js experience
2. Links to three similar live projects
3. Role and contribution in each project
4. Proposed technology stack
5. Recommended CMS solution
6. Estimated timeline
7. Fixed-price quote
8. Post-launch support duration
9. Confirmation of individual or team execution
10. Confirmation of full code and IP transfer

Questions

1. Have you implemented subdomain-based routing in Next.js?
2. What is the difference between SSR and SSG?
3. Which pages would you use SSR, SSG, or ISR for?
4. How do you prevent rewrite loops in middleware or proxy setups?
5. How do you ensure CMS only manages content, not design?
6. How do you structure staging and production deployments?
7. How do you secure environment variables and API keys?
8. How do you optimize SEO and Core Web Vitals?
9. Can you provide full documentation and handover?
10. Are you available for post-launch support?

Skills: PHP, Website Design, SEO, CSS, HTML, Cloudflare, Next.js, Tailwind CSS, Vercel, AI Development

Hi,

I’m looking for an elite software engineer and reverse engineering specialist with expert-level knowledge across a wide range of technologies. I’m looking for someone who can analyze, understand, and work with virtually any software stack or programming language.

Required expertise includes, but is not limited to:

* Reverse Engineering
* C, C++, C#
* .NET Framework and .NET (Core/5/6/7/8+)
* Win32 API
* Windows Internals
* x86/x64 Assembly
* DLL analysis and development
* Static and dynamic binary analysis
* Debugging (user mode and kernel mode)
* Low-level systems programming
* Cryptography and cryptographic libraries
* USB protocol analysis
* Serial communication
* Device communication protocols
* Driver architecture and Windows drivers
* Memory analysis
* Performance optimization
* Software architecture and large-scale codebases
* Python
* Rust
* Go
* Java
* JavaScript/TypeScript
* PowerShell
* Bash
* Git and modern development workflows

The ideal candidate should be able to understand unfamiliar codebases quickly, analyze complex software architectures, debug difficult issues, and develop robust, high-performance solutions.

I have a large collection of technical materials, including source code, DLLs, binaries, protocol captures, logs, and documentation. I’m looking for someone who can review everything, understand the complete architecture, and contribute at the highest professional level.

If you have extensive experience with complex low-level software projects and believe you have the skills to tackle virtually any engineering challenge, I’d like to discuss the project, timeline, and budget.

I have a complete USBPcap capture of the communication workflow. The objective is to analyze the recorded communication, fully understand the protocol and execution flow, and use that understanding to develop an independent engine that reproduces the same documented behavior and functionality.

The project requires someone with extensive experience in USB protocol analysis, reverse engineering, binary analysis, low-level Windows development, and systems programming. You should be comfortable working with protocol captures, DLLs, binaries, and debugging tools to understand how the components interact and to implement a robust, high-performance engine based on the observed communication.

If you have experience with projects of this complexity, I’d be interested in discussing the technical details, timeline, and budget.

Skills: C Programming, Python, .NET, Testing / QA, C# Programming, Cryptography, C++ Programming, Assembly, Debugging, Reverse Engineering

We are looking for an experienced Full Stack Developer to help build and launch a scalable multi-vendor marketplace from the ground up. This is a pre-launch project, so you'll play a key role in designing, developing, and implementing core platform features that will support buyers, sellers, and administrators.
We're seeking someone who is proactive, detail-oriented, and capable of delivering clean, maintainable, and scalable code.
Responsibilities
• Develop the marketplace frontend and backend.
• Build secure user authentication and authorization.
• Implement vendor registration, onboarding, and dashboard features.
• Create product management, inventory, categories, and search functionality.
• Develop shopping cart, checkout, and payment gateway integration.
• Implement order management, shipping, and customer notifications.
• Build an admin panel for managing vendors, users, products, and orders.
• Optimize application performance, security, and scalability.
• Integrate third-party APIs where required.

Required Skills
• Strong experience with full stack web development.
• Proficiency in JavaScript/TypeScript.
• Experience with React, Next.js, Vue, or similar frontend frameworks.