\nWe are looking for a mobile engineer who can build high quality mobile app that puts performance and user experience first. We will build an isomorphic or universal JavaScript that target Android platform. The codebase will be shared with frontend. You will work 70% on JavaScript and 30% on Android.\n\nThe successful candidates must have a good understanding of JavaScript and have experience on mobile development environment.\n\nResponsibilities:\n\n\n* Develop mobile apps based on new product development plan\n\n* Maintain existing mobile apps for updates/upgrades.\n\n* Set up deployment environment for mobile app.\n\n* Share skills and knowledge with others while building productive internal/external working relationships.\n\n* Presents facts, information, and the weight of evidence to influence others\n\n* Writing technical notes, methodologies, and best practices document\n\n\n

\nWe are hiring a full-time dev-ops person to join our core team who has significant experience configuring, managing, and monitoring frontend servers and backend services at scale. We have millions of visitors and quickly growing, and you will have the great opportunity on creating the infrastructure to support that.\n\nOur backend tech stack currently includes Linux, Scala, Python, MySQL, Redis, Cassandra, Zookeeper, Kafka, Kubernetes, AWS (EC2, ELB, RDS, ElasticCache, Elastic Search, S3, EB, CloudFormation, VPC, etc).\n\nInfrastructure-wise, we use AWS for almost everything. We use Elastic Beanstalk for our backend and front-end server deployment, S3 for static files and deployment bundles, Route 53 for DNS, RDS & ElastiCache for hosted MySQL and Redis, respectively. Outside of the AWS world, we use Incapsula as our cloud WAF & DDOS protection, Fast.ly as our static file CDN.

\nAs a front-end engineer in Sale Stock Indonesia, you write and push user-facing code that gets deployed in the same day to millions of users across Indonesia. We build our front-end codebase with love, tears, and the latest and greatest the open source world have available: Node.JS, React, React Native, Redux, GraphQL, Gulp, WebPack, and others. You’ll also work in the same team with people who have worked for world-class companies in Silicon Valley such as Facebook, Sony and Yahoo! — building products such as the PlayStation 4, Facebook Groups, Yahoo! Messenger and Mail. We’re a team of programmers trying to build a great product worth calling home about.\n\nFront-end wise, we’re basically building a React-based isomorphic SPA. We pretty religiously follow the Flux architecture, with Flummox library as our chosen Flux library implementation. We use WebPack for code bundling and Gulp as task runner. The front-end app, although very much is an SPA, is served by a custom Node.JS-server (express-based) that does a pretty interesting server-rendering mechanism, which helps us achieve things like SEO and low-latency initial client-side rendering.

\nWe are looking for a backend engineer with passion and growth mentality to tackle various challenge in developing performant, resilient and scalable system. Our core system developed in Scala, supported with several microservices written in Node.js and Python with MySQL, Cassandra, and Redis as storage.\n\nAs a Software Engineer working on our Back-End development team you'll help us develop services, exposed through clean & thoughtful APIs, that will store and process product cataloging, inventory, membership, and order. We develop most of our services today in aforementioned technologies and languages, but our microservice architecture is language-agnostic and we're open to new tools and ideas.\n\nBack-end wise, we use Scala’s Play as our web framework. We use MySQL as our primary persistence layer and Redis for more transient data. Our codebase is shaped to be a highly microservice-based infrastructure (although we’re still a monolith at current time), so our server code is very much async-driven; we use Future-based abstractions almost everywhere in the stack. We’re also in the process of adding Cassandra into the mix for our preliminary tracking infrastructure persistence layer. We use Docker heavily for both development and production deployment.