Backend: Go / Golang
Database: PostgreSQL
APIs & Integrations: REST | OAuth | Webhooks
Cloud: GCP Preferred | AWS | Azure
Architecture: Microservices | Distributed Systems | Event-Driven Processing
Infrastructure: Messaging Systems | Monitoring | Logging | Observability
What Makes You a Strong Fit
You’ll likely thrive in this role if you:
•
Prefer backend and systems engineering over frontend/UI development
•
Have built production systems designed for scale
•
Enjoy working with Go or want to make it your primary backend language
•
Understand that integrations must handle failures, retries, rate limits, and changing external APIs
•
Think carefully about distributed systems and asynchronous processing
•
Care about clean architecture and long-term maintainability
•
Think deeply about reliability, performance, and observability
•
Are comfortable optimizing databases and investigating performance bottlenecks
•
Can troubleshoot complex production issues systematically
•
Take ownership without requiring constant direction
•
Enjoy fast-moving, engineering-heavy environments
What a Typical Day Looks Like
Your day may begin by reviewing system health, integration performance, or an issue affecting production data processing.
Throughout the day, you could build and ship backend services in Go, design an integration with an enterprise platform, troubleshoot a production integration, optimize PostgreSQL queries and indexes, or improve API performance.
You may also build or refine event-driven data pipelines, review architecture decisions with other engineers, improve monitoring and observability, or contribute to AI-powered security and automation workflows.
In short: you’ll build the scalable backend infrastructure, integrations, APIs, and data systems that power a modern cybersecurity platform.
•
Backend reliability and uptime
•
API latency and performance
•
Scalability under increasing workloads
•
Reliable processing of high-volume security data
•
Reduced third-party integration failures
•
Strong integration monitoring and observability
•
Database and query performance
•
Platform stability and maintainability
•
Effective handling of production issues
•
Quality and speed of engineering execution