<div class="content-intro"><p>SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today, SpaceX is actively developing the technologies to make this possible, with the ultimate goal of making life multiplanetary and expanding consciousness to the stars.<br><br>SpaceXSI is building Super Intelligence to help humanity understand the universe. Our teams are building the full Super Intelligence stack: from our Colossus supercomputers, to Grok models, to our suite of applications, including Grok Bot, Grok Build, Grok Imagine, Grok Voice, and X. We're creating a powerful flywheel where more compute trains better models, better models power more useful products, and what we learn from people using those products shapes what we build next.</p></div><h3 data-pm-slice="1 1 []"><span style="font-family: arial, helvetica, sans-serif;">ABOUT THE ROLE:</span></h3> <p><span style="font-family: arial, helvetica, sans-serif;">Develop, maintain, and communicate construction schedules that the field, subcontractors, and leadership can actually use. You will build CPM baselines, update them from real progress, flag risk early, and explain schedule impact of changes, delays, and recovery plans. This is not a data-entry role. You need enough means-and-methods knowledge to challenge a sequence that will not work in the field.</span></p> <p><span style="font-family: arial, helvetica, sans-serif;">Superintendents run the work; project managers own cost and contracts; the scheduler is the person who can tell you what is actually driving the end date, what slips if a trade is late, and whether a recovery plan is real.</span></p> <h3><span style="font-family: arial, helvetica, sans-serif;">RESPONSIBILITIES:</span></h3> <ul> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Build baseline CPM schedules from drawings, specs, estimates, bid packages, and construction sequences (WBS, activity coding, logic, calendars, and constraints used sparingly and correctly).</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Maintain the live schedule: collect progress from superintendents, project managers, and trades; update percent complete, remaining duration, and logic; publish a clean current-period update on a set cadence (typically weekly look-aheads and monthly official updates).</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Own the critical path. Identify near-critical work, float erosion, and out-of-sequence progress. Tell the team <em>why</em> the end date moved, not just that it did.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Produce three-week (or similar) look-aheads that match the master schedule and what the field can actually crew.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Analyze schedule impact of RFIs, change orders, design late-outs, access constraints, long-lead procurement, weather, and labor shortages. Prepare time-impact analyses (TIA) and what-if, recovery, and acceleration scenarios.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Coordinate with project managers, superintendents, estimators, procurement, design, owners/CMs, and subcontractors so the schedule reflects committed dates, not wishful ones.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Resource-load and, where required, cost-load the schedule. Flag crew stacking, craft shortages, and unrealistic production rates.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Prepare narratives, variance reports, S-curves, histograms, and executive summaries for internal reviews and owner/CM submittals.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Support claims and delay documentation with contemporaneous records (as-planned vs. as-built, fragnets, delay categorization) when needed.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Enforce schedule standards: naming, coding, update process, backup, and version control so the file remains auditable.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Facilitate or support pull-planning / Last Planner sessions and convert those commitments into logic in the CPM model.</span></li> <li style="font-family: arial, helvetica, sans-serif;"><span style="font-family: arial, helvetica, sans-serif;">Visit the site regularly. A scheduler who never walks the job will be wrong.</span></li> </ul> <h3><span style="font-family: arial, helvetica, sans-serif;">BASIC QUALIFICATIONS:</span></h3> <ul> <li><span style="font-family: arial, helvetica, sans-serif;">4+ years of construction scheduling on active projects (GC, CM, owner’s project controls, or specialty contractor).</span></li> <li><span style="font-family: ari