← Back to Directory

Bilt

Mid-sized

Screna has 4 Bilt interview write-ups. The most reported round is the technical phone screen (3).

4 interview notes · updated Jul 2026

Bilt·Software Engineer·Technical Phone Screen

Jul 2026
Bilt Rewards software engineer interview that was basically one big SQL and data pipeline problem. The whole thing revolved around a merchant CSV and a transactions table, and they pushed pretty hard on design reasoning, not just syntax.
  • Given a CSV file with merchant data and a database transactions table, how would you load the CSV into a staging table?
  • Write a single SQL query that joins transactions to merchants and returns user_id, merchant_code, category, base_points as FLOOR(amount), and final_points where restaurant transactions get 3x and everything else gets 1x. Unmatched merchants should return 'UNKNOWN' for code and category.
  • Why might doing this transformation in SQL with JOINs and CASE expressions be better than handling it in application code after fetching the raw data?
  • What indexes would you add and what data-cleaning steps would you apply? Also, how would you handle approximate or inconsistent merchant name matching?

“Pretty mechanical but I fumbled explaining whether I'd validate the CSV before loading or after.”

View Post

Bilt·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Bilt for a software engineer role, basically one big question about mentorship. Pretty conversational but they wanted a lot of detail so it ran longer than I expected.
  • Tell me about a time you mentored someone. Walk through how it started, what their level and goals were, how you structured the relationship, a specific moment where you helped them grow, and what the measurable outcome was. Also what did you learn about yourself as a mentor?

“This is a lot of sub-parts crammed into one question and I did not pace myself well.”

View Post

Bilt·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Bilt and the technical portion was basically an interrogation into whether you actually wrote the code on your resume or just managed people who did. Come prepared with specifics or you'll get eaten alive.
  • For a project on your resume, walk me through exactly how much of your time went toward writing code versus designing, meeting, or coordinating. Which files or modules did you own, what languages, rough lines of code, and tell me about a specific bug you had to debug.

“This one exposed me a bit.”

View Post

Bilt·Software Engineer·Technical Phone Screen

Apr 2026
Bilt Rewards gave me a small Java debugging exercise for a credit-card rewards service. Three unit tests were failing and the job was to fix the code without writing new tests, touching at most three files. Pretty focused technical screen, no fluff.
  • You're given a Java project with three failing unit tests related to a credit-card rewards service. Without adding new tests, make minimal code changes across up to three files to get them all passing. Walk through how you'd debug and fix each failure.
  • After fixing the bugs, how would you prevent these kinds of regressions from coming back in the future?

“The three tests were around restaurant triple-points logic, a missing merchant code case, and daily points aggregation.”

View Post