Project Engineer Downstream, Capital Projects
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content about responsibilities (How You Will Contribute, What You Will Be Working On, etc). Also qualifications (What You Bring To Plantible). Benefits (Competitive health and wellness benefits...). No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also we should not repeat job title as heading. No Job ID. Remove boilerplate: EEO, fraud alert, etc. Also remove navigation/cookie/legal. Also remove application instructions (like "If you are interested...").
We need to preserve all substantive information. So we need to extract sections: About the role? Could be a brief intro about the role: maybe combine "How You Will Contribute" and "What You Will Be Working On" as responsibilities. Could have a section "About the role" summarizing the role description. But we must not invent content. The posting includes "How You Will Contribute" paragraph: "Plantible is developing the next generation of our commercial production facilities. The Downstream Project Engineer will own the engineering and field execution of the systems that receive harvested biomass and convert it into consistent, high-quality products. You will sit between Plantible's process experts and the people designing, supplying, and building our facilities. Your scope includes biomass preparation, extraction, separation, filtration, purification, concentration, drying, powder handling, packaging, CIP, and the process utilities and controls that support them. You do not need to be the deepest expert in every unit operation. You do need enough technical depth to identify gaps, challenge assumptions, connect the right people, and turn a developing process into systems we can procure, build, commission, and operate."
That's substantive. Could be placed under "About the role" or "Responsibilities". The instruction says use headings like About the role, Responsibilities, etc. We can choose to have sections: About the role (short summary), Responsibilities (list of duties), Requirements (maybe qualifications), Benefits.
We need to use - for any list of duties/requirements/benefits. So we should convert lists to
- . For prose, use
.
We must not repeat job title as heading. So no heading for "Downstream Project Engineer". Also we should not include Job ID.
We need to preserve all substantive information: that includes the list of downstream systems you will own, the list of what you bring, preferred experience, benefits list.
We need to remove boilerplate: EEO statement, fraud alert, etc. Also remove "We Are a Biology Company Plantible, backed by..." maybe that's about company; could be part of About the role? It's about the company. Might be considered "About the role" or maybe we can include a brief "About Plantible" but not required. The instruction says we can include sections only when posting has real specific content. The company description is substantive; we could include an "About the company" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? Might be okay. Or we could omit it if not fitting. But we need to preserve ALL substantive information; we cannot omit company description. So we need to include it somewhere. Perhaps we can include it in a
under About the role heading (since it's about the role context). Or we could create a separate section "About the company" but not allowed heading; but we could still use
with a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Safer to stick to those headings. We can incorporate company description into About the role paragraph.
Thus structure:
About the role
We Are a Biology Company Plantible, backed by Astanor Ventures, Lerer Hippeau, Piva Capital, Kellogg’s, and Vectr Ventures, is a vertically integrated biology company that is unlocking the power in plants in service of people & planet. Our mission is to create solutions that empower customers to make sustainable and regenerative choices without compromising on quality. We are beginning with the food industry. Plantible is developing the next generation of our commercial production facilities. The Downstream Project Engineer will own the engineering and field execution of the systems that receive harvested biomass and convert it into consistent, high-quality products. You will sit between Plantible's process experts and the people designing, supplying, and building our facilities. Your scope includes biomass preparation, extraction, separation, filtration, purification, concentration, drying, powder handling, packaging, CIP, and the process utilities and controls that support them. You do not need to be the deepest expert in every unit operation. You do need enough technical depth to identify gaps, challenge assumptions, connect the right people, and turn a developing process into systems we can procure, build, commission, and operate.
Then responsibilities: we have "What You Will Be Working On" with bullet-like paragraphs each starting with a bold phrase? Actually it's a series of sentences each starting with a capitalized phrase: Connect the Engineering, Develop the Facility Support, Buy the Equipment, Help Build It, Make It Work. Each includes multiple sentences. We could turn each into a - with the content as prose inside. Or we could keep as
but instruction says use
- for any list of duties/requirements/benefits. This is a list of duties, so we should use
- . Each
- can contain multiple sentences.
Thus:
Responsibilities
- Connect the Engineering Translate requirements from Plantible's Engineering, R&D, Operations, Maintenance, and Food Safety teams into clear scopes and deliverables for external engineering partners and vendors.Coordinate the disciplines required for your systems, including process, mechanical, piping, civil, structural, electrical, controls, utilities, and facility infrastructure.Understand where systems interface, make sure every interface has an owner, and drive technical decisions to closure.Maintain engineering deliverables, decisions, dependencies, risks, and open items against the overall project schedule.Surface gaps early. 'Waiting on Engineering' is not a project plan.
- Develop the Facility Support FEL, conceptual design, FEED, and detailed engineering for assigned systems and project packages.Coordinate development and review of Basis of Design documents, equipment lists, utility requirements, layouts, specifications, drawings, and other core project deliverables.Lead design reviews with Plantible subject-matter experts, Operations, and external engineers.Challenge designs for safety, constructability, operability, maintainability, hygienic design, cost, and unnecessary complexity.Translate lessons from Ranchito into engineering standards and repeatable design packages for future Plantible facilities.
- Buy the Equipment Develop technical scopes and bid packages for equipment, materials, and engineered systems.Coordinate RFQs, technical evaluations, bid leveling, vendor selection, and technical alignment before purchase.Manage vendor drawings, calculations, data, documentation, and interfaces with the broader facility design.Track major equipment and materials from specification through fabrication, FAT, delivery, installation, and startup.Understand which decisions and long-lead packages are driving the project schedule and act before they become constraints.
- Help Build It Serve as Plantible's engineering point of contact during construction for assigned systems and scopes.Coordinate RFIs, submittals, design clarifications, field changes, and vendor questions.Maintain a strong onsite presence during active installation: walk the work, verify progress, identify constraints, and drive issues to resolution.Resolve conflicts between drawings, equipment, contractors, and Plantible requirements without losing design intent.Support quality reviews, mechanical completion, punch lists, system turnover, and documentation closeout.
- Make It Work Plan for commissioning and startup before construction is complete.Coordinate vendor startup requirements, FATs, SATs, commissioning, performance testing, and operator training.Work alongside Operations and Maintenance to make sure systems are documented, tested, safe, and ready to operate.Verify that assigned systems achieve required capacity, performance, quality, and reliability.Capture problems and lessons learned and turn them into better standards for the next facility.
Then we have "Downstream Systems You Will Own" which is a list of systems. That could be part of responsibilities or a separate section maybe "Key Systems". But we don't have a heading for that; we could incorporate into responsibilities as another bullet. However we already have responsibilities covering phases. The downstream systems list is more detail of scope. Could be added as another responsibility bullet: "Downstream Systems You Will Own" with list. Since it's a list, we can make a - with inner list? Might be messy. Simpler: add another
- under responsibilities that contains the list of systems as a
inside? But instruction says use - for any list of duties/requirements/benefits. It didn't forbid nested lists. But to keep simple, we could treat the downstream systems as part of responsibilities and just include them as a sentence list separated by commas. However we need to preserve ALL substantive information; we can keep the list as is within a
- using commas.
Thus add another
- with the downstream systems text.
Then qualifications: "What You Bring To Plantible" includes required and preferred. We can split into Requirements (required) and Preferred Experience (preferred). Or we could have a single "Requirements" section containing both required and preferred. But we have headings Requirements, Qualifications, Skills. We could use Requirements for required qualifications, Qualifications for preferred? Or Skills for skills. Let's map:
- Required: Bachelor's degree..., Typically 5-10+ years..., Direct experience..., Experience delivering..., Strong understanding..., Ability to read..., Highly organized..., Willingness to spend...
- Preferred: Owner-side project engineering..., Experience in alternative protein..., Hands-on experience..., Experience with FAT..., Experience scaling...
We could put required under "Requirements" and preferred under "Preferred Experience" but not a standard heading. Could use "Qualifications" for both required and preferred. Or we could have "Requirements" for required, "Preferred Qualifications" for preferred but not in list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate. Let's put required under Requirements, preferred under Qualifications.
Thus:
Requirements
- Bachelor's degree in Chemical, Mechanical, Process, Bioengineering, Food Engineering, or a related engineering discipline.
- Typically 5-10+ years supporting industrial capital projects in food, ingredients, biotechnology, biochemical, pharmaceutical, fermentation, or another hygienic process-manufacturing environment.
- Direct experience with several of the downstream unit operations listed above and a working understanding of how they interact as one process.
- Experience delivering process equipment through specification, vendor selection, design integration, installation, commissioning, and startup.
- Strong understanding of sanitary process systems, hygienic design, CIP, process utilities, instrumentation, controls, and commissioning.
- Ability to read and challenge PFDs, P&IDs, equipment specifications, layouts, utility balances, construction drawings, controls documentation, and vendor submittals.
- Highly organized and able to keep parallel design packages, interfaces, decisions, and deadlines moving.
- Willingness to spend significant time onsite during construction, commissioning, and startup.
Qualifications
- . For prose, use
. We must not repeat job title as heading. So no heading for "Downstream Project Engineer". Also we should not include Job ID. We need to preserve all substantive information: that includes the list of downstream systems you will own, the list of what you bring, preferred experience, benefits list. We need to remove boilerplate: EEO statement, fraud alert, etc. Also remove "We Are a Biology Company Plantible, backed by..." maybe that's about company; could be part of About the role? It's about the company. Might be considered "About the role" or maybe we can include a brief "About Plantible" but not required. The instruction says we can include sections only when posting has real specific content. The company description is substantive; we could include an "About the company" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? Might be okay. Or we could omit it if not fitting. But we need to preserve ALL substantive information; we cannot omit company description. So we need to include it somewhere. Perhaps we can include it in a
under About the role heading (since it's about the role context). Or we could create a separate section "About the company" but not allowed heading; but we could still use
with a custom heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Safer to stick to those headings. We can incorporate company description into About the role paragraph. Thus structure:
About the role
We Are a Biology Company Plantible, backed by Astanor Ventures, Lerer Hippeau, Piva Capital, Kellogg’s, and Vectr Ventures, is a vertically integrated biology company that is unlocking the power in plants in service of people & planet. Our mission is to create solutions that empower customers to make sustainable and regenerative choices without compromising on quality. We are beginning with the food industry. Plantible is developing the next generation of our commercial production facilities. The Downstream Project Engineer will own the engineering and field execution of the systems that receive harvested biomass and convert it into consistent, high-quality products. You will sit between Plantible's process experts and the people designing, supplying, and building our facilities. Your scope includes biomass preparation, extraction, separation, filtration, purification, concentration, drying, powder handling, packaging, CIP, and the process utilities and controls that support them. You do not need to be the deepest expert in every unit operation. You do need enough technical depth to identify gaps, challenge assumptions, connect the right people, and turn a developing process into systems we can procure, build, commission, and operate.
Then responsibilities: we have "What You Will Be Working On" with bullet-like paragraphs each starting with a bold phrase? Actually it's a series of sentences each starting with a capitalized phrase: Connect the Engineering, Develop the Facility Support, Buy the Equipment, Help Build It, Make It Work. Each includes multiple sentences. We could turn each into a- with the content as prose inside. Or we could keep as
but instruction says use
- for any list of duties/requirements/benefits. This is a list of duties, so we should use
- . Each
- can contain multiple sentences.
Thus:
Responsibilities
- Connect the Engineering Translate requirements from Plantible's Engineering, R&D, Operations, Maintenance, and Food Safety teams into clear scopes and deliverables for external engineering partners and vendors.Coordinate the disciplines required for your systems, including process, mechanical, piping, civil, structural, electrical, controls, utilities, and facility infrastructure.Understand where systems interface, make sure every interface has an owner, and drive technical decisions to closure.Maintain engineering deliverables, decisions, dependencies, risks, and open items against the overall project schedule.Surface gaps early. 'Waiting on Engineering' is not a project plan.
- Develop the Facility Support FEL, conceptual design, FEED, and detailed engineering for assigned systems and project packages.Coordinate development and review of Basis of Design documents, equipment lists, utility requirements, layouts, specifications, drawings, and other core project deliverables.Lead design reviews with Plantible subject-matter experts, Operations, and external engineers.Challenge designs for safety, constructability, operability, maintainability, hygienic design, cost, and unnecessary complexity.Translate lessons from Ranchito into engineering standards and repeatable design packages for future Plantible facilities.
- Buy the Equipment Develop technical scopes and bid packages for equipment, materials, and engineered systems.Coordinate RFQs, technical evaluations, bid leveling, vendor selection, and technical alignment before purchase.Manage vendor drawings, calculations, data, documentation, and interfaces with the broader facility design.Track major equipment and materials from specification through fabrication, FAT, delivery, installation, and startup.Understand which decisions and long-lead packages are driving the project schedule and act before they become constraints.
- Help Build It Serve as Plantible's engineering point of contact during construction for assigned systems and scopes.Coordinate RFIs, submittals, design clarifications, field changes, and vendor questions.Maintain a strong onsite presence during active installation: walk the work, verify progress, identify constraints, and drive issues to resolution.Resolve conflicts between drawings, equipment, contractors, and Plantible requirements without losing design intent.Support quality reviews, mechanical completion, punch lists, system turnover, and documentation closeout.
- Make It Work Plan for commissioning and startup before construction is complete.Coordinate vendor startup requirements, FATs, SATs, commissioning, performance testing, and operator training.Work alongside Operations and Maintenance to make sure systems are documented, tested, safe, and ready to operate.Verify that assigned systems achieve required capacity, performance, quality, and reliability.Capture problems and lessons learned and turn them into better standards for the next facility.
- with inner list? Might be messy. Simpler: add another
- under responsibilities that contains the list of systems as a
- inside? But instruction says use
- for any list of duties/requirements/benefits. It didn't forbid nested lists. But to keep simple, we could treat the downstream systems as part of responsibilities and just include them as a sentence list separated by commas. However we need to preserve ALL substantive information; we can keep the list as is within a
- using commas. Thus add another
- with the downstream systems text.
Then qualifications: "What You Bring To Plantible" includes required and preferred. We can split into Requirements (required) and Preferred Experience (preferred). Or we could have a single "Requirements" section containing both required and preferred. But we have headings Requirements, Qualifications, Skills. We could use Requirements for required qualifications, Qualifications for preferred? Or Skills for skills. Let's map:
- Required: Bachelor's degree..., Typically 5-10+ years..., Direct experience..., Experience delivering..., Strong understanding..., Ability to read..., Highly organized..., Willingness to spend...
- Preferred: Owner-side project engineering..., Experience in alternative protein..., Hands-on experience..., Experience with FAT..., Experience scaling...
We could put required under "Requirements" and preferred under "Preferred Experience" but not a standard heading. Could use "Qualifications" for both required and preferred. Or we could have "Requirements" for required, "Preferred Qualifications" for preferred but not in list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate. Let's put required under Requirements, preferred under Qualifications.
Thus:
Requirements
- Bachelor's degree in Chemical, Mechanical, Process, Bioengineering, Food Engineering, or a related engineering discipline.
- Typically 5-10+ years supporting industrial capital projects in food, ingredients, biotechnology, biochemical, pharmaceutical, fermentation, or another hygienic process-manufacturing environment.
- Direct experience with several of the downstream unit operations listed above and a working understanding of how they interact as one process.
- Experience delivering process equipment through specification, vendor selection, design integration, installation, commissioning, and startup.
- Strong understanding of sanitary process systems, hygienic design, CIP, process utilities, instrumentation, controls, and commissioning.
- Ability to read and challenge PFDs, P&IDs, equipment specifications, layouts, utility balances, construction drawings, controls documentation, and vendor submittals.
- Highly organized and able to keep parallel design packages, interfaces, decisions, and deadlines moving.
- Willingness to spend significant time onsite during construction, commissioning, and startup.
Qualifications
- for any list of duties/requirements/benefits. This is a list of duties, so we should use
- with the content as prose inside. Or we could keep as