Placement into teams is pretty flexible and you can move around / try out teams after joining.
Honestly, I had a great experience with LD, and LD moves really fast! Apart from waiting for the initial recruiter screen which took maybe 2 weeks, everything else had a 1 business day turnaround.
They were willing to schedule the onsite the day after my coding challenge submission in order to meet an offer deadline I had for another company, which was super nice and flexible of them and their engineers!
I really liked the coding challenge, I thought it was reasonable to expect BE engineers to know how to build microservices with minimal guidance and I learned a good deal from it. I spent 10 hours because I picked a language and framework I didn't use for work (Python) so I probably could have spent less time if I used a framework I knew.
Onsite:
LD is very profitable and has happy engineers and a great engineering culture (described in their values page) that I personally vibed with - I would have chosen them if not for a competing offer where I really liked the team match in the other company.
Coding challenge: build a REST microservice that consumes SSE using any language / framework. No need to use a DB framework (think they updated the spec so it could be completed faster).
Onsite:
The following metrics were computed from 3 interview experiences for the LaunchDarkly Software Engineer role in Oakland, California.
LaunchDarkly's interview process for their Software Engineer roles in Oakland, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for LaunchDarkly's Software Engineer interview process in Oakland, California.