1 of 39

Skills to Bills: A Users Guide to Demonstrated Competency

Orlando Code Camp 2025

Nerando Johnson // @Nerajno

2 of 39

Sponsors

3 of 39

Code of Conduct

https://www.orlandocodecamp.com/codeofconduct/

4 of 39

Hello!

I am Nerando

I am here because I because long ago I lost a bet someone took time to talk to me .

Handle: @Nerajno [ 🦋 ]

Title: Junior~ish Software Developer

5 of 39

I Build things and Speak at places.

Community builder, Web/software Developer, mentor~ish

6 of 39

Disclaimer

7 of 39

What We are about to cover : Demonstrated Competence

  • Build It
  • Speak to It
  • Share It
  • Emotional Wherewithal

8 of 39

Skills Alone Don't Pay Bills

8

9 of 39

How Do We Fix This ?

10 of 39

“Tech is a tool, figure out how to make money and then see which tech tool is the best fit - Vibhas Zanpure”

(Software Development Manager at Amazon)

11 of 39

Create Solutions

12 of 39

People buy solutions to

their problems

  • Saves time.
  • Saves or increases revenue.
  • Makes it easier use their product or service.

13 of 39

Saving Time

=

More Money

14 of 39

Proposed Solutions : Time Saving Products

  • Problem: Time scarcity in business environments.
  • Solution Approach: Creating tools/products that save significant time.
  • Key Point: Connecting your created technical solution to business efficiency.

15 of 39

New/ Better

Products

=

More Money

16 of 39

Proposed Solution - Revenue Impact

  • Problem: Business need for revenue growth or cost reduction.
  • Solution Approach: Building products with clear financial impact.
  • Key Point: Quantifying the value of your technical solutions.

17 of 39

Ease of Use

=

More Money

18 of 39

Proposed Solution - User Experience

  • Problem: Friction in user workflows.
  • Solution Approach: Creating products that simplify processes.
  • Key Point: Demonstrating empathy for users through your technical choices.

19 of 39

Check In

20 of 39

Imposter Syndrome

Do I know it ?

Can I build it ?�Can I sell it ?

21 of 39

Imposter Syndrome

A psychological phenomenon of feeling like a fraud, even when there’s clear evidence of your competence.

22 of 39

How Do We Make $

23 of 39

24 of 39

25 of 39

  • 3 Projects @ MVP status
  • Live - Hosted
  • Documented
  • Incorporates Tests

26 of 39

The Developer Portfolio

An Evidence-Based Framework for Success

Create Polished Artifacts

  • Build small, impactful pieces showcasing your abilities (code snippets, detailed write-ups, small apps).
  • Focus on quality over quantity to demonstrate your skills.

26

27 of 39

The Developer Portfolio

An Evidence-Based Framework for Success

Explain Your Decisions

- Document your work through blogs, videos, or LinkedIn posts.

- Share your reasoning behind design choices, technology selections, and other decisions.

27

28 of 39

The Developer Portfolio

An Evidence-Based Framework for Success

Showcase Your Learning Journey

- Transform your learning process into shareable content.

- Demonstrate not just technical skills but also communication, collaboration, and learning abilities.

28

29 of 39

Portfolio

Build vs Clone + Modify

30 of 39

Storytelling - Self Advocacy

  • Lightning Talk
  • Meetup Talk
  • Conference Talks
  • Video Talks

31 of 39

Storytelling - Writing

  • Small Blogs ~ Descriptions
  • Long Blog Code and Descriptions
  • Series Blogs

32 of 39

Let’s Wrap This Up

33 of 39

Summary

Why Technical Skills Aren't Enough:

  • Technical expertise without articulation limits visibility and impact.
  • Scattered projects fail to tell a coherent story.
  • Imposter syndrome undermines deserved recognition.

33

34 of 39

Summary

The Three Pillars of Demonstrated Competency:

  • BUILD IT: Create 3 quality projects (MVP functionality, testing, live hosting, documentation).
  • SPEAK TO IT: Frame solutions in business terms (time saved, money impact, user experience).
  • SHARE IT: Engage with communities to amplify your knowledge and reputation.

34

35 of 39

Summary

Showcase Your Technical Journey:

  • BUILD IT: Create 3 quality projects (MVP functionality, testing, live hosting, documentation).
  • SPEAK TO IT: Frame solutions in business terms (time saved, money impact, user experience).
  • SHARE IT: Engage with communities to amplify your knowledge and reputation.

35

36 of 39

Summary

Overcome Imposter Syndrome :

  • Document achievements and seek objective feedback.
  • Recognize cognitive distortions and embrace growth mindset.
  • Remember: Its presence often indicates high standards, not incompetence.

36

37 of 39

Additional Resources

37

Yes, its a link

38 of 39

Want big impact?

Use big image.

38

Key Takeaway:

Your code might speak for itself, but you need to speak for it too.

39 of 39

Questions

39