Boeing · Primly Community

Boeing coding interview / online assessment, format and difficulty: what I actually got (2026)

sre_sol · 4 replies

ok so i was terrified going into this because i'd only been leetcoding for like 3 weeks and my internship experience is limited. sharing what the OA actually looked like because the internet is full of 2021 posts that are probably not accurate.

format: got two coding problems on Codility, 90 minutes total. one SQL question thrown in at the end (i was not expecting that).

difficulty: honestly lower than i feared. the coding problems were LeetCode easy-to-low-medium level. think: reverse a linked list variant, and a sliding window problem on an array. nothing with dynamic programming or graph traversal with backtracking. the SQL question was a basic JOIN with a GROUP BY.

this was for an entry-level software engineer role, fwiw. i've heard the bar goes up for senior roles but at this level it seemed really accessible.

a few things that caught me off guard: the timer is per-problem, not cumulative. so if you finish the first one early the extra minutes don't carry over there was a brief video intro prompt at the start asking me to describe a project i worked on. not graded i think but still startling i submitted at like 11pm and got a human response within 2 business days, so they actually look at these

got invited to a phone screen so something worked. prep-wise i'd say: brush up on array/string basics, know how to write a decent JOIN, and don't panic about hard LC stuff for entry level.

side note: the Codility platform is clunky. test your environment before the real thing.

4 replies

bootcamp_bri

this is so reassuring. i've been stress-grinding hard problems for a week. sounds like medium is probably the ceiling for entry level and i should make sure my easy/medium are super clean and fast instead.

analyst_ana

the SQL question showing up in a SWE OA is interesting. did they specify what the SQL was querying against conceptually, or was it like a generic employees/orders table?

jp_newgrad

it was a generic table structure, something like flights and maintenance records. nothing domain-specific that required aerospace knowledge. just basic relational query.

numbers_only

good data point. confirms what i've seen elsewhere: Boeing at entry-level is not trying to be Google. they want engineers who can build reliable systems, not solve puzzles under pressure. different philosophy.