Senior Backend Engineer (Go / AWS Streaming)
Creative Chaos (company site, opens in a new tab)5+ yrsRemoteDirect career pageEst. 18–30 LPA
Posted 15h ago
Reach people at Creative Chaos
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Creative Chaos you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Build and operate Go services connecting device telemetry through AWS IoT and Kinesis to Redshift analytics.
- Own pipeline reliability and efficiency: prevent data loss, handle spikes, monitor latency and AWS spend, and optimize cost per million events.
- Lead technical design and code reviews, document architecture, and mentor engineers.
Minimum Requirements
- Work Experience Required: 5+ years in backend engineering, including at least 2–3 years writing production Go.
- Production Go skills, including concurrency; experience building and operating high-scale streaming pipelines with Kinesis or a comparable system such as Kafka.
- Experience with AWS IoT Core or another device-telemetry platform, including MQTT, device authentication, and high-fan-in workloads.
- Production warehouse experience with Redshift or a comparable platform, strong SQL, and AWS/infrastructure skills including Lambda, S3, IAM, CloudWatch, IaC, Docker, and CI/CD.
Ideal Candidate Profile
- A hands-on senior engineer who has operated production streaming pipelines and improved them through real-world reliability incidents.
- Strong fit for device-data systems, combining telemetry ingestion, streaming delivery, and analytics warehouse design.
- Able to lead architecture decisions and explain trade-offs clearly to a US product team through discussions and written design documents.