Supervised On-Site Development Work — Phase 2 (Weeks 6–12)

Supervised On-Site Development Work — Phase 2 (Weeks 6–12)

Phase 2 is the final and most demanding stretch of your externship. You have already proven you can show up, follow workplace norms, and complete assigned tasks under close supervision. Now the expectation shifts: your employer mentor and program coordinator expect you to work with greater independence, take ownership of a real deliverable, and leave the placement with a portfolio artifact you can show in future interviews.

What Changes in Phase 2

The core rhythm of Phase 2 looks similar to Phase 1 — daily work, logged hours, mentor check-ins — but the nature of your tasks should deepen. In Phase 1 you were oriented and guided step by step. In Phase 2 you are expected to read a ticket, plan an approach, write and test code, get it reviewed, and see it through to deployment or handoff with less hand-holding. That progression is intentional. Professional developers are evaluated not just on whether they can write code but on whether they can carry a task through the full development cycle.

If your employer uses a sprint or issue-tracking workflow — common in teams that follow Agile or Kanban practices — volunteer to own at least one ticket from start to finish. That means writing or refining the acceptance criteria, breaking the work into steps, coding, writing or updating tests, submitting a pull request, responding to review comments, and confirming the feature works in a staging or production environment. Document each phase in your work log on the day it happens.

Leading or Co-Leading a Feature or Bug-Fix

Taking the lead does not require that you work alone. Co-leading with a senior developer or peer is a legitimate and common professional pattern. What matters is that you are an active driver: you schedule the planning conversation, you open the branch, you write the first draft of the code, and you follow up on the review. When you document this in your work log, capture the ticket number or task name, what you planned, what you built, what tests you ran, and who approved the merge or accepted the handoff.

If the employer cannot give you access to a production deployment pipeline for security or policy reasons, a handoff to a senior developer for final deployment still counts — document that clearly.

Mid-Phase-2 Self-Assessment

Around the midpoint of Phase 2 — roughly week 8 or 9 — complete a voluntary self-assessment using the same 100-point employer rubric your mentor uses. Score yourself honestly across all five areas: technical skill, professionalism, teamwork, communication, and initiative. Then identify the two areas where you scored yourself lowest and write down at least one concrete improvement action for each. "Be better at communication" is not a concrete action. "Send a written status update to my mentor every Friday before noon" is.

Share the completed self-assessment with your mentor and schedule a brief one-on-one to discuss it. Mentors in professional settings respond well to self-awareness. Showing that you can evaluate your own work critically and act on the gap is itself a sign of professional maturity — it reflects the same growth mindset you will need throughout your career.

Building Your Portfolio Artifact

Before Phase 2 ends, compile at least one portfolio artifact from your worksite work. This could be a documented code sample (with comments explaining design decisions), a write-up of a problem you debugged and how you solved it, or a link to a tested feature branch. The artifact must be something you can legitimately share with future employers.

Because the work you do on-site belongs to the employer, you must obtain written permission before including any employer code, screenshots, or system descriptions in your portfolio. Use the portfolio artifact release/permission form provided by your program. If the employer cannot release the code itself, a written case-study description of the problem, your approach, and the outcome — without proprietary details — is an acceptable alternative and still demonstrates your thinking to hiring managers.

Professionalism and Workplace Safety

Professionalism remains non-negotiable in Phase 2. Attendance, punctuality, and communication standards do not relax because you are further into the placement. If you must miss a shift, notify your supervisor before the shift starts using whatever channel the employer prefers.

From a safety standpoint, software development worksites carry ergonomic and data-security responsibilities. Continue to follow proper ergonomic setup — monitor height, chair adjustment, wrist position — to prevent repetitive strain injuries over a workday. Follow all employer policies on handling sensitive data, credentials, and access tokens; never store passwords or API keys in plain text in version-controlled files, and never share access credentials with fellow students or family. If you encounter a situation where you are unsure whether an action is authorized — such as deploying to a production server or accessing a customer database — stop and ask your mentor before proceeding. In professional development environments, acting on uncertainty without checking is a serious mistake.

Final Evaluation and Exit Interview

At the close of week 12, your mentor completes the full 100-point employer evaluation rubric covering technical skill, professionalism, teamwork, communication, and initiative. You must score 75 or above overall to satisfy the externship requirement. Your program coordinator will then conduct an exit interview with both you and your mentor present. Come prepared to discuss what you accomplished, what you would do differently, and how the experience connects to your career goals. The exit interview is also a professional opportunity: it is appropriate to thank your mentor formally and to ask whether you may list them as a professional reference.