LearnWorlds

Software Engineer

• - Build and run the predictable “operating rhythm” of the Engineering department (cadences, rituals, follow-ups, accountability).
• - Own the operational side of key engineering-wide rituals (e.g., monthly engineering all-hands): agenda building, coordination, action tracking and ensuring follow-through.
• - Drive continuous improvement across Engineering: identify friction, propose improvements, run experiments, and ensure adoption, not just rollout.
• - Turn leadership discussions into actionable outcomes: notes, decisions, owners, timelines, and follow-through.
• - Strengthen Tech Lead effectiveness through management enablement (This is about reinforcing shared standards and management hygiene — not owning people management or performance decisions): a) reinforce 1:1 hygiene and team rituals b) help standardize lightweight best practices across teams c) ensure key processes actually happen consistently
• - Run Hiring Operations for Engineering: a) keep pipelines moving, remove bottlenecks, coordinate interview loops b) improve screening flow and process efficiency c) continuously refine the hiring system with templates, tooling, and feedback loops
• - Own Onboarding Operations for new Engineering joiners (especially devs): a) define and oversee onboarding structure, milestones, and handoffs b) ensure shadowing of key meetings/rituals and fast relationship-building c) run onboarding feedback loops and iterate the onboarding system
• - Operate performance and growth systems (process-first): a) review-cycle timelines, checklists, prerequisites, and reporting b) ensure the right conversations happen (without writing the reviews yourself) c) support mentorship program operations (cadence, tracking, improvements)
• - Manage training/learning operations: support execution of the annual training budget plan & encourage knowledge sharing and internal learning loops
• - Improve cross-functional awareness and alignment (Engineering ↔ PM/Design/etc.) at the process level & reduce surprises, clarify how information flows, and raise shared context

Engineering Operations Manager