Data Engineering at Block
Roles, Comp & Culture
Reviews put them at 3.6 on Glassdoor, a little below the middle of the pack. Employee sentiment at Block reads neutral and employee happiness is trending down over the past year.
Block
Finance · US
live data · August 2, 2026
DE total comp
$350K–$490K
senior level · full ladder below
Hiring now
No open DE roles
tracked daily
Team happiness
Neutral
driven by industry_layoff_event_density_3mo_v1__ewma52
Employee sentiment
3.6 / 5Block employee sentiment, tracked weekly
Employee happiness for data engineers over the past year, so you can see which direction it is moving, not just where it sits today.
Block is a company where the employer reputation has slipped relative to where it stood during the Square-era growth years. The Glassdoor rating sits at 3.6, a little below the middle of the pack, and internal sentiment is neutral and trending down. That combination usually signals organizational friction rather than a compensation problem. Block went through significant workforce reductions in 2023 and has been restructuring around fewer, more focused product bets since. What you get is genuine technical scope: a multi-currency, multi-product payments business creates data problems that are harder than most fintechs your seniority band will see. What you give up is the forward momentum that makes ambiguous work feel purposeful; engineers who need a clear mandate and stable team structure have found this period uncomfortable.
The hiring signal right now is as thin as it gets: no open data engineering roles as of Aug 2, 2026. That's not a data engineering org that's scaling. Block has been in cost-discipline mode since 2023, and the absence of open roles in 2026 suggests the data engineering headcount has been absorbed into whatever the post-restructuring steady state looks like, or the org is still figuring that out. Someone joining now would be walking into a function that has already absorbed cuts and may face another round if the broader fintech credit cycle tightens further. The 12-month outlook favors people who can do a lot with a small team, not people counting on headcount to grow around them.
Walk into Block knowing the SQL pattern they'll test.
Block's core data problem is financial: Square, Cash App, and Afterpay each generate transaction streams that need to be reconciled, risk-scored, and reported under separate regulatory regimes, often in real time. A data engineer here is working across payment processing, lending, and peer-to-peer money movement simultaneously, which means schema ownership gets complicated fast. The fintech regulatory surface (KYC, AML, PCI-DSS, state money transmitter licenses) pushes a lot of pipeline work toward auditability and lineage rather than pure throughput, so pipelines carry compliance weight that a typical SaaS data team wouldn't see. Block's multi-product structure means you're unlikely to own a single clean domain; expect to straddle product lines and negotiate with multiple platform teams.
Consecutive Cost Growth Periods
> Find periods where total cloud spending increased for 2 consecutive billing periods. Return the starting bill date of each growth streak and its length.
Engineers who do best here are comfortable in regulated financial data environments and don't need a large team to feel productive. If you've worked in payments, lending, or fraud and you can reason through compliance constraints without treating them as someone else's problem, Block's cross-product scope is genuinely interesting work. Candidates who want a company trending upward on culture signals, clear headcount growth, or a well-defined data engineering ladder with published comp benchmarks should look elsewhere first; none of those conditions are met right now. The strongest fit is a mid-to-senior engineer who has seen a fintech restructuring before and knows how to deliver in that environment. If you're still interested after reading the signals honestly, prep for a loop that will care about data modeling, pipeline reliability, and your experience with regulated data.
Preparing for the Block loop
The round-by-round process, example questions, and prep plan are on the interview guide.
Compare Block with other data engineering employers
How the role, pay, and loop stack up against peer companies.
Prepare at Block interview difficulty
- 01
Reading a solution is not the same as writing one
Every engineer who has frozen on a query they had read a dozen times knows the gap. The only preparation that closes it is producing the answer yourself, under time, before the interview does it for you
- 02
76% of hiring managers reject on the coding task, not the resume
From HackerRank's 2024 Developer Skills Report. Candidates who look strong on paper still fail the live screen if they haven't done timed, executable practice
- 03
5 problem shapes cover 80% of data engineer loops
Dedup, sessionization, top-N-per-group, slowly-changing dimensions, partition tricks. Writing the shapes by hand turns the unfamiliar into pattern recognition