How to apply for Principal Software Engineer

About Eurofins

Eurofins provides analytical testing services that help clients meet safety, health, and sustainability standards worldwide. The company operates across many countries, so engineers here build systems that support regulatory and quality work at global scale. If you want your code to support testing that affects food, environment, and product safety, this is a relevant place to work.

About the role

This principal software engineer role centers on an Access Rights management system. You will translate business requirements into Rego policies and Open Policy Agent (OPA) configurations, and you will implement fine-grained access control across business applications. The work is directly tied to how users are granted or denied access to sensitive testing and business data.

A typical day

You will spend time writing and reviewing Rego policies, testing them, and integrating them with business applications. You will also meet with product stakeholders to clarify access requirements and refine the access rights management system. Part of the day may involve debugging policy decisions and documenting your work for other engineers.

Who Eurofins is looking for

• Has hands-on experience writing Rego policies and deploying Open Policy Agent (OPA) in production systems.
• Can explain different access control models (RBAC, ABAC, etc.) and knows when to apply each.
• Has implemented fine-grained access control policies for business applications, not just theoretical knowledge.
• Writes clean, maintainable, well-documented code and policy files, and performs unit testing on policies.

Tips for this application

• In your resume, list specific projects where you used Rego and OPA. Include the scale (number of policies, services, or users) and the access control model you implemented.
• Mention any experience with access rights management systems or identity and access management (IAM) platforms, even if not directly using OPA.
• Highlight unit testing practices for policy code. Eurofins explicitly asks for unit testing, so show how you test Rego policies.
• Reference Eurofins' analytical testing business in your cover letter. Explain why access control matters for regulatory and quality data in testing services.
• If you have worked with product stakeholders to gather requirements, describe that collaboration. The role requires close work with product stakeholders.

What to cover in your cover letter

['Your direct experience with Rego and Open Policy Agent (OPA), including any production deployments.', 'A concrete example of implementing fine-grained access control policies for a business application.', 'How you ensure code and policy quality through unit testing and documentation.', 'Your ability to work with product stakeholders to turn business requirements into access control designs.']

Research before applying

• Read Eurofins' public materials on analytical testing services to understand what types of data and systems need access control.
• Look up Open Policy Agent (OPA) and Rego documentation if you are not already familiar with the latest features and best practices.
• Check if Eurofins has published any engineering blog posts or talks about access management or policy as code.
• Understand common access control models (RBAC, ABAC, ReBAC) and how they apply to regulated industries like testing and certification.

Likely interview topics

Based on the job description, expect questions about:

• Explain the difference between RBAC and ABAC, and give an example of when you would use each in an access rights management system.
• Write or describe a Rego policy that grants access based on user role and resource attributes. Be ready to discuss testing it.
• How do you handle policy versioning and deployment in Open Policy Agent?
• Describe a time you worked with product stakeholders to clarify access control requirements. What questions did you ask?
• How do you unit test Rego policies? What tools or frameworks have you used?

Common mistakes to avoid

• Do not claim Rego or OPA experience if you only have general policy engine knowledge. The role requires hands-on experience.
• Avoid vague descriptions of access control work. Specify the model, the scale, and your exact role in implementation.
• Do not ignore the unit testing requirement. Submitting a resume without any mention of testing policy code is a gap.