Extending Your Development Team
TEKKON FAQ's
Everything you need to know about working with Tekkon from finding the right specialist and starting a 10-day trial to managing, supporting and scaling your embedded technology team.
What Are The Public Holidays In Nepal?
| Dates for 2026 | Holidays |
|---|---|
|
Sunday, 15th February 2026 |
Maha Shivaratri |
|
Monday, 2nd March 2026 |
Holi (Colour Festival) |
|
Thursday, 5th March 2026 |
Election Day |
|
Tuesday, 14 April 2026 |
Nepalese New Year 2082 |
|
Monday, 14th September 2026 |
Haritalika Teej Festival (Female Only) |
|
Saturday, 17th October 2026 |
Dashain Festival |
|
Sunday, 18th October 2026 |
Dashain Festival |
|
Monday, 19th October 2026 |
Dashain Festival |
|
Tuesday, 20th October 2026 |
Dashain Festival |
|
Wednesday, 21st October 2026 |
Dashain Festival |
|
Thursday, 22nd October 2026 |
Dashain Festival |
|
Monday, 9th November 2026 |
Tihar Festival |
|
Tuesday, 10th November 2026 |
Tihar Festival |
|
Wednesday, 11th November 2026 |
Tihar Festival |
|
Thursday, 1st January 2027 |
New Years Holiday (International) |
About Tekkon
Tekkon helps startups, scale-ups and established businesses add skilled technology specialists to their existing teams.
Rather than taking your product away and delivering it through a separate project team, we provide people who work inside your existing environment. They can join your stand-ups, use your development and communication tools, contribute to your documentation and work on the priorities you set.
Tekkon supports the matching, setup and ongoing assignment. You retain control of your product direction, technical decisions, day-to-day priorities and delivery outcomes.
An embedded specialist works as part of your existing team rather than operating separately from it.
They learn how your product works, develop an understanding of your business context and contribute through the same tools and processes as the rest of your team.
That might mean working from your Jira board, contributing through your GitHub repositories, joining stand-ups through Slack or Microsoft Teams and following your existing review, testing and release processes.
The aim is to give the specialist enough context to contribute effectively within their agreed responsibilities—not simply complete an isolated list of tasks.
“Tekkie” is the name we use for a Tekkon specialist.
A Tekkie might be a frontend, backend or full-stack developer, a test analyst, a DevOps engineer, a UI/UX designer, an AI or data specialist, a senior developer or a solution architect.
The role depends on what your team needs. What stays consistent is that they work within your environment and contribute to an agreed assignment.
A traditional software agency may be given a scope and asked to deliver the entire project independently.
Tekkon’s standard model is different. We provide specialists who join your existing team and work under your day-to-day direction.
You retain control of what is built, how work is prioritised, how technical decisions are made and when work is reviewed, accepted or released.
If you need a completely independent team to take responsibility for a fixed-scope project, we should first discuss whether Tekkon’s embedded model is appropriate for that situation.
We primarily work with startups, scale-ups and SMEs that need additional technology capability.
Some clients come to us because a local role has been difficult to fill. Others need to increase delivery capacity, add a specialist skill or grow their product team without hiring several permanent employees at once.
The model works best when the client has clear ownership of the product and can provide the Tekkie with suitable direction, access and feedback.
If you are still defining your product or are not sure what kind of support you need, talk to us. We can help you determine whether an embedded specialist is the right next step.
No.
We have a strong connection with the startup and scale-up community, but the same model can support established SMEs and larger organisations.
The important question is whether you need a specialist who can join an existing team, work within your systems and contribute to priorities managed by your business.
Tekkon’s technology talent base is in Nepal, supported by Australian leadership and account support.
Tekkies generally work from Tekkon’s supported workspace in Kathmandu and collaborate remotely with their client teams.
Working hours, required time-zone overlap and any particular operational or security requirements are discussed before the assignment begins.
Roles and Technical Capabilities
Tekkon can provide specialists across a range of technology roles, including:
- Frontend, backend and full-stack developers
- Mobile application developers
- Senior and lead developers
- Test analysts and automation engineers
- DevOps and cloud specialists
- UI and UX designers
- AI and machine-learning engineers
- Data analysts and data engineers
- Solution architects
- Technical consultants and leaders
The right role depends on the work, the capability already available within your team and how independently the person needs to operate.
If you are not sure which role you need, tell us where your team is getting stuck. We can help you clarify the capability gap.
Our specialists work across a broad range of web, mobile, desktop, cloud, data and AI technologies.
This includes technologies such as React, Angular, Vue, Node.js, Python, Django, Java, Spring, PHP, Laravel, C#, .NET, Flutter, React Native, Kotlin and Swift.
We also support cloud and DevOps environments using AWS, Microsoft Azure, Google Cloud, Docker, Kubernetes and Terraform, together with testing, database, business intelligence and machine-learning technologies.
That is not an exhaustive list. If your technology stack is not mentioned, send us the details and we will assess whether the right capability exists within our current team or recruitment pipeline.
Yes.
Depending on your requirements, Tekkon can provide specialists to support AI-enabled product development, machine learning, automation, data engineering, analytics and business intelligence.
This might involve integrating an existing AI platform, developing an AI-enabled product feature, automating an internal workflow, preparing and processing data or improving the way business data is reported and used.
AI and data assignments still need clear responsibilities, appropriate technical oversight and agreed security and privacy controls. Your business remains responsible for deciding how the resulting technology will be used and identifying any legal, privacy or regulatory requirements that apply.
Yes.
Our DevOps and cloud specialists can work with platforms such as AWS, Microsoft Azure and Google Cloud.
Depending on the assignment, they may support CI/CD pipelines, cloud infrastructure, containerisation, infrastructure as code, development environments, deployment processes, monitoring and operational tooling.
Because these roles can involve sensitive access, the responsibilities, systems and permission levels should be agreed before the assignment begins.
You retain control of your cloud accounts and infrastructure. Access should be limited to what the specialist needs to perform their agreed responsibilities.
Yes.
We can provide manual testers, test analysts and automation specialists who work within your existing product and development process.
They may assist with test planning, regression testing, release testing, automated test coverage and identifying quality issues earlier in the development cycle.
The Tekkie contributes to your quality process, while your business remains responsible for defining acceptance criteria and making final release decisions.
Yes.
UI and UX specialists can assist with user flows, wireframes, prototypes, product interfaces, design systems, usability improvements and developer-ready design documentation.
Depending on what you need, this may be arranged as an ongoing embedded assignment or a shorter specialist engagement for a clearly defined piece of work.
Yes, depending on the level of support required and specialist availability.
Senior developers, technical consultants and solution architects may support architecture decisions, technical planning, development practices, team guidance and technology-roadmap discussions.
It is important to define the role clearly. Adding a senior specialist does not automatically transfer responsibility for your product, budget or business decisions to Tekkon.
If you need someone to take on technical leadership responsibilities, those responsibilities and decision boundaries should be agreed before the assignment starts.
Yes, provided we can find someone with the relevant experience.
The Tekkie will need suitable access to the repository, development environment, documentation and people who understand the existing system.
How quickly they can contribute will depend on the codebase’s size, complexity, age, documentation and current condition.
For a legacy system, it is particularly important to be realistic about onboarding time. A new specialist cannot be expected to understand years of technical decisions immediately, but clear documentation and access to the right people can make the transition significantly easier.
Yes.
Many clients begin with one developer and add capability as their product, workload and budget grow.
You might start with a full-stack developer and later add frontend or backend capability, quality assurance, UI/UX, DevOps, AI, data or technical architecture.
This allows you to build a broader product team progressively rather than recruiting every role at once.
Each new role is matched separately based on the capability your team needs at that stage.
Pricing and the 10-day Trial
Our technology specialists start from $150 AUD per day plus GST, depending on the role, experience level and skills you need.
Mid-level frontend, backend and full-stack developers and test analysts typically start from this rate. Specialist roles such as DevOps, UI/UX, AI and machine learning, senior development and solution architecture are priced higher.
Your exact rate will be confirmed before the assignment begins.
We’ll recommend the level of specialist that suits the work you actually need done, not simply the most expensive person we can provide.
Rates vary because different assignments require different levels of experience and technical capability.
The rate may be influenced by the role, seniority, technology, scarcity of the required skills, complexity of the responsibilities and the working arrangement.
For example, a mid-level developer working within an established team will usually have a different rate from a solution architect expected to provide senior technical direction.
We’ll explain the recommended level and rate before you proceed.
Yes. We generally start with a prepaid 10-day trial, subject to the applicable agreement.
The trial allows you to work with your selected Tekkie on real tasks inside your existing environment before deciding whether you would like to continue.
It gives you an opportunity to assess the things that matter in practice: technical capability, communication, responsiveness, working style and how well the person fits into your team.
At the end of the trial, both sides can review the experience and confirm whether to move into an ongoing arrangement.
No. The 10-day trial is prepaid at the specialist’s agreed day rate.
It is a real working assignment rather than an unpaid assessment. Your selected Tekkie joins your team and works on agreed tasks within your environment.
The trial reduces the need to make a longer commitment before you have seen how the person works, but it does not make the work itself free.
Your selected Tekkie joins the agreed communication channels, receives the required system access and begins working on suitable tasks within your existing environment.
They may attend relevant meetings, contribute through your development or project-management tools and work with your internal team in the same way they would during an ongoing assignment.
During the trial, you can assess how they understand requirements, communicate, respond to feedback, navigate the existing system and contribute to real work.
Tekkon remains available throughout the trial if either side has questions or concerns.
Choose real but appropriately scoped work.
A good trial task allows you to observe how the Tekkie thinks, communicates and contributes without depending on a large outcome that cannot reasonably be completed within ten working days.
This could include investigating a defined issue, completing a contained development task, adding tests, reviewing part of the codebase, improving a small workflow or contributing to an existing sprint.
The trial should assess how the Tekkie works within your environment. It should not be treated as a guarantee that a major product feature or complex outcome will be completed within ten days.
Yes, unless you tell us otherwise before the trial ends.
The 10-day trial is designed to move into an ongoing assignment if the fit is right. Unless you tell us before the trial ends that you do not want to continue, the assignment will continue under the agreed ongoing arrangement.
We will check in during the trial so any questions about fit, performance or the ongoing arrangement can be raised before the trial finishes.
If you do not want the assignment to continue, let us know before the end of the trial so we can confirm the appropriate next steps.
No. Tekkon assignments are designed to give growing businesses flexibility without locking them into a long fixed-term project contract.
After the trial, you can continue working with your Tekkie on an ongoing basis and adjust your wider team as your requirements evolve, subject to specialist availability, agreed terms and applicable notice periods.
The model gives you the benefit of having someone embedded in your team without immediately taking on another permanent local hire.
Flexible does not mean an assignment can be changed or stopped without notice. The applicable conditions will be explained in your agreement.
Our standard Tekkie assignments are generally full-time and continuous. Part-time arrangements are mainly available for specialist roles such as DevOps, UI/UX and, in some cases, project management.
A standard full-time assignment runs continuously across the Tekkie’s normal working days, with breaks for weekends, Nepal public holidays and approved leave. It is not designed to be paused and restarted informally from week to week.
Where a part-time specialist arrangement is suitable, the expected days or hours, availability and billing arrangement are agreed before the assignment begins.
Yes, for some clearly defined specialist requirements.
For example, you may need a short period of DevOps assistance, an architecture review or several days of UI/UX support.
These arrangements can work well when the responsibilities and expected output are clear, but they are different from the standard ongoing embedded-developer model.
Availability, minimum billing and the scope of the specialist’s responsibility should be agreed upfront.
Working with Your Tekkie
They work inside your environment as an extension of your existing team.
Your Tekkie can work in your project-management system, development environment, repositories, email, Slack or Teams, meetings, documentation and other approved tools you already use.
You set the priorities and maintain control over what gets built, how technical decisions are made and when work is reviewed or accepted.
Tekkon stays involved throughout the assignment to support the relationship and help address operational, communication or resourcing concerns.
Your team manages the day-to-day priorities, requirements and technical direction.
You decide what the Tekkie works on, how the work fits into your product roadmap and when work is reviewed, accepted or released.
Tekkon manages the broader assignment relationship. We support the matching, setup, payroll and operational arrangements and can help with feedback, performance or fit concerns.
The responsibilities of each party should be clearly understood before the assignment begins.
The client is responsible for giving the Tekkie the context and direction needed to perform their agreed responsibilities.
That normally includes providing appropriate system access, explaining priorities, defining requirements, answering questions, reviewing work and giving timely feedback.
The client also retains responsibility for product direction, business decisions, technical approvals, security permissions, release decisions and the overall delivery outcome.
A Tekkie can bring experience and initiative to your team, but they should not be expected to make unclear commercial or product decisions on your behalf.
Tekkon supports the people and operational relationship around your Tekkie.
That includes matching, assignment setup, payroll, attendance and operational support, timesheet review, performance conversations and help if the requirements or team structure change.
We stay connected throughout the assignment rather than disappearing after the Tekkie starts.
Your team continues to manage the Tekkie’s day-to-day responsibilities and product priorities.
A clear onboarding plan makes a significant difference.
Before the start date, you should prepare the relevant system access, development environment, product context, documentation, communication channels and suitable initial tasks.
It also helps to identify one person who can answer questions, explain decisions and provide feedback during the first few weeks.
The trial is more useful when the Tekkie can begin working inside the real environment. If access or priorities are delayed, there will be less meaningful work available to assess.
That depends on your product, codebase, documentation and the complexity of the role.
A Tekkie may begin contributing to contained tasks relatively quickly, but understanding the wider product and making confident decisions takes time.
Clear documentation, access to the right people and well-scoped initial work can make onboarding more effective.
The 10-day trial helps you assess how the Tekkie learns and works within your environment. It is not a promise that they will understand an entire complex system immediately.
Tekkies work from Nepal, which is 2 hours 15 minutes behind Perth, Western Australia, and 4 hours 15 minutes behind Australia’s east coast. During eastern Australian daylight saving, the difference is 5 hours 15 minutes.
This gives Australian teams useful working-day overlap. The exact schedule and any required collaboration hours are discussed and agreed for each assignment.
Some flexibility may be possible depending on the role and individual, particularly where recurring meetings or collaboration hours are important.
Because daylight saving changes the time difference for some Australian states, the agreed working hours should be recorded as part of the assignment.
Yes, where the meetings are relevant to their work and fall within the agreed schedule.
The Tekkie can join stand-ups, sprint planning, reviews, retrospectives and other appropriate team discussions.
Including them in the right conversations helps them understand priorities, dependencies and decisions.
At the same time, the meeting schedule should leave enough focused time for them to complete their work.
Yes.
A Tekkie can collaborate with your employees, founders, product managers, technical leaders and other approved partners.
What matters is that responsibilities and decision-making authority are clear.
If several teams or providers are contributing to the same product, everyone should understand who owns each part of the work, how changes are reviewed and who makes final decisions.
Yes.
Your Tekkie works under your day-to-day direction, so you can set the level of work logs, code comments, documentation and progress updates you expect as part of their agreed responsibilities.
Tekkies also record their working days and work notes for assignment and billing visibility. Your Tekkon invoice can include a link to this assignment log.
Tekkon supervisors also review Tekkie timesheets. Your own project-management and development tools remain the main source of detail about progress and completed work, and you can require appropriate documentation within those tools during the Tekkie’s paid working time.
Tekkies generally work from Tekkon’s supported workspace in Kathmandu.
The workspace provides a professional environment, development equipment, internet connectivity and operational support.
If your assignment requires specialised hardware, additional software, particular internet capacity or another unusual setup, let us know before the assignment begins.
We can then confirm what is required and whether any additional cost applies.
Tekkies generally observe Nepal public holidays and may take approved leave in line with Tekkon’s policies.
Tekkon can provide the relevant holiday calendar so you can consider those dates in your delivery planning.
Client holidays, quiet periods or internal delays do not automatically pause the assignment.
If there is an upcoming period when your team’s availability or workload will change, talk to us early so the best option can be discussed.
AI, Security and Ownership
Yes, where it is appropriate and permitted by your organisation.
Our Tekkies are comfortable using modern AI-assisted tools, but they must still follow the client’s security, privacy and development policies.
Confidential code, customer data, credentials or commercially sensitive information should not be entered into an unapproved AI tool.
We recommend discussing approved tools and boundaries during onboarding so everyone understands how AI can and cannot be used within the assignment.
Tekkon’s published Security Statement describes a risk-based information-security approach aligned with ISO 27001 and NIST 800-37.
Our published practices cover areas such as staff screening, confidentiality, information classification, least-privilege access, password management, asset controls, encryption and physical workspace security.
Alignment with a security standard should not be interpreted as formal certification.
The security of an assignment also depends on the client’s systems, permissions and internal practices. Your business decides what the Tekkie can access and should provide only the access required for the agreed responsibilities.
Tekkon and its staff are subject to confidentiality obligations under the applicable agreement.
A Tekkie should only access and use confidential information where it is required to perform the assignment.
If your organisation has additional confidentiality requirements, security policies or an NDA, provide those documents before the assignment begins so they can be reviewed.
Tekkon will not use your confidential work in a case study or marketing material without your permission.
Subject to the applicable agreement, intellectual property created specifically by the Tekkie while providing services for your assignment belongs to the client.
Your existing code, data, documentation and other pre-existing intellectual property also remain yours.
Pre-existing materials belonging to another party, third-party software and open-source components remain subject to their existing ownership and licence conditions.
Clients should review the applicable agreement for the complete intellectual-property terms.
Your business remains in control of its repositories, infrastructure, accounts and permissions.
You decide which systems the Tekkie can access and what level of permission is appropriate.
Access should follow the principle of least privilege, meaning the Tekkie receives only the access needed for their agreed responsibilities.
We also recommend ensuring that your organisation retains administrative access and does not make critical systems dependent on any one individual.
Only where you approve the access and it is appropriate for the assignment.
Production access should be controlled, documented and limited according to your organisation’s security policies.
Where practical, development, testing, approval and production responsibilities should be appropriately separated.
If the role requires sensitive or privileged access, discuss the controls with Tekkon before the assignment begins.
Potentially, but the requirements need to be identified before access is provided.
If the assignment involves personal, financial, health or other regulated information, your organisation should determine which legal, privacy, security and compliance requirements apply.
Additional contractual, technical or access controls may be required.
Tekkon can explain its security and operational practices, but your business remains responsible for determining the regulatory requirements that apply to its product and data.
Your organisation should retain administrative ownership and appropriate access to its repositories, documentation, infrastructure and other business-critical systems.
The Tekkie should work within client-controlled systems wherever practical.
We also recommend maintaining current documentation, recording important decisions and avoiding situations where only one person has access to critical information.
This protects continuity whether you work with Tekkon, internal employees or another technology partner.
Assignment Support and Changes
The 10-day trial gives you an early opportunity to assess the fit.
But people, businesses and assignments can change. Something that worked well initially may be affected later by workload, communication, responsibilities, the client environment or personal circumstances.
If something is not working, tell us early.
We can help clarify the issue and support feedback or performance conversations with the Tekkie and their supervisor.
If the concern cannot be resolved, we can discuss whether a different specialist or another arrangement is the right next step, subject to the applicable agreement and specialist availability.
Yes, you can discuss a change with Tekkon.
We will first try to understand what has changed and whether the issue relates to expectations, communication, technical fit, workload or another factor.
Depending on the circumstances, the agreement and specialist availability, we can discuss possible alternatives and how any transition should be managed.
A change is not always immediate, so raising concerns early gives us more time to find an appropriate solution.
Let us know as soon as the role, responsibilities or technology changes.
We can assess whether the existing Tekkie can continue, whether additional support is required or whether the assignment needs a different type or level of specialist.
A significant change in responsibilities may require an updated assignment specification and could affect the rate or commercial terms.
Discussing the change early helps avoid placing expectations on the Tekkie that were not part of the original assignment.
Standard embedded assignments are designed to run continuously rather than being switched on and off from week to week.
Unless something different has been agreed upfront, a full-time Tekkie works their normal Nepal working days on an ongoing basis.
Nepal public holidays and approved leave are exceptions, but client holidays, quiet periods or internal delays do not automatically pause the assignment.
That continuity matters because the Tekkie’s capacity is reserved for your team.
If you expect a quieter period or need to change capacity, talk to us early so we can work through the available options.
Yes, subject to specialist availability, notice periods and the terms of each assignment.
You can add different capabilities as your product and workload grow or discuss reducing capacity when your requirements change.
Scaling works best when it is planned rather than treated as an immediate weekly adjustment.
Talk to us early so matching, knowledge transfer and any changes to responsibilities can be managed properly.
If a Tekkie is leaving an assignment, Tekkon will communicate the change and discuss the available next steps with you.
Where circumstances allow, we will work with you on an appropriate transition, including documentation and handover.
The effectiveness of any handover also depends on your organisation maintaining current documentation, shared repository access and visibility over important systems.
Handover overlap may not be possible in every circumstance, so important knowledge should never sit with only one person.
Direct employment may be possible, but it is subject to the conditions in Tekkon’s agreement.
Restrictions, notice requirements and a placement fee may apply if a client wants to employ a current or recent Tekkie directly.
Talk to us before making an offer so we can explain the applicable process and commercial terms.
Yes, subject to the notice periods and other conditions in the applicable agreement.
Notice requirements may vary depending on how long the assignment has been running and the reason it is ending.
If you are considering ending or changing an assignment, talk to us early.
That gives everyone time to manage current work, system access, documentation and handover properly.
Billing and Practical Details
Ongoing assignments are billed under the arrangement confirmed in your proposal and agreement.
Full-time embedded assignments may be structured around regular 20-working-day cycles, while part-time or specialist arrangements may be billed differently.
The applicable day rate, payment timing and any additional costs will be explained before the assignment begins.
The 10-day trial is prepaid, and ongoing assignments generally use an agreed advance or regular payment arrangement.
Your proposal and invoice will explain the amount, due date and payment method.
It is important to review the relevant documents because payment may also form part of the process for accepting the assignment terms.
Standard workspace, development equipment and operational support are generally included in the assignment arrangement.
If you require specialised hardware, paid software licences, enhanced connectivity or another non-standard setup, an additional cost may apply.
We will discuss those requirements before the specialist starts rather than adding something unexpected later.
Tekkon provides the Tekkie’s standard working setup, while the client generally provides access to its own systems and any client-specific licences needed for the assignment.
This might include project-management software, repositories, cloud platforms, communication tools or specialist applications.
Licensing and access responsibilities should be confirmed during onboarding.
Getting Started
Start by telling us about your product, current team and the problem you need help solving.
It is useful to know your technology stack, the skills you think you need, expected responsibilities, preferred start date, working hours and any security requirements.
You do not need to arrive with a perfect position description.
If you can explain what you are building, where delivery is slowing down or what capability is missing, we can help you clarify the role.
We start with a conversation about your business, product, team and current needs.
If Tekkon’s embedded model appears suitable, we clarify the role, experience level, working arrangement, timeline and likely pricing.
Our Resource Manager then reviews the current team and recruitment pipeline. We introduce the recommended Tekkie or a small shortlist, confirm the assignment terms and arrange the prepaid trial.
If the trial demonstrates a good fit and both sides want to continue, the Tekkie can move into the agreed ongoing arrangement.
Yes.
The initial conversation is an opportunity for us to understand what you need and for you to decide whether Tekkon’s model is suitable.
There is no obligation to proceed simply because you speak with us.
If there is a potential fit, we’ll explain the proposed role, matching process, pricing and next steps before you make a decision.
Tell us what you are building or where your team needs support.
You can share as much or as little detail as you currently have. We’ll ask the right questions, help clarify the need and let you know whether Tekkon is likely to be a good fit.
Still Have a Question?
Every team, product and assignment is different.
If your question is not covered here, tell us what you are building, where your team needs support or which capability is currently missing.
We’ll give you a clear answer about whether and how Tekkon may be able to help.
These FAQs provide general information about Tekkon’s services. The applicable proposal, assignment documentation and Staff Augmentation Agreement govern each assignment and take precedence where terms differ.