JFrog has an authentic culture where values like “Care” and “Open Communication” are truly lived, and leadership genuinely prioritizes employees during “high seas.” The product domain is highly relatable and engaging for engineers, and I have full confidence in the company’s strategic direction.
There is a high level of autonomy where your voice is heard, allowing everyone to influence technology and design regardless of their role or level.
Executing cross-product and cross-domain initiatives can be challenging and often requires significant effort to align.
Additionally, it is sometimes a struggle to push through and finish long-running contributions to fundamental technical debt in the platform and core products.
Continue the joint technical management brainstorming meetings across different domains.
These sessions are vital not just for solving specific platform gaps, but for building the informal alignment necessary for a cohesive platform.
1. telephone interview with hr 2. technical interview with the hiring manager, what is ip, what is static variable, write a function that get the first non repeated character 3. another 1.5h technical interview with 2 guys … tell me about your exp
A call from a team leader that asked about my skills and gave one technical question. then was invited to technical interview with vp r&d and a different team leader. after that an hr.
The first interview is with the CTO. The second is a session with ML architects (they probably have SW background, but not ML), then an HR interview, and finally the job proposal discussion.
1. telephone interview with hr 2. technical interview with the hiring manager, what is ip, what is static variable, write a function that get the first non repeated character 3. another 1.5h technical interview with 2 guys … tell me about your exp
A call from a team leader that asked about my skills and gave one technical question. then was invited to technical interview with vp r&d and a different team leader. after that an hr.
The first interview is with the CTO. The second is a session with ML architects (they probably have SW background, but not ML), then an HR interview, and finally the job proposal discussion.