Production Build Specialist
Drips
- Cleveland, United States
- Remote
- Mid Level
- Posted
Skills
Required
- JSON
- software engineering
- XML / CSV
Preferred
- phone
- QA
- CRM
- SMS
- automation platforms
- CRMs
- dialers
The Production Build Specialist role sits at the center of how those campaigns are configured and supported.
Responsibilities
- Production Build Specialist
- Production
- Remote (U.S.)
- Full-time (40 hours/week)
About Drips
- Drips engages people in two-way, compliance-governed SMS conversations — the kind that get responses, drive action, and close the gaps traditional outreach leaves open.
- In practice, that means Drips helps organizations connect with their customers through large-scale, automated text and phone campaigns. Our proprietary platform lets clients design conversations, schedule outreach, and route responses so the right messages reach the right people at the right time.
- As a Production Build Specialist, you configure customer campaigns in our proprietary software and keep them running smoothly. This is a great opportunity to build technical and operational skills at a fast-growing company: you'll succeed here by staying organized, following process carefully, and being willing to learn a system that doesn't have an equivalent anywhere else. No coding or software engineering background is required to get started, and this role is well-suited to entry-level candidates — though prior experience in a technical, operations, or support-focused role is a plus.
- Set up and update projects in our internal tools (Drips’ platform), so campaigns send the right messages, at the right time, to the right audience.
- Work through a queue of support requests (cases) from internal teams and occasionally clients — making changes, fixing issues, and answering “how do we do this in Drips?” questions.
- Act as a problem-solver: when a request is vague, you help translate business objectives (e.g., “we need to follow up on missed calls”) into concrete configuration choices in the software.
- Configure Campaigns in Drips’ Platform
Build and update campaign workflows in our internal tools
- Set up outreach schedules (when messages or calls go out).
- Configure branching logic and actions based on how people respond.
- Attach and map audio files for outbound calls.
- Work with JSON-based configuration files to define campaign behavior (for example, mapping inputs and outputs, configuring rules, or connecting to other systems).
- Occasionally use simple scripts or structured data files to support configuration, data prep, or bulk updates. You won’t be writing software — basic familiarity with structured data (like JSON) is a plus, and we'll train you on the rest.
- Own a Queue of Build & Support Request s
- Manage a steady flow of cases (requests) in our ticketing system from internal partners like Client Success and Operations.
- For each case, understand what the requester is trying to accomplish (e.g., new campaign, change to messaging, routing adjustment) and decide what needs to change in the platform.
- Make updates, test them, and clearly document what you did so others can follow the history of the campaign.
Provide Strategic Configuration Recommendations
- When a request is underspecified (for example, “we just want more people to answer calls”), ask the right questions and suggest how best to use the platform to achieve that goal.
- How many messages to send and on what schedule.
- How to route calls and responses (e.g., when to transfer to a call center, when to stop outreach).
- How to structure the campaign so it’s maintainable and easy to adjust later.
- Balance client goals, technical constraints, and operational reality when recommending a path forward.
Quality and Troubleshooting
- Run basic tests after you configure or change a campaign to make sure it behaves as expected (for example, checking that messages send in the right order, or that an audio file plays correctly).
- Investigate issues reported by internal teams (e.g., “this flow isn’t behaving as expected”) by checking configurations.
- Work with peers in QA and other teams when a problem requires deeper investigation.
Examples of Day-to-Day Tasks
- Take a new request from Client Success to launch a follow-up campaign and: review the requirements, propose settings and a routing approach, configure the campaign using UI, upload and map audio files, and test the flow end-to-end.
- Handle a support case where a campaign needs a quick routing change (e.g., changing which phone number is used or where a “press 1” call should go).
- Use a JSON configuration file to fine-tune how a project interacts with an external system (for example, what data is passed in or out).
Requirements
- If you're highly organized, detail-oriented, and enjoy learning how a system works inside and out, this role is a strong fit.
- Use a JSON configuration file or a simple script to reformat a batch of configuration data, check that a set of files meets a required structure, or help automate a repetitive change across several campaigns.
- This role is about organization and follow-through more than technical pedigree. You do not need a background in software engineering or a computer science degree — you do need to be sharp, dependable, and comfortable picking up a new system.
- Exceptional organization: you can manage a steady queue of requests, prioritize competing work, and keep things moving without dropping tasks. This is the single most important trait for this role.
- Comfort with structured data: reading and editing JSON (or similar formats like XML or CSV), and using spreadsheets to track and organize configuration details.
- Willingness and ability to learn proprietary software: you can pick up new interfaces, understand how settings fit together, and follow documentation without prior exposure to our specific tools.
- Strong attention to detail: you catch mismatched IDs, incorrect mappings, and inconsistent rules before they cause issues.
- Good problem-solving and communication skills: you ask clarifying questions when requirements are unclear, and can explain what you changed in plain language to non-technical partners.
Preferred
- Our platform doesn’t have a direct equivalent anywhere else, so we don’t expect candidates to already know it — the following are pluses, not requirements:
- Experience configuring a similar type of system (marketing automation platforms, CRMs, dialers, or comparable workflow/rules-based tools).
- Experience with Salesforce or a similar CRM — not required, since we'll train you on our own platform, but a plus if you have it.
- Experience managing a ticket queue or support caseload (help desk, IT support, customer service, or similar) — the skill of triaging and working through a queue transfers directly to this role.
- Experience running outreach campaigns of any kind (email, SMS, call center, etc.).
- Basic familiarity with a scripting or query language — not required, but a plus.
- Experience processing audio files (trimming, exporting, or organizing files) for use in phone systems or other customer outreach tools.
- Background in a technical, operations, or configuration-heavy role (IT support, marketing operations, QA, data operations, or similar).
Work Environment
- This is a remote role; you’ll collaborate daily via chat, video calls, and shared documentation.
- You’ll spend most of your time in our internal configuration tools (Drips’ platform), in our ticketing system managing cases, and in supporting tools for data and configuration.
- You’ll work closely with other Build Specialists, QA, Client Success, and Production leadership in a team that values accuracy, transparency, and continuous improvement.
How to Apply
- If this sounds like you, please apply via the Drips careers page and include:
- Your resume.
- A brief summary of why you think you’d be a good fit for this role in a cover letter.
- We look forward to reviewing your application.
