Lead Unity Engineer

Lead Unity Engineer - Careers - LILA GAMES Skip to content LILA GAMES HOME CAREERS Menu Toggle Art Design Engineering HR Product Freelance EVENTS INSIDE LILA LILA GAMES Main Menu 3D Character Artist – Careers Art Art Director – Careers Art Manager – Careers Backend Developer CAREERS Character Concept Artist (All Levels) – Careers Confirmation Design Director Of Engineering – Careers Engineering Events FAQ Freelance Game Animator – Careers Game Designer Home HR-Careers Inside Lila Inside Lila(Test Page) Lead 3D Character Artist – Careers Lead Gameplay Engineer – Careers Lead Level Designer Lead Software Engineer (Unity) – Careers Lead Technical Artist – Careers Lead Unity Engineer – Careers LII – Privacy Policy LII – Terms and Conditions LILA Black – Privacy Policy LILA Black – Terms and Conditions Principal Game Animator Principal Game Animator Product Product Engineer – Careers QA Recruiter-Careers Saturdayschool Senior Environment Concept Artist – Careers Senior Software Engineer Senior Software Engineer (Unity) – Careers Systems Designer – Careers Technical Artist – Careers UI-UX-Designer-Careers Unity Engineer – Careers Lead Unity Engineer Apply About Lila Games: Lila Games strives to build a world-class engineering team (eventually) that can compete with the best in the world. We are a long way from that ambition, but we hope to find others to help us build this team from Bangalore, India. Built in India, published to the world. More information about Lila: https://tr.ee/7DD-CnUfci Why This Role Exists: We have a talented but young engineering team that has accumulated meaningful technical debt. We need a Lead Unity Engineer who can hold two things simultaneously – and be clear-eyed about the tension between them: Fix the foundation: refactor the codebase, introduce engineering discipline, and reduce the risk that technical debt costs us the launch. Ship the game: maintain development velocity and hit our soft launch milestones. You will not be handed a clean codebase. You will be handed a real one, with real problems and real stakes. If that excites rather than discourages you, this role is for you. What You Will Own: Own performance as a first-class concern . Run the profiler before features ship, not after performance is already bad. Every PR that touches gameplay, rendering, or memory should come with a profiler pass. On mobile, this is a non-negotiable engineering habit, not an occasional task. Build for liveops operability from day one. Every feature you ship should be operable without engineering involvement after launch. Designers should be able to adjust weapon balance, drop rates, event timing, and economy levers through config or dashboards – not by filing engineering tickets. Think about who operates what you build, not just whether it works on launch day. Establish and enforce engineering standards: code reviews, clean architecture, SOLID principles, and documentation – not as academic exercises but because a mobile live-ops game is a codebase your team will modify thousands of times post-launch. Bad structure makes hotfixes dangerous and kills your ability to iterate quickly. Build testable systems, not just tested systems . Pure logic – economy calculations, matchmaking, config parsing, anything that does not touch the engine – should be unit tested. Gameplay systems should be designed so their logic can be validated without running the full game. You do not need TDD dogma everywhere, but you must know what to test, what not to test, and how to architect so testing is possible. Lead and mentor the engineering team in Bangalore. Most engineers have not received structured technical feedback. Code review is your primary mentorship tool – specific, technical, and instructive. Your goal is to raise the floor of every engineer around you. Address inherited technical debt systematically: god class decomposition, async error handling, dependency injection hygiene, and event/signal system clarity. Work with a plan, not ad hoc. Collaborate with product and design to translate feature