📘 Resource Overview & Documentation Details

You are viewing the technical directory listing for MES Developer: Skills, Responsibilities and Plant Impact. This engineering resource is curated under our Manufacturing Execution System division to support automation specialists, control systems engineers, and manufacturing technicians looking for verified reference materials.

🔍 Contextual Abstract & Technical Scope

Share Summary:LinkedInEmail

A Manufacturing Execution System (MES) depends on more than software code: its applications must be designed, tested, integrated and maintained in line with business requirements. The MES developer role described by Corticeira Amorim brings these activities together, supporting applications and integrations within the company’s ERP–MES environment. For industrial automation and IT teams, the responsibilities illustrate how development work connects technical specifications with implementation and production readiness.

What an MES developer does

The role sits within an information systems team responsible for application support and the management and evolution of ERP and MES systems. Its central purpose is to design, code, configure, debug and test application functionality, while maintaining the related integrations in accordance with established standards.

This scope places the MES developer between functional requirements and working software. The developer first reviews and validates functional specifications, then prepares the technical specifications and design needed to build a solution. Once requirements have been translated into a technical approach, implementation includes coding programs to meet both functional and technical specifications.

That sequence matters to teams responsible for manufacturing applications. A requirement needs to be understood before it is translated into code, and the resulting change needs to be checked before it is introduced into the operational environment. The job description therefore covers a development lifecycle rather than coding alone.

From requirements to tested functionality

Technical design and development

Reviewing functional specifications gives the developer an opportunity to confirm the intended scope and produce a corresponding technical design. Coding then follows those specifications. The role calls for knowledge of programming technologies including .NET, HTML and XML, as well as databases and reporting services using SQL.

The listed skills point to a position that works across application logic, data and information presentation. The source also names TracksYs, OPC and JSON among the relevant tools or technologies. These are part of the stated profile for the position; the job description does not specify particular projects or define how each is used.

Testing and integration

Testing is a defined responsibility, including participation in integration tests. This means the developer’s work does not end when an individual program has been coded. The changed functionality and its connections with other components must also be checked as part of the implementation process.

For system integrators and application teams, that distinction is practical: a change can involve both the application itself and the way it exchanges information with other systems. The role’s emphasis on maintaining integrations, debugging and integration testing makes those activities part of ongoing MES development and support.

Supporting releases and go-live activity

The responsibilities extend beyond development and testing into implementation. The MES developer collaborates on corrections and new versions, supports the functional area during data migration, and participates in cutover tasks and stabilization after go-live. The role also includes preparing changes, improvements and new functionality for entry into production.

These activities connect software delivery with operational readiness. Data migration and cutover are identified as collaborative tasks, so the developer works alongside the functional area rather than acting in isolation. After go-live, stabilization provides a further stage of support as the new or updated functionality is put into use.

For plant managers and operations leaders, this broad scope is relevant when considering how technical teams support change. Development, integration testing, migration and production handover are linked steps. A role that spans them can contribute to continuity between the design of a change and its implementation, while working within the organization’s standards and processes.

Skills for the role

Corticeira Amorim’s stated profile combines technical experience with the ability to work across teams and demanding contexts. The requested qualifications and capabilities include:

  • A degree or master’s qualification in computer science or a similar field.
  • At least three years of experience in a similar position.
  • Knowledge of .NET, HTML and XML, along with SQL databases and reporting services.
  • Familiarity with the listed tools and technologies, including TracksYs, OPC and JSON.
  • English proficiency, both spoken and written.
  • Autonomy, initiative, an innovative mindset and resilience.
  • The ability to work in urgent, complex and critical situations.

The profile reflects the combination of application development, database knowledge and coordination needed for the described responsibilities. Communication and adaptability are also relevant because the work involves collaboration with functional colleagues during migration, cutover and post-go-live stabilization.

A role across business operations

The position supports the company’s businesses in Portugal and abroad, within a multidisciplinary information systems team and a varied business context. That setting makes the remit broader than a single coding task: application support and evolution are part of the same function, and changes need to be prepared for implementation across the company’s operations.

The opportunity described by Corticeira Amorim includes professional development through team integration and exposure to different business realities in national and international contexts. The recruitment notice asks applicants to send a CV with the reference OSI/01 to the company’s human resources email address. It states that only candidates selected for the first recruitment phase would be contacted.

Conclusion

The MES developer role highlights the full range of work behind manufacturing application changes: validating requirements, producing technical designs, coding, testing integrations and supporting implementation through production handover. For industrial organizations, the practical takeaway is that effective MES development depends on coordinated attention to applications, integrations, data migration and go-live support—not development in isolation. Bringing those responsibilities together helps connect technical changes with the operational processes they are intended to support.

Access Official Technical PDF