Expert Qualtrics Programmer — Complex Multi-Track Survey

Overview We are a university research team fielding a national study of professionals, distributed through professional associations. The instrument is large and structurally complex: roughly 500 items across fourteen sections plus seven randomly assigned thematic modules, with two independent screening questions that route respondents into one of four tracks. Target sample is 4,000 completions, with fielding across approximately 30 separately source-coded distribution channels. We need an experienced Qualtrics programmer to build the instrument, implement the routing and randomization architecture, configure quota monitoring across roughly twenty strata, and stand up a live dashboard that lets the research team see cell fill against target during fielding so we can trigger targeted recruitment when cells lag. This is a build-plus-support engagement: a defined build phase, a soft launch, and then part-time support through an active fielding period. Scope of work 1. Instrument programming - Program approximately 500 items from a fully drafted Word instrument that already specifies question text, response options, and intended logic - Sections include matrix/grid batteries, validated scales, drop-down menus (state, birth year), text entry, and multi-select items - Piped text, display logic, and carry-forward across sections - Loop-and-merge where respondents report on multiple care recipients - Item randomization within scale batteries where specified 2. Routing architecture - Two independent qualifying questions produce a 2 × 2 exposure structure and four respondent tracks - Each track receives a different combination of mandatory sections and randomly assigned modules - Track-length varies from roughly 20 to 45 minutes; survey flow must handle this without dead ends or orphaned branches 3. Randomized module assignment - Seven thematic modules assigned randomly, balanced within track, using evenly-present randomization - Three exceptions must be implemented: one module assigned at 1.5× the base rate; one track receives a mandatory module; a second track receives a different mandatory module - Module assignment must be written to embedded data and exportable, since it functions as a planned-missing design in the analysis 4. Quota management - Approximately twenty quota cells across routing cells, caregiver type, work setting, gender, employment type, and seniority - Two hard floors that must be protected during fielding - Additional monitored (not enforced) dimensions: career stage, race/ethnicity, LGBTQ+ status, disability status, region - Quotas must be adjustable mid-field without republishing or breaking in-progress responses 5. Source coding - Approximately 30 distribution channels, each with a distinct anonymous link and embedded source code - Two-wave recruitment structure: general channels at launch, boost channels opened later against observed shortfalls - Source code must be captured for every response and available in the dashboard 6. Live fielding dashboard and reporting - Real-time view of completions against target for every quota cell and monitored dimension - Module assignment distribution within track - Breakoff/abandonment by section, and median completion time by track — we expect to act on this after soft launch - Source-code performance, so we can see which channels are producing which cells - Automated weekly summary report to the research team - Please advise on whether this is best built in Qualtrics dashboards given our license, or via API into Power BI, Tableau, or Google Sheets. Recommending the right approach is part of the job. 7. Data quality and integrity - Attention checks, speeder detection, duplicate-response prevention, bot and fraud screening - Open-text quality flags 8. Sensitive content handling - Portions of the instrument address bereavement, serious illness, and other difficult experiences, and carry content warnings and support-resource language - One module cannot be fielded until specific IRB approvals are documented, so the build must allow that module to be switched on or off without republishing the instrument - An optional follow-up interview invitation must collect contact information in a way that is not linkable to survey responses 9. Accessibility and delivery - Mobile-responsive across the full instrument, including grids - Screen-reader compatible; WCAG-conformant where achievable in Qualtrics - Save-and-continue enabled given survey length - Custom CSS for progress indication and readable grid formatting 10. Testing and documentation - A written test plan covering every routing path and module combination, with documented results - Test responses generated across all four tracks and all module assignments - Logic map documenting survey flow, embedded data fields, and quota definitions - Variable naming aligned to the instrument’s existing item numbering, with a codebook - Clean export to SPSS, Stata, and R-readable formats - Handoff documentation and a walkthrough session so our team can manage the study after launch Required experience • Demonstrated expert-level Qualtrics work: Survey Flow, embedded data, branch and display logic, randomizer with evenly-present, quota logic, and authenticator or contact-list workflows where relevant • Prior experience programming academic research instruments of comparable size and structural complexity (multi-track routing, randomized modules, planned-missing designs) • Qualtrics dashboards or equivalent reporting built via API • Custom JavaScript and CSS in Qualtrics • Experience supporting an active fielding period, not only delivering a build • Familiarity with IRB-governed research and the confidentiality constraints that come with it Preferred • Qualtrics XM certification • Experience with panel or association-distributed samples and source-code tracking • Prior work on surveys with sensitive or emotionally difficult content • Working knowledge of SPSS, Stata, or R data structures, so the export is usable rather than merely available Deliverables and milestones Milestone Deliverable 1 Programmed instrument, all sections, no logic 2 Full routing architecture, module randomization, and embedded data 3 Quota structure and source-coded distribution links 4 Test plan executed and documented; test data across all tracks 5 Dashboard and automated weekly reporting live 6 Soft launch support (approximately 50 responses) on Prolific, with revisions from observed breakoff and timing 7 Documentation, codebook, and team handoff Ongoing Fielding support: quota adjustments, boost link deployment, dashboard changes Engagement and timeline • Build phase: 1 week, beginning immediately • Soft launch: 9/1 • Full fielding: approximately 8 weeks from 9/1, with part-time support throughout • Preferred structure: fixed-price milestones for the build, hourly for fielding support. Open to alternatives if you propose a structure that fits the work better. • Budget: [state range or “please propose”]. We would rather pay for genuine expertise than rebuild this twice. Confidentiality The instrument, sampling plan, and partner list are confidential and will be shared with shortlisted candidates under NDA. This is IRB-governed research; the freelancer will have no rights to the data and will be required to follow our data handling protocol. To apply, please include 1. A description of the most structurally complex Qualtrics instrument you have built — specifically, how many branching paths, how randomization was handled, and what went wrong 2. An example of a fielding dashboard you have built, with a screenshot or description of what it tracked 3. Your approach to the following: we need module assignment balanced within each of four tracks, with one module oversampled at 1.5× and two tracks receiving a mandatory module. How would you implement this in Survey Flow, and how would you verify it is working during fielding? 4. Whether you would recommend Qualtrics dashboards or an external BI tool for our reporting needs, and what you would need to know about our license to decide 5. Your availability over the next 12 weeks and your typical response time during an active field period 6. Your rate structure Applications that do not address item 3 will not be reviewed