Software Engineering Intern

Week 1: findlucid mission and remote setup

• Study findlucid's mission, memberships (FindLucid Plus and FindLucid Founding Member), and product surface with your mentor.
• Set up your dev environment: Git, Node, your editor, and read access to the findlucid repo.
• Meet your mentor, agree on your 10 to 15 hour weekly schedule, and write your personal learning plan.
• Read the intern handbook, data-handling rules, and code-of-conduct sections that apply to your role.

Week 2: Codebase orientation

• Guided tour of the repo: app router structure, lib/ modules, drizzle schema and migrations.
• Walk through one real pull request end to end with your mentor: the change, the tests, the review comments.
• Learn the review and deploy controls: every change is reviewed, production database changes are off-limits.
• First supervised exercise: set up the app locally and document anything in the setup that confused you.

Week 3: TypeScript and Postgres fundamentals

• Refresher curriculum on TypeScript strictness, async patterns, and SQL fundamentals.
• Study findlucid's drizzle schema: how users, matches, messages, and memberships are modeled.
• Practice exercise: write small SQL queries against a sample dataset and have them reviewed.
• Shadow a bug-triage session: how a bug report becomes a scoped fix.

Week 4: Mobile-first testing and testing culture

• Learn findlucid's mobile-first rule: every visual change is tested at 390 by 844 first.
• Run the existing test suite (unit and migration-order tests) and learn what each suite guards.
• Complete your first guided micro-task: a small documentation fix or typo correction in a practice branch.
• Phase 1 checkpoint review with your mentor and updated learning plan.

Month 2: Guided bug fixes and code-review shadowing

• Fix assigned, scoped defects in a practice branch with your mentor reviewing every change before merge.
• Write tests for each fix and learn why coverage matters around billing and safety code.
• Shadow code reviews: read the founder's review comments on real pull requests and discuss what he was checking.
• Weekly mentor topics: reading unfamiliar code, scoping a fix, writing a useful test.

Month 3: Small supervised features and docs

• Build a small supervised feature in the practice environment, planned and reviewed in pieces.
• Update developer docs for the area you worked in so the next trainee starts easier.
• Present your practice-branch work to your mentor and walk through the design choices.
• First portfolio piece: a write-up of the feature you built, the tests you wrote, and what broke along the way.

Mobile-first component practice (Months 4 to 5)

Design and build a set of small UI components at 390 by 844, studying findlucid's existing patterns and accessibility expectations.

• A small library of practice components with documented states.
• Screenshots at 390 by 844 and a short review write-up.

API and data practice (Months 6 to 8)

Study findlucid's API route patterns, build practice endpoints in a sandbox, and document how rate limiting and audit trails protect members.

• Practice API routes with tests in the practice environment.
• A short explainer on how one real findlucid endpoint handles auth, limits, and logging.

Full-stack practice build (Months 9 to 11)

Plan and build a larger practice project, a small app of your own design, applying everything from phases 1 and 2 with weekly mentor guidance.

• Working practice project with README, tests, and deployment notes.
• Architecture one-pager explaining your data model and route design.

Capstone (month 12)

Month 12: present your full practice build and your year of work to the founder, walk through your architecture and testing decisions, and leave with a documented portfolio and a written skills summary.