Backend Integration Engineer [Remote]

• Location: San Francisco, California, United States
• Remote: Remote
• Type: Permanent
• Job #26101

If you enjoy building the “plumbing” that makes a security product  actually work —auth flows, brittle third‑party APIs, weird edge cases, and pulling reliable signals out of messy systems—this role is built for you.

You’ll join a fast‑growing, Series A security & compliance SaaS company building a platform that continuously monitors customer cloud environments and connected tools to detect misconfigurations, risky access, encryption gaps, exposed storage, and compliance drift. Your focus: the integrations layer that powers those detections.

What you’ll build (the low-level, technical work)

You’ll build and own production integrations connecting the platform to:

• Cloud provider APIs (AWS/GCP/Azure)for inventory, configuration, and security posture signals
• Third‑party security / SaaS tools with APIs that evolve, rate-limit, paginate, and sometimes break
• Authentication + identity flows across systems: OAuth 2.0 / OIDC, service accounts, signed creds, API keys

This is not “hit an endpoint and map JSON.” It’s:

• designing resilient ingestion + normalization pipelines
• dealing with  unstable schemas ,  partial failures , retries/backoff, and idempotency
• building  observability (logs/metrics/alerts) so you can detect when a provider changes behavior
• caring about  data quality and coverage , because downstream security features depend on it

What you’ll do

• Build and maintain integrations with  AWS, GCP, Azure and third‑party services
• Normalize and validate data across providers so signals are consistent and trustworthy
• Implement and maintain authentication patterns (OAuth/OIDC/API keys/service accounts)
• Ensure integrations are reliable and operable in production (retries, monitoring, alerting, runbooks)
• Write clear documentation for mappings, behaviors, and troubleshooting
• Collaborate closely with product/engineering to ensure integrations deliver what detections need

What we’re looking for (hard requirements)

• Recent, production Go (Golang)experience (recency matters) ideally or ability to quickly move to Go from C++ OR C# OR C or other low level languages
• Real-world  REST API integration experience (pagination, rate limits, evolving schemas, quirks)
• Exposure to at least one of  AWS or GCP or Azure APIs/SDKs (not just “hosted on AWS”)
• SQL (hands-on querying; ideally some schema ownership too)
• Concrete experience with  OAuth 2.0 / OIDC / service accounts / signed credentials
• Strong reliability instincts: monitoring/logging/alerting + robust error handling
• Experience operating a  SaaS backend (not a one-off integration project)

Nice-to-haves

• Security domain familiarity (IAM, identity, audit trails, compliance)
• Integration testing approaches (contract tests, sandbox strategies, debuggability)
• Background in compiled, strongly typed languages (Go preferred; Rust/Java/C#/C++ also relevant)

Next steps

Interested in building endpoint software and/or transitioning into Go while staying close to systems-level engineering?

Apply with your CV, and we’ll come back quickly to arrange a first conversation.

Job Ref: BBBH26101