Jaspersoft Integration Developer – Word Document Export We are looking for a developer to build a custom Jaspersoft integration that improves our Word document export capabilities, similar to Aspose. The ideal candidate can evaluate open-source vs. paid API options and deliver a working solution. Required Skills & Experience Proven experience with Jaspersoft Studio / JasperReports Server customization and plugin development Strong Java development skills (Jasper's core integration language) Experience building or extending Jaspersoft export options (custom exporters via the export menu/dropdown) or similar experience Hands-on experience with Word document generation libraries such as: Apache POI Aspose.Words docx4j Experience with PDF-to-Word conversion pipelines using tools such as: LibreOffice headless / LibreOffice UNO API pdf2docx (Python) ilovepdf, Smallpdf, or similar APIs Ability to evaluate and compare open-source vs. paid API solutions (cost, quality, licensing, support) Familiarity with REST API integration for third-party document services Nice to Have Experience with Aspose.Words or similar commercial document SDKs Knowledge of OOXML / .docx format internals Prior work integrating document conversion into enterprise reporting platforms Python or Node.js experience for conversion microservice development Experience with one or more of the following: PDFBox iText / OpenPDF Pandoc OnlyOffice or similar document conversion tools Experience converting between: Jasper report output to PDF PDF to Word/DOCX HTML to Word/DOCX DOCX post-processing and cleanup Deliverables Expected A working Jaspersoft export plugin that adds an improved Word (.docx) export option to the export dropdown menu A documented recommendation on open-source vs. paid API options (with trade-offs) A conversion pipeline (e.g., report → PDF → Word, or direct-to-Word) Clean, maintainable code with setup/deployment documentation What We're Building A replacement for the default Jaspersoft Word exporter that produces cleaner, better-formatted .docx output — with the conversion option accessible directly from the Jaspersoft export menu, just like the built-in PDF and Excel export options.

We are a digital marketing SaaS startup called Twelve Tribe. Our platform connects small business clients to Meta, Google, TikTok, and LinkedIn ad accounts with zero-touch onboarding. The software is built and ready to go — we just need the final platform approvals to unlock ad creation for our clients. You will not write any code. This is a 100% administrative task — filling out forms, recording a brief screencast, and tracking approval status across four platforms. WHAT YOU WILL DO: 1. Meta (Facebook / Instagram Ads) • Submit our app for App Review • Request permissions: ads_management, ads_read, business_management, pages_show_list, pages_read_engagement • Record a 2-minute screencast showing our platform in action • Submit Business Verification documents • Monitor approval status and respond to any platform requests 2. Google Ads • Apply for Basic Access to the Google Ads API • Fill out the API use case form • Link our developer token to the correct Google Ads Manager account • Monitor for approval 3. TikTok for Business • Apply for Marketing API access (separate from Login Kit, which we already have) • Provide our app description and intended use case • Monitor for developer approval 4. LinkedIn Marketing Solutions • Apply for Marketing Developer Platform (MDP) access • Submit our app for review with the correct use case • Monitor for approval (typically 10–14 days) -------------------------------------------------- WHAT YOU NEED: • A clear, professional writing style for filling out platform forms • Basic screen recording ability (Loom or similar) • Patience — most approvals take a few business days, some up to 2 weeks • Comfort reading platform documentation and following exact instructions • A Gmail account and basic familiarity with Google services NO CODING REQUIRED. NO DESIGN REQUIRED. -------------------------------------------------- WHAT WE WILL PROVIDE: • Step-by-step checklist for every platform with exact links • Privacy Policy and Terms of Service URLs ready to paste • Screencast script and talking points • Direct answers to any questions within 24 hours • Access credentials to the relevant platform dashboards

I need a full stack developer to build a simple web application called WriteTheDeal. The frontend design is already 100% complete — I have fully designed HTML files ready to hand over. You are building the backend and making everything functional. This is Phase 1 of a larger project — if this phase goes well, there is a strong chance of continued paid work for Phase 2 with additional features. Here is exactly what needs to be built: 1. An embeddable JavaScript widget that dealers paste on their website with one line of code. When a buyer clicks Make an Offer a modal opens with a form collecting the following information from the buyer: offer amount, first name, last name, email address, phone number, and card details via Stripe. 2. Payment intent question — the offer form must ask the buyer how they intend to pay for the vehicle, with three options presented as selectable buttons: Finance through the dealership, Cash, or Outside lending. This is a required field and must be completed before the offer can be submitted. The dealer must see this answer clearly displayed alongside the rest of the offer details in their dashboard. 3. Trade-in question — the offer form must ask the buyer “Do you have a trade-in?” with a Yes or No option. If the buyer selects Yes, the following additional fields must appear: Vin Number - Year, Make, Model, Trim, Mileage, and Condition. Condition must be a dropdown with exactly these three options: “Showroom condition,” “Good — some scratches here and there, may need new tires,” and “Poor — needs a lot of TLC.” All trade-in details must be clearly visible to the dealer in their dashboard alongside the rest of the offer. 4. Notes field — both the buyer and the dealer must be able to add a note at any point in the process. The buyer can add a note when submitting their original offer. The dealer can add a note when responding to an offer. All notes must be stored and visible in the full offer history so both sides can see the complete conversation thread at any time. 5. A Stripe integration using Stripe Connect — when a dealer accepts an offer, the $1,500 deposit must go directly into the dealer’s own connected bank account, not mine. I must never receive the buyer’s deposit money in my account at any point. I earn only a separate platform fee automatically deducted at the time of each transaction. The buyer’s card must be authorized but not charged at the time of offer submission — it is only captured when the dealer accepts. If the dealer declines, the hold must be released immediately and the buyer is never charged. 6. ADF/XML lead delivery — when a buyer submits an offer, the system must automatically send a correctly formatted ADF/XML lead email to the dealer’s CRM intake email address. This must work with all major automotive CRMs including VinSolutions, ELEAD, DealerSocket, DriveCentric, ProMax, and AutoRaptor. The lead email must include all offer details — offer amount, buyer contact info, payment intent, trade-in details, and any notes. 7. Instant dealer notifications — the moment a buyer submits an offer, the dealer must automatically receive both an email notification and a text message notification containing the buyer’s name, offer amount, and a direct link to view the full offer in their dashboard. Text messages must be sent using Twilio. 8. Dealer dashboard — a secure, password-protected login page where dealers can see all of their incoming offers. Each dealer must only ever see their own offers and their own buyers — no dealer should ever be able to see another dealer’s data. The dashboard must clearly display for each offer: buyer name, email, phone, offer amount, payment intent, trade-in details if applicable, notes, and the full offer history. Each offer must have three action buttons: Accept, Decline, and Counter Offer. 9. Counter-offer functionality — in addition to Accept and Decline, the dealer must be able to send a counter-offer back to the buyer with a revised amount and an optional note. The buyer must receive an email and text notification when a counter-offer is sent. The buyer must be able to accept the counter, decline it, or send their own counter back. This back-and-forth negotiation must be able to continue for multiple rounds until one side accepts or declines. Every round of the negotiation must be stored and visible in the offer history for both the buyer and the dealer. 10. Maximum discount threshold with automatic decline — each dealer must be able to set a maximum percentage off MSRP they are willing to consider, for example 5%. If a buyer submits an offer that falls below this threshold — meaning the discount requested is greater than the dealer’s set maximum — the system must automatically decline the offer immediately without the dealer needing to take any action. The buyer’s card must never be charged on an auto-declined offer. This threshold setting must be adjustable by the dealer at any time from their dashboard settings, and must be settable as both a store-wide default and on a per-vehicle basis. 11. Salesperson send-link tool — inside the dealer dashboard there must be a tool where a salesperson can enter a customer’s name, email, phone number, offer amount, and vehicle details, and the system generates a unique pre-filled link. When the customer opens this link the offer form loads with all their details already filled in — they only need to add their card to submit. The salesperson must be able to send this link via email or text directly from within the dashboard. 12. Admin panel for me — I need a completely separate and private admin login at a secure URL. From this panel I must be able to: add a new dealer by entering their basic info, automatically generate their unique dealer ID, automatically generate their dashboard login credentials, automatically generate the exact widget code snippet ready to send to their webmaster, and view all dealers and all offers across the entire platform. I must never need to contact the developer to add a new dealer after launch. 13. Individual dealer login accounts — each dealer must have their own unique username and password to access their dashboard. When they log in they must only see their own data. No dealer should ever be able to access or view another dealer’s offers, buyers, or settings. 14. Public website — I have a fully designed landing page and pricing page already built as HTML files. I need these deployed and made live at writethedeal.com as the public-facing marketing website for the product. 15. All accounts must be created under my ownership — please set up all hosting, database, Twilio, and any other third-party service accounts using my email address and my payment method from day one. Even though you will be handling the technical setup, I must own every account. I must be able to access, manage, and if necessary transfer every account without needing your involvement after the project is complete. Please use Node.js for backend and PostgreSQL for the database, deployed on Render or Railway. If you strongly prefer a different approach please explain why in your proposal, but I would like to stick with widely used tech so I can easily find another developer to maintain or update the product in the future if needed. Deliverables: — Fully working embeddable widget with all form fields described above — Payment intent question (finance with dealer, cash, or outside lending) — Trade-in question with year, make, model, trim, mileage, and condition dropdown — Notes field on every offer visible to both buyer and dealer — Stripe Connect integration with deposits going directly to dealer accounts — ADF/XML lead delivery to dealer CRM intake email — Email and SMS notifications to dealers via Twilio — Dealer dashboard with accept, decline, and counter-offer functionality — Full negotiation history stored and visible on every offer — Maximum discount threshold settings with automatic decline per dealer and per vehicle — Salesperson send-link tool with pre-filled customer links — Admin panel where I can add new dealers and generate widget codes myself — Individual dealer logins with complete data separation between dealers — Public marketing website deployed at writethedeal.com using my existing designs — All third-party accounts created under my ownership — Fully deployed and live on a real URL — A 20 minute Loom video walkthrough of the entire system — A simple plain-English document explaining how to add a new dealer from start to finish Timeline: 4 to 6 weeks Budget: $3000-$4000 fixed price for everything listed above, paid across 6 milestones Note on hiring: Before I hire anyone I will ask all candidates to explain in plain English how they would set up Stripe Connect so that the $1,500 deposit goes directly to the dealer’s bank account and never passes through my account. The clarity and accuracy of your answer to this question will be a significant factor in my hiring decision.

EQUEST FOR PROPOSAL (RFP) Temporary Marketing & Communications Support Society of American Florists (SAF) Contract Period: August 1, 2026 – November 15, 2026 Location: Remote (U.S.-based contractors only) PROJECT OVERVIEW The Society of American Florists (SAF) is seeking proposals from qualified freelancers or agencies to provide temporary marketing and communications support services on an hourly and/or project basis between August 1 and November 15, 2026. SCOPE OF WORK The following outlines the anticipated projects and deliverables. Priorities may shift slightly based on organizational needs. PROJECT 1: SAF ANNUAL CONVENTION 2026 Event Dates: August 18–21, 2026 Deliverables August 18-21: Event Social Media Coverage Repost tagged attendee content to SAF Instagram and Facebook Stories throughout the event (depending on tags about 10 stories daily). Post SAF content (provided via text by on-site staff) to SAF Instagram and Facebook Stories throughout the event (about 10-15 stories daily) Tag speakers, sponsors, exhibitors per guidelines. Create and publish daily recap social media post or reel (using the day’s content) at end of day, Aug. 18, 19 and 20. Create and publish final convention thank-you and recap post or reel at end of day on Aug. 21. August 18 & 19: Event Photography and slideshows Coordinate with SAF’s event photographer to obtain daily event photos each evening. Update general session slideshow presentations using event photography and save to folder for SAF staff by 10 PM on the evening of Aug. 18 and 19. By Wednesday, August 26: Post-event Content Develop and deploy approximately 10 convention-related press releases (emailed and posted to the SAF website). Receive event photography from on-site photographer and organize and upload to SAF Flickr albums. Create and deploy convention wrap-up email to attendees. SAF will provide: Photos and video from on-site staff via text message for posting. Detailed social media posting schedule with outlined dates, posts, tagging guidelines, and instructions for guidance. Access to SAF social media accounts, Flickr, website, Canva, and email marketing platform. Existing SAF branding assets, templates, and style guidelines will be provided. Email templates from prior convention campaigns for reference and reuse. PROJECT 2: PETAL IT FORWARD 2026 Project Period: September–October 2026 Event Date: October 14, 2026 Deliverables Weekly promotional email (Sept. 7 – Oct. 5) Day of social media reposting tagged content from participants on Facebook and Instagram Stories – about 30 posts (Oct. 14). Instagram highlight reel of event-day participation reposts. Post-event “thank you” email to all participants (Oct. 15). SAF will provide Campaign messaging direction, timelines, and event details. Previous Petal It Forward marketing and thank you emails and templates for reuse. Recipient lists. Approvals of all emails. PROJECT 3: PROFIT BLAST – MILFORD, CONNECTICUT Project Period: September–November 2026 Event Date: November 8, 2026 Deliverables Provide weekly marketing updates to SAF staff to share with stakeholders. Seven promotional emails throughout September and October (using existing assets). Three to four promotional social media posts in weeks leading up to event. On Nov. 8 post to SAF to Facebook and Instagram Stories throughout the event and tag sponsors and speakers (content provided by on-site staff and re-posting from attendees). Create Instagram highlight reel of event content. On Nov. 9 create a wrap up event social media post – tag sponsors and speakers Update event webpage content and promotional assets as needed. SAF will provide: Photos and video of event for social posting, sent via text. Access to existing email templates, Canva assets, and website backend. Event details, timelines, speaker information, and sponsorship assets. Strategic direction and approvals. PROJECT 4: SOCIAL MEDIA COORDINATION & CONTENT MANAGEMENT Ongoing Aug. through Nov. 15 Deliverables Participate in monthly 30-minute social media planning meeting for September content planning (Aug. 28, Sept. 28, Oct. 28); assign content to various social team members via Trello. Update SAF’s social media content calendar in Google Docs (template provided) Create 5–6 social media posts each month (inclusive of event posts listed above in projects). SAF will provide Existing branding guidelines and templates. Content ideas and posting for various social media categories (several staff members contribute to it). Access to Trello, Canva, Hootsuite, and SAF social media accounts. **Contractor is not responsible for full-time community management. PROJECT 5: EMAIL MARKETING & CONTENT CALENDARS Ongoing Throughout Contract Period Deliverables Update Google Doc marketing calendar with any changes to email and campaign schedules (as needed) Provide weekly marketing and email performance updates to SAF staff via Trello each Monday. Create and send monthly Retailer Top Picks email and related social promotion (first week of Sept, Oct. and Nov). Create and send Two Floral Management magazine announcement emails (end of August, end of October). Create and send/resend 3 virtual event promotional emails (Aug. 21/25; Sept. 4/8; Nov. 6/10) Create and send two monthly Aster promotional emails (as requested). Create and send one-off email campaigns as requested. Create and send press releases as needed. SAF will provide Existing email templates and prior campaign examples. Strategic direction, approvals, and campaign priorities. Google Doc calendar template with critical dates and deadlines. Access to Higher Logic/MagnetMail and texting platform. Target lists and audiences. PROJECT 6: WEBSITE CONTENT MANAGEMENT Ongoing Throughout Contract Period – as requested Deliverables Update SAF website pages and content; maintain homepage promotional banners (as requested). Upload Sept./Oct. and Nov./Dec. Floral Management magazine issues to the website. Update Retailer Top Picks webpage (first week of each month). SAF will provide: Existing page templates and branding assets. Copy, approvals, and strategic direction as needed. WordPress/Divi access and basic website training/documentation if needed. PROJECT 7: VENDOR & CREATIVE COORDINATION Ongoing Throughout Contract Period Deliverables Coordinate marketing and design requests from SAF staff with freelance graphic designer as needed. Send materials to SAF staff for approval of brand consistency and accuracy before finalizing. SAF will provide Access to existing brand guidelines and marketing assets. Strategic direction and final approvals. Final creative approvals will remain with SAF staff. PROPOSAL REQUIREMENTS Interested contractors should submit the following: Company overview and relevant experience Description of the individual(s) who would perform the work Proposed pricing structure (hourly, project-based or blended) Relevant work samples or portfolios Estimated availability during the contract period References (optional) We thank all applicants for their interest in this position; however, only those selected for an interview will be contacted. ABOUT SAF The Society of American Florists (SAF) is the national trade association representing all segments of the U.S. floral industry, including retailers, wholesalers, growers, and suppliers. SAF provides education, advocacy, networking opportunities, events, and business resources that help floral professionals grow and succeed. SAF reserves the right to select one contractor for all projects or multiple contractors for individual projects and may modify the scope of work based on organizational needs and budget considerations.

We run a white-label health platform. The core app already exists and is in good shape — passwordless magic-link auth, row-level security / tenant isolation, PHI kept out of analytics and logs, server-side data handling, encryption in transit and at rest. This is not a greenfield build. We need a developer to close a specific, bounded set of HIPAA technical-safeguard gaps and security-test the result. Stack: TypeScript, Next.js (App Router, Server Actions), Supabase (Postgres + RLS), Vercel. What you'll build (quote EACH item separately, not a lump sum) 1. Audit logging (highest priority) Append-only, immutable audit_log table in Postgres (DB triggers/grants block UPDATE/DELETE; RLS insert + scoped select only) A single reusable helper called at every PHI touchpoint: record view, intake submit, checkout, auth issue/consume, admin reads, exports, deletions Acceptance: every PHI view/modify/export/delete + every auth event writes exactly one immutable row (who / what / when / where / success) 2. Rate limiting Applied to login, intake submit, and checkout endpoints. Per-IP and per-email. Postgres-backed (no new external service) Acceptance: over-limit requests return 429; login throttled per email + IP 3. Security headers HSTS (preload), CSP, X-Frame-Options DENY, X-Content-Type-Options, Referrer-Policy, Permissions-Policy CSP must still allow our third-party payment and identity-verification embeds Acceptance: securityheaders.com grade ≥ A, and checkout + verification flows still work end-to-end 4. Idle-session timeout Auto sign-out after N minutes of inactivity on the patient portal; confirm token expiry/refresh config Acceptance: idle session is invalidated and redirected to login 5. Patient data export + secure deletion Admin-initiated export of a single patient's full record (JSON) and a deletion workflow consistent with retention policy. Admin-run is fine — no patient-facing UI needed for v1 Acceptance: given a patient ID, export returns the full record; delete removes it and writes an audit row 6. Monitoring hooks (code portion) Emit structured events for failed logins, rate-limit trips, and audit anomalies (we wire the alerting) Acceptance: events emitted in a consumable, structured shape 7. Admin MFA + RBAC — conditional Only if there is a surface that reads PHI across multiple tenants: TOTP MFA + role checks + separate admin accounts. If no such surface is in scope, mark N/A Out of scope (do not quote) Managed infrastructure (encryption, backups, point-in-time recovery, SSL enforcement, dashboard-level config) — handled on our side All vendor BAAs Risk assessment, incident-response plan, DR plan, policies, training — our paperwork, not engineering Rebuilding anything already in place (listed above) Security testing (part of the deliverable) Per-layer tests for each item An adversarial pass: attempt to bypass rate limits, mutate/forge audit rows, access another tenant's data, inject PHI into analytics or URLs A short written summary of what was tested and the results Deliverables All code as reviewable PRs with tests passing The audit-log SQL migration as a standalone file (we apply it to our live database) A short doc listing every PHI touchpoint instrumented and every security header set Security-test summary Requirements Strong TypeScript + Next.js App Router (Server Actions, middleware) Solid Supabase/Postgres: RLS, triggers, grants, migrations Practical HIPAA technical-safeguards experience (audit controls, access control, integrity, transmission security) CSP tuning with third-party iframes (payments / identity verification a plus) Clean, test-covered work How to apply Quote each of the 7 items separately (line-by-line estimate), not a lump sum. Tell us specifically how you'd guarantee the audit log is immutable, and share one example of prior HIPAA or healthcare-data work.

We are seeking an experienced Integration/Solutions Engineer to design, develop, and maintain RESTful APIs for our clients. The ideal candidate will have a strong background in API development, integration, and documentation. You will work closely with our team to ensure seamless API integration and provide technical support throughout the implementation process. This is a full-time, long-term opportunity, and will consider contracted arrangements for someone who can deliver reliable and scalable API solutions. This role sits at the center of complex system interactions — translating real-world clinical, workforce, and operational workflows into reliable, scalable integrations. You’ll work closely with customers, internal engineering teams, and external vendors to connect systems such as EHRs, Workforce Management, Time & Attendance, and HRIS platforms. Success in this role requires strong technical fundamentals, comfort navigating ambiguity, and the ability to own integrations end-to-end — from discovery through delivery. What You’ll Do  Design, implement, and maintain integrations between healthcare systems, including: o EHR / EMR platforms o Workforce Management & Scheduling systems o Time & Attendance systems o HRIS and related operational systems  Lead technical discovery with customers to understand data flows, workflows, constraints, and integration requirements  Translate business and clinical requirements into clear technical designs, mappings, and implementation plans  Own data modeling, transformation, and mapping between disparate systems and schemas  Build and troubleshoot API-based, file-based, and event-driven integrations  Collaborate with internal product and engineering teams to ensure integrations are scalable, secure, and supportable  Manage integration delivery timelines, risks, dependencies, and stakeholder communication  Support authentication and identity integrations, including SSO patterns where applicable  Act as a technical escalation point for complex integration issues in production environments Required Experience & Skills Healthcare & Integration Experience  6+ years hands-on experience integrating healthcare systems such as EHRs, WFM, Time & Attendance, and/or HRIS platforms  Strong understanding of healthcare data concepts and operational workflows  Experience delivering integrations in regulated or high-compliance environments Technical Fundamentals  Strong API integration experience (REST, webhooks, JSON, XML)  High comfort with data structures, schemas, and transformations  Experience with data mapping, normalization, validation, and reconciliation  Ability to read, understand, and debug unfamiliar systems and data formats quickly Project & Delivery Ownership  Proven ability to manage integrations from discovery through go-live  Strong project management skills: scoping, sequencing, dependency tracking, and stakeholder communication  Comfortable working directly with customers and external technical teams Bonus / Nice-to-Have  Familiarity with healthcare interoperability standards such as FHIR and/or HL7  Experience with authentication and identity integrations, including: o SAML, OAuth, OpenID Connect o SSO integrations with enterprise identity providers  Experience working in multi-tenant SaaS environments  Exposure to healthcare compliance considerations (HIPAA, SOC 2, etc.) What Success Looks Like  Integrations are delivered on time, with clear expectations and minimal surprises  Data flows are reliable, well-mapped, and resilient to upstream/downstream changes  Customers and internal teams trust you to own complex integration work  Integration designs scale beyond a single customer or implementation

Backend Engineer – API Integrations, Messaging & Automation UPDATE: We have broadened the desired skillset beyond the messaging interface described below, to include a full-stack aspect as well - essentially, working hand-in-hand with our lead developer to accelerate completion of the overall build. Owning the messaging piece is still a key requirement, although we are looking for someone experienced and flexible enough to assist in other areas - including troubleshooting issues as they arise with clients during our current beta period. Our lead developer needs a capable ally to complete delivery on our timetable. We would love to hear more about why you could be that person. Thank you for your interest! We’re preparing to launch an industry-specific marketing and growth platform designed to help businesses deliver high-performance, data-driven marketing campaigns through intelligent automation. Our platform combines real-time POS data, advanced analytics, AI-powered workflow automation, campaign management, customer engagement tools, and marketing attribution into a single system that helps businesses market more effectively and measure real results. The core platform is essentially complete and in active pilot deployments with select customers. We’re preparing for commercial launch within 60-90 days and are looking for a Backend Integration Engineer – Messaging & APIs to help bring one of our final major capabilities online: integrated SMS and email communications. This is an opportunity to join an exciting pre-launch product at a pivotal stage while working alongside our lead developer on a focused, well-defined engineering project. About the Role Our platform already includes a robust CRM, AI-powered audience segmentation and journey builder capabilities, advanced analytics, and real-time integration with commercial point-of-sale (POS) systems, among other features. The automation engine is designed to create campaigns and customer journeys. Your role is to connect those capabilities to the outside world by integrating the platform with SMS and email providers, building reliable messaging workflows, processing messaging events, and enabling campaign attribution. You’ll become the primary developer responsible for messaging integrations while working closely with our lead developer, who owns the overall platform architecture. Responsibilities * Integrate the platform with an SMS provider already in use by existing pilot customers to support immediate campaign testing (API documentation/access already secured) * Implement the platform's production messaging capabilities for A2P 10DLC SMS and transactional email. * Process inbound webhooks. * Track message delivery, replies, clicks, and opt-outs. * Build campaign attribution using tracked links and landing pages. * Design integrations so additional messaging providers can be added with minimal changes to the platform. * Design the messaging architecture to support future short code implementation. * Integrate with email providers (Mailgun, SendGrid, or similar). * Build clean internal APIs between our platform and external messaging providers. * Write clean, maintainable, production-quality code and documentation. Required Skills * Backend software development * REST API integration * Webhook development and processing * SQL databases * Git * Experience integrating third-party APIs Experience with one or more of the following is highly desirable: * SMS messaging platforms * Twilio * Telnyx * Mailgun * SendGrid * A2P 10DLC * Queue processing * Background workers * Event-driven systems Contract Details This is a part-time contract expected to average approximately 10–20 hours per week over the next 2 months as we prepare for launch. The platform is in active pilot deployments, and this engagement is focused on completing one of the final capabilities before commercial release. While this engagement is intended to achieve a specific pre-launch objective, there may be opportunities for future work if the platform continues to grow and the working relationship is a good fit. Confidentiality Because this project involves proprietary software currently under development, applicants selected for interviews will be asked to sign a mutual Non-Disclosure Agreement before receiving demonstrations, architecture documentation, API documentation, or industry-specific information. To Apply Please answer the following: 1. Tell us about a communications or API integration project you’ve built that you’re proud of. 2. Which SMS and email platforms have you integrated with? 3. Describe your experience building webhook-driven systems. 4. If you were designing a messaging capability that initially supported one SMS provider but might later support several, how would you architect it so the rest of the application wouldn’t need to change? 5. Include links to your GitHub profile, portfolio, or examples of similar backend work, if available. 6. What is your expected hourly rate for this engagement? 7. What is your availability (days, times, etc.) and how soon can you start? To confirm you’ve read this posting in full, please begin your proposal with the words: “Integrated messaging is my world.” We’re looking for someone who enjoys connecting great software to the outside world through clean, scalable integrations. If you’re excited by messaging systems, APIs, and helping launch a SaaS product for real-world success, we’d love to hear from you. # # #

Project Overview: I am building Reseller Bro, a mobile utility application designed for on-the-go users to analyze product images and instantly retrieve live, accurate marketplace valuation metrics. The front-end user interface and layout are largely complete. The application uses an AI workflow for visual recognition and keyword generation, but the backend data retrieval and sync pipeline needs optimization for speed and absolute accuracy. I am looking for a highly skilled backend developer to conduct a code audit, repair a broken data aggregation pipeline, and optimize our database caching architecture. The Core Tasks: Database Cache Failure: The app currently fails to properly save or recall data on repeat queries. We need a high-speed caching layer so that if an item has already been searched once, the second lookup pulls from the internal database instantly (under 1 second). Data Sync & Engine Accuracy: The live data gathering process is currently unstable and occasionally returns empty results even for common consumer items with deep market history. Once the AI identifies the item keywords, the data pipeline must reliably sync and aggregate live pricing data from major public e-commerce and secondary marketplaces. Data Array / Tier Mapping Mix-up: The app currently handles item condition mapping poorly, sometimes displaying irrational pricing tiers (e.g., valuing low-tier condition higher than top-tier condition). We need a clean pre-fetch matrix that normalizes marketplace conditions into three clean categories on the first search and automatically filters out pricing anomalies or extreme statistical outliers. Required Technical Skills: Strong backend development experience using Node.js or Python. Advanced expertise in data extraction, handling complex HTML/JSON payloads, managing dynamic connection protocols, and optimizing marketplace data synchronization. Deep experience with database optimization and high-speed caching layers (such as PostgreSQL, Redis, or similar). Ability to step into an existing codebase, audit backend logic, and refactor code without disrupting the current frontend UI layout. 💰 Budget & Performance-Based Milestones ($700 Total) This contract is fixed-price and strictly milestone-driven based on functional performance metrics. No milestones will be released without successful live-testing verification. Milestone 1 ($150) - Code Review & Cache Repair: Audit the inherited repository. Fix the database caching system so that previously queried items bypass the live search entirely and load data instantly (under 1 second). Milestone 2 ($250) - Data Pipeline Optimization & Matrix Mapping: Fix the live data aggregation process to consistently pull reliable pricing from target market channels using the AI-generated keywords. Implement data-cleaning and normalization rules to ensure price tiers always reflect a logical tier structure while removing extreme outliers. Milestone 3 ($300) - Final Integration & Testing: Fully connect the optimized database cache, clean data sorting logic, and application backend into a finalized, stable build ready for deployment testing. To Apply: Please respond with your relevant experience in optimizing high-speed database caches and managing high-volume marketplace data aggregation. Please briefly explain your typical approach to ensuring stable, reliable data connections with public e-commerce platforms. Full project source files and existing code repositories will be shared with top candidates during the interview phase.

Deploy an existing Node.js/Express app and configure SMS. I have a complete, working dispatching app (Node + Express + SQLite, plain-JS frontend). I need someone to: (1) deploy it to Render or Railway with a persistent disk and HTTPS, (2) set up a Twilio account/number and wire in the credentials so it sends automated daily texts, (3) confirm the 6 AM scheduled texts fire reliably, and (4) be available for small tweaks afterward. Code, README, and deploy steps are all included. Should be a few hours for someone experienced. Please share similar Node deployment work you've done.