Skip to content

Instantly share code, notes, and snippets.

@narcisbcn
Created April 4, 2019 22:01
Show Gist options
  • Save narcisbcn/792adf5c25eb66818be527d03b693f0d to your computer and use it in GitHub Desktop.
Save narcisbcn/792adf5c25eb66818be527d03b693f0d to your computer and use it in GitHub Desktop.
Introduction
------------
letgo's the largest app to buy and sell locally. With over 100M downloads and hundreds of millions of listings added by users, letgo’s already been named among the “Hottest Startups” by Wired and “Best Apps” by Google, and it’s the second fastest growing app in America since its 2015 launch. Business Insider calls letgo “the go-to app for selling your stuff” and it’s been featured by The New York Times, The Today Show, Mashable, Fast Company, The Wall Street Journal, Fortune and hundreds of others worldwide. Listing something on letgo is as simple as taking a photo thanks to its advanced technology. It’s the only app of its kind that can automatically title and categorize an item using artificial intelligence. Users can easily browse local listings, chat instantly in the app, and view each other’s profiles, ratings and reviews.
Based in our New York and Barcelona offices, our team of over 230 represents more than 40 nationalities. Fueled by our diverse expertise, letgo’s goal is to build the largest marketplace of its kind in the world.
Technology @ letgo
Currently at letgo we are using squad methodologies to be organized as a company. This methodology consists on having multidisciplinary teams where mostly are composed by:
Technical Project Manager
Software Engineers (Backend, Mobile and/or Web)
DevOps
Quality Assurance
Product Manager
Data Science and/or BI Analyst
Designer
Questions:
----------
ORGANIZATION:
=============
How is the engineering team organized?
How is the whole company organized?
How you manage dependencies between teams?
Which team organizations did you tried in the past and didn’t worked?
What methodologies do you use to manage your projects?
Do you have deadlines? How do you enforce them?
How do you decide product priorities? They come from the product team or it is a decision between Tech&Prod
If you have multidisciplinary teams, how do you organize the time which have to be carried on product tasks vs technical tasks?
TECH ORGANIZATION:
==================
How do you manage many teams working in the same codebase?
How do you define company’s best engineering practices? How do you enforce them?
How are engineer’s trainings, conferences, etc being managed?
If you are working in squads, how the team is organized, is there any Scrum Master position or this role is taken by the developers?
How does the rotation between teams work?
How do you push transversal tasks from core teams which have to be implemented on multidisciplinary teams
Do you have internal projects? how do you organize them and how do you decide who will participate on them?
Do you have hackathons?
Regarding beta releases: Can a beta release get production traffic? Do you have internal betas? Which is your release cycle? Do you have continuous deployment?
GROWTH:
=======
Do you have a career plan? How do you help engineers to grow?
How do you focus mentorship? And technical leadership?
How can a developer start coding in different code languages, different roles?
MANAGEMENT:
===========
Who’s the engineer’s manager? What are their responsibilities?
How do you track 1:1, how do you share with your team if you does?
QA
==
How do you take into account QAs work into teams’ plannings?
Regarding the bugfixing: how do you prioritize the bug backlogs? When do you consider that a release has to be stopped? Can a bug be in a todo status forever? who is the ownership to have that bug fixed? Do you have strategies such us bug fixing day? Is there a limit of open bugs?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment