Sea SDE onboarding and first 90 days tips 2026
What does Sea's SDE onboarding process look like in 2026?
Sea's SDE onboarding in 2026 starts with a two‑day orientation, followed by a three‑week buddy‑driven ramp‑up, and ends with a 90‑day review that includes code contribution metrics and peer feedback.
The orientation takes place at Sea’s headquarters in Singapore and introduces new hires to SeaHub, the internal portal that houses policies, benefits, and the Sea Engineering Ladder.
During the first week, each SDE is paired with a buddy who is a senior engineer (L4 or L5) from the same squad; the buddy runs a daily 30‑minute check‑in and walks the newcomer through the SeaStack development environment.
By the end of week three, the new SDE is expected to have submitted at least one small pull request to a non‑critical service, such as the internal tooling for game analytics, and to have completed the mandatory security and data‑privacy e‑learning modules.
How do I set up my development environment at Sea during the first week?
You should allocate the first two full days to installing SeaStack, configuring your IDE, and gaining access to the relevant repositories.
SeaStack is a monorepo‑based platform that uses Bazel for builds and gRPC for inter‑service communication; the setup script is available on SeaHub under “Engineering → Setup Guide”.
Your buddy will grant you read‑only access to the squad’s codebase and help you create a personal feature branch named onboarding/<your‑email>; you will then run the unit‑test suite locally to confirm that the build passes.
A common first task is to fix a typo or improve a comment in the logging utility; this change is reviewed via Phabricator and typically lands within 24 hours, giving you an early confidence boost.
What are the key expectations for an SDE in the first 30 days at Sea?
In the first month, Sea expects you to own a well‑defined feature or bug fix, participate in squad rituals, and begin contributing to the team’s technical documentation.
By day 15, you should have completed at least one end‑to‑end task that touches the product’s user‑facing API, such as adding a new filter to the Sea Games leaderboard service.
Your manager will review your progress during the bi‑weekly one‑on‑one, focusing on code quality, test coverage, and your ability to ask clarifying questions in sprint planning.
Sea’s engineering ladder defines L3 engineers as those who can deliver small, self‑contained changes with minimal supervision; achieving this level by the end of month one is a strong signal of a successful ramp‑up.
How can I build relationships with my team and stakeholders in the first 60 days?
You should schedule informal coffee chats with at least three cross‑functional partners—product, data science, and UX—each week, and treat these conversations as learning opportunities rather than status updates.
Sea encourages “pair‑on‑call” sessions where an SDE shadows a data scientist during a model‑performance review; this helps you understand the latency constraints that affect backend services.
Participating in the weekly squad demo and offering a concise summary of your recent pull request demonstrates visibility and invites feedback.
By the end of month two, having a shared understanding of the squad’s OKRs and being able to articulate how your work supports them is considered a baseline for effective collaboration.
📖 Related: Sea SDE interview questions coding and system design 2026
What metrics do Sea managers use to evaluate SDE performance in the first 90 days?
Managers look at three quantitative signals—code churn, review turnaround time, and ticket completion rate—combined with qualitative feedback from peers and the buddy.
Code churn is measured as the percentage of lines rewritten after the first review; Sea’s benchmark for L3 engineers is under 15 % during the first 90 days.
Review turnaround time tracks how quickly you respond to reviewer comments; the target is to address feedback within one business day on average.
Ticket completion rate compares the number of story points you commit to versus the number you close; Sea expects a ratio of at least 0.8 for new hires.
In addition, the 90‑day review includes a written peer feedback form where teammates rate your communication, willingness to help, and adherence to Sea’s engineering values; a score of 4 / 5 or higher is typically required to pass the probation period.
How should I approach learning Sea's internal tools and codebase?
Start by completing the “SeaStack Fundamentals” self‑paced module on SeaHub, which walks you through the build system, testing framework, and observability stack.
After finishing the module, spend one afternoon exploring the monorepo’s directory structure; locate the service that owns the feature you are working on and read its architecture decision record (ADR).
When you encounter an unfamiliar tool, such as the internal feature‑flag service “Flipper”, ask your buddy for a 15‑minute walkthrough and then try to toggle a flag in a sandbox environment.
Document any gaps you find in the existing wiki and submit a pull request to improve the documentation; this not only reinforces your learning but also contributes to the team’s knowledge base.
Preparation Checklist
- Review Sea’s Engineering Ladder and identify the competencies expected at your target level (L3/L4).
- Complete the SeaStack Fundamentals module on SeaHub within the first three days.
- Set up your development environment using the official Bazel‑based setup script and verify the build passes.
- Schedule introductory chats with your buddy, product manager, and data‑science partner before the end of week two.
- Work through a structured preparation system (the PM Interview Playbook covers effective communication strategies for engineers with real debrief examples).
- Fix a low‑risk typo or documentation issue in your squad’s repository and aim to have it merged within 24 hours.
- Draft a 30‑day plan that outlines one feature bug fix, one learning goal, and one relationship‑building activity per week.
Mistakes to Avoid
BAD: Waiting for your buddy to assign you work before exploring the codebase.
GOOD: Proactively cloning the SeaStack monorepo, reading the ADR for the service you will contribute to, and proposing a small improvement on day three.
BAD: Ignoring code review feedback and pushing the same change again without addressing comments.
GOOD: Responding to each reviewer comment within a few hours, summarizing the changes made in your reply, and requesting a re‑review only after all concerns are resolved.
BAD: Focusing solely on writing new code and neglecting to write unit tests or update existing tests.
GOOD: Treating test coverage as a gatekeeper; ensuring every new function has at least one unit test and running the full test suite before submitting a pull request.
FAQ
What is the typical base salary for a new SDE at Sea in 2026?
A typical base salary for a Sea SDE hired in 2026 is around $152,000 per year, with equity grants averaging 0.025 % and a sign‑on bonus of approximately $22,000. These figures reflect offers extended to L3 candidates during the Q2 2026 hiring cycle.
How long does Sea’s probation period last for SDEs?
Sea’s probation period for new SDEs lasts 90 days, after which a formal review is conducted using code metrics, peer feedback, and manager assessment; successful completion confirms the employee’s level on the Engineering Ladder.
Which internal tools should I prioritize learning during my first month?
Prioritize learning SeaHub for policies and documentation, SeaStack (Bazel‑based build system) for local development, Flipper for feature flagging, and the observability stack that integrates OpenTelemetry with Sea’s internal dashboards; proficiency in these tools is frequently cited in 90‑day reviews as a predictor of strong performance.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.
Related Reading
- Should New Managers at Amazon Buy 1on1 System or Use Internal Tools?
- Cisco PM onboarding first 90 days what to expect 2026
TL;DR
What does Sea's SDE onboarding process look like in 2026?