I’m working as a backend engineer in Japan, and i have N2 and i did explain simple flow but i did not the Japanese words because db has many fields and Japanese name are all construction related. and I recently had to explain an API workflow I implemented to my manager.
The system involves a background job that:
– calls an external API to fetch data
– stores it in the database (including audit/history)
– pushes data into a queue for asynchronous processing
– later processes the queue, maps/transforms data, calls another API for validation, and sends it to another system
I tried to explain this, but my manager said my explanation was unclear. They also mentioned I should understand the meaning of different IDs and database fields better. And all those sequence digram are in Japanese and i don't really look those because construction words are difficult.
My questions:
-
In Japanese companies, how do engineers usually explain complex backend flows clearly? When many words are in Japanese.
-
How detailed should we be when explaining database fields and IDs?
-
Any tips for handling technical discussions in Japanese (especially difficult terms)?
Would appreciate advice from people working in Japan or similar environments.
by abinash21