You get to build great, well-designed, well-tested solutions that solve real problems, have ownership of your work, deliver it end-to-end, and support it for the duration of your tenure. You also have a captive audience for watching your demos on delivery, at least in the part of the org that I worked in.
Most people believed in the mission, worked long hours, and stayed around in the company for a long time.
Top-down leadership structure sets the direction and priority of everything, moves slowly, and becomes an active blocker for R&D.
Leadership avoided listening to advice that didn't conform with their worldview, spent years addressing tech debt and refusing to innovate, and failed to pivot on AI agents fast enough.
Keysight doesn't have a big enough AI budget, doesn't invest enough into AI R&D or building custom solutions in-house; prior to the data center boom, it mostly grew by acquisition rather than further investing into and growing existing business units.
Affecting change or adopting new tools across the larger Keysight organization can take many, many months or years as evidenced by AI agent adoption.
There were relatively frequent changes in product direction and leadership staff over the years, which led to a lot of short-term, stop-gap solutions that someone needed to maintain and extend, leading to a lot more tech debt, product delivery slowing down a lot in the long run, dependencies getting severely outdated for a prolonged period, and the products becoming very hard to maintain.
The company pays around the average for a region. Hiring, bonuses, and promotions might get frozen for years during downturns for the parent organization while your part of the organization delivers double digit growth for many successive quarters.
If the reverse happens and the company as a whole is having record breaking profits while your business unit fails to hit growth targets once-twice, you might get laid off regardless of your level and contributions, and your job might get offshored to increase profitability.
We should listen to the engineers more.
- Questions about the main programming language that you will use - Data structures and algorithms problems, LeetCode style - SQL and NoSQL database questions, comparison, differences, advantages vs disadvantages
The interview process typically consists of multiple rounds, starting with an HR screening to discuss your background and expectations. Then, a technical interview assesses your knowledge of automation, manual testing, Java, Selenium, API testing, an
I had an interview by phone with a human resources member then I had a prescheduled interview in the office. Finally I was invited to participate in an interview with the manager who is located in the USA, this interview has been through a video conf
- Questions about the main programming language that you will use - Data structures and algorithms problems, LeetCode style - SQL and NoSQL database questions, comparison, differences, advantages vs disadvantages
The interview process typically consists of multiple rounds, starting with an HR screening to discuss your background and expectations. Then, a technical interview assesses your knowledge of automation, manual testing, Java, Selenium, API testing, an
I had an interview by phone with a human resources member then I had a prescheduled interview in the office. Finally I was invited to participate in an interview with the manager who is located in the USA, this interview has been through a video conf