Senior Full Stack Developer

3. WHAT YOU WILL OWN

A. End-to-End Application Development

• Develop and maintain frontend, backend and database components.
• Build reliable, maintainable and production-ready applications.
• Support mobile applications and mobile-related backend systems.
• Translate business requirements into practical technical solutions.
• Take responsibility for how the complete system works together.

B. Backend Systems & APIs

• Design and develop scalable backend services.
• Build and maintain APIs and system integrations.
• Manage authentication, permissions, business logic and data flows.
• Handle API security, validation, rate limiting and error handling.
• Integrate internal systems with third-party platforms.

C. Databases & Data Architecture

• Design appropriate database structures.
• Optimise queries and application performance.
• Protect data integrity and reliability.
• Understand indexing, caching, transactions, consistency, backup, recovery and migration.
• Identify and resolve database bottlenecks.

D. Deployment & Production Reliability

• Support development, staging and production environments.
• Work with cloud infrastructure and hosting.
• Improve CI/CD and deployment processes.
• Monitor applications, APIs, databases and infrastructure.
• Diagnose production incidents and identify root causes.
• Implement permanent solutions instead of repeated temporary fixes.

When something fails, we want to understand:

What happened?
Why did it happen?
How do we prevent it from happening again?

E. Mobile Applications & Integrations

• Build services required by iOS and Android applications.
• Support app releases, updates and production issues.
• Support push notifications, authentication, analytics and payment integrations.
• Understand Apple App Store and Google Play requirements.
• Build integrations involving payments, analytics, advertising, content, e-commerce, CRM, AI services and other APIs.

F. Technology Quality

• Review existing systems and identify technical weaknesses.
• Improve architecture, code quality, security, performance and maintainability.
• Reduce unnecessary technical debt.
• Implement appropriate testing, code review, monitoring and documentation.
• Ensure important technical knowledge does not depend on only one person.

4. END-TO-END OWNERSHIP

You will work closely with:

Product • UI/UX • Growth • Operations • Management • Other Developers

You should be able to take a requirement through:

Understand → Challenge Assumptions → Design → Build → Test → Deploy → Monitor → Learn → Improve

Your responsibility is the outcome, not simply completing the code.

5. QKSC — WHO WE ARE LOOKING FOR

We do not select people only based on years of experience, academic qualifications or how well they speak during interviews.

We assess candidates through:

Q — Qualification
Do you have the minimum evidence to enter?

K — Knowledge
Do you understand what needs to be done?

S — Skill
Can you actually do it?

C — Competency
Can you repeatedly deliver results with the right behaviours and judgement?

Our hiring approach follows:

Ask → Evidence → Scenario → Practical Test → Reference Check

6. Q — QUALIFICATION

There is no strict degree requirement and no fixed minimum number of years.

However, you must demonstrate evidence of real production development.

You should have personally contributed significantly to at least one production system involving several of these areas:

Frontend • Backend • Databases • APIs • Authentication • Cloud / Hosting • Deployment • Production Troubleshooting

Where available, show:

GitHub • Technical Portfolio • Live Systems • Published Applications • Architecture Examples • Other Verifiable Work

Most importantly, you must be able to explain:

What did YOU personally build?

Production systems are more valuable to us than tutorial projects, certificates or unfinished prototypes.

7. K — KNOWLEDGE

You should demonstrate practical knowledge across areas such as:

Frontend & Backend Architecture • API Design • Database Design • Authentication & Authorisation • Cloud Infrastructure • CI/CD • Git • Security • Testing • Debugging • Monitoring / Observability • Caching • Queues / Background Processing • CDN • Object Storage • Database Indexing • Backup & Recovery • Performance Optimisation • Third-Party Integrations • Scalability

We do not require one fixed technology stack.

What matters is whether you understand software engineering fundamentals and can adapt to the technologies required by the product.

8. S — SKILL

You should be able to:

• Build features end-to-end.
• Design databases and APIs.
• Integrate third-party services.
• Implement authentication and permissions.
• Deploy production systems.
• Debug production incidents.
• Identify performance bottlenecks.
• Review and improve existing code and architecture.
• Explain technical trade-offs.
• Estimate technical complexity.
• Translate business requirements into technical solutions.
• Decide what should be built now versus later.

9. C — COMPETENCY

We particularly value:

Ownership — Take responsibility for outcomes.

Problem Solving — Identify symptoms, root causes, options, trade-offs and solutions.

Pelaksanaan Berkesan — Move from idea to working production system.

Product Thinking — Understand users, business objectives, cost, speed, technical constraints and scalability.

Learning Agility — Learn new frameworks, platforms, APIs and AI tools when required.

Tanggungjawab — Communicate risks early and follow through.

Prioritisation — Separate critical issues from nice-to-have improvements.

Communication — Explain technical matters clearly.

Working Under Ambiguity — Clarify objectives and propose solutions without waiting for every detail.

10. WHAT MATTERS MORE THAN YEARS OR CERTIFICATES

We want to understand:

• What production systems have you built?
• What did you personally build?
• How many users or transactions did they support?
• Why did you choose the architecture?
• What failed after launch?
• How did you fix it?
• How did you monitor reliability?
• What changed as usage increased?
• What would you do differently today?
• Can you take a feature from requirement to production?

11. BITESHORTS CONTEXT

One key platform you may work on is BiteShorts.

BiteShorts is being developed beyond a short-form entertainment application into an ecosystem that may include content, users, creators, membership, rewards, Bite Shop, merchant missions, commerce, payments, advertising, analytics, AI and third-party integrations.

As usage grows, we need engineers who ask not only:

“Does the feature work?”

but also:

“Will it remain reliable when usage increases?”

12. SELECTION PROCESS

Shortlisted candidates may be asked to:

• Explain a production system they personally helped build.
• Explain or draw its architecture.
• Discuss a real production incident and root cause.
• Explain what might fail if traffic increased significantly.
• Complete a practical assessment covering architecture, API/database design, coding, debugging or performance analysis.
• Discuss how they would strengthen BiteShorts technology during their first 90 days.

We are not looking for one perfect answer.

We want to understand how you think, what you can actually do and what you have genuinely owned.

13. OUR VALUES

CUSTOMER-CENTRIC
PURPOSE-DRIVEN & RESULTS-ORIENTED
TEAMWORK
RESPONSIBILITY
EFFECTIVE EXECUTION
HUMBLE & LEARNING
PURSUIT OF EXCELLENCE
CONTINUOUS INNOVATION
CONTRIBUTE TO SOCIETY

14. THIS ROLE IS FOR YOU IF…

You want to take ownership of production systems, not simply complete assigned tickets.

You can move from requirement to architecture, development, deployment and continuous improvement.

You care about what happens after launch.

And you want to strengthen the technology behind BiteShorts and ToYm’s growing digital businesses.

To Apply: Submit your resume and, where available, GitHub, technical portfolio or examples of production systems you personally helped build. Be prepared to explain your personal contribution, technical decisions, production challenges and results.