NODE_21 · GLOBAL · any

DogeSMS in Anywhere

○ On the radar here: Senior Backend Engineer (Go)○ On the radar here: Senior Frontend Engineer (Next.js / React)○ On the radar here: SRE / Platform Engineer○ On the radar here: Blockchain & Crypto Integration Engineer○ On the radar here: Security Engineer○ On the radar here: Communication Equipment Engineer (R&D)○ On the radar here: Channel Partnerships Manager (ISV / Reseller)○ On the radar here: Payment Operations Manager○ On the radar here: Crypto Settlement Operations Lead○ On the radar here: Treasury & FX Analyst○ On the radar here: Growth Engineer○ On the radar here: Content & SEO Lead○ On the radar here: Social Media & Creative Lead○ On the radar here: Demand Generation Marketing Manager○ On the radar here: Enterprise Customer Success Manager○ On the radar here: Solutions Engineer○ On the radar here: Developer Advocate○ On the radar here: Developer Experience Engineer (DX)○ On the radar here: AML / Compliance Officer○ On the radar here: Senior Finance Analyst○ On the radar here: Technical Support Engineer — English (Global)○ On the radar here: Technical Support Engineer — Cantonese (Hong Kong / Guangdong)○ On the radar here: Technical Support Engineer — Korean○ On the radar here: Technical Support Engineer — Vietnamese○ On the radar here: Technical Support Engineer — Thai○ On the radar here: Technical Support Engineer — Turkish○ On the radar here: Technical Support Engineer — Portuguese (Brazilian + European)○ On the radar here: Technical Support Engineer — Spanish (LATAM + Iberia)

Why we're building presence in Anywhere

We hired our first five engineers before we had a headquarters. We still don't have one in the traditional sense. The way we work: decisions in writing, code reviewed asynchronously, incidents triaged in shared channels where timezone is a scheduling detail not an exclusion criterion. What we optimize for is not physical co-location but documented reasoning — the kind of communication that scales when your team spans UTC-5 to UTC+9. If you write clearly, give and receive feedback without ego, and can hold context across async threads for days at a time, the absence of an office is not a limitation. The constraint we do enforce: at least 4 hours of overlap with UTC+1 to UTC+4 per working day, because that is where most of our infrastructure incidents occur and where most of our carrier partners operate.

Distributed teammate hub

Timezone: any. Working language: English (and likely local). Decisions live in writing; we coordinate across timezones via async docs.

Future openings in this hub will likely include: Any.

What life looks like here for our team

Wherever you live, what we care about is that you can ship narrow, write clearly, and disagree productively. Time zone overlap with at least one other teammate is helpful, not required.

Interested?

Email careers@dogesms.com or see all open roles.