We're building a new service with data pipeline infrastructure and REST APIs. You'll join our team to design and implement production-grade data ingestion, transformation, and delivery pipelines, plus enhance and maintain REST APIs using Node.js, Java, and AWS services.
By month 4–5, we expect working, tested pipelines and API enhancements handling real data at scale. You'll work embedded with the team, shipping code fast while maintaining quality.
What You'll Do
Core Responsibilities
- Design and implement data pipeline services (ingestion, transformation, delive
- Enhance and maintain REST APIs for service integration and external consumpt
- Write clean, testable backend code in Node.js and J
- Build event-driven architectures using AWS (Lambda, Kinesis, SQS, SNS, DynamoDB,
- S3)Set up CI/CD pipeline automation in Git
- Build own end-to-end testing strategy (unit, integration, contract, API tes
- Collaborate tightly with software engineers, platform engineering and product team on design decisi
- Deliver working code on a predictable cadence (sprints/iteration
Execution
- Ship features weekly/bi-w
- Maintain production-grade code quality from da
- Resolve production issues and optimize system perfor
- Write minimal, effective documentation for handoff/runb
- Participate in daily standups, sprint planning, and code
- Provide thoughtful PR feedback and accept feedback on yo
- Work synchronously with team during full CDT overla
- Communicate blockers and dependencies
Required Qualifications
- 5+ years backend software engineering (shipping product code)
- Proficiency: Node.js and J
- S/SNS, S3Infrastructure-as-Code: Hands-on experience with Terraform; comfortable managing infrastructure
Data Fundamentals
SQL (PostgreSQL) and/or NoSQL (DynamoDB), event streaming
System Thinking
Understand tradeoffs (throughput vs. latency, consistency, cost); desig
n for scale
Skills
Code quality: Write clean, maintainable, documented code without hand-holding Agile mindset: Thrive in sprints; comfortable with iteration and scope prioritization Communication: Clear, concise technical updates; able to unblock teammates Independent: Take ownership; minimal supervision; ask for help when needed Problem solver: Debug production issues; sugges t improvements
Nice to Have
- (not required): Event-driven archit
- Observability/loggi ng best practicesWhat Success Looks L
- ed and documentedReliable, tested, and mo
- nitorable systemsTeam can maintain/extend pipelines and APIs post-con
- tract without youClear API documentation and integration pat
Sign in
To continue your applicationor continue with email
By continuing you agree to our Terms & Privacy Policy.
