Let me say the honest part first. My OJT was not a developer OJT. I did not ship a feature. I did not push a single commit. If you came here for a story about an intern who built an app for a big tech company, this is not that post.
But if you’re looking up OJT for IT students because yours is coming and you don’t know what to expect, or because you’re headed somewhere that has nothing to do with coding and you’re worried, stay. Mine had nothing to do with coding either, and I picked it on purpose.
OJT for IT students: what it really looks like
In your head, OJT is you at a desk, writing code beside senior developers. For some people it is. For a lot of us, it’s a government office, a school department, or a small company that needs an extra pair of hands.
That means encoding, filing, fixing the printer because you’re “the IT,” making tarpaulin layouts, and yes, sometimes actual system work if you’re lucky. Especially in the province, where there are more students than tech companies.
Nobody tells you this before deployment, so I’m telling you now. It’s normal, and it doesn’t decide your career.
My OJT experience at SRDI
I did mine at the Sericulture Research and Development Institute, in the Office of the Executive Director. Sericulture is silk farming, in case you’re wondering. Silkworms. I was a BS Information Systems student in a silk research institute.
How many hours is OJT? It depends on your school and your course, so check your own program. My OJT hours were 600, from December 2024 to May 2025, with some Saturdays and overtime. Tuesday to Friday was 8 to 5. Monday was 7 to 4, because government office.
The work was mostly paperwork. Research papers, documents, things that needed a signature. Because I was in the executive director’s office, a lot of it had to travel. A budget paper, for example, had to be signed by the accountant in another department, so I was the one walking it there. I ended up dealing with people from all over the institute.
There were three staff in that office, and I was the fourth. There were times when all three were out and it was just me. So I did the work of the three. I was scanning research papers through lunch, more than once. I was honestly more tired on the days they were gone than on the days they were there.
And it was basic work. Scanning, printing. I’m not into it, to be honest. But I still did it properly, because it was mine to do.
What my OJT taught me
I’ll be honest. Technically, almost nothing. I did not come out of my OJT a better programmer. If I wrote “it sharpened my technical skills” here, I’d be lying to you the same way a narrative report does.
What I learned was people.
- How to communicate at work. Every paper I carried to another department was a conversation with someone I didn’t know. Not classmates, not friends. People with positions, people who were busy. That’s where my communication grew, not my tech side.
- Working with people who aren’t in IT. Different departments, different jobs, different ways of explaining things. Most of the people you’ll build for as a developer don’t speak tech either.
- Being reliable. I have to be honest, I was late sometimes. So I won’t preach about punctuality. But when the office was left to me, the work got done. I know myself. I can’t relax when there’s something I’m supposed to be doing.
Was I disappointed that it wasn’t technical? No. I chose it. I had two options, an IT placement or the Office of the Executive Director, and I picked the higher office because it would look better on my resume. Haha. Not the noblest reason, but I don’t regret it.
If your OJT is not a developer OJT
Then your OJT is not where you become a developer. That’s fine. It just means the technical part is on you.
Everything in my projects page, I built outside of school and outside of OJT. Small apps, one at a time, each one teaching me a thing I didn’t know before. A project is what I presented in the interview that got me hired, not my OJT certificate.
So do your hours properly, learn what the office has to teach you, and keep building at home. The two don’t cancel each other out.
Tips before you start your OJT
- Start looking early. The good slots go fast, and the OJT requirements take longer than you think. The endorsement letter, your resume, and the MOA, which is the memorandum of agreement between your school and the office that takes you in.
- Ask what you’ll actually be doing. Before you say yes. “IT related tasks” can mean anything.
- Fill in your DTR every day. Not at the end of the week, not at the end of the month. Every day.
- Ask questions. Nobody expects an intern to know everything. They do expect you to ask before you guess.
- Offer your IT skills. If you see something done by hand that could be a simple form or a spreadsheet, say so nicely. That’s how a non dev OJT turns into a small dev one.
- Be kind to everyone in the office. They sign your evaluation, and some of them will be your references later.
About the OJT narrative report
You’ll have to write one at the end. Your school will give you its own format, so I won’t pretend to have a template that fits everyone.
What I can give you is the thing that makes it easy. Keep an OJT journal. Three lines a day about what you did, or a short weekly report if daily is too much. Take photos while you work, with permission. Keep every signed paper in one folder. When the report is due, you’re just putting together what you already have instead of trying to remember February in May.
What came after my OJT
I finished my hours and graduated from DMMMSU on May 28, 2025. If you want the full course story, I wrote about my BSIS degree and where it took me.
Then I rested for a month. After that I went back to the very beginning. HTML, CSS, all of it, like I had never seen them before.
I was not consistent, and I won’t pretend I was. A lot of typhoons passed that year. We had no internet for more than a month and no power for more than a week. It’s hard to learn React when you can’t charge your laptop.
The real consistency started in January. You can see it on my GitHub contribution graph, that’s where the green starts. I had a roadmap and a list of sites where I could apply, all written on index cards. The plan was three months. It did not take three months. I got stuck on React for a very long time.
I started applying on March 1. Two weeks in, nothing. That’s when I realized I didn’t have even one strong project. All I had was a weather app. So I built Trackr, a finance tracker, while I kept sending applications.
Rejections came every single day. In almost two months I got three or four interviews.
Then OFFLINE Web Agency. Two interviews. It turned out their main stack is Laravel, and I told them straight that I had never used it. They use Tailwind though, and they said it was okay. The first interview had a Laravel project. In the second one I presented Trackr. I got hired.
I started on May 1, 2026. About a year after I graduated.
So today I’m a frontend developer, fully remote, from La Union, with a team that runs on Thailand time. I went from walking documents between departments to building the pages people actually click on.
And the funny part is that the OJT still shows up in my work. Not in my code. In how I message my manager, how I ask when I’m stuck, how I give an update without being chased for it. I learned the code part on my own. I learned the people part in an office full of silk research.
Take note, this is my experience, not a rulebook. Your OJT might be nothing like mine. Whatever it turns out to be, it’s a few hundred hours. What you do after is the bigger story.
If you want to see what I build now, my projects are here.
