cswork / libraryOpen practice workspace

Interview guides · Sea Blue Shipyard

Sea Blue Shipyard Software Engineer Interview Guide

Sea Blue Shipyard Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Sea Blue Shipyard, you will play a pivotal role in the digital transformation of maritime infrastructure. This position sits at the intersection of traditional heavy engineering and modern software solutions, requiring you to bridge the gap between complex physical systems and the digital tools that keep them operational. You are not just writing code; you are building the systems that monitor, calibrate, and optimize shipyards that are vital to global trade and defense. The impact of your work is immediate and tangible. Whether you are developing software to support mechanical calibration, structural integrity monitoring, or large-scale civil infrastructure management, your contributions directly influence safety, efficiency, and project timelines.

This guide is scoped to a Software Engineer candidate at Sea Blue Shipyard.

Focus areas

  • Calibration Engineering
  • Civil Engineering
  • Software Engineering

The Sea Blue Shipyard interview process

Sea Blue Shipyard candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Technical Screening

Initial assessment of foundational knowledge to gauge technical capabilities.

What to demonstrate

  • Initial assessment of foundational knowledge to gauge technical capabilities
  • Depth in Calibration Engineering

How to prepare

  • Answer aloud and timed: How would you design a software interface for a mechanical calibration tool?
  • Answer aloud and timed: Describe your approach to handling sensor data latency in real-time monitoring systems.

Technical Discussions

In-depth conversations focusing on technical skills and problem-solving approaches.

What to demonstrate

  • In-depth conversations focusing on technical skills and problem-solving approaches
  • Depth in Calibration Engineering

How to prepare

  • Answer aloud and timed: How do you ensure software reliability when it interacts with physical hardware?
  • Answer aloud and timed: What are the common challenges when integrating legacy hardware with modern software stacks?

Behavioral Interviews

Interviews that evaluate problem-solving processes and team fit through situational questions.

What to demonstrate

  • Interviews that evaluate problem-solving processes and team fit through situational questions
  • Depth in Calibration Engineering

How to prepare

  • Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
  • Re-read the description of the behavioral interviews above and write down what you would ask to confirm before it.

Where candidates lose points

Focus on the 'Why'

When explaining your past projects, don't just explain what you built—explain the physical or operational problem you were trying to solve.

Prepare for Ambiguity

In the maritime industry, things change. Show us how you adapt when a project's requirements shift due to physical site constraints.

Connect with the Mission

Show that you understand the significance of Sea Blue Shipyard in the broader context of engineering and industry.

Questions & practice

How do you prioritize technical debt when working under tight project deadlines?

Medium · Technical Proficiency & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Describe your process for optimizing code performance in a resource-constrained environment.

Medium · Technical Proficiency & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

What testing methodologies do you employ to ensure software stability?

Medium · Technical Proficiency & Problem Solving

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Explain why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.

Approach

  1. Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
  2. For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
  3. Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
  4. Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.

Follow-up

  • 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
  • A dashboard runs this for 40 owners in one page load. What changes about the design?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

  1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
  2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
  3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
  4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

  • The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
  • A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

How would you design a software interface for a mechanical calibration tool?

Medium · Domain-Specific Engineering

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Describe your approach to handling sensor data latency in real-time monitoring systems.

Medium · Domain-Specific Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do you ensure software reliability when it interacts with physical hardware?

Medium · Domain-Specific Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What are the common challenges when integrating legacy hardware with modern software stacks?

Medium · Domain-Specific Engineering

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

Explain how you would automate the reporting process for structural integrity inspections.

Medium · Domain-Specific Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.

Approach

  1. Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
  2. Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
  3. Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
  4. Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.

Follow-up

  • The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
  • How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?

Suggested practice checklist

Built from the rounds and topics Sea Blue Shipyard candidates report.

Day 1 — Map the Sea Blue Shipyard loop

  • Write out the reported sequence: Technical Screening, Technical Discussions, Behavioral Interviews.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.

Day 2 — Work Calibration Engineering

  • Spend the session on Calibration Engineering, which Sea Blue Shipyard candidates report being tested on.
  • Write one worked example in Calibration Engineering and time yourself on it.

Deliverable: One timed worked example in Calibration Engineering.

Day 3 — Work Civil Engineering

  • Spend the session on Civil Engineering, which Sea Blue Shipyard candidates report being tested on.
  • Write one worked example in Civil Engineering and time yourself on it.

Deliverable: One timed worked example in Civil Engineering.

Day 4 — Work Software Engineering

  • Spend the session on Software Engineering, which Sea Blue Shipyard candidates report being tested on.
  • Write one worked example in Software Engineering and time yourself on it.

Deliverable: One timed worked example in Software Engineering.

Day 5 — Answer out loud: Domain-Specific Engineering

  • Answer aloud, timed: How would you design a software interface for a mechanical calibration tool?
  • Answer aloud, timed: Describe your approach to handling sensor data latency in real-time monitoring systems.

Deliverable: Spoken answers to 2 reported Domain-Specific Engineering question(s), under time.

Day 6 — Answer out loud: Technical Proficiency & Problem Solving

  • Answer aloud, timed: Walk me through a time you had to debug a system that involved both software and hardware components.
  • Answer aloud, timed: How do you prioritize technical debt when working under tight project deadlines?

Deliverable: Spoken answers to 2 reported Technical Proficiency & Problem Solving question(s), under time.

Day 7 — Answer out loud: Behavioral & Collaborative Impact

  • Answer aloud, timed: Tell me about a time you had to explain a complex technical concept to a non-technical stakeholder.
  • Answer aloud, timed: How do you resolve disagreements with team members regarding architectural decisions?

Deliverable: Spoken answers to 2 reported Behavioral & Collaborative Impact question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Walk me through a time you had to debug a system that involved both software and hardware components.

Medium · Technical Proficiency & Problem Solving

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle edge cases where physical sensor input might be corrupted or incomplete?

Medium · Technical Proficiency & Problem Solving

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Tell me about a time you had to explain a complex technical concept to a non-technical stakeholder.

Medium · Behavioral & Collaborative Impact

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you resolve disagreements with team members regarding architectural decisions?

Medium · Behavioral & Collaborative Impact

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a situation where you had to adapt quickly to changing project requirements.

Medium · Behavioral & Collaborative Impact

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

What motivates you to work in the maritime and infrastructure sector?

Medium · Behavioral & Collaborative Impact

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?