Civil Engineer Interview Questions

"I grew up watching a flyover go up near my home, and I was hooked by how many people it took to get one span right. In college I leaned toward structures and did my final-year project on a small two-storey building, from load calculations to the footing design. My internship was with a building contractor, where I spent most days checking reinforcement and keeping the pour records. That showed me I like being close to the work, where a drawing turns into something real. Next I want a site engineer role on building or infrastructure projects, where I can own a section of the work, learn from senior engineers and get better at planning and quality, not just supervising."

"Right now I want to be on site. I learn fastest when I can see the result of a decision the same day, like a level that is off or a bar spacing that does not match the drawing. I'd like to move toward design later, but I think a few years of execution will make me a better designer, because I'll know what is hard to build. From what I read, you're running mid-rise residential and a couple of commercial buildings, so the work is concrete frames, foundations and finishing, which is exactly the range I want to learn properly. I'd rather go deep on buildings first than jump between very different project types."

"The biggest one was an eight-storey residential block with a basement and a raft foundation. I joined at excavation and stayed until the roof slab. I was one of two site engineers, and I owned the structure from the plinth up for one of the two towers. That meant checking reinforcement against the drawings and bar bending schedules, planning pours with the foreman, keeping cube records and preparing the weekly quantities for billing. I had two supervisors and the formwork and steel gangs working with me, and I reported to the project manager. The part I'm proudest of is cutting our floor cycle by a few days by planning formwork reuse between the towers, without skipping any striking times."

"The grade is the characteristic compressive strength of the concrete at 28 days, in megapascals or newtons per square millimetre. Characteristic means only about one result in twenty is expected to fall below it. Some codes test cubes and some test cylinders, and a cylinder gives a lower number for the same concrete, so you always read the grade with the code in mind. To choose one, I'd start with what the structural design needs, then check the exposure condition. A foundation in wet, aggressive soil or a structure near the sea needs a higher minimum grade, a lower water-cement ratio and more cover than an interior slab, because durability decides it as much as strength does."

"A nominal mix is a fixed recipe, like one part cement, two parts sand and four parts coarse aggregate by volume, with water added to suit. It's quick and fine for small or non-structural work like blinding, but it ignores the actual sand and aggregate, so you use extra cement to be safe and still get more variable concrete. A design mix is worked out for the job. You start from the grade and add a margin for how variable the production is, which gives the target mean strength. Then you choose the water-cement ratio for that strength and the exposure, the water content for the workability you need, and the proportions from tests on the real materials. Trial batches confirm it before use. It's batched by weight and far more consistent, which is why most codes allow nominal mixes only for the lower grades."

"Cement needs only a limited amount of water to hydrate. Anything extra is there just to make the concrete workable, and when it dries out it leaves a network of tiny pores. So as the water-cement ratio goes up, strength goes down, the concrete becomes more permeable, water and chlorides reach the steel more easily, and drying shrinkage and cracking increase. That's why codes cap the ratio for each exposure condition. When a crew adds water on site because the mix is stiff, they are quietly lowering the grade we paid for. If workability is a real problem, the fix is an approved plasticiser or superplasticiser, or asking the plant to adjust the mix. On my sites, a truck that has been watered without approval gets rejected."

"Curing means keeping the concrete moist and at a reasonable temperature after it's placed, so the cement keeps reacting and the concrete gains strength. If it dries out early, the surface stays weak and dusty, the strength falls short, and you get more shrinkage cracks. On slabs I like ponding with small bunds or wet hessian kept wet all day. On columns and walls ponding doesn't work, so we wrap them in wet hessian or plastic, or spray a curing compound when water is hard to manage. For ordinary Portland cement a common minimum is seven days, and longer for blended cements or in hot, dry, windy weather, but I follow the project spec. The hardest part is not the method, it's making sure someone actually does it on day five."

"I look at when they appeared, what they look like, and whether they're moving. Fine random cracks on a slab within hours of the pour are usually plastic shrinkage, from the surface drying too fast in sun or wind. Cracks that follow the line of the top bars in the first hours are plastic settlement. Cracks that show up days or weeks later on a long restrained wall or slab are usually early thermal contraction or drying shrinkage. In a beam, vertical cracks at the bottom around mid-span are flexural, and diagonal cracks near the supports are shear, which worries me more. Cracks along a bar with rust staining mean corrosion. I measure the width, fix a monitor to see if it grows, and check the history. Anything structural or growing goes to the designer before we decide how to repair it."

"First I read the delivery ticket: right grade and mix, right quantity, and the batching time, because concrete that has been sitting too long in the drum can't be accepted. Then I do a slump test, or a flow test for self-compacting mixes, and compare it with the spec. I also look at the mix itself for segregation or a watery look. Then we cast test cubes or cylinders at the frequency the spec asks for, mark them with the date and the exact pour location, and cure them properly. The 7-day results give an early warning, and acceptance is on the 28-day results under the code's rules. Cubes tell you the concrete that arrived was good. They don't prove it was placed, compacted and cured well, so I still watch the pour itself."

"First I stop anyone from plastering over it. I photograph it, mark the area and chip out the loose material to see how deep it goes and whether the bars are exposed. If it's shallow and small, the usual fix is to cut back to sound concrete, clean and wet the surface, and fill with an approved polymer-modified repair mortar, then cure it. If it's deep, runs through the core, or covers a large part of the base of a column that carries a lot of load, I report it to the designer, who may ask for ultrasonic testing or cores and decide between grouting, jacketing or in the worst case breaking out and recasting. Then I find the cause. Near the base it's often a grout leak at the kicker or concrete dropped from too high, so I'd fix the formwork joint and use a tremie or a pour window next time."

"I wouldn't panic or hide it. I'd tell my manager and the designer straight away. Then I'd check whether the result is real. Were the cubes from that pour, marked correctly, cured in water, and tested on a calibrated machine? Does the set actually fail under the code's acceptance rules, or is it one low cube? If it truly fails, I'd do a rebound hammer and ultrasonic survey across the slab to see whether the weak concrete is local, then take cores at the worst and a few typical spots. Core results have their own acceptance rules in the code. The designer then rechecks the slab with the real strength. Often it's still adequate. If not, the options are a load test, strengthening, or removal as a last resort. Meanwhile I'd hold loading on it and look at the supplier's batch records."

"I understand the pressure, because formwork is a big part of the floor cycle. But a young slab hasn't reached its strength yet, and with the floor above being built, it carries more load than it will for years. Striking the soffit props early is how slabs sag, crack or worse. So I'd say we stick to the minimum times in the spec, or if we want to go faster, we cast extra cubes cured beside the slab and strike only when they show the strength the designer agrees to. Then I'd offer ways to speed up that don't gamble: side forms and beam sides can come off much earlier than soffit props, we can back-prop and reuse the panels, hire a second set, or ask the plant about a mix that gains strength faster."

"I take the latest structural drawing and the bar bending schedule and go bay by bay. I check bar diameter, number, spacing and which layer runs in which direction. Then cover: cover blocks of the right thickness under the bottom mesh, and chairs strong enough to hold the top steel at its level, because top bars that get stepped down lose their lever arm. I look at laps, that they're long enough and not all at the same section, extra bars around openings, and anchorage into beams. The steel should be free of loose rust, oil or mud. Finally I check the formwork is tight and propped, and that sleeves and electrical conduits are in and not sitting on the bottom cover. Only then do I sign the pour card."

"For a slab supported on all four sides, I divide the longer span by the shorter span. If that ratio is more than 2, the slab behaves as one-way, because almost all the load travels across the short direction. If it's 2 or less, it's two-way, and it bends in both directions. That decides the steel. In a one-way slab the main bars run along the short span, and the bars in the long direction are distribution steel, which spreads load and controls shrinkage and temperature cracks. In a two-way slab both directions carry main steel, with the short-span bars usually placed in the outer layer because they carry more moment. A slab supported on only two opposite sides is one-way whatever the ratio."

"In a simply supported beam under gravity load, the beam sags, so the bottom is in tension and the top in compression. Concrete is weak in tension, so the main bars go at the bottom, with the most needed around mid-span where the moment is largest. Shear is highest near the supports, so that's where the stirrups are closest together, and they open out toward the middle. A cantilever is the opposite. It hogs, so the tension is on top and the main bars go at the top, and they must run well back into the support or the back span so they're properly anchored. The classic site mistake is someone placing a cantilever's main steel at the bottom out of habit. I always check cantilevers twice for that reason."

"I'd ask for boreholes spread over the footprint, deep enough to go below the zone the foundations will stress. In each one the standard penetration test gives N-values, which show how dense a sand is or how stiff a clay is, and the log shows the layers and the groundwater level. From samples, the lab does grain size and Atterberg limits to classify the soil and flag swelling clays, moisture content, shear strength tests for bearing capacity, and consolidation tests on clay to estimate settlement. A plate load test on site gives a direct check of bearing at a given level. I'd also want the soil and groundwater tested for sulphates and chlorides, because they decide the cement type and cover. Together those give a safe bearing pressure and an expected settlement."

"I start with the column loads and the soil report: safe bearing capacity, how much total and differential settlement the structure can take, how deep the good layer is, and where the water table sits. If a firm layer is near the surface and loads are moderate, isolated footings are the cheapest, and I'd use combined footings where two columns are close or one sits on a boundary. If the footings start covering more than about half the plan area, or the soil is soft and uneven so differential settlement is the worry, a raft is usually better, and it suits basements too. If the good stratum is deep, the loads are heavy, or the top soil is soft, swelling or liable to scour, I go to piles and carry the load down. Cost and construction access then decide between the options that work."

"I set up the level between the benchmark and where I'm going, and take a backsight on the benchmark. Its known reduced level plus that reading gives the height of the instrument. Any foresight after that, subtracted from the height of instrument, gives the reduced level of that point. If the site is far, I use change points: take a foresight on a firm point, move the instrument, and backsight the same point. I keep the book neatly and do the arithmetic check, where the sum of backsights minus the sum of foresights equals the last level minus the first. Most importantly, I don't stop at the site. I close the line back on the benchmark or another known one, and if the misclosure is outside the allowed limit, I redo it before anyone uses those levels."

"First the boring but vital part: the title block, the revision letter or number, and whether it's marked for construction, because building from a superseded revision is one of the most common and expensive site mistakes. Then I read the general notes, since they hold the grade of concrete, cover, lap rules and anything that applies everywhere. After that I get the grid lines and levels in my head from the plans, and go to sections and details for the parts I'll build first. The step many people skip is putting the structural drawing next to the architectural and services drawings. Beam depths against ceiling heights, column positions against walls, sleeves for pipes. Anything that doesn't match, I list and send as a query before work begins, not on pour day."

"I wouldn't let anyone choose one drawing and carry on. Moving a beam to fit a window is a structural decision, and cutting a window through a beam is worse. First I'd confirm both are the latest revisions, because sometimes one has already been updated. Then I'd send a written query to the design team, with both drawings marked up and the grid reference, saying which work is held and by when we need an answer. I'd call as well so it doesn't sit in an inbox. Meanwhile I'd re-sequence the crew to other bays so we don't lose the day, and hold only the affected area. When the answer comes, I want it as a revised drawing or a signed instruction, not just a phone call, and I'd log the delay."

"I work member type by member type, footings, columns, beams, slabs, using the dimensions on the drawings and the method of measurement the contract follows. Concrete goes in cubic metres. For example, a footing two metres by two metres and half a metre deep is two cubic metres. I'm careful at junctions so the beam and slab aren't both counted in the same volume. Steel comes from the bar bending schedule, lengths times unit weight, and a quick way to get the weight per metre is the diameter in millimetres squared over 162, in kilograms. Formwork is the contact area in square metres. I keep it all in a sheet with references to drawing and grid, then sanity-check against steel per cubic metre of concrete for similar jobs. If a number looks odd, I recheck that member."

"I break the job into activities I can measure, like excavation, footings, each floor's columns, slab and so on, and get durations from the quantities and what a crew really achieves per day. Then I link them by logic, for example the slab can't start until the columns below are cast, and put it into scheduling software as a network. The critical path is the longest chain of linked activities, and it sets the finish date. Anything on it has zero float, so a day lost there is a day lost at the end. Float is the slack an activity has before it hurts the finish. In practice, if we're behind, I don't add people everywhere. I look at the critical activities and either add resources to them, which is crashing, or overlap them where it's safe, which is fast-tracking. Then I update the schedule every week."

"On a school building I was checking the subcontractor's monthly bill for the frame, and the concrete for the first-floor slab looked high against my own take-off. I went through their sheet line by line. They'd measured the slab over the full floor area and then the beams to full depth as well, so the part of each beam inside the slab was counted twice, and they hadn't deducted the stair opening. It was only a few cubic metres, but over six floors that adds up. I didn't accuse anyone. I sat with their quantity surveyor, put both sheets side by side with drawing and grid references, and we agreed the corrected figure. After that we started a shared measurement sheet at the start of each floor, so both sides worked from the same numbers and the bills went through much faster."

"On a six-storey building we lost about three weeks in a long spell of heavy rain at the foundation stage. I went back to the schedule and saw the frame was critical but finishing had some float. So we added a second formwork set so one floor's slab could be prepared while the one below was curing, brought the steel fabrication for the next floor forward so it was ready before the slab was, and moved to two shifts for reinforcement fixing. What I refused to do was strip props early or cut curing, because that just moves the problem into the structure. We recovered about two of the three weeks by the roof slab. I reported the recovery plan to the client in writing, with the remaining delay, rather than promising the full date and missing it."

"On a residential job, groundwater kept filling our footing excavations overnight, and the pour for a row of footings was due in two days. The pumps were clearing it in the morning, but the bottom was turning soft. I checked the soil report: the water table was already shallow, and a week of heavy rain had pushed it higher. I proposed digging a sump at one corner of each pit, running a pump continuously the night before the pour, and removing the soft layer and placing a lean concrete blinding right after the last trim so the base stayed firm. My manager and the designer agreed. We poured one day late instead of a week late, and I added a dewatering check to our pre-pour list for the rest of the footings."

"On a commercial job a set of sleeves for drainage pipes was missed in a deep first-floor beam. We found it a week after casting, when the plumbers came to fix the pipes. I had signed that pour card, so part of it was mine. I told my manager the same day, before anyone started drilling, because a core through a heavily loaded beam can cut main bars. We got the designer to site, scanned the beam to locate the steel, and she approved two cores at specific positions away from the bars, with the pipe route adjusted for the rest. It cost us a few days. After that I added a services sign-off to our pour card, so the plumbing and electrical leads had to initial it before any beam or slab pour."

"A formwork foreman on my last site wanted to pour a column with the shutter slightly out of plumb, because the crane was booked and he said it was within tolerance. I checked with a plumb bob and it was outside the tolerance in our spec. I didn't argue in front of his crew. I showed him the reading and the clause privately, and said I couldn't sign it but I'd help him make up the time. We re-braced it in about forty minutes while the concrete truck waited, and I had the next column checked before his team started so it didn't happen twice. He was annoyed that day, but after that he started calling me over to check before he asked for the pour, which saved us both time."

"In my first year I noticed the steel fixers were bending the stirrup hooks at ninety degrees, when the drawing asked for 135-degree hooks bent back into the core, which keep holding even if the cover spalls off. They'd done it their way for years. I didn't just point at the drawing. I took a short piece of bar, showed how a ninety-degree hook can open out when the concrete around it cracks, and how the 135-degree hook stays locked in the core. The foreman got it quickly. We made a sample stirrup and hung it at the bending yard as the reference, and I checked the first batch that afternoon. After that I rarely had to raise it again, because the reference piece did the talking."

"I'd look at how long the pour will really take against the forecast. If we can start at first light and finish well before the rain, I'd confirm with the concrete plant that they can keep trucks coming without gaps, and have polythene sheets and people ready to cover the finished area. I'd also agree a construction joint position with the designer in advance, usually where shear is low, so if the weather turns early we stop at a planned line, not wherever the last truck ends up. If the pour is too big to finish safely before the rain, I'd postpone. Heavy rain on fresh concrete washes out cement from the surface and adds water, and a cold joint in the wrong place is a structural problem. Losing a day is cheaper."

"I'd start by being honest that they know things I don't. In my internship I learned more about formwork from one carpenter in a week than from a whole semester, just by asking why he did things a certain way. Respect also comes from being useful. If I get their questions answered by the designer quickly, have the drawings ready and the steel and concrete ordered on time, they see I make their day easier. Where I won't bend is quality and safety. If something doesn't match the drawing or isn't safe, I say so, but I explain the reason and I do it privately, not in front of the whole crew. Over time, they trust that when I stop something, there's a good reason."

"I'd stop the work right then, calmly, and ask him to step back from the edge. A fall from that height can kill, so it doesn't matter whose crew he's on. Then I'd find the supervisor and make the area safe before anyone goes back: guardrails or edge barriers put back, or if the work needs the edge open, a harness clipped to a proper anchor point. I'd ask why it was missing, not to blame him but because there's usually a reason, like the guardrail was removed to lift material and nobody put it back. I'd report it as a near miss so the safety officer sees the pattern, and at the next toolbox talk we'd cover edge protection and who restores it after a lift."

"The visible part is easy to list: edges protected, clean access routes, scaffolds tagged as inspected, people wearing the right gear, and permits for things like hot work, excavations and confined spaces. But the real sign is how people behave when nobody senior is watching. On a safe site, a worker will stop a job and say it isn't right, and near misses get reported because nobody gets punished for reporting. My part is to build safety into the work plan, like planning edge protection before the slab is poured, not after. I wear my own gear properly, because the crew notices. And when I see something unsafe, I deal with it right then, even when we're behind, because that tells everyone the real priority."