Tulip MES (Manufacturing Execution System) Developer

Role: Tulip MES (Manufacturing Execution System) Developer Location: Milpitas, CA- Onsite Duration: 3+ Months Brief Information: • This position supports the Tulip MES (Manufacturing Execution System) implementation within the manufacturing environment. • The group is focused on converting paper-based manufacturing and quality records into electronic files through Tulip applications. • The role primarily involves creating, configuring, and maintaining applications within Tulip to support manufacturing and quality operations. • The environment includes electromechanical devices such as flow cytometers, optics, actuators, transducers, motors, PCBAs, fluidics, tubing, and large-scale equipment used in assembly and testing. • The candidate must be able to hit the ground running — no training will be provided. • Medical device experience is not required, but familiarity with regulated or manufacturing environments is preferred. • The role is fully onsite, Monday through Friday, in Milpitas, CA. • Assignment will likely be extended depending on performance and project needs. • Resume submission deadline: 10/22 at 1:00 PM EST. Qualifications & Requirements / Skillset: • Bachelor’s degree required in Computer Science, Process Engineering, Continuous Improvement, or a related field (preference for Computer Science). • Minimum 3 years of experience in a manufacturing environment. • Strong understanding of Manufacturing Execution Systems (MES) — Tulip experience is required or at least hands-on familiarity to contribute immediately. • Ability to create and configure applications, not hardcore coding. • Knowledge of software development principles, automation, and process control. • Familiarity with C#, .NET, or Java (hiring manager to if this is required). • Agile experience is not mandatory. • Excellent communication, problem-solving, and documentation skills. • Ability to collaborate with manufacturing engineers to map production routes and create digital applications that reflect assembly, testing, and product flow. Q&A: Q1: What percentage of the work involves new development versus enhancing existing Tulip applications? A1: The majority of the work involves new development. The team is currently developing and piloting new Tulip applications that replace paper-based records. Enhancements may occur later, but initial efforts are heavily focused on new builds guided by existing pilot structures. Q2: Are you open to candidates who have MES development experience in other platforms? A2: Yes, but the candidate must be able to hit the ground running. The team currently has no bandwidth for training, so prior Tulip experience is strongly preferred. Candidates who have built applications in other MES systems may be considered if they demonstrate hands-on Tulip knowledge. Q3: What kind of cloud infrastructure hosts the Tulip environment — AWS, Azure, or Tulip Cloud? A3: The system runs entirely on Tulip Cloud. Q4: Is there any possibility of extension or conversion for this role? A4: The assignment is initially set for a few months, but since the project spans nearly a year and a quarter, extension is highly possible depending on performance and project requirements. Conversion cannot be promised at this stage. Q5: What programming languages or tools are being used for application development? A5: The team primarily focuses on application creation and configuration rather than extensive coding. C#, .NET, or Java may be used for integration components (hiring manager to confirm). Q6: Are you open to candidates with MES experience outside of Tulip? A6: While experience with other MES systems such as Preactor is potentially acceptable if they have some Tulip familiarity but not ideal, it doesn’t guarantee Tulip proficiency. The team previously had to train candidates without Tulip exposure, which delayed projects. Therefore, candidates must have at least some working knowledge of Tulip and be ready to contribute immediately. Q7: Is this role 100% onsite or does it allow hybrid flexibility? A7: This position is 100% onsite in Milpitas, California, with no hybrid flexibility. Q8: Do candidates need to come from a medical device or FDA-regulated background? A8: Not required. Candidates from manufacturing or regulated industries are acceptable. The role does not specifically require prior medical device experience. Q10: Is Agile experience required? A10: It is helpful. While the team collaborates cross-functionally, Agile methodology experience is beneficial. Q11: What types of devices or systems will the engineer work with? A11: The engineer will work on flow cytometers, optics, motors, actuators, transducers, PCBAs, fluidics, and tubing—complex electromechanical systems integrated into production and testing environments. Q12: Can candidates from an academic background (e.g., PhD) with hands-on Tulip experience be considered, even without corporate manufacturing experience? A12: Yes. If the candidate has hands-on Tulip application experience, academic or research-based experience is acceptable. They can be paired with a senior engineer for manufacturing guidance. Q13: What kind of technical development is expected—coding or application creation? A13: The focus is on creating and configuring Tulip applications that streamline workflows and digitalize manual processes. It is not heavy coding, but rather building interactive applications that capture data and guide operators through manufacturing steps. Q14: What MES platform is currently in use, and what transition is taking place? A14: The team is transitioning from a previous MES platform to Tulip MES, which is being used to convert manual paper device history records into digital systems. Q15: Who will this individual primarily collaborate with? A15: The engineer will work closely with manufacturing engineers and production teams to create applications that reflect the product routing, assembly, and testing processes from start to finish. Q16: What kind of manufacturing environment does this role support? A16: The environment is manufacturing and assembly focused, dealing with electromechanical products. The engineer will design Tulip applications that guide the process flow, capture data at each step, and replace traditional paper-based records.