Python Developer Interview Experience - San Francisco, California
Process
I was asked to code a fairly basic web-related tool, which I did. They said it looked great, and I was invited for an in-person interview at their HQ.
At the onsite interview, I pair-programmed with a Square developer for about an hour on a web-related script, and I more or less got it working.
A couple of days later, they got in touch and said they wouldn't be continuing the interview process.
Questions
They seemed to be searching for someone who knew which tools to use to create the script without doing any research.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Block Python Developer role in San Francisco, California.
Success Rate
Block's interview process for their Python Developer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Block's Python Developer interview process in San Francisco, California.
Block Work Experiences
- 5.0Good place to work atSoftware Engineer • Current EmployeeSan Francisco, California, United StatesOctober 7, 2017Pros: Good place to work at. Good environments and food.Cons: Lots of movements/reorg etc. Bad refreshment/bonus. Mediocre benefits.
- 5.0Great people, great cultureSoftware Engineer • Former EmployeeSan Francisco, California, United StatesFebruary 6, 2021Pros: Some of the most amazing ICs I've ever worked with. Incredibly talented and driven teams, a high bar for quality, and genuinely kind people.Cons: Disputes and politics between leadership often impacted the entire organization negatively.
- 4.0Good first jobSoftware Engineer • Current EmployeeSan Francisco, California, United StatesAugust 8, 2016Pros: My coworkers are great. I really enjoy working with my team, and we get along very well. Both my manager and his manager were previous engineering leads who worked up to senior positions, which I really like.Cons: Documentation is not the best, and there's a lot of "tribal knowledge." Some growing pains are due to recent expansions. For example, a lot of tools that worked while we were smaller aren't working so well now (though this is a work in progress to build new ones).
Block Interview Questions
