10 Aug
|
Teamified
|
Melbourne
10 Aug
Teamified
Melbourne
Aboutrole:
Thisroleisthesecond-in-commandwithintheengineeringteam.Thetechleadsplitstheirtimeacrosscoding,managing,planning,andstakeholderwork-meaningforlargepartsofanygivenday,thispersonisthemostseniorengineeractivelyworkinginthecodebase.Theymakeimplementationdecisionsindependentlyandkeeptheteamunblockedduringworkinghourswhenthetechleadisunavailable.
Keyresponsibilities:
1. Leadend-to-enddeliveryoffeaturesacrosstheLearningPortalandsupportingservices-scoping,building,andshippingrequiringjustminimaldirectiononimplementation
2. Proposetechnicalapproachesandwritedesigndocsfornon-trivialwork,bringingforwardrecommendationsbyaligningwiththeteamandteamlead
3. Givethorough,constructivecodereviewsonpeers'PRs
4. Participateinplanningwithrealisticestimatesandsurfacedrisks
5. Flagtechdebt,performancerisks,andarchitecturalconcernsearly.Notexpectedtodecidethefixforeverything,butexpectedtospotproblemsbeforetheyescalate
6. Ensuretestcoveragewhereitmatters(notjustforcoveragemetrics)
7. Keepdocumentationcurrentforallsystemstheyownsotheteamneverdependsontheiravailabilitytounderstandtheirwork
8. Considersthestudentexperienceaspartoftechnicaldecision-making-notaboveengineeringstandards,butalongsidethem
9. FollowandreinforceInnerSourceprinciples:cleardocs,async-firstcollaboration,modulardesign
10. Keeptheteamunblockedduringworkinghours.Whenthetechleadisinmeetingsorunavailable,they'rethepersonothersturnto
Corecompetencies:
- Designingcleanboundariesbetweenserver&client;,gooduseofbothframeworkcapabilities(Next)andconventionalwebdesignprinciples
- DatamodelingdecisionsSupabase/Postgresschemadesign,etc.)
- Consistentabstractions(hooks,APIpatterns,etc.)thattheteamcanfollow
- Knowingwhennottoabstract-avoidingprematureDRY
- Observability-logging,errortracking,understandingwhattomonitor
- Authflows(SupabaseAuth,RBAC,middleware-basedprotection)
- Inputvalidationatsystemboundaries
- WritingPRsthatreviewerscanactuallyfollow
- Breakinglargechangesintoreviewable,deployable+meaningfulincrements
- Knowingwhentospike/prototypevs.planthoroughly
- Shippingoverperfection-butknowingwheretodrawtheline
- Goodsenseofprioritisationwhenitcomestoplanningoutissues
- Makingbuild-vs-buydecisions(e.g.,usingSupabaseinsteadofrollingcustomauth)
Idealcandidateattributes:
- Knowswhentotradeoffscope,quality,andspeedappropriatelyforthesituation.Doesn'tover-engineerwhentheteamneedstomovefast,anddoesn'tcutcornerswhenreliabilitymatters.Makespragmaticcallswithoutneedingtoescalateeverydecision
- Takesfeaturesfromstarttofinishwithoutneedingtobechased.Ifsomething'satrisk,raisesitearly
- Structuredissues,thoughtfulreviews,cleardocumentation,andLinearworkflow.Communicatesclearlyenoughthatasyncworkdoesn'tcreatebottlenecks
- Consistentlydeliversoncommitments.Theteamcancountonyourworkbeingdone,reviewed,andshippedwithoutsurprises.Focusedonoutputsandoutcomes,notinputsandhours
- Figuresthingsoutwithincompleteinformation.Doesn'twaitforperfectspecsordetailedinstructionstomakeprogress
#J-18808-Ljbffr
📌 Senior Software Engineer (Melbourne)
🏢 Teamified
📍 Melbourne