Industrial Engineering is System Efficiency Engineering. It is Machine Effort and Human Effort IE. 4 Million Page View Blog. 200,000+ visitors. (36,000+ pv, 25,500+ visitors in 2025.)------------------
Blog Provides Industrial Engineering Knowledge: Articles, Books, Case Studies, Course Pages and Materials, Lecture Notes, Project Reviews, Research Papers Study Materials, and Video Lectures. 2025 - New Project - Effective Industrial Engineering and Productivity Management.
European Professors of Industrial Engineering and Management (EPIEM).
European Professors of Industrial Engineering and Management (EPIEM) is a growing European-wide network, connecting researchers and professors at European universities within the academic IEM field. The goal of EPIEM is to initiate and to foster collaboration between IEM academics across Europe to enhance the field of IEM.
MY IE - ISE STORY. How I Joined IE Program - What did I achieve?
Requested by IISE on the Occasion of FIRST ISE Day on 15 September 2025.
IISE requested members to post their ISE Joining and Career Story.
------------------
In the final year of my B.Tech Mechanical Engineering course, I came to know that Industrial Engineering course from NITIE is a very valuable PG degree in India and I sent my application.
I got selected in the first list of 50 candidates. Joined the program in 1977. An achievement to remember during that program is my recommending MRP system for an electric motor plant in 1979.
The recommendation was accepted and the company got a pilot program prepared in the latter year. It is my first success as Industrial Engineer to improve a system.
I started my industrial career in materials planning and then did two years in production planning. I used a manual MRP systems already in practice in the company.
I shifted to teaching in the year 1982 and taught production planning and control and operations research for five years.
I then started my doctoral studies in the area of investment analysis of equity shares. My dissertation was on rates of return in equity shares which is related to cost of capital to be used in share valuation as well as project appraisal.
Cost reduction projects proposed by industrial engineers are to be assessed based on the cost of capital applied cash flows.
I started my proper industrial engineering teaching in NITIE in the 1994. I taught cost accounting and engineering economics. But did number of training programs in cost reduction. Learned Japanese cost management practices.
A shift occurred in the year 2000, as I joined as stockbroking company. From there I became a full professor in corporate finance. In 2006, I joined back NITIE and continued in Finance till 2010.
From 2011 to 2021, my full focus was on the basic course on industrial engineering for PG program and advanced course for research students.
This full focus helped me to create a globally popular blog, Industrial Engineering Knowledge Center https://nraoiekc.blogspot.com and a popular EBook - INTRODUCTION TO MODERN INDUSTRIAL ENGINEERING.
Very Popular Free Download EBook. 13,500+ Downloads/Views so far from three locations.
In my role as Assistant Vice President IISE for Europe, I'm available to discuss with anyone about how to raise awareness and make strong connections in Industrial and Systems Engineering within Europe and how to cooperate and have synergies with our friends and colleagues from rest of the world!!
Contact me - This is my linkedin page: https://www.linkedin.com/in/fabio-sgarbossa-5a8bb03/
Requested by IISE on the Occasion of FIRST ISE Day on 15 September 2025.
------------------
In the final year of my B.Tech Mechanical Engineering course, I came to know that Industrial Engineering course from NITIE is a very valuable PG degree in India and I sent my application.
I got selected in the first list of 50 candidates. Joined the program in 1977. An achievement to remember during that program is my recommending MRP system for an electric motor plant in 1979.
The recommendation was accepted and the company got a pilot program prepared in the latter year. It is my first success as Industrial Engineer to improve a system.
I started my industrial career in materials planning and then did two years in production planning. I used a manual MRP systems already in practice in the company.
I shifted to teaching in the year 1982 and taught production planning and control and operations research for five years.
I then started my doctoral studies in the area of investment analysis of equity shares. My dissertation was on rates of return in equity shares which is related to cost of capital to be used in share valuation as well as project appraisal.
Cost reduction projects proposed by industrial engineers are to be assessed based on the cost of capital applied cash flows.
I started my proper industrial engineering teaching in NITIE in the 1994. I taught cost accounting and engineering economics. But did number of training programs in cost reduction. Learned Japanese cost management practices.
A shift occurred in the year 2000, as I joined as stockbroking company. From there I became a full professor in corporate finance. In 2006, I joined back NITIE and continued in Finance till 2010.
From 2011 to 2021, my full focus was on the basic course on industrial engineering for PG program and advanced course for research students.
This full focus helped me to create a globally popular blog, Industrial Engineering Knowledge Center https://nraoiekc.blogspot.com and a popular EBook - INTRODUCTION TO MODERN INDUSTRIAL ENGINEERING.
Very Popular Free Download EBook. 13,500+ Downloads/Views so far from three locations.
This year the 58th Engineers’ Day will be celebrated all over the country on the theme “Deep Tech & Engineering Excellence: Driving India’s Techade".
Deep Tech is technology developed on the basis of scientific and engineering research in new areas providing new engineering devices, and machines to benefit the society in new areas. Technology includes product designs and processes to produce them.
I requested Dr,, P Sivasankaran to write a blog post with message to Industrial Engineers with Mechanical and Production Engineering Branch Foundation on this theme. The blog post published by the professor is available in the link.
I thank Dr. Sivasankaran. I request other industrial engineers with mech/production background to write their messages.
My post on the topic.
The theme, “Deep Tech & Engineering Excellence: Driving India’s Techade,” underscores the crucial role of engineers in steering discoveries and inventions all deep technologies in all branches of engineering (Digital transformation, AI, Sustainable automobiles, Quantum Computing, Semiconductors, Robotics, Advanced Materials, new-non renewable energy) toward national growth and global competitiveness.
As India enters its Techade, a decade in which importance is being given to deep tech, deep tech innovations are reshaping industries and redefining progress. Unlike conventional engineering solutions, these technologies demand long-term R&D, scientific rigor, and advanced engineering expertise. Recognizing this, the Government of India introduced the National Deep Tech Start-up Policy (NDTSP) in 2024 to support startups and researchers working on transformative technologies. The policy being implemented by the Government has to be used by academic institutions, research institutions, development organization and enterpreneurs to create a robust ecosystem where research translates into industrial applications. Engineers play a defining role in this shift.
By fostering research, bridging academia with industry, and nurturing talent, Institution of Engineers India (IEI) has positioned itself as a key enabler of India’s deep tech journey. As we mark Engineers’ Day 2025, it is evident that deep tech is no longer an emerging field—it is already avaibale in the present and has a great potentail for the future. The opportunity ahead is immense. Challenges accompany the opportunity.
With vision, expertise, and unwavering commitment, engineers must innovate, lead, and build technologies that will drive India’s transformation into a global powerhouse. And as always, IEI stands ready to support this mission, ensuring that India’s engineering community continues to push the boundaries of possibility.
Industrial engineers focus on cost reduction through productivity improvement. Cost reduction leads to rapid growth of deep tech products in global markets by facilitating price reductions.
Effective Industrial Engineering
Effective industrial engineering has to satisfy management about the contribution it made to the organization.
The prime contribution of IE has to be cost reduction through productivity improvement.
Productivity improvement is achieved through time reduction of capital assets and human resources and usage reduction of consumable items.
Reduction of machine time and man time have to be made through time studies. Time study was developed by F.W. Taylor to do this task. The purpose of time study is to measure the time taken being taken currently by each element of the task and study each element to find opportunities for time reduction. The time study includes time measurement (or work measurement) and analysis for drivers of time at element level. Later material studies to reduce consumption of consumable materials were developed. Inventory of material on the shop floor was the focus of reduction in Toyota and Toyota made great strides in productivity.
If the Time study is taken as the highest level task, it will have many lower level studies.
Machine Capabilities
Manpower capabilities
Method study
Motion study
Machine Appropriateness Study etc.
Industrial Engineers with Mechanical and Production Engineering Branch Foundation have to now focus on new deep technologies like smart CNC machines in various industries, Additive manufacturing machines, Machine Vision Inspection Systems, Automated Guided Vehicles, Robots and Cobots, Automated Storage and Retrieval Systems and Computerised scheduling systems to improve the processes using process chart approach.
Value stream as a focus of design and improvement was used by Japanese companies especially Toyota Motors and Womack and Jones provide the theory for the development of lean value streams. Industrial engineers have to develop value stream maps like process charts and related information sheets for value stream studies also. A value stream study map is available under the name VSM developed by Rather and Shook based on the chart used in Toyota.
Industrial engineers have to learn every technology that is being developed in mechanical and production engineering fields when they are associated with these branches and when they are in charge of productivity management of processes using these technologies.
Read for more details.
IE 4.0 - Industrial engineering of connected equipment instructed in real time by computers or cloud software systems.
Connected Equipment - Smart CNC machines in various industries, Additive manufacturing machines, Automated Guided Vehicles, Robots and Cobots, Automated Storage and Retrieval Systems and Computerised scheduling systems
Industrial Engineering 4.0 - IE in the Era of Industry 4.0 - Blog Book.
Redesigning products or processes by including software solutions, or developing software solutions to improve productivity in any activity or process.
Lesson 113 of Industrial Engineering ONLINE Course
Illustration: Google's Engineering Productivity Department - Evolution of the Department through Automation of Testing. Emergence of Software Engineering Productivity Engineer & Specialist.
Industrial engineering is applicable to all engineering tasks in the organization.
Engineering product design - Production - Engineering stores - Operation of engineering equipment and goods - Maintenance - Retirement - Replacement - Recycling
Industrial engineering is concerned with redesign of engineering systems with a view to improve their productivity. Industrial engineers analyze productivity of each resource used in engineering systems and redesign as necessary to improve productivity.
It has to be ensured that the increase in productivity due to the use of low-cost materials, processes and increasing speed of machines and men, should not lead to any decrease in quality of the output.
Similarly, operators should not feel any discomfort, not have any health problems or safety issues in the redesigned more productive processes.
Developments in Productivity science provide more and more directions for productivity engineering over the period.
Productivity engineering is engineering or engineering changes to machines, facilities, products and processes to increase productivity.
Interesting Statement.
"Creating a better workstations, work-aids, making things better and easier in order by upgrading it in such way which will be cheaper and more effective. To enhance the working efficiency through method industrial engineering, to make workplace a better place in order to make works quicker by introducing workplace Engineering."
Mamatha Kg
Senior Industrial Engineer executive
Print Point, Yuno Group · Full-timePrint Point & Yuno Group ·
Productivity Engineering: Redesigning engineering and engineering related products and processes using engineering and engineering related knowledge relevant to improving the productivity.
Productivity science provides input to carry out productivity engineering. It means productivity science provides the opportunity to invent and patent new product features and process components that will improve productivity. Inventions are not always preceded by science. Many times inventors came out with engineering devices even when there is no science supporting it. Air conditioning is one example where invention came first and then science was developed that helped in designing air conditioners to fit various needs.
24 July 2021
Productivity Engineering is designing and redesigning engineering elements or complete engineering systems to improve the productivity of the system and reduce its cost or the unit cost of its output.
Productivity Science is the collection of laws that indicate, facilitate and promote Productivity Engineering. Productivity Management is managerial activities that promote Productivity Science and Productivity Engineering
Making improvements to machines and other facilities in use is productivity engineering. Apart from it , productivity engineering has two main areas product industrial engineering and process industrial engineering. Process industrial engineering has two important components process machine effort industrial engineering and process human effort engineering. In addition there are facility level industrial engineering and enterprise level industrial engineering. Equipment decisions for the whole facility and layout of all the facilities are facility level decisions to which IE may be applied. Enterprise level policy and strategy decisions can be there and they may form part of productivity management. Information systems can be enterprise level and IE may be applied in those decisions. It is because overall enterprise productivity may be affected by the information system and IEs have to evaluate it.
Principles of Productivity Engineering - Mundel - Nadler
Methods Redesign for Efficiency/Productivity - Material, Product Design, Material Transformation Steps, Machine Effort, Human Effort - Marvin Mundel, Gerald Nadler
Nadler credits Mundel for the following steps to be followed in methods redesign.
Product Industrial Engineering
1. Change the material being used or contemplated to help meet the goal for the operation being studied. 2. Change the present or contemplated design of product to help meet the goal for the operation being studied.
Process Industrial Engineering
3. Change the present or contemplated sequence of modification work on the material or product to help meet the goal of for operation being studied. 4. Change the equipment used or contemplated for the operation to help meet the goal for the operation being studied.
Human Effort Industrial Engineering
5. Change the method or hand pattern used or contemplated for the operation to help the goal for operation being studied.
(Source: Gerald Nadler, Motion and Time Study, McGraw-Hill Book Company, New York, 1955, p.193. Nadler in turn gives credit to Marvin E. Mundel, Motion and Time Study Principles and Practice, Prentice-Hall, New York, 1950, pp. 23-26.)
How to improve your developer experience and key software development processes.
Developer Productivity Engineering is a discipline of using data and acceleration techniques to improve essential software development processes for greater automation, fast feedback cycles, and reliable feedback.
FSM's Equipment Productivity Group is hiring a technical Engineering Manager to focus on lithography technologies. With Intel's ambitious IDM2.0 manufacturing goals, the focus on equipment performance and productivity has never been more critical to the future success of the company. The Lithography Equipment Productivity Engineering Manager will focus on the following objectives to drive area performance to new heights helping achieve best in world module productivity in our current FSM and future foundry factories:
Partner with TD, supply chain, and suppliers to establish best output targets for future nodes
Partner with TD modules to hit MOR on 'day 1' of transfer
Drive strategy to opportunistically insert leading-edge tooling on older technologies
Drive the sharing of process and equipment productivity BKMs across Intel's technology nodes
Work with suppliers to implement 'Rest of World' equipment solutions that will help Intel
Drive cross MSO strategy for Intel foundry tool selection and maximize node fungibility
Work with supply chain to increase and enforce productivity focus inside purchase specs
Develop enabling equipment support systems (APC, machine learning, predictive analytics)
Develop business process to push past MOR commitments to avoid capital spending
In this module, productivity engineering activity is presented through projects done in various companies to increase productivity.
Operation Information Sheet
In the operations sheet we collected the following information. We need to use them in productivity engineering. Areas or items to be redesigned are identified in productivity analysis of operations.
Information to be collected about the following items/elements (Case of Machining Operations).
1. Purpose of operation.
There is a change in shape of the part or there is a change in its properties of an operation. This needs to be identified in analysis of the complete operation.
2. Whether process analysis related to the operation was completed: Yes/No.
Normally an systematic analysis it will be done. The team doing operation analysis needs to know the logic followed in process analysis.
Productivity Measurements of the Operation
Time taken for machining cuts (Machine Work Measurement - Estimation)
Time taken by the operator (Operator Work Measurement)
Total cycle time
Output of the component per machine hour
Cost of operation per hour (Cost Measurement)
Cost per piece (Cost Measurement)
Consumable materials used in the operation and consumption per piece.
Energy consumed per hour by process and cost per piece.
The above information is required and minimizing times and materials consumption is the objective of productivity improvement exercise or study.
Is there an alternative machine within the shop that is a better choice. Is there an alternative in vendor's shops that can be a better alternative. Is there a new machine that is a better alternative?
Can the machine be replaced by a like by like machine for more benefit? Industrial engineers must have patience for identifying alternative machines and data collection and analysis.
They have to seek alternatives from all persons concerned with the process. They have to maintain the operation related information on alternatives in a database which can be referrer to by other associates.
Motion sutdy. Within the motion study tools used by the operators and various machine knobs and levers require analysis. Lever used in jigs and fixtures also need analysis.
15. Common possibilities for job improvement.
a. Coupling with other machines - Multiple machines for man. (Human Effort Industrial Engineering)
There are many engineering aspects which need analysis by industrial engineers in process/operation study/analysis.
Process Productivity Engineering - Course Lessons
Process productivity engineering is done through process charts at the highest level. They capture processing, inspection, material handling, delays and long-term control storage. In each of these operations there is machine effort, human effort, materials input, energy input and information input. For each of the operation more information is needed than that is entered in a process chart. For each operation, operation analysis sheets and additional documents are required to do complete analysis of all inputs that go into the operation.
At this year's intersolar North America show, M+W's Ankush Halbe, Technology Director Renewable Energy, presented the latest PV capacity drivers as well as successfully proven fab design concepts opportunities complying with the environmental and security requirements.
Productivity with an automated packaging solution.
Client is the world's largest tool manufacturing company, renowned for its engineered fastening systems.
We installed a highly automated small part packaging machine from Bonotto. This machine facilitated the automated packaging of small parts, streamlining the packing process.
Productivity Engineering is a field that focuses on improving efficiency and effectiveness in various industries through the utilization of technology, processes, and strategies. By analyzing current workflows and identifying areas for improvement, productivity engineers aim to streamline operations and maximize output.
Productivity Analysis - Comparison of Current Process to Ideal or the Best Process has to be done from System level up to Element level.
A process consists of operations. Five types of operations are specified by ASME/IISE to be recorded on process charts - Material processing - Inspection - Transport - Storage - Delays. A process to produce a part may have many operations. In the process analysis, for each operation, the possibility of eliminating it is discussed. The possibilities for combining two adjoining operations or dividing an operation into more steps are examined. The sequence of operations can be altered to increase productivity. After these analyses are complete, the operation is given for detailed study to improve machine work, operator work, work station layout etc. Thus process analysis is to be followed by operation analysis. The operation analysis requires detailed information on all inputs going into the operation and the steps or elements used to complete the operation.
The operation analysis of the processing operation starts with collecting information on the processing information. In the developing this complete procedure, initially machine tool operation is being used for illustrating the details to be collected and analyzed. Subsequently, analysis of other machine operations will be added as annexures.
What is "operation analysis"?
The task in "operation analysis" is to improve productivity consists principally of finding out all known facts about equipment and operators that affect a given operation, and compare it with the possible alternatives to identify improvement opportunities and redesign the operation to give better efficiency, productivity and lower cost. Both machine effort and human effort that go into an operation are studied at element level and improved.
Importance of Systematic Procedure in Operation Analysis
In making operation analysis, a systematic procedure is to be followed so that points of cardinal importance are analyzed without giving a miss. The information to be collected is likely to differ from machine to machine or equipment used in operations.
Operation Information Sheet
Information to be collected about the following items/elements (Case of Machining Operations).
1. Purpose of operation.
2. Whether process analysis related to the operation was completed: Yes/No
Productivity Measurements of the Operation
Time taken for machining cuts (Machine Work Measurement - Estimation)
Time taken by the operator (Operator Work Measurement)
In order to structure the work of making written analyses, " analysis sheet" has to be used. In asking questions based on operation information sheet, securing the information needed to complete the analysis of each item to fill out the form completely, one will understand the operation more thoroughly that will help to make a complete analysis and come out with alternatives to increase productivity.
At the top of the sheet, the operation details for identifying completely the analysis, the part, and the operation have to be recorded.
Item 1. The first point considered is the purpose of the operation. If analysis shows that the operation serves a definite purpose, various other means of accomplishing the same result are considered to see if a better way can be found.
Item 2. If operation or flow process charts have not been constructed, all the operations performed on the part are next listed.
Item. 3 to 5 Design
Item. Material handling.
Although it is commonly thought that conveyers can be used to advantage only in mass-production work, there are types on the market that are equally successful in jobbing work.
Item 6. Equipment, Tools, Workholding, Setup, Work Place Layout
The equipment and tools used on any operation is the most important item of operation analysis and it is worthy of careful study.
Jigs, fixtures, and other work holding devices too often are designed without thought of the motions that will be required to operate them. Unless a job is very active, it may not pay to redesign an inefficient device, but the factors that cause it to be inefficient may be brought to the attention of the tool designer so that future designs will be improved.
"Setup" is loosely used throughout industry to signify the workplace layout, the adjusted machine tool, or the elemental operations performed to get ready to do the job and to tear down after the job has been done.
More exactly, the arrangement of the material, tools, and supplies that is made preparatory to doing the job may be referred to as the " work-place layout."
Any tools, jigs, and fixtures located in a definite position for the purpose of doing a job may be referred to as "being set up' or as "the setup."
The operations that precede and follow the performing of the repetitive elements of the job during which the workplace layout or setup is first made and subsequently cleared away may be called " make-ready" and "put-away" operations.
The workplace layout and the setup, or both, are important because they largely determine the method and motions that must be followed to do the job. If the workplace layout is improperly made, longer motions than should be necessary will be required to get materials and supplies. It is not uncommon to find a layout arranged so that it is necessary for the operator to take a step or two every time he needs material, when a slight and entirely practical rearrangement of the workplace layout would make it possible to reach all material, tools, and supplies from one position. Such obviously energy-wasting layouts are encountered frequently where methods studies have not been made and when encountered serve to emphasize the importance of and the necessity for systematic operation Analysis.
The manner in which the make-ready and put-away operations are performed is worthy of study, particularly if manufacturing quantities are small, necessitating frequent changes in layouts and setups. On many jobs involving only a few pieces, the time required for the make-ready and put-away operations is greater than the time required to do the actual work. The importance of studying carefully these non-repetitive operations is therefore apparent. When it can be arranged, it is often advisable to have certain men perform the make-ready and put-away operations and others do the work. The setup men become skilled at making workplace layouts and setups, just as the other men become skilled at the more repetitive work. In addition, on machine work it is usually possible to supply them with a standard tool kit for use in making setups, thus eliminating many trips to the locker or to the toolroom.
Item. Common possibilities for job improvement.
There are a number of changes that can be made to workplace layouts, setups, and methods which are brought to light by job analysis. Of these, there are 10 that are encountered frequently, and one or more may be made on nearly every job studied.
1. Install gravity delivery chutes.
2. Use drop delivery.
3. Compare methods if more than one operator is working on
same job.
4. Provide correct chair for operator.
5. Improve jigs or fixtures by providing ejectors, quick-acting
clamps, etc.
6. Use foot-operated mechanisms.
7. Arrange for two-handed operation.
8. Arrange tools or parts within normal working area.
9. Change layout to eliminate backtracking and to permit coupling of machines.
10. Utilize all improvements developed for other jobs.
These improvements are comparatively easy to make. If the analyst is observant and on the alert for inefficient operating practices, the possibility of applying them can be recognized without resorting to detailed motion or time study.
Item. Working conditions have an important influence on production.
Item Operator Method. The analysis of the method followed in performing the operation is the part of the study dealing with human effort in the production system or engineering activity system.
The method that is established after analysis and motion study is recorded under 9 in order that the analysis sheet may provide a complete record of the job, although, strictly speaking, this information does not belong under the head of analysis.
Usually the analysis of the method requires the drawing of one or more types of process chart, and often a number of computations are involved. This information should be gathered together in the form of a supplementary report and identified by a note on the analysis sheet.
The foregoing gives a general description of the items on the analysis sheet.
Engineering Productivity : Delivering frictionless engineering and excellent products
What is Engineering Productivity?
We are a data-driven engineering discipline focused on optimizing the engineering process so that Google can deliver amazing experiences to our users, faster.
Philosophy
Qualities that humanize Engineering Productivity
Evolution of the Department through Automation of Testing. Emergence of Software Engineering Productivity Engineer & Specialist.
Initial attempts to automate testing focused on the frontends, which worked, because Google was small and products had fewer integrations. However, as Google grew, longer and longer manual test cycles delayed feature launches. Since bugs were identified late in testing, it took longer time to fix them. Making possible testing upstream in the development cycle via automation was thought to help address the issues and reduce development time.
Testing was transitioned to automated processes and operations. Two separate roles began to emerge to develop automated testing software at Google:
Test Engineers (TEs) having deep product knowledge, and ability to develop testing/quality control check specifications. TEs focused on what should be tested and the manual process of testing.
Software Engineers in Test Automation Development (SETs) -- Software engineers with deep development expertise and experience in automating manual testing processes. SETs built the frameworks and packages required to implement automation of testing procedures.
The impact of this section and its expertise was significant:
Automated tests became more efficient by improving runtimes.
Automated testing led to higher quality products.
TEs developed extreme depth of knowledge for the testing of products. They became go-to engineers for product teams that needed expertise in test automation and integration. Their role evolved into a broad spectrum of responsibilities: writing scripts to facilitate automated testing, and constantly designing better and more creative ways to identify weak spots and break software.
SETs built a wide array of test automation tools and developed best practices that were applicable across many products. Release velocity accelerated for products. All was good, and there was much rejoicing!
SETs initially focused on building tools for reducing the testing cycle time, since that was the most manually intensive and time consuming phase of getting product code into production. Some of these tools were made available to the software development community: webdriver improvements, protractor, espresso, EarlGrey, martian proxy, karma, and GoogleTest. SETs were interested in sharing and collaborating with others in the industry and established conferences. The industry has also embraced the Test Engineering discipline, as other companies hired software engineers into similar roles, published articles, and drove AutomatedTest-Driven Development into mainstream practices.
Through these efforts, the testing cycle time decreased dramatically. Other phases in the development cycle now became the bottleneck. SETs started building tools to accelerate all other aspects of product development, including:
Extending IDEs to make writing and reviewing code easier, shortening the “write code” cycle
Automating release verification, shortening the “release code” cycle.
Automating real time production system log verification and anomaly detection, helping automate production monitoring.
Automating measurement of developer productivity, helping understand what’s working and what isn’t.
In summary, the work done by the SETs naturally progressed from supporting only product testing efforts to include supporting product development efforts as well. Their role now developed into a much broader Software Engineering Productivity Engineer & Specialist.
With a system-level view and a user-centric view, we work hard to identify gaps and inefficiencies in our engineering process so that we can build solutions to improve engineering excellence and velocity.
Instrumentation
We believe that you can’t improve what you can’t measure. Google is a data-driven company and we are a data-driven discipline. We obsess over metrics and work hard to move them in the right direction.
Tools and Infrastructure
Much like a bustling metropolis needs great infrastructure to enable happy and productive residents, Google engineers working on complex systems need the right tools and infrastructure to be productive.
Focus on the user
We embed in product engineering teams where we champion polished products for Google’s users and fast, scalable engineering for our users, Google’s engineers.
Interested in joining Engineering Productivity?
We are looking for world class engineers that bring a quantitative mindset, execution velocity, leadership skills, and a passion to change the way engineering is done at Google and beyond.
Google strives to cultivate an inclusive workplace. We believe diversity of perspectives and ideas leads to better discussions, decisions, and outcomes for everyone.
Reasoning about the correctness of Engineering and Engineering Change
Reasoning about the correctness of your change is now much more difficult.
Some questions come up, including: How do you make sure your change works? How do you make sure your change didn’t break an obscure use case for a user in a different geography? How do you prepare your change such that the next 100 engineers that modify the system don’t break the feature you just added?
These are complex problems that require tooling and infrastructure to help engineers reason about the correctness of their change. EngProd’s purpose is to make engineering easier and better, so we spend a lot of time on the hardest part of the process: building tools and infrastructure to make testing and debugging simpler.
Careers
Software Engineer, Tools and Infrastructure (SETI)
SETI at Google is a Software Engineering role that focuses on building software, infrastructure, harnesses, tooling to help improve engineering velocity and product excellence.
You might love this role if:
You love developing tools that make the engineering process better - be it command line tools, web services, debugging tools, test data factories, etc.
You are passionate about high-quality software and unhappy about shortcuts and hacks in the code.
You have worked to automate and remove repetitive and manual tasks because inefficiency drives you crazy.
You believe that unless you can quantify or measure something, you probably can’t improve it.
Test Engineer (TE)
TE at Google is a technical role that focuses on advancing product excellence and engineering productivity.
You might love this role if:
You have an unwavering passion for, and focus on, polished products, engineering excellence, and productivity.
You love thinking through complex product and system interactions to find gaps, failure modes, and edge cases.
You have worked to automate and remove repetitive and manual tasks because inefficiency drives you crazy.
You love to design, implement, and improve tools, frameworks, metrics, and processes.
You love to work, collaborate, and lead cross-functionally.
Google Research - A Human Centered Approach to Developer Productivity
Google Research - What Predicts Software Developers’ Productivity?
Emerson Murphy-Hill, Ciera Jaspan, Caitlin Sadowski, David C. Shepherd, Michael Phillips, Collin Winter, Andrea Knight, Dolan Edward K. Smith, Matthew A. Jorde
Transactions on Software Engineering (2019) https://research.google/pubs/pub47853/
We're rebuilding Google’s EngProd on the modern engineering stack to solve collaboration challenges at every stage of the development process, from code reviews to builds, testing, merging, and deployment.
2020 August Advertisement for Software Engineer, Engineering Productivity
Note: By applying to this position your application is automatically submitted to the following locations: Mountain View, CA, USA; Palo Alto, CA, USA; San Bruno, CA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA
Minimum qualifications:
Bachelor's degree in Computer Science or related technical field or equivalent practical experience.
Software development experience in one or more general purpose programming languages.
Experience in one or more of the following: test automation, refactoring code, test-driven development, build infrastructure, optimizing software, debugging, building tools and testing frameworks.
Preferred qualifications:
Master's or PhD degree in Computer Science or related technical field.
Experience with one or more general purpose programming languages including but not limited to: Java, C/C++, C#, Objective-C, Python, JavaScript, or Go.
Scripting skills in Python, Perl, Shell or another common language.
About the job
Google's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. Our products need to handle information at massive scale, and extend well beyond web search. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google’s needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward.
Google aspires to be an organization that reflects the globally diverse audience that our products and technology serve. We believe that in addition to hiring the best talent, a diversity of perspectives, ideas and cultures leads to the creation of better products and services.
Google is and always will be an engineering company. We hire people with a broad set of technical skills who are ready to take on some of technology's greatest challenges and make an impact on millions, if not billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive scalability and storage solutions, large-scale applications and entirely new platforms for developers around the world. From Google Ads to Chrome, Android to YouTube, Social to Local, Google engineers are changing the world one technological achievement after another.
Responsibilities
Lead/contribute to engineering efforts from design to implementation, solving complex technical challenges around developer and engineering productivity and velocity.
Design and build advanced automated build, test, and release infrastructure.
Drive adoption of best practices in code health, testing, and maintainability.
Analyze and decompose complex software systems and collaborate with cross-functional teams to influence design for testability. https://careers.google.com/jobs/results/72445869200155334-software-engineer-engineering-productivity/
Engineering Productivity at Google; Increasing Developer Productivity and Code Health - Google Event
July 19, 2018
Sunnyvale, CA
About
At Google, we have over 2,000 engineers who contribute to Engineering Productivity. They work hard to help make developer tools and processes more efficient by building test automation tools, accelerating release processes and discovering new ways to optimize workflows.
There are multiple teams in which Engineering Productivity plays a key role. Please join us for an evening to hear from Googlers whose work directly impacts thousands of Google engineers and billions of users.
The evening will kickoff with a welcome by Jennifer Bevan, Software Engineering Lead, whose team works toward helping Google products have easy, stable, and testable integrations for all user scenarios. Following this, we’ll hear from other Engineering Productivity teams, including Google Photos, Hardware, Cloud, and Google Ads. We’ll learn how these various teams work toward providing tools for efficiency across Google. Lastly, we’ll dive into a Q&A panel for your chance to ask questions.
After the Q&A panel, we invite you to stick around, chat with speakers and their teammates, make connections and enjoy the reception! Also be sure to check out our Nest corner to get hands on experience with Nest products and mingle with Engineering Productivity teams from Nest.
The event will be hosted on Thursday, July 19th from 5:30PM - 8:30PM at Google in Sunnyvale. Dress is business casual. Check-in at 111 W Java Dr., Sunnyvale at 5:30PM for registration.
Featured Speakers
Jennifer Bevan
Lead, Software Engineer, Tools and Infrastructure
User Test & Productivity for Google Products
Jennifer Bevan started working at Google in 2006 working on core Google-wide test infrastructure. She then worked on Privacy, Policy, and Accessibility testing with Photos, G+, and Counter-Abuse Technologies, and now leads Google Product Infrastructure's User EngProd team. Prior to Google, Jennifer got her B.S. in Electrical Engineering / Computer Science from UC Berkeley, worked at the Jet Propulsion Laboratory building control and data verification systems, and got her Ph.D. from UC Santa Cruz in Software Evolution and Maintenance.
Jonathan Velasquez
Lead, Software Engineer, Tools and Infrastructure
Test Infrastructure for Google Home, Google WiFi, and Cast
I was born in Peru and went to school in SUNY Binghamton where I graduated in Computer Engineering in 2007. I have been working as a SETI at Google since 2011 and have been part of several major launches including Google+, Project Fi and the Google Home Max. Today I manage the Home Platform infrastructure team supporting Chromecast, Google Home and Google WiFi. In my spare time I enjoy playing classical piano and practicing tennis.
Amod Kulkarni
Senior Engineering Manager
Engineering Productivity for Google Ads
Amod earned a Masters degree in CS from the Indian Institute of Science, India. He has been working in Google as SETI over twelve years. For last 3 years he is Tech Lead / Manager for Shopping Engineering Productivity team focusing on building tools and infrastructure to enable Shopping engineers build and launch high quality shopping features quickly.
His favorite part of being SETI is an entrepreneurial nature of this role. You get lot of freedom to come up with new ideas, prototype and solve challenging problems.
Abhi has been working at Google for over 13 years now. He started at Google in 2005 and has worked mainly on developer productivity tools across ads, core infrastructure and most recently on Google Cloud Platform. His area of work spans storage systems used within Google (GFS for those of you who are familiar with it) and its replacement, software that runs in Google data centers and building large scale productivity improvement tooling. He is currently managing a team of 20 Software Engineers and the products built by his teams over the year are used by close to 800 engineers within Google Cloud Platform.
Victor Tse
Engineering Productivity Manager
Engineering Productivity for YouTube
Victor Tse is an Engineering Manager at Youtube. He is part of the Youtube Engineering Productivity team that focuses on transforming the way products are architected, developed and tested. Previously, he built enterprise software applications and held engineering leadership positions at Siebel Systems, Oracle and Marin Software.
Stephanie Tsao
Software Engineer
Photos Engineering Productivity and Test for Photos
Stephanie worked at Microsoft for 5 years as a Hotmail backend software engineer. She switched to Google and the engprod world early 2014 and is now leading the Photos engprod team to help better scale Photos to be the next 1B user app. https://engineeringproductivity.splashthat.com/