[{"data":1,"prerenderedAt":134},["ShallowReactive",2],{"system-sharkscode-frontend-leadership":3},{"id":4,"title":5,"slug":4,"company":6,"role":7,"period":8,"description":9,"isNda":10,"tags":11,"metrics":17,"highlights":21,"body":25,"bodyMarkdown":128,"order":57,"seo":129},"sharkscode-frontend-leadership","Frontend Leadership & Delivery","Sharkscode","Frontend Team Lead","Aug 2024 - Present","Leading frontend delivery, team growth, and execution quality across active client work in a fast-moving environment.",true,[12,13,14,15,16],"leadership","frontend","delivery","mentoring","process",[18,19,20],"Team leadership across active frontend delivery","Mentoring developers and raising execution quality","Stronger coordination between technical direction and delivery",[22,23,24],"Built a healthier balance between hands-on engineering and team leadership","Helped developers grow through day-to-day review, guidance, and support","Improved delivery predictability by making priorities and ownership clearer",[26,37,46,54,64,72,80,88,96,104,112,120],{"_key":27,"_type":28,"style":29,"markDefs":30,"children":31},"k0","block","h2",[],[32],{"_key":33,"_type":34,"text":35,"marks":36},"k1","span","Context",[],{"_key":38,"_type":28,"style":39,"markDefs":40,"children":41},"k2","normal",[],[42],{"_key":43,"_type":34,"text":44,"marks":45},"k3","This role sits at the intersection of leadership and hands-on engineering. The work is not limited to writing code. It includes shaping how the frontend team delivers, how technical decisions get made, and how developers grow over time.",[],{"_key":47,"_type":28,"style":29,"markDefs":48,"children":49},"k4",[],[50],{"_key":51,"_type":34,"text":52,"marks":53},"k5","Focus",[],{"_key":55,"_type":28,"style":39,"listItem":56,"level":57,"markDefs":58,"children":59},"k6","bullet",1,[],[60],{"_key":61,"_type":34,"text":62,"marks":63},"k7","Clarifying priorities and delivery expectations",[],{"_key":65,"_type":28,"style":39,"listItem":56,"level":57,"markDefs":66,"children":67},"k8",[],[68],{"_key":69,"_type":34,"text":70,"marks":71},"k9","Supporting the team through reviews, direction, and mentoring",[],{"_key":73,"_type":28,"style":39,"listItem":56,"level":57,"markDefs":74,"children":75},"k10",[],[76],{"_key":77,"_type":34,"text":78,"marks":79},"k11","Keeping implementation quality high without slowing delivery down",[],{"_key":81,"_type":28,"style":39,"listItem":56,"level":57,"markDefs":82,"children":83},"k12",[],[84],{"_key":85,"_type":34,"text":86,"marks":87},"k13","Acting as the bridge between execution, architecture, and day-to-day team needs",[],{"_key":89,"_type":28,"style":29,"markDefs":90,"children":91},"k14",[],[92],{"_key":93,"_type":34,"text":94,"marks":95},"k15","What This Work Looks Like",[],{"_key":97,"_type":28,"style":39,"markDefs":98,"children":99},"k16",[],[100],{"_key":101,"_type":34,"text":102,"marks":103},"k17","In practice, this means helping the team move with less ambiguity. Some tasks are managerial, some are technical, and many sit in between: deciding where standards need to be enforced, where speed matters more, and where a developer needs guidance instead of just feedback.",[],{"_key":105,"_type":28,"style":39,"markDefs":106,"children":107},"k18",[],[108],{"_key":109,"_type":34,"text":110,"marks":111},"k19","The strongest part of this role is not a single system or metric. It is the ability to keep delivery moving while raising the quality bar for the people doing the work.",[],{"_key":113,"_type":28,"style":29,"markDefs":114,"children":115},"k20",[],[116],{"_key":117,"_type":34,"text":118,"marks":119},"k21","Constraints",[],{"_key":121,"_type":28,"style":39,"markDefs":122,"children":123},"k22",[],[124],{"_key":125,"_type":34,"text":126,"marks":127},"k23","Client and project details are abstracted. The public version of this case focuses on the leadership shape of the work rather than implementation specifics.",[],"\n## Context\n\nThis role sits at the intersection of leadership and hands-on engineering. The work is not limited to writing code. It includes shaping how the frontend team delivers, how technical decisions get made, and how developers grow over time.\n\n## Focus\n\n- Clarifying priorities and delivery expectations\n- Supporting the team through reviews, direction, and mentoring\n- Keeping implementation quality high without slowing delivery down\n- Acting as the bridge between execution, architecture, and day-to-day team needs\n\n## What This Work Looks Like\n\nIn practice, this means helping the team move with less ambiguity. Some tasks are managerial, some are technical, and many sit in between: deciding where standards need to be enforced, where speed matters more, and where a developer needs guidance instead of just feedback.\n\nThe strongest part of this role is not a single system or metric. It is the ability to keep delivery moving while raising the quality bar for the people doing the work.\n\n## Constraints\n\nClient and project details are abstracted. The public version of this case focuses on the leadership shape of the work rather than implementation specifics.\n",{"title":130,"description":131,"ogImage":132,"noIndex":133},"Frontend Leadership & Delivery — ilsrbn","Frontend team leadership, delivery ownership, and mentoring work at Sharkscode.",null,false,1775381663357]