Career Development Guidance

First, thank you for sharing all of that. I genuinely respect the level of thought you’ve put into your future. Many people stay stuck because they never slow down long enough to build a real plan. You are clearly not doing that.

You’re 32, you have a family, you’re finishing your Associate’s degree, and you’re thinking strategically about building a real career. That already tells me a lot about your maturity and readiness.

1. How important is a bachelor’s degree?

A bachelor’s degree can help, especially for larger companies or government roles, but it is not the only path into the field. What matters most for entry-level development roles is proof of skill. If you can demonstrate competence through a strong capstone project, a portfolio, and the ability to discuss your code confidently, you can absolutely enter the field without immediately pursuing a bachelor’s degree. You can always complete one later once you’re employed, and some companies will even help pay for it.

2. Does this seem like a good path forward?

Yes. Your plan shows intentional growth. You are not just trying to “get a job in tech.” You are trying to build something meaningful, learn deeply, and position yourself thoughtfully. That mindset matters. Building something you personally need is one of the best ways to stay motivated and produce something authentic for your portfolio.

3. Insight on the stack (Expo, Supabase, TypeScript, VS Code)

This is a modern and relevant stack. TypeScript is widely used and very marketable. Supabase introduces you to backend concepts and databases. Expo gives you exposure to mobile-style development.

My only caution would be to make sure you understand the fundamentals underneath the tools. Frameworks change. Core programming concepts do not. Make sure you understand data structures, logic, state, APIs, and version control as you build.

4. Will this help you begin work sooner rather than later?

If you execute consistently, yes. The key factor will not be the stack — it will be consistency. Over the next 6–12 months, focus on:

• Finishing your Associate’s degree
• Building and completing your capstone
• Learning Git and version control
• Deploying your application publicly
• Practicing how to explain your architecture decisions clearly

Doing these things will place you in a strong position to apply for junior roles, internships, or contract work.

5. Additional recommendations

• Build one smaller full-stack project from scratch.
• Contribute to an open-source repository, even in a small way.
• Practice technical interviews (basic algorithms and problem solving).
• Learn how to read documentation independently.
• Become comfortable debugging without relying entirely on AI tools.

Remote work is possible, but it is competitive at entry level. Be open to hybrid or local opportunities if necessary to gain experience.

6. Preparing for the competition

Treat it as a learning experience, not a performance test. Focus on:

• Working well in a team
• Communicating clearly
• Building something functional, even if simple
• Managing time effectively

The biggest thing to guard against is losing momentum. Consistent, disciplined effort over the next year will change your life more than any single decision about stack or degree.

You are not behind. You are at a pivot point. If you commit now and follow through, this is absolutely achievable.