Jobs / United States / QuickMail
Technical Customer Support
QuickMail · 🇺🇸 Remote · Remote
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal — ask the recruiter.
- No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- Confirmed live todayWhen a source last listed this job as open.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Why not apply?
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
SponsorApply flags time-wasters so your applications go where they can land. These come from the posting's own wording — read the original listing to confirm. See better-fit alternatives →
Sponsor Radar — QuickMail
This employer posted directly and does not match a government sponsor register.
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for QuickMail →
About the role
QuickMail is a cold email and LinkedIn outreach platform for markets you can't afford to burn. Our customers can't easily replace leads that land in spam, which is why deliverability matters more to us than anything else. We have been running since 2014, and we pioneered deliverability technology such as Inbox rotation⢠and deliverability AIâ¢. The Role We are hiring a technical customer support person with an owner's mentality. You will own support for QuickMail and Mailflow, our deliverability add-on. There is no first or second line. You are the first and last person our customers talk to. Customers count on you to solve their problems and find the real cause when something breaks. You work closely with engineering, and you tell the founder what we need to know to make the product better: where the friction is and where the opportunities are. The role covers the help desk, system health checks, testing new releases before they ship, and leading the weekly team meeting. It takes excellent communication, solid technical understanding and sharp critical thinking. This is not a script-reading job. Most tickets involve deliverability, DNS records, LinkedIn automation or campaign setup. You dig into customer accounts in our Support Dashboard, reproduce the issue, then decide what to do and how to explain it to the customer. We are a remote team spread across time zones. Most routine tasks have a written guide with a checklist, so you know what done looks like. You are expected to refine and improve those processes. When something new comes up, you work out the most efficient way to handle it. If you want a lot of autonomy across many areas, real responsibility and a fast-paced environment, this role is for you. What Work Looks Like You own two things: customers get unstuck fast, and the product stays reliable. Every day • Set the day's support priorities and work the Help Scout queue for QuickMail and Mailflow. Triage, resolve, and dig deeper when a ticket needs it. • Check the support dashboard: job queue, event-stream latency, blacklist status, newly purchased domains. If something is off, investigate, diagnose, and drive it to resolution. • Review fraud alerts and disable accounts that are scams or abusing the platform. Delighting customers • Comfortable jumping on calls with customers, building rapport fast, and setting them up for success. • Update the changelog and help articles based on what shipped and what customers asked. • Share customer feedback with the team, ask happy customers for reviews and case studies, and watch NPS for testimonial candidates. Making support smarter with AI • Improve the AI support agent. Review its answers, fix the docs it drew from when it is wrong, and contact the customer when its reply was off. • Write and maintain automated tests, built with AI, that try to break staging before customers do. • Use the MCP connections we have in place (Helpscout, GitHub, Postmark, and others) to get an accurate picture of support and find the next thing worth improving. Keeping the product solid • Gatekeep releases. New fixes and features land on staging every week. Test them, confirm when staging is ready to ship, and think through how existing and new users will be affected. • Report bugs as GitHub issues with everything the developer needs: steps to reproduce, screenshots or a Loom, and any GraphQL or console errors. • Captain red alerts. When a core feature breaks (emails not sending, login down), confirm it, alert the team on Slack or Telegram, update the status page every 30 minutes, keep affected customers informed, and drive the fix. Then run the retrospective so it does not happen twice. Running the week • Lead the weekly team meeting in MonsterOps: issues written up, to