{"id":6295,"date":"2026-10-05T15:52:42","date_gmt":"2026-10-05T07:52:42","guid":{"rendered":"https:\/\/www.thousandsofyearsmedia.com\/?post_type=career&p=6295"},"modified":"2026-10-06T09:03:47","modified_gmt":"2026-10-06T01:03:47","slug":"senior-full-stack-developer","status":"publish","type":"career","link":"https:\/\/www.thousandsofyearsmedia.com\/zh\/career\/senior-full-stack-developer\/","title":{"rendered":"Senior Full Stack Developer"},"content":{"rendered":"
\n

\n <\/h1>\n<\/section>\n
\n\t\t\t\t\"Full\n\t<\/figure>\n

\n\t\t\t\t<\/h2>\n\n
\n

\n Role Overview <\/h3>\n

Product & Platform<\/strong><\/p>\n

Build Complete Products. Own the Technology. Ship Systems That Work.<\/strong><\/p>\n

Company: Thousands of Years Media Sdn. Bhd. (ToYm)<\/strong><\/p>\n

    \n
  1. ROLE MISSION<\/strong><\/li>\n<\/ol>\n

    At Thousands of Years Media Sdn. Bhd. (ToYm)<\/strong>, we are looking for a proven Senior Full Stack Developer<\/strong> who can take ownership of building, improving and maintaining our web, mobile and backend systems.<\/p>\n

    You will work across BiteShorts and other current or upcoming ToYm digital products<\/strong>.<\/p>\n

    Your mission is not simply to write code.<\/p>\n

    Your mission is to help ToYm:<\/p>\n

    Build \u2192 Own \u2192 Operate \u2192 Improve \u2192 Scale<\/strong><\/p>\n

    reliable digital products that support our growing businesses.<\/p>\n

    For BiteShorts, this means strengthening technology that may support:<\/p>\n

    Content \u2022 Users \u2022 Creators \u2022 Membership \u2022 Rewards \u2022 Missions \u2022 Bite Shop \u2022 E-Commerce \u2022 Transactions \u2022 Payments \u2022 Analytics \u2022 Advertising \u2022 AI Services \u2022 Third-Party Integrations<\/p>\n

    We want to continue strengthening ToYm’s in-house technology capability<\/strong>.<\/p>\n

    This is not a role where you only work on one layer of a system.<\/p>\n

    We need someone who understands how a complete product works – from frontend and backend logic to APIs, databases, infrastructure, deployment, monitoring and production support.<\/p>\n

      \n
    1. WHY THIS OPPORTUNITY IS DIFFERENT<\/strong><\/li>\n<\/ol>\n

      Technology at ToYm supports businesses across:<\/p>\n

      Entertainment \u2022 Content \u2022 Commerce \u2022 Digital Platforms \u2022 AI \u2022 Creator Economy \u2022 Consumer Applications<\/strong><\/p>\n

      You may work across mobile applications, web applications, internal systems, consumer platforms, e-commerce, content platforms, APIs, integrations, AI services and new digital products.<\/p>\n

      You will work across the complete product cycle:<\/p>\n

      Planning \u2192 Architecture \u2192 Development \u2192 Testing \u2192 Launch \u2192 Monitoring \u2192 Scaling \u2192 Continuous Improvement<\/strong><\/p>\n

      We want someone who can build, troubleshoot and deliver<\/strong>, not someone who only understands one part of development.<\/p>\n

      \n Job Description <\/h3>\n
        \n
      1. WHAT YOU WILL OWN<\/strong><\/li>\n<\/ol>\n

        A. End-to-End Application Development<\/strong><\/p>\n

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

          B. Backend Systems & APIs<\/strong><\/p>\n

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

            C. Databases & Data Architecture<\/strong><\/p>\n

              \n
            • Design appropriate database structures.<\/li>\n
            • Optimise queries and application performance.<\/li>\n
            • Protect data integrity and reliability.<\/li>\n
            • Understand indexing, caching, transactions, consistency, backup, recovery and migration.<\/li>\n
            • Identify and resolve database bottlenecks.<\/li>\n<\/ul>\n

              D. Deployment & Production Reliability<\/strong><\/p>\n

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

                When something fails, we want to understand:<\/p>\n

                What happened?
                Why did it happen?
                How do we prevent it from happening again?<\/strong><\/p>\n

                E. Mobile Applications & Integrations<\/strong><\/p>\n

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

                  F. Technology Quality<\/strong><\/p>\n

                    \n
                  • Review existing systems and identify technical weaknesses.<\/li>\n
                  • Improve architecture, code quality, security, performance and maintainability.<\/li>\n
                  • Reduce unnecessary technical debt.<\/li>\n
                  • Implement appropriate testing, code review, monitoring and documentation.<\/li>\n
                  • Ensure important technical knowledge does not depend on only one person.<\/li>\n<\/ul>\n
                      \n
                    1. END-TO-END OWNERSHIP<\/strong><\/li>\n<\/ol>\n

                      You will work closely with:<\/p>\n

                      Product \u2022 UI\/UX \u2022 Growth \u2022 Operations \u2022 Management \u2022 Other Developers<\/strong><\/p>\n

                      You should be able to take a requirement through:<\/p>\n

                      Understand \u2192 Challenge Assumptions \u2192 Design \u2192 Build \u2192 Test \u2192 Deploy \u2192 Monitor \u2192 Learn \u2192 Improve<\/strong><\/p>\n

                      Your responsibility is the outcome<\/strong>, not simply completing the code.<\/p>\n

                      \n Job Requirements <\/h3>\n
                        \n
                      1. QKSC – WHO WE ARE LOOKING FOR<\/strong><\/li>\n<\/ol>\n

                        We do not select people only based on years of experience, academic qualifications or how well they speak during interviews.<\/p>\n

                        We assess candidates through:<\/p>\n

                        Q – Qualification<\/strong>
                        Do you have the minimum evidence to enter?<\/p>\n

                        K – Knowledge<\/strong>
                        Do you understand what needs to be done?<\/p>\n

                        S – Skill<\/strong>
                        Can you actually do it?<\/p>\n

                        C – Competency<\/strong>
                        Can you repeatedly deliver results with the right behaviours and judgement?<\/p>\n

                        Our hiring approach follows:<\/p>\n

                        Ask \u2192 Evidence \u2192 Scenario \u2192 Practical Test \u2192 Reference Check<\/strong><\/p>\n

                          \n
                        1. Q – QUALIFICATION<\/strong><\/li>\n<\/ol>\n

                          There is no strict degree requirement and no fixed minimum number of years<\/strong>.<\/p>\n

                          However, you must demonstrate evidence of real production development.<\/p>\n

                          You should have personally contributed significantly to at least one production system involving several of these areas:<\/p>\n

                          Frontend \u2022 Backend \u2022 Databases \u2022 APIs \u2022 Authentication \u2022 Cloud \/ Hosting \u2022 Deployment \u2022 Production Troubleshooting<\/strong><\/p>\n

                          Where available, show:<\/p>\n

                          GitHub \u2022 Technical Portfolio \u2022 Live Systems \u2022 Published Applications \u2022 Architecture Examples \u2022 Other Verifiable Work<\/p>\n

                          Most importantly, you must be able to explain:<\/p>\n

                          What did YOU personally build?<\/strong><\/p>\n

                          Production systems are more valuable to us than tutorial projects, certificates or unfinished prototypes.<\/p>\n

                            \n
                          1. K – KNOWLEDGE<\/strong><\/li>\n<\/ol>\n

                            You should demonstrate practical knowledge across areas such as:<\/p>\n

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

                            We do not require one fixed technology stack.<\/p>\n

                            What matters is whether you understand software engineering fundamentals<\/strong> and can adapt to the technologies required by the product.<\/p>\n

                              \n
                            1. S – SKILL<\/strong><\/li>\n<\/ol>\n

                              You should be able to:<\/p>\n

                                \n
                              • Build features end-to-end.<\/li>\n
                              • Design databases and APIs.<\/li>\n
                              • Integrate third-party services.<\/li>\n
                              • Implement authentication and permissions.<\/li>\n
                              • Deploy production systems.<\/li>\n
                              • Debug production incidents.<\/li>\n
                              • Identify performance bottlenecks.<\/li>\n
                              • Review and improve existing code and architecture.<\/li>\n
                              • Explain technical trade-offs.<\/li>\n
                              • Estimate technical complexity.<\/li>\n
                              • Translate business requirements into technical solutions.<\/li>\n
                              • Decide what should be built now versus later.<\/li>\n<\/ul>\n
                                  \n
                                1. C – COMPETENCY<\/strong><\/li>\n<\/ol>\n

                                  We particularly value:<\/p>\n

                                  Ownership<\/strong> – Take responsibility for outcomes.<\/p>\n

                                  Problem Solving<\/strong> – Identify symptoms, root causes, options, trade-offs and solutions.<\/p>\n

                                  \u9ad8\u6548\u6267\u884c<\/strong> – Move from idea to working production system.<\/p>\n

                                  Product Thinking<\/strong> – Understand users, business objectives, cost, speed, technical constraints and scalability.<\/p>\n

                                  Learning Agility<\/strong> – Learn new frameworks, platforms, APIs and AI tools when required.<\/p>\n

                                  \u52c7\u62c5\u8d23\u4efb<\/strong> – Communicate risks early and follow through.<\/p>\n

                                  Prioritisation<\/strong> – Separate critical issues from nice-to-have improvements.<\/p>\n

                                  Communication<\/strong> – Explain technical matters clearly.<\/p>\n

                                  Working Under Ambiguity<\/strong> – Clarify objectives and propose solutions without waiting for every detail.<\/p>\n

                                    \n
                                  1. WHAT MATTERS MORE THAN YEARS OR CERTIFICATES<\/strong><\/li>\n<\/ol>\n

                                    We want to understand:<\/p>\n

                                      \n
                                    • What production systems have you built?<\/li>\n
                                    • What did you personally build?<\/li>\n
                                    • How many users or transactions did they support?<\/li>\n
                                    • Why did you choose the architecture?<\/li>\n
                                    • What failed after launch?<\/li>\n
                                    • How did you fix it?<\/li>\n
                                    • How did you monitor reliability?<\/li>\n
                                    • What changed as usage increased?<\/li>\n
                                    • What would you do differently today?<\/li>\n
                                    • Can you take a feature from requirement to production?<\/li>\n<\/ul>\n
                                        \n
                                      1. BITESHORTS CONTEXT<\/strong><\/li>\n<\/ol>\n

                                        One key platform you may work on is BiteShorts<\/strong>.<\/p>\n

                                        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.<\/p>\n

                                        As usage grows, we need engineers who ask not only:<\/p>\n

                                        “Does the feature work?”<\/strong><\/p>\n

                                        but also:<\/p>\n

                                        “Will it remain reliable when usage increases?”<\/strong><\/p>\n

                                          \n
                                        1. SELECTION PROCESS<\/strong><\/li>\n<\/ol>\n

                                          Shortlisted candidates may be asked to:<\/p>\n

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

                                            We are not looking for one perfect answer.<\/p>\n

                                            We want to understand how you think, what you can actually do and what you have genuinely owned<\/strong>.<\/p>\n

                                              \n
                                            1. OUR VALUES<\/strong><\/li>\n<\/ol>\n

                                              CUSTOMER-CENTRIC<\/strong>
                                              PURPOSE-DRIVEN & RESULTS-ORIENTED<\/strong>
                                              TEAMWORK<\/strong>
                                              RESPONSIBILITY<\/strong>
                                              EFFECTIVE EXECUTION<\/strong>
                                              HUMBLE & LEARNING<\/strong>
                                              PURSUIT OF EXCELLENCE<\/strong>
                                              CONTINUOUS INNOVATION<\/strong>
                                              CONTRIBUTE TO SOCIETY<\/strong><\/p>\n

                                                \n
                                              1. THIS ROLE IS FOR YOU IF…<\/strong><\/li>\n<\/ol>\n

                                                You want to take ownership of production systems, not simply complete assigned tickets.<\/p>\n

                                                You can move from requirement to architecture, development, deployment and continuous improvement<\/strong>.<\/p>\n

                                                You care about what happens after launch.<\/p>\n

                                                And you want to strengthen the technology behind BiteShorts and ToYm’s growing digital businesses.<\/p>\n

                                                To Apply:<\/strong> 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.<\/p>\n<\/section>\n\t\t\t