Skip to main content

Career Goals

Long-term aspirations

Near term, I want a software engineering internship or new-grad role where I ship production features, learn from strong code review, and grow on teams that care about reliability and measurable user impact. Long term, I want to lead software that thousands rely on—balancing observability, performance, and UX—while still writing code and mentoring others.

Timeline & milestones

2026 – Dec 2027

Finish strong at Georgia Tech

Complete the B.S. in Computer Engineering while scaling GT Web Dev’s platform and deepening the VIP data-science contribution—using both as proof points for recruiting and technical depth.

2027 – 2028

Launch post-grad career

Convert internship and project experience into a full-time software role (full-stack or backend-leaning), with clear ownership of features, on-call or reliability practices where applicable, and a habit of shipping with metrics.

2028 – 2032

Specialize with impact

Go deeper in a chosen lane—likely distributed systems, data platforms, or developer tooling—with security, performance tuning, and cross-team design work as regular responsibilities.

2032+

Lead without leaving the keyboard

Grow toward staff or lead scope: technical direction, mentorship, and tying engineering decisions to customer and business outcomes.

Concrete next steps

These are the repeatable actions I am taking now to bridge today's portfolio to the milestones above:

  1. Keep Plot Armor, SpendWise, and HarmonyAPI READMEs and demos recruiter-ready—with clear architecture diagrams, metrics, and honest limitations.
  2. Maintain a disciplined interview loop: LeetCode-style practice, systems design stories grounded in Next.js/Django, PostgreSQL, and VIP pipelines, and behavioral examples from GT Web Dev leadership.
  3. Publish at least two technical write-ups per year (architecture notes, retro, or open-source docs) to sharpen communication.
  4. Grow network through GT clubs, alumni, and target companies’ engineer communities; ask for feedback on resume and project pitches early.
  5. Track quantifiable outcomes for each major role and project (latency improvements, engagement %, dataset sizes, uptime) so interviews stay concrete.