Email Deliverability Expert
Reliable delivery of the organization's transactional and operational email: applicant and donor correspondence, secure sign-in links, receipts, and platform notifications. Covers domain authentication with SPF, DKIM, and DMARC, sender reputation and deliverability monitoring, suppression and bounce handling, and delivery troubleshooting, working alongside engineering, cloud infrastructure, security, and communications.
- Compensation
- Contract
- Participant-facing
- No
- Credential required
- No
- Training before activation
- No
- Conflict review
- Standard disclosure
Important boundaries
- This is internal infrastructure for Herbal Trials' own correspondence. Herbal Trials does not provide email or deliverability services to the public, and email deliverability is not part of its scientific purpose.
- Email events, suppression lists, and recipient data are handled under the same access controls and retention rules as other organizational data.
- Email is not used to transmit participant health information. Any future study communication would be governed by the approved protocol and consent documents, not by this role.
What your application includes
- Profile & contact
- Data, statistics & technology
- Conflict-of-interest disclosure
- Document uploads
What to have ready
A CV or résumé is part of every profile. For this role, also have:
- Code sample or portfolio (GitHub)
- Representative analysis (redacted)
What we’ll ask you
You'll handle people's personal data and private documents. We care how you protect them. Everyone also answers a few shared questions on research integrity and why this work. You answer these in your private portal after verifying your email. Your answers are stored with your private application and may be reviewed by authorized personnel when the role becomes active. They are never scored or rejected solely by an automated system.
- This system holds applicants' personal data and private documents. Walk us through how you'd protect it — authentication, storage, access control, and audit.
- How would you keep any screening or routing automation from quietly disadvantaging applicants, and where must a human stay in the loop?
- Where would you push back if speed or a stakeholder request conflicted with privacy, accessibility, or data integrity?
- Show us relevant work — a portfolio, repo, or shipped system — and the part you're proudest of. (optional)