Back End Developer

Job Description:

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

DoCore Responsibilitie

• s:
  Design and implement data pipeline services (ingestion, transformation, delive
• ry)Enhance and maintain REST APIs for service integration and external consumpt
• ionWrite clean, testable backend code in Node.js and J
• avaBuild event-driven architectures using AWS (Lambda, Kinesis, SQS, SNS, DynamoDB,
• S3)Set up CI/CD pipeline automation in Git
• LabOwn end-to-end testing strategy (unit, integration, contract, API tes
• ts)Collaborate tightly with software engineers, platform engineering and product team on design decisi
• onsDeliver working code on a predictable cadence (sprints/iteration

s).
Execution Fo

• cus:
  Ship features weekly/bi-w
• eeklyMaintain production-grade code quality from da
• y oneResolve production issues and optimize system perfor
• manceWrite minimal, effective documentation for handoff/runb

ooks.
Collabor

• ation:
  Participate in daily standups, sprint planning, and code
• reviewsProvide thoughtful PR feedback and accept feedback on yo
• ur codeWork synchronously with team during full CDT overla
• p hoursCommunicate blockers and dependencies

early.
Required Qualifi

• cations;
  5+ years backend software engineering (shipping product
• ion code)Proficiency: Node.js and J
• ava (17+)AWS hands-on experience: Lambda, API Gateway, DynamoDB, Kinesis, SQ
• S/SNS, S3Infrastructure-as-Code: Hands-on experience with Terraform; comfortable managing infrastructure

in code.
Data fundamentals: SQL (PostgreSQL) and/or NoSQL (DynamoDB), event streaming

concepts.
Testing discipline: Unit tests, integration tests, CI/CD pipelin

es, GitLab.
System thinking: Understand tradeoffs (throughput vs. latency, consistency, cost); desig

n for scale.
Code quality: Write clean, maintainable, documented code without

hand-holdingAgile mindset: Thrive in sprints; comfortable with iteration and scope p

rioritizationCommunication: Clear, concise technical updates; able to unbl

ock teammates
Independent: Take ownership; minimal supervision; ask for hel

p when needed.
Problem solver: Debug production issues; sugges

t improvements.
Nice to have

• (not required):
  Event-driven archit
• ecture experienceObservability/loggi
• ng best practicesWhat Success Looks L
• ike in 4–5 MonthsMultiple data pipelines (ingestion, transformation) l
• ive in productionREST API enhancements deploy
• ed and documentedReliable, tested, and mo
• nitorable systemsTeam can maintain/extend pipelines and APIs post-con
• tract without youClear API documentation and integration pat
• terns establishedPredictable delivery cadence (no