Tempo is hiring a IT Systems Engineer in Operations — USA (Remote). The overview below is synthesized from the employer posting on jobs.ashbyhq.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Tempo is a layer-1 blockchain purpose-built for stablecoins and real-world payments, born from Stripe’s experience in global payments and Paradigm’s expertise in crypto tech.
Tempo’s payment-first design provides a scalable, low-cost predictable backbone that meets the needs of high-volume payment use cases. Our goal is to move money reliably, cheaply, and at scale.
We're building Tempo with design partners who are global leaders in AI, e-commerce, and financial services: Anthropic, Coupang, Deutsche Bank, DoorDash, Mercury, Nubank, OpenAI, Revolut, Shopify, Standard Chartered, Visa, and more.
We’re a team of crypto-optimists, building the infrastructure needed to bring real, substantial economic flows onchain. We like to move fast and swing for the fences — join us!
The Role
Day-to-day scope for the IT Systems Engineer as described in the posting:
You'll own and build Tempo's corporate IT infrastructure — identity, device management, endpoint security, and the automation that ties it all together. This is a hands-on engineering role, not a help desk seat.
Responsibilities
Day-to-day scope for the IT Systems Engineer as described in the posting:
- Architect and automate the full identity lifecycle — HRIS → Okta → SaaS apps — eliminating manual provisioning and off boarding gaps
- Complete and maintain SSO/SCIM integrations across the entire SaaS stack
- Own Jamf Pro end to end: PreStage enrollment, configuration profiles, software updates, certificate distribution
- Deploy and tune endpoint security (SentinelOne) — policy management, MDM-driven deployment, alert triage
- Expand SIEM coverage and write detection/alerting rules with a detection-as-code approach
- Build toward infrastructure-as-code management of all IT tooling (Terraform, GitHub Actions)
- Resolve hard identity, device, and access escalations that get past first-line support
- Drive SOC 2 readiness — unified audit trails across identity, device, and security systems
Qualifications
Experience and skills the team lists as required:
- 4+ years in IT engineering roles
- Hands-on Okta administration: SSO, SCIM, SAML/OIDC integrations, lifecycle policies, Okta Workflows. Understands HRIS-as-source-of-truth (Rippling or similar)
- Production Jamf Pro experience: PreStage enrollment, configuration profiles, software update management, certificate distribution. macOS-first
- Deployed and operated an EDR platform (SentinelOne or comparable) — policy tuning, MDM deployment, alert triage
- Strong scripting (Python/Bash/Go preferred), comfortable with REST APIs, webhooks, JSON, auth flows, and event-driven workflows
- Git-based config management, CI/CD pipelines (GitHub Actions), Terraform or equivalent
- Solid grasp of DNS, certificates/PKI, ZTNA (Tailscale or similar), and modern access control models
Nice-to-Haves
- Crypto/blockchain security exposure — multisig/hardware-wallet workflows (Fireblocks or similar), phishing/lookalike-domain campaigns, high-value signer threat models
- Detection-as-code: SIEM detections as version-controlled rules (Panther Python models, Sigma, or equivalent)
- Apple platform depth beyond basic Jamf — DDM, MDM protocol internals, notarization/signing/packaging, macOS security frameworks (TCC, system extensions)
- Mapped controls to SOC 2, ISO 27001, NIST CSF, or CIS — understands what audit-ready evidence looks like
- Built Slack-driven workflows, bots, or self-service internal tooling
- Public open-source contributions to IT/security tooling
Build a standout application
For the IT Systems Engineer at Tempo, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.