IDCamp Alumni Dialogue #5 - Beyond the Code: Soft Skills That Shape Your Tech Career5

Main ideas, concepts, and lessons

1) Soft skills are essential in tech (especially in an AI era)

• Technical “hard skills” (coding, tools, frameworks, architectures) are required as a baseline.
• Soft skills become a key differentiator because:
  • AI can replace or speed up repetitive technical tasks.
  • The gap between junior/middle/senior levels can shrink technically due to AI assistance (code generation, refactoring, testing, etc.).
• What still remains hard to “boost by AI”:
  • Leadership, initiative, responsibility, judgment, problem framing, and deeper decision-making.
  • These show up through how people communicate, coordinate, and take ownership—not only through code quality.

2) Two broad skill categories you must balance

• Hard skills: programming languages, system design/architecture, tooling, frameworks, implementation.
• Soft skills: communication, collaboration, problem solving, networking, professional presence, adaptability, growth mindset, accountability.

3) Professional presence: how to become a “visible developer”

The session emphasizes three components:

A. Proactive communication

• Communicate clearly and in business terms, not only with IT jargon.
• Example concept:
  • When reporting delays to non-technical stakeholders/PMs, explain timeline + impact + progress rather than internal technical causes.
• Proactive behavior:
  • Don’t wait to be asked if you are stuck or blocked.
  • If blocked for ~2 hours, raise your hand and ask a senior.
  • Report status and risks early (possible delays, blockers, timeline changes).
• Reason:
  • PMs manage stakeholder expectations; delays should be communicated immediately to prevent expectation mismatch.

B. Personal branding (especially digital footprints)

• Personal branding = professional digital presence (not “influencer” behavior).
• Goal: when recruiters/search engines find your name, they see your professional track record (not a blank page).
• Suggested actions:
  • Search your full name on Google and review what appears.
  • Use platforms like:
    • LinkedIn for credibility with recruiters/HR
    • GitHub for technical proof and project understanding
    • Writing (articles/posts) to demonstrate understanding
• LinkedIn checklist themes from the talk:
  • Add/optimize a clear headline (what you do + focus/interest).
  • Don’t only set “Open to work”; also share learning, certificates, and projects.
  • Use featured/pinned items (so recruiters can quickly see your best work).
• GitHub checklist themes from the talk:
  • Don’t just store code—include explanations:
    • what the project is
    • techniques used
    • features/demo videos
  • Prioritize clarity and project documentation quality.
• Writing as branding:
  • Use writing as an “understanding test” (e.g., the Finment technique mentioned).
  • Write posts/articles about what you learn and how you interpret concepts.

C. Networking

• Networking is framed as long-term investment.
• Key points:
  • Many jobs are “hidden” and accessed via referrals (not only public portals).
  • Referrals typically speed up response and reduce the low/high uncertainty of applications.
• Practical networking guidance:
  • Maintain good relationships during internships (with supervisors, coworkers).
  • Participate in communities/meetups/talks.
  • Seek mentorship (the talk references “ADPlist” as a mentoring platform).
• Story-based lesson:
  • Opportunities can come unexpectedly through maintained relationships and informal channels (the speaker cites getting a full-time offer after an Instagram DM from a former boss).

4) Grow beyond technical expertise: adaptability + growth mindset

The talk explains that career resilience depends on ongoing learning and adjustment:

A. Adaptability in a fast-changing tech environment

• AI and automation reduce manual coding time in many settings.
• Frameworks and tools become legacy over time; you must be willing to learn new approaches (example: Android moving from XML-based UI toward Jetpack Compose).
• How to adapt:
  • Learn from articles, communities, and industry tools.
  • Use AI tools as assistance (without clinging to one workflow).

B. Growth mindset (problem-solving identity, not tool identity)

• Avoid a “fixed mindset” like:
  • “I only do Java” or “I only work with X framework forever.”
• Instead:
  • Be a problem solver, not a tool specialist.
  • Learn based on the problem requirements, then choose tools accordingly.
• Mental model:
  • Tools/frameworks are “hammers and nails”; the goal is building software and solving user/business needs.

C. Accountability and initiative (especially for mid-to-senior levels)

• Take responsibility for outcomes, not just assigned tasks.
• Proposed practical behavior:
  • Identify outdated/inefficient approaches.
  • Propose improvements to PMs (with estimated budget/timeline impact).
  • Deliver business value and unblock work.
• Included expectation-management technique (underpromise/overdeliver):
  • Underpromise timeline (e.g., estimate completion in 2 days but plan a buffer).
  • Overdeliver by using buffer time for testing/docs or to absorb unexpected issues.
  • Purpose: avoid stakeholder disappointment from overoptimistic deadlines.

5) Continuous learning habits

• Burnout is common after long coding sessions.
• Tips given:
  • Learn in the morning (or at lunchtime) for ~20 minutes; avoid relying on late-night study.
  • Consistency > intensity: small daily learning beats cramming.
• Motivational principle cited:
  • “Every action you take is a vote for the type of person you wish to become” (Atomic Habits concept).
• Action-oriented goal-setting:
  • Set steps, not only lofty goals.
  • The speaker suggests using a participation platform (“coding elite” / decoding.com/elite) to stay active and contribute.

---

Methodologies / frameworks and instruction-like lists (detailed bullets)

A. Professional communication (proactive + stakeholder-aware)

• Convert IT details into business context:
  • Replace heavy jargon with user/business impact.
  • Structure updates around: timeline + impact + status/progress.
• Practice proactive escalation:
  • Explore independently first.
  • If stuck ~2 hours, ask a senior.
  • Update PM/product on risks early (possible delays/blockers).
• Maintain trust with accurate reporting:
  • Don’t wait until asked; communicate changes immediately so PM can manage stakeholder expectations.

B. Personal branding execution (practical checklist)

• Audit your discoverability:
  • Google your full name; evaluate whether results reflect your professional story.
• Optimize LinkedIn:
  • Add a strong headline (role + focus area).
  • Don’t only post “Open to work”; also share learning and proof (certs, projects).
  • Pin/feature key achievements or posts so recruiters see them first.
• Optimize GitHub:
  • Provide explanations for each project (purpose, techniques, features).
  • Avoid “empty repos” with no narrative or demo content.
  • Include demo videos where possible.
• Use writing to demonstrate understanding:
  • Publish posts/articles that reflect what you learned and how you explain it.

C. Networking strategy

• Treat networking as long-term:
  • Maintain relationships with interns/seniors/supervisors after internships.
• Participate actively:
  • Join communities (IDC/oding communities mentioned), attend meetups/offline events.
  • Engage via talks, discussions, and mentorship.
• Use mentorship intentionally:
  • Seek mentors via platforms (example mentioned: ADPlist).

D. AI vs soft skills: what to delegate vs keep

• Delegate to AI:
  • Repetitive, time-consuming technical tasks (e.g., parts of testing described as tiring/repetitive).
• Keep and develop yourself:
  • Architectural thinking (choose architecture, understand trade-offs).
  • Problem-solving and empathy (understand user needs and propose improvements).
• Don’t “AI-build from scratch” blindly:
  • You still decide requirements/architecture and reason about trade-offs; AI supports execution.

E. Underpromise & overdeliver (expectation management)

• Estimate realistically with a buffer:
  • Example: expect completion in 2 days, but communicate 2 days (or planned conservative date) and keep time for testing/docs.
• Purpose of buffer:
  • Absorb unexpected bugs/complexity.
  • Use remaining time for QA and documentation.
• Avoid oversimplified promises:
  • Don’t promise “tomorrow” if hidden complexity exists.

F. Continuous learning habit plan (simple routine)

• Daily or near-daily short sessions:
  • Prefer ~20 minutes in the morning or at lunchtime.
• Consistency over cramming:
  • Avoid “pile it up” studying that causes burnout and rapid forgetting.
• Tie learning to contributions:
  • Register/participate in “elite contribution portal” and use it to practice communication and sharing.

---

Q&A takeaways (what answers focused on)

• Getting client trust while in college:
  • Build proof: portfolio and evidence of similar work.
  • If code can’t be shared, show results via documentation/demo screenshots/videos.
  • Use MVP (minimum viable product) to visualize and reduce client uncertainty.
• Which skills AI replaces vs not replaceable:
  • AI can handle repetitive work; keep architectural thinking, problem-solving, trade-offs, and empathy.
• Personal branding priority (LinkedIn vs GitHub vs social media):
  • Entry point suggestion: optimize LinkedIn first (HR sees it first).
  • Use GitHub for deeper technical validation; social media is “bonus.”
  • If you have little portfolio, start with LinkedIn; if you have many projects, GitHub becomes stronger.
• Balancing AI/tech learning with soft skills practice:
  • For students/juniors: prioritize hard skills first (soft skills are developed via experience).
  • Soft skills can’t always be “learned in isolation”—prepare mentally so you can seize opportunities (speaking, leadership roles) when they appear.

---

Giveaway process (instructions described)

• Participants fill out a form displayed on screen.
• The form contains 3 quiz questions.
• Winners are selected from participants who score 100.
• Selection is handled randomly/objectively using AI from the qualified answers.
• Winners are contacted within up to 14 working days via the decoding team through email/WhatsApp.

---

Speakers / sources featured

Speakers / hosts

• Adelia Larastrihastuti (Adel) — Associate Program Manager at Decoding Indonesia; host/facilitator
• Adityya Wana (Adit / Wana) — Software engineer at Shopee; IDCAM alumni (2019); main resource person

Sources referenced

• World Economic Forum (WEF) — report noting technical skills becoming easier to replace by AI by 2025
• Atomic Habits (James Clear) — concept/quote about actions reflecting the type of person you become
• Kang Eko Kurniawan Kanedi (“modern programmer” YouTube channel) — mentioned as an example of a company emphasizing AI usage
• ADPlist — mentioned as a platform to find mentors
• decoding.com/elite (Decoding Elite / contribution portal) — mentioned as a place to practice contributions/communication
• LinkedIn / GitHub / Google Search — mentioned as branding and discoverability tools
• Coding/Decoding community channels (WA/Telegram/communities) — mentioned generally as networking spaces