Job description for Software Engineer (Project Based 6 Month) at PT. ALL DATA INTERNATIONAL
Software Engineer
About the Role:
We are looking for a Software Engineer with a backend engineering background to join our team. You will work closely with the Senior Software Engineer on application-layer integration with our cache infrastructure, contributing to caching implementation, integration test coverage, and migration validation. This is a hands-on engineering role with a strong learning curve — you will gain deep, practical experience with enterprise-grade caching infrastructure in a structured team environment.
Job Description:
- Implement caching logic in application services using cache client libraries, under the guidance of the Senior Software Engineer
- Write and maintain integration tests for cache-backed application behaviour — testing cache hits, misses, TTL expiry, and reconnection logic
- Assist with data migration validation — running key comparison scripts, spot-checking values, and documenting findings
- Support the investigation of cache-related application bugs and performance regressions
- Contribute to internal documentation of caching patterns, client library usage, and integration test results
- Participate in code reviews and incorporate feedback from senior team members
Requirements:
- 1–3 years of backend or software engineering experience
- Comfortable reading and writing application code in at least one backend language
- Familiar with writing integration or unit tests as part of normal development work
- Basic understanding of caching concepts — TTL, eviction, cache invalidation
- Comfortable working with REST APIs and reading technical documentation
- Experience in at least one language (Python, Java, Node.js, Go, etc.) at a production level
- Good written communication skills — able to document test results and findings clearly
Plus Points:
- You have a bachelor's degree in computer science or informatics
- You have used Redis in at least one project — even as a consumer rather than someone who administered it
- You have worked on a backend service where the caching layer was a critical dependency and you understand what happens when it misbehaves
- You have written scripts to inspect or manipulate Redis data directly via redis-cli
- You are comfortable asking questions early and flagging ambiguity rather than making assumptions
