I currently have 1 YoE at a role that mostly uses low-code tools, and I’m applying to more code-heavy roles. On my resume, I left off the low-code tools and focused on achievements and business impact.
When I talk with hiring managers, I know that I’ll be asked to talk in detail about the tools I used. I will tell the truth. But if anyone who’s done a similar transition has advice on talking about describing or answering questions on work experience while minimizing the “low-code disadvantage”, I’d really appreciate it.
submitted by /u/flyTendency
[link] [comments]
r/cscareerquestions I currently have 1 YoE at a role that mostly uses low-code tools, and I’m applying to more code-heavy roles. On my resume, I left off the low-code tools and focused on achievements and business impact. When I talk with hiring managers, I know that I’ll be asked to talk in detail about the tools I used. I will tell the truth. But if anyone who’s done a similar transition has advice on talking about describing or answering questions on work experience while minimizing the “low-code disadvantage”, I’d really appreciate it. submitted by /u/flyTendency [link] [comments]
I currently have 1 YoE at a role that mostly uses low-code tools, and I’m applying to more code-heavy roles. On my resume, I left off the low-code tools and focused on achievements and business impact.
When I talk with hiring managers, I know that I’ll be asked to talk in detail about the tools I used. I will tell the truth. But if anyone who’s done a similar transition has advice on talking about describing or answering questions on work experience while minimizing the “low-code disadvantage”, I’d really appreciate it.
submitted by /u/flyTendency
[link] [comments]