Monday morning, an HR manager at a manufacturing company in Lampung opens her email and finds three pieces of bad news at once: a software engineer resigned with two weeks' notice, the candidate who was "almost a done deal" last week chose a bigger company's offer, and two job postings that have been up for two months only attracted three applicants—two of whom never answered the interview invitation.
She isn't a lazy HR team. Her company offers salaries that are reasonable by local standards, decent benefits, and a clear career path. The problem: she's competing in a labor market that is no longer local. Candidates in Lampung can work remotely for companies in Jakarta, Singapore, even the United States. "Reasonable by local standards" now faces global benchmarks—and most Indonesian companies haven't adjusted their strategies to this reality.
Indonesia's tech talent gap isn't a secret. Various industry research reports thousands of technology positions going unfilled every year, while demand keeps growing alongside digitalization in nearly every sector. Government bodies and industry associations project Indonesia's digital economy will need hundreds of thousands of additional digital talents in the coming years. Meanwhile, many mid-sized companies outside big cities feel they "can't possibly compete" for talent.
This article is a practical guide—not HR theory—on finding, hiring, and keeping tech talent in Indonesia: from writing job descriptions people actually read, to effective interviews, to retention strategies that work on engineers' real motivations.
Understand Indonesia's Tech Talent Market First
Before discussing recruitment tactics, understand the market's actual conditions.
Talent is concentrated, but work is no longer
The majority of Indonesian developers have historically been concentrated in Jabodetabek, Bandung, Yogyakarta, and Surabaya. But the pandemic permanently changed how the industry works: remote work is now the norm for many tech companies, and candidates in mid-sized cities—including Lampung—can work for companies anywhere in the world. The consequences run both ways: your competition is no longer local, but you also have access to talent outside your city.
The seniority gap is the biggest problem
Indonesia's tech market isn't short of juniors. Every year, new graduates and bootcamp graduates flood the market. What's scarce is senior engineers: people who have led system architecture, handled production failures, and mentored teams. The fiercest competition happens at this layer, and senior salaries in Jakarta have reached levels comparable to regional standards.
Salary isn't everything—but it's still number one
Data from various Indonesian tech salary surveys shows a wide range: junior developers at Rp 6-12 million per month, mid-level at Rp 12-25 million, senior at Rp 25-50 million or more at major tech companies. Beyond salary, the factors engineers most often cite when staying or leaving: quality of work, career growth, work flexibility, and management quality. Salary attracts them in; the other factors decide whether they stay.
Writing Job Descriptions People Actually Read
A bad job description is a wrong applicant filter: it attracts the wrong people and drives away the right ones. The most common mistakes in Indonesia:
1. Requirements copied from global templates
Listing "minimum 5 years experience with Python, React, AWS, Kubernetes, and microservices" for a role that actually needs 2 years and one core technology. JDs like this signal that the company doesn't understand its own job—and competent engineers will avoid it.
The right principle: separate must-haves from "nice-to-haves", and limit must-haves to 3-5 items that are truly essential.
2. Focusing on technology, not problems
The best engineers are motivated by the problems they solve, not technology lists. An attractive JD explains: what you'll work on, who it's for, and why it matters. Example: "You'll build a system processing 50,000 orders per day and keep online stores in remote areas selling without friction" is far stronger than "You'll use Node.js and PostgreSQL".
3. Not mentioning the team, the manager, or how work happens
Candidates read between the lines. Mention: team size, who the direct manager will be, how work happens (sprints? remote? on-site?), and what success looks like in the first 6 months. This transparency dramatically raises applicant quality because candidates can self-filter.
4. Not mentioning salary
Many Indonesian companies still avoid publishing salary ranges. Yet this practice wastes everyone's time: HR interviews candidates who'll decline at offer stage, and candidates go through full processes for offers that would never fit. Publishing an honest salary range is the most efficient filter that exists, and the practice is increasingly accepted in the tech job market.
Where to Find Candidates
Once the JD is right, make sure it reaches the right people. Channels that work in Indonesia:
Job platforms and communities
Jobstreet, LinkedIn, and tech-specific platforms (like Glints or Kalibrr) are the main channels. But for engineering roles, communities often beat platforms: developer groups on Telegram, meetups, local tech communities, and conferences are where engineers recommend each other. Companies known in the community—through contributions, sharing sessions, or regular presence—get a stream of referrals that never appears in job ads.
Employee referrals
Referral programs are the channel with the best applicant quality and lowest cost per hire. Good engineers know other good engineers. Offer real referral incentives—not just "appreciation"—and make the process easy to report.
Outbound approaches
Instead of waiting for applications, actively find candidates who aren't applying. Senior engineers rarely browse job boards; they receive offers through networks. A personal, specific approach—"I saw your open-source project on X, we face a similar problem at Y"—is far more effective than mass template messages.
Bootcamps and non-traditional paths
Coding bootcamp graduates in Indonesia are now a legitimate source of talent for junior roles. Their advantages: they're usually job-ready, familiar with modern practices, and have realistic salary expectations. The risk: varied depth of fundamentals. A selection process that tests fundamentals—not just portfolios—separates the truly ready from the merely graduated.
Interview Processes That Don't Waste Everyone's Time
Technical interviews in Indonesia often fall into two extremes: too easy so they filter nothing, or too academic so they reject competent engineers. There's a healthier pattern.
1. An honest initial screening
Start with a short conversation (30 minutes) about real experience: what projects they've worked on, what architecture decisions they've made, and what failures they've fixed. This phase filters 80 percent of mismatches at low cost. Stories about real projects are far more informative than memorized answers.
2. Technical tests relevant to the job
Coding tests should reflect real work: debugging broken code, designing a simple data schema, or explaining the trade-offs of a technical decision. Avoid algorithmic puzzle questions that never appear in daily work unless the role genuinely requires them. Give humane time limits and allow access to documentation—engineers work with documentation, not without it.
3. Take-home projects (compensated)
A well-designed take-home assesses real work ability: reading requirements, writing clean code, and communicating decisions. But a take-home that takes days is a disguised rejection of strong candidates who have many options. Keep it to 3-4 hours of work, and respect candidates' time by giving specific feedback to everyone who completes it.
4. Involve the team they'll join
The final interview should involve team members who will work with the candidate. Two goals: assess technical fit from the perspective of direct colleagues, and give the candidate an honest picture of team culture. Candidates accepted by their team are more likely to survive their first year.
5. Speed is quality
In a competitive talent market, a drawn-out recruitment process is silent rejection. Good candidates juggle multiple offers. A healthy target: from first application to offer within 2-3 weeks, with regular status updates at every stage. Candidates who feel respected by the process tend to accept—even below a competitor's offer.
Common Hiring Mistakes
Hiring for "can code", not for mindset
Code can be learned; ways of thinking aren't easily changed. The right engineer has curiosity, comfort with feedback, and the ability to explain complex things simply. These three qualities matter more to long-term success than a list of programming languages.
Ignoring internal candidates
Promoting from within—from support, QA, or non-technical roles interested in technology—often produces the most loyal employees. They already know the business, have proven their work ethic, and this path sends a strong signal across the organization that growth is real.
Using candidates as "price comparators"
Some companies interview external candidates only to pressure internal employees' salaries down. This practice leaks fast, destroys trust, and damages the company's reputation in the tightly connected engineering community. The job market is small; reputation spreads faster than you think.
Retention: Why Engineers Stay and Why They Leave
The cost of replacing an engineer isn't just recruitment cost—there's a much larger cost: lost system knowledge, slowed development, and the burden falling on the remaining team. Understanding retention motivations is a business skill, not just an HR matter.
Factors that make engineers stay
- Meaningful work: interesting problems, products people use, and autonomy in solving them.
- Real growth: not just job titles, but increasing responsibility and new skills to learn.
- Quality peers and management: engineers stay in good teams; they leave bad management. A competent technical manager is the strongest retention magnet.
- Work-life balance: work flexibility, realistic workloads, and a culture that doesn't glorify overtime.
- Fair compensation: doesn't have to be the highest, but must follow the market. Compensation unfairness is the most common reason for departures that can't be saved.
Factors that drive engineers away
- Unresolved technical debt: years of patching a system that should be rebuilt exhausts engineers. They know when a system is beyond saving.
- No room to grow: when promotion paths are blocked and tasks don't change for years, the best talent looks elsewhere.
- Chronic overtime: a culture that treats overtime as devotion is the most commonly cited informal reason for leaving.
- Non-technical management: technical decisions made without understanding consequences—impossible deadlines, features that break architecture—make engineers feel their work isn't valued.
Retention Strategies That Work
1. Clear and honest career paths
Engineers don't always want to be managers, but everyone wants to know where their career is heading. Build dual tracks: a technical path (senior engineer, staff, principal) and a management path, with transparent promotion criteria and regular career discussions that aren't just annual formalities.
2. Structured learning investment
A learning budget—courses, conferences, books, study time—is a real signal that growth is promised sincerely. More important than budget is time: a team that can spend a few hours weekly on learning (not squeezed between overtime) shows rare commitment.
3. Keep technical challenges alive
Senior engineers leave boring jobs faster than hard ones. Maintain challenges: new projects, architecture improvements, mentoring juniors, or exploring relevant technologies. The chance to "occasionally work on something nobody in the company has done before" is priceless retention.
4. Market-following compensation
Do data-driven salary reviews at least once a year, with updated market benchmarks. The most cost-effective long-term strategy: proactively raise good employees' salaries rather than lose them and pay more for replacements who may not be as good.
5. Honest exit interviews—followed up
When an engineer decides to leave, ask why sincerely—and more importantly, fix causes that recur. Departure data is product feedback for your organization.
6. Proper onboarding: the first 90 days decide
There's a phase often forgotten in retention strategy: the first days. New engineers form their judgment of the company within their first 90 days—and that judgment is far harder to change afterward. Bad onboarding is the quietest way to lose talent you just struggled to recruit.
Healthy technical onboarding covers three things. First, access and a ready work environment from day one: accounts, repositories, server access, internal documentation. An engineer spending the first week waiting for access reads a clear signal about how the company treats its employees. Second, context: not just "here's the code", but why the system was built this way, what major decisions were made, and where the fragile parts are. This knowledge usually lives only in senior engineers' heads—good onboarding copies it into the new person's head in a structured way. Third, a meaningful first task: not busywork, but a real problem with clear success criteria, solved with guidance from a senior colleague.
One simple indicator for evaluating onboarding: when can the new engineer ship their first change to production without hand-holding? The faster—with confidence—the better. Assign a mentor for the first 90 days, schedule weekly check-ins, and don't let the new person drift alone. Good onboarding costs little compared to re-hiring.
Alternatives to Hiring: When Adding Full-Time Staff Isn't the Answer
There are times when technology needs don't justify the cost of building a full team. For certain phases, there are healthier paths.
1. Flexible capacity
Instead of hiring three permanent engineers for a 6-month project, companies can rent engineering capacity as needed. This reduces fixed costs, hiring-mistake risk, and management burden. This model is maturing in Indonesia—companies can get senior engineers without permanent salary commitments.
2. Extended teams
The internal team keeps ownership of the product and direction, while a technology partner provides additional capacity working alongside the internal team—with agreed processes, code standards, and communication. This differs from traditional outsourcing that throws projects into a black box.
3. Forward-deployed engineers
For complex initiatives, senior engineers from a partner work inside your team for a period: joining sprints, writing code in the same codebase, transferring knowledge, and building internal team capacity. The result: skills rise, not just output.
When full-time hiring is still right
Permanent teams remain essential for core functions: main products, domain knowledge, and continuity. The healthy pattern: hold the core inside, use flexible capacity for peak loads, experimental projects, or specialized skills that aren't economical to hire permanently. Read our guide on when you need an IT consultant to understand when technology decisions should involve external perspective.
Building a Culture That Attracts Talent
In the end, hiring and retention are two sides of one thing: the company's reputation as a workplace. Engineers talk to each other. One employee's experience becomes a story heard by hundreds of candidates.
The culture that attracts tech talent in Indonesia doesn't have to be luxurious—no need for a snack-filled pantry or ping-pong tables. Indonesian engineers stay at companies that: respect their expertise, give room to grow, pay fairly, and lead with competence. This sounds simple, but it's surprisingly rarely practiced consistently.
Practical steps you can start this week: fix one job posting with an honest, specific JD; set a 3-week recruitment process target; and hold a career conversation with every engineer on your team—not to evaluate, but to hear what makes them stay and what threatens that.
The Role of Technology Partners in Talent Strategy
For mid-sized companies outside big cities, there's one obstacle that can't be solved with recruitment strategy alone: scale. Attracting senior engineers to a company with a small tech team is a long struggle. In this situation, a technology partner isn't a replacement for an internal team, but a way to keep moving while building capacity.
The Kartech. team in Bandar Lampung works in models designed for this need: forward deployed engineering for complex initiatives requiring seniority, project-based delivery for products with clear scope, and IT consulting for architecture and strategy decisions. We also help companies assess when to hire, when to rent capacity, and how to structure a team that's economically healthy. Start a conversation through our contact page—we start from your problem, not from a package.
Conclusion
Indonesia's tech talent market is tight, but it's not closed. Companies outside Jakarta can compete if they play with the right strategy: honest JDs, fast processes, relevant assessment, fair compensation, and a culture that genuinely values growth.
Remember the basic pattern: fair salaries attract people in; meaningful work keeps them; and the reputation built from both makes them come on their own. All three layers need to be managed deliberately—not left to run on their own.
If you're building or strengthening a technology team, make hiring and retention a strategic agenda, not an administrative matter. Companies that take this seriously will enjoy an advantage competitors can't copy: a stable team, accumulated knowledge, and consistent development speed. Also read our guide to choosing a software house if you're considering a technology partner to complement your talent strategy.
