Backend Engineer – API Integrations, Messaging & Automation

Backend Engineer – API Integrations, Messaging & Automation 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. # # #