top of page

What It Took to Move from Junior Architect to Project Lead in Clark

  • Writer: Anne Robles
    Anne Robles
  • 2 days ago
  • 5 min read
Man in plaid shirt focused on drafting blueprints at a desk, surrounded by papers and a calculator. Office setting with a plant in the background.

I started my career in Clark Freeport Zone while exploring architecture jobs in Pampanga, not really knowing what to expect from the industry. As a junior architect, I thought good drawings were enough. Fresh out of school, I believed that if a design looked right, everything else would follow. That idea did not last long.


My first months were spent doing the usual work. Drafting plans, updating details, and helping senior architects meet deadlines. I worked daily on AutoCAD and SketchUp, focusing on accuracy and speed. At that stage, I was more concerned about clean drawings and presentation quality than how things would actually be built.


It did not take long to realize that drawings are not just drawings. They are instructions. A missing note, an unclear section, or a wrong dimension can affect cost, delay construction, or create confusion on-site. That was my first real lesson, and it came from small mistakes that had real consequences.


Learning the Hard Way on Site

The biggest shift in my mindset happened when I was assigned to support a project on-site. It was a commercial development within Clark, and it was the first time I saw how drawings translated into actual construction.


Things were not as clean as they looked on paper.


Contractors questioned details that seemed obvious in the office. Some dimensions did not match site conditions. There were clashes between structural and MEP systems that were not visible in 2D drawings. At first, I found it frustrating. I thought the problem was execution.


Later, I realized the problem often started in the drawings.

Being on-site forced me to slow down and pay attention to how things were built step by step. I started to understand sequencing, tolerances, and material limitations. I also had to learn how to communicate clearly with different people. Engineers focused on performance, contractors focused on buildability, and clients focused on cost and deadlines.


That experience changed how I approached every drawing after that. I stopped drawing just to complete a task. I started drawing with construction in mind.


Moving from Tasks to Responsibility


Man in glasses sketches with pencil, holding a coffee cup. He's in a workshop with wood models and a metal ladder in the background.

After a couple of years, my role began to shift. I was no longer just following redlines or completing assigned sheets. I was expected to think through problems and make decisions.

I started handling client coordination, explaining design changes, and adjusting plans based on budget constraints. I also worked closely with engineers to resolve conflicts before they reached the site. This was also when I transitioned into using Revit.


Learning BIM was not just about using a new tool. It changed how I understood projects. Instead of working in separate drawings, everything became part of a single coordinated model. It became easier to detect clashes, visualize spaces, and explain design intent to both clients and contractors.


Projects in Clark Freeport Zone exposed me to a range of developments. Office buildings, hotels, and mixed-use spaces were common. Many of these projects followed stricter standards, sometimes aligned with systems like Leadership in Energy and Environmental Design. This added another layer of responsibility, especially in terms of material selection, energy performance, and long-term efficiency. Roles like these are often considered among the in demand jobs in the Philippines, especially in growing hubs like Clark.


At this stage, I began to see that architecture is not just about design. It is about balancing design with cost, time, and constructability. Every decision had trade-offs, and part of my job was to manage those trade-offs carefully.


Stepping into a Leadership Role

Becoming a project lead did not happen suddenly. It was a gradual shift based on trust and consistency.


At first, I was asked to handle small packages within a project. Then I was given a small team. Eventually, I was trusted to manage entire projects from design development to construction.


Two construction workers in orange vests and helmets examine blueprints against a backdrop of tall buildings under a clear blue sky.

As a project lead, my responsibilities expanded beyond design. I had to manage timelines, coordinate with consultants, and make sure deliverables were completed on schedule. I also had to keep the client informed and handle concerns before they became bigger problems. At the same time, I became more aware of the growing number of job vacancies in Clark, which reflected how fast the area was developing.


Leading a team was another challenge. Junior architects needed guidance, but they also needed space to learn. I had to balance reviewing their work with letting them solve problems on their own. I saw a lot of my younger self in them, especially in the way they focused heavily on drawings without fully understanding construction.


One thing I learned quickly is that leadership is not about control. It is about clarity. When the team understands the goal, the process becomes smoother. When expectations are unclear, even simple tasks become difficult.


Mistakes still happen, even at this level. The difference is that you are now responsible for resolving them quickly and making sure they do not affect the overall project.


What Actually Helped Me Grow

Looking back, a few things made a real difference in my growth.

Site experience helped more than anything else. It connected theory to reality and exposed gaps in my understanding.


Clear communication saved time and prevented mistakes. This applied to everyone involved in the project, from clients to contractors.


Learning tools like BIM was important, but only because it improved coordination. Software alone does not make someone a better architect. How you use it does.


Taking responsibility early also played a big role. There were times I was not fully prepared, but stepping into those situations forced me to learn faster.


Consistency mattered as well. Delivering work on time, being reliable, and following through on commitments built trust over time. Opportunities also tend to follow environments with active job hiring in Pampanga, especially in areas with continuous development like Clark.


Where I Am Now

Today, I am still working in Clark Freeport Zone, handling projects from early design stages up to construction. The pressure is higher now, but the work is more meaningful.


I am more involved in decision-making, not just in design but in how projects are executed. I spend less time drafting and more time coordinating, reviewing, and solving problems. The challenges are different, but the goal remains the same. Make sure what is designed can actually be built, within the given time and budget.


If there is one thing I would tell junior architects, it is this. Do not stay comfortable doing repetitive tasks. Get involved in coordination meetings, visit the site, and ask questions. The more you understand the full process, the faster you grow.


This field does not reward perfection at the start. It rewards those who are willing to learn, adjust, and take responsibility.


 
 
 

Comments


bottom of page