Senior Project Controls Engineer (US)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- Intro: "Join nPlan — build the cities of the future We’re nPlan, a Series B startup backed by leading investors, including GV (formerly Google Ventures) and DeepMind’s founder, Sir Demis Hassabis. Our technology helps the world’s biggest construction projects make faster, more confident, data-driven decisions. By combining one of the world’s largest datasets of project plans with advanced machine learning, we forecast project outcomes and reduce risk — reshaping how infrastructure gets built."
That's about company. Could be placed under maybe "About the role"? Actually "About The Role" heading appears later. The posting includes a section "About The Role" with bullet points.
We need to decide sections.
We have:
- About The Role (description of role responsibilities). This includes bullet list: Client engagement, Product deployment, Commercial, Product, Mentorship and management.
- What We're Looking For (requirements/qualifications). This includes bullet list: Approximately 3+ years experience..., Client-facing transformation experience..., Good understanding..., Demonstrable experience..., Passion..., Attention to detail..., Excellent relationship-building skills..., Nice to haves...
- Why You'll Love Working Here (benefits, pay, schedule, culture). Contains: Competitive salary between $80k - $110k + generous equity, Flexible hours, remote-friendly, with a Shoreditch office HQ, Uncapped holiday, private medical insurance, personal learning and development budget, enhanced family and sick leave, and more, Room to grow..., Guided by our values..., Listen to interviews..., Our Culture...
- Application Process (but we must remove application instructions). The instruction says: remove application instructions. So we should drop the "Application Process" section entirely.
- Accessibility & Inclusion (maybe keep? It's not boilerplate? It's inclusion statement. Might be considered boilerplate but it's substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is inclusion statement, could be considered EEO. Probably remove.
Thus we keep: About the role (maybe as "About the role" heading), Responsibilities (maybe we can treat the bullet list under About The Role as responsibilities), Requirements (maybe "What We're Looking For" as requirements/qualifications), Benefits (maybe "Why You'll Love Working Here" includes benefits, pay, schedule, culture). We need separate headings for Pay, Schedule, Benefits if content exists.
We have Pay: "Competitive salary between $80k - $110k + generous equity". That's pay.
Schedule: "Flexible hours, remote-friendly, with a Shoreditch office HQ." That's schedule.
Benefits: list of uncapped holiday, private medical insurance, personal learning and development budget, enhanced family and sick leave, etc. Also "Room to grow — we’re just over 50 people and scaling fast." maybe culture.
We also have "Guided by our values: Learn from Everything. Be Radically Truthful. Aim High, Run Fast." and "Listen to interviews with our team here, to hear how they found the move from construction to tech". That's culture.
We could combine culture into Benefits or maybe a separate section? The instruction says prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits (including pay, schedule, perks). But we need to follow rule: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples but not mandatory to include all; we should include a section only when posting has real specific content. So we can include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. But we might combine Pay and Schedule into Benefits? The rule says prefer few substantive sections over many thin ones. So maybe we combine Pay and Schedule into Benefits section, but we still need to include Pay and Schedule headings only if they have specific content. Could include them as subheadings? But only allowed headings are . Could we have multiple sections: About the role, Responsibilities, Requirements, Benefits (which includes pay, schedule, perks). That would be few sections.
But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not require all. It says "Prefer a few substantive sections over many thin ones." So we can combine.
Thus we will output:
About the role
. Could we have multiple sections: About the role, Responsibilities, Requirements, Benefits (which includes pay, schedule, perks). That would be few sections.
But the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not require all. It says "Prefer a few substantive sections over many thin ones." So we can combine.
Thus we will output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not require all. It says "Prefer a few substantive sections over many thin ones." So we can combine.
Thus we will output:
About the role
... company description and role overview? Actually About the role should contain description of role and maybe what you'll do. We have "The Role" paragraph earlier: "We are looking for a Senior Project Controls Engineer...". Also "About The Role" section later with bullet list. We'll combine. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep the details. Let's extract substantive content: Company intro: "Join nPlan — build the cities of the future We’re nPlan, a Series B startup backed by leading investors, including GV (formerly Google Ventures) and DeepMind’s founder, Sir Demis Hassabis. Our technology helps the world’s biggest construction projects make faster, more confident, data-driven decisions. By combining one of the world’s largest datasets of project plans with advanced machine learning, we forecast project outcomes and reduce risk — reshaping how infrastructure gets built." Role description: "We are looking for a Senior Project Controls Engineer with a background in project controls, risk analysis and/or complex construction schedules of major projects to join our growing client team. You will also have exposure to generative AI (personal or professional) and a strong interest in this space. In this role, you’ll use your expertise to help our clients maximise the value they get from nPlan, and be part of the change to revolutionise the industry. If you’ve ever been frustrated by the limitations of QSRA workshops, poor forecasting data, or limited time for analysis, this could be the job for you. You’ll have autonomy, ownership, and trust from day one, and you’ll be working with talented people who care deeply about our mission. While you work remotely, you will also attend monthly client visits and team meetings in our London office as well as have the opportunity to visit our international clients." About The Role bullet list: - Client engagement: Coaching our most important clients on how they can maximise the value they get from nPlan. Building, maintaining and growing strong relationships within client organisations, understanding their needs and pain points. Setting up the product so it brings maximum value to our clients. - Product deployment: Managing strategic projects to improve how we embed our products within client organisations. Mentoring clients on how to use our advanced features (e.g. LLM-based features) to best support clients. - Commercial: Collaborating with the Commercial team to drive engagement, retention, and expansion. - Product: Working closely with Product Managers and AI Engineers on prototyping. Becoming a key domain-expert link in our LLM evaluation cycle to ensure reliable, accurate analyses. - Mentorship and management: Potential line management of more junior client engineers. Why You'll Love Working Here: - Competitive salary between $80k - $110k + generous equity - when nPlan succeeds, so do you! - Flexible hours, remote-friendly, with a Shoreditch office HQ. - Uncapped holiday, private medical insurance, personal learning and development budget, enhanced family and sick leave, and more. - Room to grow — we’re just over 50 people and scaling fast. - Guided by our values: Learn from Everything. Be Radically Truthful. Aim High, Run Fast. - Listen to interviews with our team here, to hear how they found the move from construction to tech. Our Culture: "We’re a curious, diverse, and mission-driven team united by a belief that better data can change how the world builds. We value openness, honesty, and diversity of thought — and believe the best ideas win, no matter where they come from. Expect openness, collaboration, and balance — plus plenty of socials!" We could incorporate culture into Benefits or maybe a separate section but we want few sections. Thus we can have sections: - About the role (company + role overview) - Responsibilities (the bullet list under About The Role) - Requirements (What We're Looking For) - Benefits (including pay, schedule, perks, culture) We need to ensure we don't repeat job title as heading. We are not. We need to use
- for any list of duties/requirements/benefits, and
for prose. Thus:
About the role
Join nPlan — build the cities of the future We’re nPlan, a Series B startup backed by leading investors, including GV (formerly Google Ventures) and DeepMind’s founder, Sir Demis Hassabis. Our technology helps the world’s biggest construction projects make faster, more confident, data-driven decisions. By combining one of the world’s largest datasets of project plans with advanced machine learning, we forecast project outcomes and reduce risk — reshaping how infrastructure gets built.
We are looking for a Senior Project Controls Engineer with a background in project controls, risk analysis and/or complex construction schedules of major projects to join our growing client team. You will also have exposure to generative AI (personal or professional) and a strong interest in this space. In this role, you’ll use your expertise to help our clients maximise the value they get from nPlan, and be part of the change to revolutionise the industry. If you’ve ever been frustrated by the limitations of QSRA workshops, poor forecasting data, or limited time for analysis, this could be the job for you. You’ll have autonomy, ownership, and trust from day one, and you’ll be working with talented people who care deeply about our mission. While you work remotely, you will also attend monthly client visits and team meetings in our London office as well as have the opportunity to visit our international clients.
Responsibilities
- Client engagement: Coaching our most important clients on how they can maximise the value they get from nPlan. Building, maintaining and growing strong relationships within client organisations, understanding their needs and pain points. Setting up the product so it brings maximum value to our clients.
- Product deployment: Managing strategic projects to improve how we embed our products within client organisations. Mentoring clients on how to use our advanced features (e.g. LLM-based features) to best support clients.
- Commercial: Collaborating with the Commercial team to drive engagement, retention, and expansion.
- Product: Working closely with Product Managers and AI Engineers on prototyping. Becoming a key domain-expert link in our LLM evaluation cycle to ensure reliable, accurate analyses.
- Mentorship and management: Potential line management of more junior client engineers.
Requirements
- Approximately 3+ years of experience in a planning, risk, PMO, or project management role on major construction projects.
- Client-facing transformation experience, where you’ve worked to change processes with clients, where the change was challenging to implement and involved multiple stakeholders agreeing to a new way of working (preferably related to technology).
- Good understanding of large construction schedules (P6), how they are built, and how to analyse them.
- Demonstrable experience in implementing strategic projects that significantly improve an important outcome for an organisation.
- Passion for implementing technology to improve the construction industry.
- Attention to