OpenEvenings and weekends, paced around a college calendar
Working sessions and reviews of what you built
Who it is for
Students and early professionals, including people who have been told their college will decide their pay. You need time in the evenings and a willingness to explain your own build.
What you build
- A sales path with records, owners, and a required field that can fail
- An approval flow with a real rejection, not only a happy path
- A screen for the next action, plus a short note a teammate could follow
Modules
01
The org as a workplace
Objects, records, and a path a person would actually click. We name the job before we name the feature.
02
Rules that protect the record
Validation and security that stop a blank or a stranger from moving a deal forward.
03
A flow for the handoff
When a field is missing, the flow asks. When someone rejects the step, the record says so.
04
A screen you can defend
Lightning web components, or a guided UI, for the next action. If a classmate cannot use it, it is not done.
05
Apex where clicks stop
Server-side work only for the part a flow should not fake. You can point at the line and say why it exists.
What changes for you
- You can demo the org without reading from a script
- You can say what you would change if the team sold differently
- You have work to show. We do not attach a salary or a placement rate to that