I'll be starting at FB soon. From the convo I had with existing engineers and manager I have come to understand that there are generally no sprint cycles or daily stand-ups? And are people working on 6 month long projects? So as an E5 engineer am I supposed to come up with most impactful project or projects to work on for the next 6 months and then set goals and accomplish them? This is very different from every other company I've worked for, where projects come from the product manager or higher ups. And we work in 2 week sprint cycles. And projects usually change quarterly. How to adjust to this new setting, any tips?
Depends on the team. On my previous team, we had standups and no sprints. On my current team, no standups or sprints. And yes, E5 is expected to come up with projects.
Can you give me some insight into how you come up with a project? I'm not 100% sure if I'm a product oriented person. I am a good coder if you tell me what to do. But how do I come up with what to code?
But who forms teams? How big the teams are?
no stand ups or sprints. it’s organized chaos.
Can you elaborate on how this works? Super curious
exactly what it sounds like—engineers find scope and manage their own projects and are responsible for delivering. it kinda works because fb engineers are v good and driven by PSC, but it’s definitely not the most structured environment i’ve been in.
Tech Industry
Yesterday
1196
The end of Backdoor Roth?!
Tech Industry
Yesterday
322
What does it mean to have a bunch of McKinsey contractors hired in "strategy" roles
India
Yesterday
465
Modi is a legend, will be remembered for centuries to come
2024 Presidential Election
Yesterday
551
Heartwarming peaceful protests
India
Yesterday
566
Who are these retards asking for dictatorship in India?
We have stand-ups twice a week and monthly sprint cycles. Depends a lot on the team.
How about picking what you are working on. Who comes up with that? Are engineers supposed to look for what will create most impact for the company and break it down into stories and work on those?
Depends on the team, generally speaking, E5s are responsible for contributing to the roadmap as well (working with EMs, design, PM, etc.) there are specific instances of E5s that I know who are just coding machines & execute at a much quicker rate than anyone else, and they tend to be less roadmap driven