Company
Saildrone
Annual salary
$145k – $300k/yr
Location
Alameda, CA
Listed
50d ago
- Experience:
- 4 to 8 years
- Workplace:
- This is a hybrid role. Engineers are expected in the office 3 days a week at Saildrone's headquarters in Alameda, CA, where most of the engineering team works. Candidates must already be in the SF Bay Area (e.g., San Francisco or Alameda) and able to commute, because relocation support is not offered for this role.
- Equity:
- Equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Hybrid in Alameda, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
What you'll do
- Design, build and operate production cloud services that ingest, process, store and expose sensor, detection and operational data from Saildrone's fleet of autonomous surface vessels (USVs)
- Take ownership of projects that span multiple repos in an existing codebase. You'll debug, refactor and improve that infrastructure as it scales, rather than starting new projects from scratch
- Work closely with the Fleet Engineering hiring manager and front-end-focused teammates to give downstream applications and mission operators the backend services and APIs they need
- Develop backend services and APIs in Python and TypeScript that connect vessels with intermittent connections to the applications used to monitor and operate them
- Lead the design of data models and database systems for operational and sensor-derived data, from early design through production rollout
- Deploy, monitor and debug services in AWS, improving reliability, scalability, observability and graceful handling of delayed or incomplete data
What you need
- We need a backend-leaning engineer with about 4, 8 years of experience building and running production cloud and distributed systems. You must be strong in both Python and TypeScript, not just one of them. You should be comfortable working in an existing legacy codebase, debugging and making changes across several repos without much hand-holding. You should also have a track record of owning production services and APIs from design through deployment and operation, ideally on AWS. Bonus points if you've worked with real-time or streaming data, or with telemetry, sensor or geospatial data from robotics, autonomous vehicles, IoT, aerospace or defense systems.
- This is a mid-level role on Saildrone's new Fleet Engineering team. It is called full stack, but about 80, 90% of the work is platform and APIs. The front end is a small part of the job. More senior engineers with the right hands-on skills are also welcome.
Common questions
How do I apply for the Software Engineer, Full-Stack (US) role at Saildrone? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Saildrone role pay? +
The listing gives $145k – $300k/yr.
Is this role remote? +
The listing gives the location as Alameda, CA. This is a hybrid role. Engineers are expected in the office 3 days a week at Saildrone's headquarters in Alameda, CA, where most of the engineering team works. Candidates must already be in the SF Bay Area (e.g., San Francisco or Alameda) and able to commute, because relocation support is not offered for this role.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →