Software Engineering Manager

Role & Responsibilities
You will lead backend (Node.js, Type Script) and frontend (React Native, JavaScript, Type Script) development while ensuring architectural integrity, execution discipline, and delivery visibility.
Your responsibilities include:
Reviewing all backend and frontend code before merge and maintaining high code quality standards
Conducting daily pull request reviews and enforcing clean architecture practices
Ensuring strict Type Script implementation and preventing technical debt
Identifying security risks, scalability concerns, and performance bottlenecks
Supervising individual developer output and productivity
Providing structured daily updates to the founder without fail
Daily updates must clearly include:
Work completed by each backend developer
Work completed by each frontend developer
Blockers or dependencies
Technical risks or architectural concerns
Sprint and timeline health
You will also be responsible for:
Validating backend system design and API structure
Overseeing database schema design and optimization
Reviewing authentication and role-based access systems
Monitoring scalability decisions and long-term architecture
Managing sprint planning and engineering workflow

If required, you must be capable of working side by side with developers and writing production-level code yourself. This includes fixing critical backend issues, refactoring architecture, helping unblock integrations, and improving performance where necessary.
This role is approximately 50% technical oversight and code review, 30% team supervision and planning, and 20% hands-on development when needed.
Required Experience & Skills
6 to 8+ years of hands-on experience as a software developer
Strong expertise in Node.js and Type Script
Strong understanding of scalable React Native architecture
Deep knowledge of backend architecture and API design
Experience reviewing production-level code
Strong debugging and refactoring skills
Ability to detect architectural weaknesses early
You must understand:
Monolith vs microservices tradeoffs
API versioning strategy
Database optimization principles
Authentication and authorization systems
Background job processing and async workflows
Logging, monitoring, and performance optimization
Git branch strategy and pull request workflows
CI/CD fundamentals

Preferred Experience
Marketplace platform development
Payment gateway integrations
Inventory or supplier management systems
AWS or cloud infrastructure knowledge
Startup experience building products from early stage
Who We Are Looking For
We are looking for someone who thinks in systems, not tickets.
Someone who protects architecture, enforces discipline, and takes ownership of engineering execution.
You should be confident enough to challenge developers technically, structured enough to maintain daily reporting discipline, and strong enough to step in and build when needed.
If you are looking for a coordination-only position, this role is not suitable.