Job Description
About Quizlet:
Inspired by our belief that anyone can learn anything and powered by our own curiosity, we build the smartest tools we can imagine to help students learn.
Quizlet is the popular, global learning platform and app that millions of students, teachers and everyday people use to study any subject imaginable for school, work or as part of their personal interests -- including two-thirds of high school students and half of all college students in the US. Combining cognitive science and machine learning, Quizlet guides students through adaptive study activities to confidently reach their learning goals. We’re on track to become the undisputed leader in user-generated learning content and engagement, at the scale of YouTube.
Valued at $1 billion, Quizlet has raised over $60 million in venture capital from investors including Icon Ventures, Union Square Ventures, General Atlantic, Costanoa Ventures, Owl Ventures, and Altos Ventures.
To serve our global community of learners, our teams tackle lofty technical challenges and design for use cases across cultures and languages. We work hard, act like owners, and collaborate every chance we get. We’re energized by the potential to power more learners through multiple approaches and various tools.
With offices in major cities around the world and ambitious plans for expansion, we remain grounded in our commitment to our mission of helping people learn. We’re looking for new team members who crave a challenge and want to help us continue amplifying our impact. If you’d like to learn more, reach out at or visit our careers page.
About the team:
The Android team is focused on building the best app to help people learn on their Android devices. The team works with other product teams across the organization to ensure we’re building mobile-first experiences that allow students to get the most out of Quizlet on their Android phones and tablets.
We collaborate with Product Managers, Designers, Data Analysts, iOS Engineers, and Web Engineers from other teams to ensure their vision aligns with the way Android does things.
As a platform team, we ensure the Android application is robust, defect-free, and fast. Besides implementing new features, we also ensure our tech-debt is kept in check, and plan to refactor to modernize the older parts of our codebase.
A breakdown of the average day for this role:
As a Senior Android Engineer on the Android team, an average day likely starts by working on what's the highest priority for your current area of focus. We follow the Kanban process, so you then join the rest of the team at 10 AM Pacific to walk the board and help communicate status on any of your stories that are still in-progress, highlighting anything that might be getting in your way or in the way of the team.
Some days, you’ll meet with the team to plan and discuss what goals the team can accomplish in the next couple of weeks and what will need to be done to accomplish them. Similarly, after every 2 weeks, you’ll meet for a team retrospective to discuss what has gone well and what could be improved in our development process.
Typically, the team aims to schedule meetings between 10 am and 2 pm, so that you have blocks of uninterrupted time in the morning and the afternoon to focus. Though Wednesdays are our no-meetings day, so you can expect to have a whole day to really push work forward!
During the uninterrupted time, typically you get deep into coding and building the things you researched and estimated. Another good use of this time is to set up a pair-programming session with another engineer that has experience in the codebase you’re working on, or that wishes to learn more about that part of the codebase.
You can also use that time to research a project and identify what will need to be groomed with the product manager, or what questions you need to ask the designer, or how does the project need to be structured to work with our data along a data scientist, or what specific events will the data analyst need to answer our experiment hypothesis.
This research allows you to understand the product requirements and create an engineering plan to later estimate with a larger group of Android engineers to ensure your approach is sound and others are familiar with your decisions, and ultimately to help you estimate the work so it can be scheduled at a better time. Once you code the feature and build the tests to ensure it works as designed, you create a pull request where you can help other engineers learn how you built the new feature or fixed a defect, and get feedback to grow as a developer.
Outside the team process and meetings, the Android t
Job Specification