Software Engineer

Fiery LLC is the leading provider of Digital Front Ends (DFEs) and workflow solutions for the growing industrial and graphic arts print industries. Fiery is leading the transformation from analog to digital imaging with scalable, digital, award-winning products for the printing industry. Based in Silicon Valley, California with offices around the world and a customer-base that includes over 2 million DFEs sold globally, we offer innovative software and cloud-based technologies that deliver fast performance, stunning colour, and exceptional print quality across a broad range of production printing devices. Fiery DFEs are installed in a diverse range of industry segments, including commercial print, packaging, signs and display graphics, ceramics, building materials, textiles etc. With over 30 years of excellent support and service, we have presence in 19 countries with 800+ employees.Fiery Vision: Enable the printer to produce what the designer imaginedWe are currently growing and looking forward to hiring an Software Engineer for Fiery team at Silicon Valley CA .Visit here to know more .Role And ResponsibilitiesAs an Software Engineer : You will perform, develop and execute exploratory and automated tests to ensure product quality for assigned projects. With a passion for technology and curiosity to explore, detect errors, in this role, you will contribute in making our products bugs-errors free. You will be part of the development team, working in a multidisciplinary environment.Job RequirementsEducational Qualification: Bachelor’s degree in Computer Science, Engineering, Math or related.Experience:2-5 Year of experiencePrimary Responsibilities One goal might be to set up systems in IDC for testing. Is this feasible? To be able to resurrect M* process for PDF module, labeling, backporting in ClearCase. Test script failures on marvin in depth understanding, ie difference between isolated tests and automated tests on respective machine (most time consuming thing) In case something goes wrong with john-win10 machine, How & where can we build the TCC libraries ? How to run individual sanity checks on each of the newly created binaries especially MAC. Understand why universal bins encounter failure on some MAC machines and not on others. Individual issues : acsredux.dll is not getting build. What was left to be covered in previous training like powerpage, Monsoon etc Viewing the output from difference pages – is someone doing this? Do you need help making this reliable? How to add to the test cases: We might get buggy files which force changes – some of these should be added to existing regression tests. For new APIs developed in Cyclone, we will need help for that. What validation is there for Translib changes? Is there an understanding of how to build PowerPage? Does that need to be better understood? Behavioural Skills: Should have strong verbal and written communication, stakeholder management, accountability, strategic orientation, take initiative, learnability, strong decision-making capabilitiesDesirable But Not Mandatory Printing domain experience Ability to work in a matrix environment Comfortable with ambiguity What’s in it for you? Opportunity to work in a Multinational Product Organization Partner with and learn from seasoned professionals / leaders Exposure to latest tech stack Accelerated career growth Flexible, hybrid work environment with a healthy work life balance Culture of meritocracy, inclusion, empowerment and fun Competitive pay and benefits