Contact us

Feeling Underqualified? How to Fake Confidence (Safely)

by Arif Ikhsanudin, Backend Developer

Everyone feels underqualified sometimes, especially early in their career.
Here’s how to appear confident without pretending to be an expert you’re not.

Own What You Do Know

Feeling underqualified doesn’t mean you know nothing:

  • List your skills and experiences honestly.
  • Speak clearly about what you can contribute.
  • Avoid overexplaining; simple clarity shows competence.

Confidence comes from knowing your strengths, not faking mastery of everything.

Prepare for the Unknown

Nobody expects you to know everything:

  • Anticipate questions or scenarios and prepare answers.
  • Have resources ready to back up your claims.
  • Practice framing “I don’t know, but I can find out” as a strength.

Being ready to learn on the spot is more impressive than pretending to know it all.

Use Body Language Wisely

Non-verbal cues sell confidence quickly:

  • Stand or sit upright; avoid fidgeting.
  • Make eye contact without staring.
  • Speak at a calm, steady pace—pauses are okay.

Your posture and tone can convince others you’re competent before words even start.

Leverage Questions as Power

Asking smart questions shows thoughtfulness:

  • Clarify requirements instead of guessing.
  • Ask for context or examples when unsure.
  • Turn questions into opportunities to contribute ideas.

Questions framed strategically make you look engaged, not inexperienced.

Fake Confidence, But Learn Fast

Temporary confidence is fine, but skills must catch up:

  • Identify knowledge gaps immediately after meetings.
  • Spend focused time closing gaps—books, tutorials, or mentors.
  • Repeat until you can speak as confidently about those areas as you initially faked.

Safe “faking” is really just confidence with a plan to learn.

Closing Thought

Feeling underqualified is normal; hiding it doesn’t have to be.
Fake confidence safely by owning your strengths, asking smart questions, and learning fast.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Say Hej

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

What It Actually Costs to Hire a Senior Backend Developer in Sydney

You budgeted $160K for a senior backend hire. Then you saw what they actually cost once super, recruiter fees, and three months of low output were factored in.

Read more

How to Deliver Bad News to a Client Without Losing Their Trust

Every engagement has at least one difficult conversation. The contractors who handle those conversations well end up with stronger client relationships, not weaker ones.

Read more

Charging What You Are Worth Is Hard Until You Understand What You Are Actually Selling

Contractors who struggle to charge high rates are usually selling the wrong thing. The shift from selling time to selling outcomes changes everything about the pricing conversation.

Read more

Jenkins Still Works. But Ask Yourself Why You Are Still Using It.

Jenkins is capable, battle-tested, and widely understood. It is also operationally expensive, slow to configure, and increasingly mismatched to how teams want to work. The question is not whether Jenkins can do the job — it's whether it's the right tool for your context.

Read more