Interview

Question 1

Why do you want to transition from First Assistant Editor to Post-Production Coordinator?

1AE role is coordinating + administrative, organizing, fixing + solving

Answer 1

What most people don’t realize is that the role of a 1AE is significantly composed of coordinator and administrative tasks, not creating cinema. So, naturally, those tasks and that skillset are intrinsic to the success of any 1AE, and focusing on those tasks is inherent. I’ve never been compelled to have my name on the marquee or in the head credits. I’ve always gleaned more satisfaction from organizing, fixing, and solving puzzles. Taking time over the last year to pursue project management training confirmed that this is the path I want to focus on. It’s a natural lateral move.

1AE role is coordinating + administrative, organizing, fixing + solving

Question 2

You’ve been a First Assistant Editor for 13 years. What made you realize coordination was where you wanted to focus?

— these tasks + skillset are inherent to a 1AE success: organize, solve

Answer 2

What most people don’t realize is that the role of a 1AE is significantly composed of coordinator and administrative tasks. So, naturally, those tasks and that skillset are intrinsic to the success of any 1AE, and focusing on those tasks is inherent. I’ve never been compelled to have my name on the marquee or in the head credits. I’ve always gleaned more satisfaction from organizing, fixing, and solving puzzles. Taking time over the last year to pursue project management training confirmed that this is the path I want to focus on.

— these tasks + skillset are inherent to a 1AE success: organize, solve

Question 3

The job posting specifically notes this is a “logistics/management role, not an Assistant Editor role.” How do you feel about stepping away from the technical editing side?

—my tech background is an advantage, understand workflows, codecs + tech

Answer 3

My technical background as a 1AE is an advantage. I have a deep understanding of workflows, codecs, and technical requirements, which helps me anticipate problems and communicate effectively with editors and vendors. I’ve never been compelled to have my name on the marquee or in the head credits. I’ve always gleaned more satisfaction from organizing, fixing, and solving puzzles. Taking time over the last year to pursue project management training confirmed that this is the path I want to focus on.

—my tech background is an advantage, understand workflows, codecs + tech

Question 4

You’ve held a Post-Production Supervisor role before (Milton’s Secret). Why did you return to being a First AE after that experience?

—crowded field, top of my field, always in high demand, guaranteed work—

Answer 4

The Post-Production Supervisor field is very crowded. And I quickly moved to the top of my field as a 1AE. There weren’t (and isn’t) enough 1AEs willing to remain career 1AEs. Most of them wanted to springboard from the position into editng. I knew that by staying where I was as a 1AE I would always be in high demand, guaranteed work. And I would rather make a $150K/year than struggle as an editor to find work in an ever-growing and crowded pool of talent. Then the industry strikes happened, the industry decelerated as a whole, and everything was recalibrated.

But that supervisory experience stayed with me—I kept the coordination and organizational aspects of that role alive in my AE work.

—crowded field, top of my field, always in high demand, guaranteed work—

Question 5

What aspects of coordination work excite you the most?

—the puzzle-solving aspect, finding linear through lines, answers—

Answer 5

I like the puzzle-solving aspect of it. I like finding the linear through-line that turns the supposed chaos of a complex post-production schedule with multiple moving parts (picture lock, color sessions, sound mix, VFX deliveries) into an organized system. I also like being a reliable point of contact who has answers and keeps everyone aligned.

—the puzzle-solving aspect, finding linear through lines, answers—

Question 6

What will you miss least about being a First Assistant Editor?

— unhealthy work/life balance —

Answer 6

I won’t miss the pressure of being the person who has to troubleshoot a vague Avid system error that occurs at midnight while exporting a cut for an AM screening. Meaning, precisely, I will not miss the unhealthy work/life balance. I’m much more energized by preventing problems through good planning and organization than by solving technical crises after they happen.

— unhealthy work/life balance —

Question 7

The posting emphasizes “Excel Mastery.” Walk me through your most complex Excel tracking system you’ve built.

Answer 7

For a Netflix series I worked on, I built a comprehensive VFX tracking system that monitored over 400 shots across 10 episodes. It used multiple linked sheets: one master sheet with all shots, individual sheets per episode, a vendor assignment sheet, and a delivery tracking sheet. I used conditional formatting to color-code shot status—red for overdue, yellow for approaching deadline, green for delivered. The system used VLOOKUP formulas to pull vendor contact information and rates automatically, and I built in dropdown menus for shot status so people couldn’t enter inconsistent data. I also created pivot tables that let the post supervisor see at a glance how many shots each vendor had and what our delivery pipeline looked like week by week. It became the single source of truth for the entire team.

Question 8

What specific Excel formulas do you use regularly? Can you give examples of how you’ve used VLOOKUP, INDEX/MATCH, or pivot tables?

Answer 8

I use VLOOKUP constantly for pulling vendor information—like if I have a vendor name in one column, VLOOKUP pulls their email, phone number, and rates from a master vendor sheet. For more complex lookups where VLOOKUP won’t work, I use INDEX/MATCH combinations. For example, on Milton’s Secret, I needed to match delivery dates with specific requirements that weren’t in the first column, so INDEX/MATCH handled that.

For formulas, I regularly use:
- SUMIF and COUNTIF to track how many shots are in each status category
- IF statements with nested logic for automatic deadline warnings
- Conditional formatting with formulas to highlight overdue items
- CONCATENATE to create standardized file naming conventions
- DATE and DATEDIF functions for tracking turnaround times

Pivot tables are my go-to for reporting. I use them to give post supervisors quick insights—like ‘how many deliverables do we have due this week by vendor’ or ‘what’s our completion percentage by episode.’ They’re great for turning raw data into actionable information.

Question 9

How do you approach building a tracking sheet from scratch when starting a new project?

— identify decisions + data points, logical, validation, automation —

Answer 9

Start by identifying the decisions that need to be made by data in a tracking sheet. The key is to make it powerful enough to track everything but simple enough that users can update it without breaking it. Then:

First, identify all the data points that need tracking: shot numbers, episode numbers, deadlines, vendor names, status, notes, etc.

Second, structure it logically—usually one master sheet with detail sheets breaking down by episode or department.

Third, build in data validation so users can’t enter inconsistent information—dropdown menus for status fields, date formats for deadlines.

Fourth, add automation—formulas that calculate turnaround times, conditional formatting that flags problems, maybe a summary dashboard at the top.

Finally, test it with real data and get feedback from users. Create a simple how-to-use-this-sheet tab so it’s self-explanatory.

— identify decisions + data points, logical, validation, automation —

Question 10

Have you ever created Gantt charts in Excel? What’s your process?

Answer 10

I’ve created Gantt charts for delivery schedules, where I track milestones from picture lock through final delivery. My process is to set up tasks in rows with start dates, end dates, and duration calculated automatically. Then I apply conditional formatting to create the visual timeline—cells are colored based on whether today’s date falls within the task’s date range. I also include milestone markers for key events like picture lock, first color pass, sound mix, and final delivery.

For TV series work, I would create one master Gantt chart showing the pipeline for all episodes, with color coding by episode so you can see how they overlap and cascade.

— tasks in rows, dates, duration, milestones, color code —

Question 11

Tell me about a time when your Excel tracking system caught a problem before it became critical.

— conditional formatting is crucial, numerical ranges —

Answer 11

When applied intelligently, Excel’s conditional formatting tool can help to prevent any crises. Setting rules to flag any and all cell items that don’t meet the criteria of your numerical ranges—in our case, budget and dates, whether they be exact budgets and dates, or with buffer built in—is crucial in helping catch the problems hiding in the gaps between departments.

— conditional formatting is crucial, numerical ranges —

Question 12

How do you ensure others can understand and use the tracking systems you create?

Answer 12

A few key principles: First, I use clear, descriptive column headers—not abbreviations that only I understand. Second, I color-code logically and include a legend so people know what the colors mean. Third, I lock or protect cells that contain formulas so nobody accidentally breaks the automation. Fourth, I often create a simple instruction sheet or ‘Read Me’ tab explaining how to update the sheet.

But most importantly, I do a brief walkthrough with anyone who needs to use it. I’ll show them: ‘Here’s how you update shot status, here’s how the deadlines are calculated, here’s what the red highlighting means.’ I also make myself available for questions initially. The goal is to make these systems helpful tools, not confusing spreadsheets that people avoid using. If people don’t use it, it’s failed—so making it intuitive and approachable is crucial.

Question 13

Walk me through how you would create and maintain a master schedule for a TV series episode from picture lock to final delivery.

—work backward from delivery date, add buffer, create Gant, review daily

Answer 13

Work backward from the delivery date:

Delivery: Sep 30
Delivery prep: 3-5 days before (Sept 25-27)
Final mix and mastering: 5-7 days (Sept 18-24)
Sound mix: 7-10 days (Sept 8-17)
Color correction: 5-7 days (Sept 1-7)
VFX final delivery: Sept 1 (need buffer before color)
Online conform/finishing: 3-4 days (Aug 28-31)
Picture lock: August 27

Then build in buffer days for revisions and notes at each stage. Create an Excel sheet or Gantt chart showing each milestone with start and end dates, dependencies clearly marked (eg, color can’t start until VFX are delivered; can’t start final mix until color is approved).

Review it daily, updating actual dates versus planned dates. If something slips, immediately assess the impact downstream and flag it to the post supervisor so they can decide if other stages need adjustment or if a delivery extension needs to be requested.

—work backward from delivery date, add buffer, create Gant, review daily

Question 14

How do you track milestones like Picture Lock, Color, and Sound simultaneously across multiple episodes?

— master tracking sheet, dependencies, check-ins —

Answer 14

I’d create a master tracking sheet with episodes in rows (in ascending order of delivery dates, rather than episode number) and milestones in columns, so we can see the status of every episode at a glance. Each cell would be color-coded: red for not started, yellow for in progress, green for complete. I’d include actual dates next to planned dates so we can see variance.

The key is understanding the dependencies and ripple effects. If Episode 3 picture lock is delayed, that pushes its color session, which might create a resource conflict if Episode 4 was scheduled for color the same week. So I’d build in alerts—conditional formatting that flags potential conflicts.

I’d also hold regular check-ins—probably weekly schedule review meetings with the post supervisor where we look at the master board together and make decisions about priorities, resource allocation, and whether we need to escalate any concerns to production. The goal is no surprises—everyone should know where every episode stands at all times.

— master tracking sheet, dependencies, check-ins —

Question 15

Tell me about a time when you had to juggle multiple concurrent projects. How did you prioritize?

—prioritize deadlines + impact, urgent-vs-important matrix, review daily

Answer 15

The key to juggling multiple projects is clear prioritization based on deadlines and impact, and using a simple urgent-versus-important matrix. True emergencies obviously take priority. But a good coordinator also has to protect time for important-but-not-urgent tasks, like building tracking systems or scheduling future sessions, because neglecting those tasks creates emergencies later.

Review all project deadlines and identify what absolutely must happen daily. Block time for those critical tasks first, then fill in coordination work, communication, and planning. Communicate clearly with stakeholders. (I’m prioritizing the HBO delivery today, but I’ll have the vendor quotes for the CTV project ready by tomorrow morning.) Managing expectations is as important as managing the actual work.

In those moments where everything feels equally urgent, defer to the post supervisor for guidance to ensure my priorities align with the production’s priorities.

—prioritize deadlines + impact, urgent-vs-important matrix, review daily

Question 16

How do you handle it when a milestone gets delayed and cascades into other deadlines?

—assess, communicate quickly, update tracking, follow up, seek solution

Answer 16

First, assess the impact immediately. If picture lock gets delayed by two days: Does that affect the color session? Does the colorist have flexibility or are they booked? Is there any buffer in the schedule or does it push final delivery?

Second, communicate quickly and alert the post supervisor immediately with solutions: Picture lock is now Wednesday instead of Monday. This impacts our color session scheduled for Thursday. Here are three options: 1) Push color to the following Monday, which keeps us on track for delivery. 2) See if the colorist can accommodate Friday. 3) Request a 2-day delivery extension.

Third, update all tracking documents immediately so everyone’s working from accurate information.

Fourth, follow up with all affected parties—notify the colorist of the date change, update production on the new timeline, make sure editorial knows the revised deadlines.

The key is to stay calm and solution-oriented. Delays happen. My job is to minimize their impact and keep everyone informed.

—assess, communicate quickly, update tracking, follow up, seek solution

Question 17

What’s your process for coordinating screening schedules when multiple stakeholders have conflicting availability?

—propose 2-3 options, who is essential, confirm, send calendar invite —

Answer 17

Start with a scheduling poll, not a proposal. Reach out to all required attendees and gather their availability for a specific duration. Then identify the overlapping windows and propose 2-3 specific options, not “what works for you?” If there’s no overlap, prioritize based on who’s most essential.

Being specific about the screening details also helps: ‘This is a 42-minute episode, so allow 90 minutes for screening plus notes discussion.”

Once a time is set, confirm in writing with all attendees and send calendar invites immediately.

—propose 2-3 options, who is essential, confirm, send calendar invite —

Question 18

How do you ensure nothing falls through the cracks when managing multiple deliverables?

Answer 18

A combination of systems and discipline. The system side is my tracking sheets—everything that needs to be delivered gets logged with a deadline, owner, and status. I review these daily, not weekly. Things change fast in post, so daily review is essential.

The discipline side is follow-up. If a vendor says ‘I’ll get you that quote by Wednesday,’ I mark it in my calendar to follow up Wednesday afternoon if I haven’t heard from them. I don’t assume silence means it’s handled—I verify.

I also use a simple daily checklist approach. Each morning I ask: What must be delivered today? What’s at risk of falling behind? Who am I waiting on for information? That keeps me focused on what matters now.

And honestly, I build in redundancy. For critical deliverables, I set up calendar reminders at multiple points: two weeks out, one week out, three days out, day before. Yes, it’s extra work, but it means nothing sneaks up on me. I’d rather over-communicate and over-track than miss something.

Question 19

You’ve worked with major facilities like Technicolor, Deluxe, and Tattersall. How would you approach managing freelance vendors who may have less infrastructure?

— detailed brief, check-in, file transfer familiarity, more buffer time

Answer 19

Clear communication, respect and professionalism.

Initiate every freelance vendor relationship with a detailed brief: deliverable specifications, deadline, file formats, delivery method, who to contact with questions, and what the approval process looks like. Confirm they have everything they need before they start.

Establish a check-in rhythm. That way any problems that surface early can be addressed early.

For file transfers, ensure that they’re comfortable and familiar with whatever system we’re using—Frame.io, Aspera—and test it before the project begins.

Build in more buffer time with freelancers as they often don’t have a team to back them up if they hit a technical problem.

— detailed brief, check-in, file transfer familiarity, more buffer time

Question 20

How do you handle communication when a vendor misses a deadline or delivers work that doesn’t meet specifications?

Answer 20

First, I’ll find out what happened from the vendor and ask for an update on the status. It is more often than not for a legitimate reason: a technical issue, a miscommunication about the deadline, a family emergency. Understanding the cause helps to determine the solution. Getting angry doesn’t solve the problem.

If the issue is quality—the work doesn’t meet specs—I’ll document specifically what’s wrong and communicate clearly: (The ProRes files we received are 1920x1080, but we specified 3840x2160 in the delivery specs.)

For missed deadlines, I’ll assess the impact and communicate up the chain immediately: “The colorist missed today’s delivery. They’re now committing to Friday morning. This pushes our sound mix start by one day but we can still hit final delivery if sound stays on schedule.” I give the post supervisor the information they need to make decisions.

I’d also keep a record of vendor performance so we can make informed decisions about who to work with in the future. If a vendor consistently misses deadlines, that’s valuable information for planning. And post-production is a small world; you’ll work with the same people again.

— what and why? quality: communicate. deadline: assess + communicate to PS —

Question 21

Tell me about a time when you had to be the main point of contact for multiple vendors simultaneously. How did you manage it?

Answer 21

On one of the Sony projects, I was coordinating VFX across three different vendors, plus a colorist, a sound designer, and a captioning service—all with overlapping timelines. The key was structure and clear communication.

I created a master vendor contact sheet with everyone’s details, preferred contact methods, and current task list. Each vendor had their own folder in our shared drive with specific delivery instructions and technical specs.

I established a daily email routine: every morning I’d send status updates to the post supervisor summarizing where each vendor stood. Every afternoon I’d follow up with vendors who had deliverables coming up: ‘Just confirming we’re on track for tomorrow’s VFX delivery.’

When conflicts arose—like two vendors needing notes from the director at the same time—I’d coordinate that centrally. I’d collect all the materials, schedule one consolidated review session, then distribute notes to each vendor with clear prioritization.

The trick was staying organized and not letting communication become chaotic. Every vendor interaction was logged. Every deadline was tracked. Every deliverable was verified. It was a lot of plates spinning, but having systems in place kept it manageable. And honestly, I enjoyed it—that’s the kind of coordinated logistics work I thrive on.

Question 22

How do you build and maintain strong relationships with external vendors?

— respect, early communication, acknowledge good work, reliability —

Answer 22

First, respect. Vendors are professionals, not order-takers. Listen to and implement their input on timelines and technical approaches rather than just dictating terms.

Second, early and clear communication. Give them as much advance notice as possible about bookings, and provide detailed briefs.

Third, acknowledge good work.

Fourth, make an effort to remember vendors’ preferences—like, ‘x colorist prefers AM sessions’ or ‘x sound designer needs two days’ notice for schedule changes.’

Lastly, reliability on my end. If I say I’ll get them reference materials by Thursday, I get it to them by Thursday. Commit to a payment timeline. If I’m organized and professional, they’re more likely to go the extra mile when I really need it.

— respect, early communication, acknowledge good work, reliability —

Question 23

What information do you typically need to collect from vendors before work begins?

—contacts, tech specs, admin logistics, delivery details, review process

Answer 23

I would create a standard vendor intake form covering:

Contact information
- Main point of contact name, email, phone
- After-hours contact for emergencies
- Invoicing contact/address

Technical specifications
- What file formats they can accept and deliver
- Their preferred transfer method (Aspera, Frame.io, hard drive, etc.)
- What resolution and codec they work in
- Any technical limitations we should know about

Logistics
- Their availability/booking calendar
- Turnaround time for the specific scope of work
- Rate structure (day rate, project rate, per-shot for VFX, etc.)
- Payment terms (50% upfront, etc.)

Delivery details
- How they’ll deliver finals (file transfer, which platform)
- What format the deliverables will be in
- Whether they provide backups

I would also ask about their review process. Do they do an internal QC before delivering? How do they handle revision rounds? Do they charge for revisions beyond a certain scope?

Getting all this upfront prevents misunderstandings later.

—contacts, tech specs, admin logistics, delivery details, review process

Question 24

How do you track vendor quotes and compare options for a post supervisor to make decisions?

—vendor comparison spreadsheet, highlight differences, red flags—

Answer 24

Create a vendor comparison spreadsheet with all quotes side by side. Key columns would be:

• Vendor name
• Scope of work (making sure we’re comparing apples to apples)
• Total cost
• Rate structure (day rate vs. project rate vs. per-unit)
• Timeline/turnaround
• Deliverable format
• What’s included (are revisions included or extra?)
• Additional fees (transfer fees, render time, etc.)
• Past experience with this vendor (if any)
• Notes (like “this vendor came recommended by the director”)

Highlight key differences: Vendor A is $2,000 cheaper but needs an extra three days. Vendor B has the faster turnaround but charges for revision rounds. Vendor C is mid-range pricing and we’ve worked with them successfully before.

Also, flag any red flags: Vendor D’s quote is very low, but they’re asking for 100% payment upfront which is unusual. Or Vendor E can’t deliver ProRes, only H.264, which creates extra work for us.

—vendor comparison spreadsheet, highlight differences, red flags—

Question 25

Walk me through your understanding of a complete asset pipeline from raw footage intake to final master delivery. | —camera/sound files, transcoded, NLE proxies, turnovers, deliverables—

Answer 25

Raw camera and sound files are delivered for processing to the lab. Said camera files are transcoded to an NLE codec like ProRes or DNxHD, ensuring that all metadata (scenes, takes, camera rolls, LUTs, lenses, creation dates, etc) is properly imported. Transcoded files are synced with recorded set audio. Transcoded synced files (proxies) are organized by scene and take and delivered to the edit suite and imported into the NLE system of choice. The editor works with said proxy files until picture lock. The picture lock is the master for all subsequent downsteam work. Turnover packages are then provided for VFX, composers, foley, sound mix, and colour. These vendor-specific packages can include files like EDLs, XMLs, AAFs, OMFs, and reference picture QuickTimes. VFX will also require pull lists for any shots that need VFX work. VFX will return completed shots. The sound team will also require ADR locator lists. The sound team will return final mixed audio stems. Online will also require locator lists for any shot opticals and text elements. Online will conform the picture lock to the original, full resolution camera files, and integrate the completed VFX shots. That conformed timeline is provided to the colorist, who grades it and returns a color-corrected master. Final deliverables combine the color-corrected picture, the mixed audio, and closed captions into the format specified by the broadcaster or streaming platform. That master gets delivered along with all required paperwork. | —camera/sound files, transcoded, NLE proxies, turnovers, deliverables—

Question 26

How do you ensure proper codec conversions when footage moves between different stages of post?

Answer 26

Create a technical spec sheet at the start of the project and distribute it to all parties (editors, vendors, facilities). The spec sheet defines what codec is used at each stage: editorial working format, VFX turnover format, color working format, final delivery format. Second, verify compatibility before work begins. If we're sending files to a vendor, confirm that they can work with ProRes 422 HQ QuickTime files, and that they will deliver back in the same format. Third, test early. Verify that a vendor can open your files and that the format looks correct before sending everything. Better to catch issues on shot 1 than shot 50. Fourth, QC every handoff. When we receive files back from a vendor, verify the technical specs match what was requested: resolution, frame rate, codec, audio channels, all correct before passing it up the chain. | —distribute tech specs, verify compatibility, verify workability, QC

Question 27

Explain your experience with Frame.io. How have you used it for review and approval workflows?

Answer 27

Setup: Create a project for each episode (or deliverable) with precise folder structure—Editor's Cuts, Producer Review, Network Review, Final Approved. Invite relevant stakeholders and assign appropriate permissions—the editor has full access, the director has commenting rights, the network has commenting only. Upload and Organize: When the editor delivers a cut, title and upload it clearly (Ep_103_Directors_Cut_v1_2023-05-15), and follow that naming structure without deviation. Review Coordination: Use Frame.io's notification system to alert reviewers that cuts are ready for review, and when comments/notes are due. Consolidation: After review, export all comments and compile them into a consolidated notes document for the editor, organized by timecode. Version control: As revisions are made, upload new versions to the same project so there's a full history of viewable cuts. Frame.io's version stacking keeps everything organized. Approval: Once a cut is approved, move it to the Final Approved folder and lock it to prevent everyone from reviewing an outdated version. The key to Frame.io is to use it deliberately, be thoughtful about the project setup, and stay on top of version control.

Question 28

What's your process for ensuring metadata accuracy throughout the post pipeline?

Answer 28

Metadata accuracy starts at the beginning and requires constant vigilance. In the dailies process, that means proper scene/take numbers, camera roll IDs, date stamps—all that needs to be correct from day one. If metadata is wrong at dailies, it's wrong everywhere downstream. Throughout editorial, I'd maintain a database or spreadsheet tracking key metadata: episode numbers, scene numbers, VFX shot IDs, music cue IDs. When we generate turnovers for VFX or sound, the metadata in those files needs to match our tracking system. For deliverables, broadcasters and streamers have very specific metadata requirements—show title, episode number, air date, aspect ratio, audio configuration, closed caption language, and more. I'd create a metadata checklist based on the delivery spec and verify every field before delivery. I'd also implement checks: When we receive files back from vendors, does the file name match our naming convention? Does the embedded metadata match what we sent? Catching metadata errors before they propagate saves huge amounts of time. And critically, I'd maintain a master source of truth—one spreadsheet or database that defines the correct metadata for everything. If there's ever a question, 'What's the correct scene number for this shot?' there's one place to check, not five different documents with five different answers. Metadata sounds boring, but it's essential. Incorrect metadata can delay delivery, cause versioning nightmares, and create real problems. As a coordinator, ensuring metadata accuracy would be a top priority for me.

Question 29

How do you troubleshoot technical issues when a vendor says they can't open a file or something isn't playing back correctly?

Answer 29

First, I'd gather specific information: What exactly is the problem? Is the file not opening at all? Is it opening but showing black frames? Is audio missing? Is it the wrong aspect ratio? Vague 'it doesn't work' doesn't help me solve it. Second, I'd verify the basics: Did the file transfer completely? Sometimes large files timeout or corrupt during transfer. I'd check the file size matches what was sent. Third, I'd check the technical specs: What codec was it delivered in? What codec is the vendor expecting? Do they have the right software to open that format? Sometimes it's as simple as 'they don't have the ProRes codec installed.' Fourth, I'd test it myself or have someone test it: Can we open the file on our end? If we can open it but they can't, the problem is likely on their end—maybe a software version issue, maybe a missing codec. If we can't open it either, then we sent a corrupted file and need to retransfer. Fifth, I'd propose solutions: 'Can you try opening it in DaVinci Resolve instead of Premiere?' or 'Let me transcode it to a different format and send that,' or 'Let me reupload via Aspera instead of Dropbox to ensure a clean transfer.' Throughout, I'd stay calm and collaborative. Technical glitches happen. The goal is to solve it quickly so the vendor can get to work. My technical background means I can usually diagnose these issues efficiently rather than playing 20 questions over email.

Question 30

Tell me about a time when you caught a technical error before it reached final delivery.

Answer 30

On a Lionsgate feature, we were preparing for final delivery and I was doing a final QC check of the master file. The delivery spec required stereo audio—left and right channels with identical content (not true stereo, but dual mono for distribution purposes). When I checked, I noticed the audio waveforms looked different between left and right channels. I played it back, and sure enough, the right channel was slightly out of sync—maybe four frames. It wasn't immediately obvious in casual playback, but it was definitely wrong. If we'd delivered that, it would have failed broadcaster QC and created a huge scramble to fix and redeliver. I immediately flagged it to the post supervisor and the sound facility. Turns out there'd been an export error where the audio got slightly offset during the final mixdown. The sound mixer was able to re-export quickly with the correct sync, and we verified it thoroughly before actually delivering. That's the kind of thing that happens when you actually check the deliverables yourself rather than assuming everything is correct. I've made it a habit to do a complete technical QC on final files—check resolution, frame rate, aspect ratio, audio channels, timecode, everything—before they go out the door. Catching problems early is so much better than dealing with rejected deliveries.

Question 31

The posting mentions being "the bridge between Production and Editorial." Can you give an example of when you successfully facilitated communication between these departments? | —translate post information for non-technical stakeholders, + vise versa

Answer 31

The parties involved in this work generally understand the process and rarely need to have anything translated. Implementing a simple weekly status email—Episode status: E01 in final color, E02 in director's cut, E03 in rough cut—goes far in keeping everyone aligned and reduces back-and-forth questions. But “bridging” is about translation—taking technical post-production information and making it accessible to non-technical stakeholders, and taking production constraints and communicating them clearly to the post team. Both sides have legitimate needs; the coordinator makes sure those needs are communicated effectively. | —translate post information for non-technical stakeholders, + vise versa

Question 32

How do you communicate technical information to non-technical stakeholders (producers, network executives)?

Answer 32

I avoid jargon and focus on impact, not process. For example, instead of saying 'We're waiting on the online conform before we can start the color grade because the VFX vendor delivered shots in the wrong color space,' I'd say: 'We have a technical issue with the VFX files that needs to be fixed before color can start. This will delay color by two days, but we can absorb it in our buffer time and still hit delivery.' The key is: What do they need to know? Producers and executives care about: Will we hit the deadline? Is it going to cost more money? Is there a quality issue? They don't need to know the technical details of codecs and color spaces unless those details affect those three things. I also use analogies when helpful. Explaining why we can't just 'make the fix' might sound like: 'Think of it like baking a cake. Once the cake is baked, you can't go back and change how much sugar was in the batter. We need to go back to the ingredients stage—the original files—and rebuild the shot correctly.' And I always follow up technical explanations with clear next steps: 'Here's what's happening to fix it, here's the new timeline, here's what we need from you if anything.' Give them information they can act on, not just technical details.

Question 33

Tell me about a time when there was miscommunication between departments. How did you handle it?

Answer 33

On one project, production sent a camera crew to shoot pickup shots, and editorial was expecting them to be delivered for a specific scene. When the footage arrived, it was the wrong scene entirely—production had shot different pickups than what editorial requested. The immediate response was finger-pointing: production said 'editorial didn't tell us clearly what they needed,' editorial said 'we sent a detailed shot list.' I pulled both sides together and asked questions until we found the root cause: there had been two different email chains with two different shot lists, and production had worked from the old one. The fix was process: From then on, all pickup requests went through me. I'd work with editorial to create the shot list, get it approved by the director, then send ONE clear document to production with 'This is the official pickup shot list for shooting on X date.' No more confusion about which version was correct. I also made sure the tone stayed collaborative—this wasn't about blame, it was about fixing the process so it didn't happen again. Miscommunications happen, especially on fast-moving projects. The coordinator's job is to catch those gaps and create systems that prevent them. That experience taught me that my role isn't just passing messages—it's creating clarity in communications and making sure everyone's working from the same information.

Question 34

How do you ensure everyone stays informed without overwhelming people with too many emails or updates? | —strategic communication, regular, actionable, tailored to audience

Answer 34

The goal is strategic communication—frequent enough that people feel informed, but structured enough that it doesn't become overwhelming. First, regular scheduled updates—for example, a weekly status email that goes out every Friday—rather than constant ad-hoc messages. Second, make emails actionable and scannable. Use subject lines like 'ACTION REQUIRED: VFX Notes Due Friday' so people know what's needed from them. Use bullet points and bold text for key information so busy people can skim and get what they need. Third, tailor communication to the audience. The post supervisor gets detailed information about every deliverable and deadline. The producer gets high-level summaries about what's on track and what needs attention. Copying everyone on everything only creates noise. Fourth, use the right channel for the right message. Urgent messages might be a phone call. Routine updates are emails. Reference information goes in a shared document people can check when needed. | —strategic communication, regular, actionable, tailored to audience

Question 35

How would you handle a situation where production and editorial have conflicting priorities? | —understand why, surface to PS, solve, communicate the decision—

Answer 35

First, I would make sure I fully understand both sides. What's production's priority and why? What's editorial's priority and why? Conflicts often occur because of lack of context—one side doesn't understand what's driving the other side's urgency. My role is to facilitate resolution, not to pick sides. Second, I would surface the conflict to the post supervisor or whoever needs to make the decision. Third, I would look for creative solutions that serve the project's overall needs. Sometimes there's a middle ground. Fourth, once a decision is made, communicate it clearly to both sides with the reasoning. | —understand why, surface to PS, solve, communicate the decision—

Question 36

The posting states you'll be working under a post supervisor and head of post department. How do you feel about that structure? | —support, implement, collaborate, take direction, organize, defer to PS—

Answer 36

As a coordinator, my role is to support the post team and execute on the priorities set by the post supervisor. I'm not there to make creative decisions or override scheduling choices. I’m there to implement those decisions efficiently and keep everything organized. I'm there to collaborate, take direction, and be proactive within my scope—but also to know the coundaries of my scope. Having a clear reporting structure is helpful. When questions arise regarding priorities, I can defer to the post supervisor rather than making that call myself. I want to eventually grow toward a supervisory role, so working closely with an experienced post supervisor lets me observe their decision-making process, understand how they balance creative and logistical concerns, and learn what makes a good supervisor. ## Footnote —support, implement, collaborate, take direction, organize, defer to PS—

Question 37

Tell me about a time when you disagreed with a supervisor's decision. How did you handle it?

Answer 37

On one project, the post supervisor wanted to start color before all VFX were finaled, thinking we could work around the temp VFX shots. I was concerned this would create rework—if VFX shots changed after color, we'd need to regrade them, which costs time and money. I raised my concern directly but respectfully: 'I understand we're trying to stay on schedule, and I support that. My concern is that if VFX change after color, we'll need additional color sessions to integrate them. Would it be worth building in a few extra days upfront to wait for final VFX, rather than potentially needing rework later?' I presented it as a question, not a challenge. The supervisor heard me out, but ultimately decided to proceed with color anyway—the schedule pressure was too significant. I said, 'Understood, let's do it,' and moved forward with their decision. I made sure the colorist knew some shots might change, and we documented carefully which shots had temp VFX so we could identify what needed rework. Turned out, the supervisor was right—only two shots changed significantly, and the colorist was able to handle the revisions quickly. I learned that sometimes schedule pressure justifies accepting some rework risk. The key was: I raised my concern clearly once, accepted the decision, and executed fully. I didn't sulk or say 'I told you so.' You offer your perspective, but you support the final decision—that's what working effectively under a supervisor means.

Question 38

How do you take direction while also being proactive in solving problems? | —be proactive in my lane, escalate when decisions are outside my scope—

Answer 38

Be proactive within my lane, but escalate when decisions are outside of my scope (and have budget implications or creative impact). Keep the post supervisor informed about what I’m handling and what needs their input. I never want them to be surprised. If they're confident I'll escalate anything that needs their attention, they can trust me to handle the day-to-day coordination independently. The key is communication and not to make assumptions. | —be proactive in my lane, escalate when decisions are outside my scope—

Question 39

What do you need from a supervisor to be successful in your role?

Answer 39

First, clarity on priorities. When everything feels urgent, I need guidance on what's actually most urgent. That helps me make good decisions. Second, decision-making authority within defined boundaries. If I know I can book vendors under $5,000 on my own, that allows me to operate efficiently without being constantly micro-managed. Third, regular check-ins. Even just 15 minutes a few times a week to review the schedule, flag issues, and align on priorities is invaluable. I don't need constant oversight, but I do need regular touchpoints. Fourth, feedback—both positive and corrective. And finally, trust. Mutual respect makes the working relationship effective. Having a clear reporting structure and an experienced post supervisor who knows what they need from a coordinator sets me up for success. I'm here to make your job easier, and clear communication makes that possible.

Question 40

Have you ever trained or supervised others? (They may ask about managing assistant editors in the future) | —it's about organizing people and processes to work efficiently

Answer 40

In my 1AE roles I often worked with second AEs or post-production assistants and provided guidance on workflows, organization systems, and mechanicals (software, systems). I approached it by setting clear expectations, and helped them to understand not just what to do but why we do it that way. Ultimately, I see supervision as an extension of coordination—it's about organizing people and processes to work efficiently. | —it's about organizing people and processes to work efficiently

Question 41

Tell me about a time when a major scheduling conflict arose. How did you resolve it?

Answer 41

I was on a film where picture lock got delayed by over a week due to notes from the studio, and the sound team had a hard out that wasn’t flexible. If we missed the sound mix dates, we'd be pushed by three weeks, which would blow our delivery deadline entirely. The first step was to assess if we had any flexibility. Could we compress any stages? Could we split the sound mix into shorter sessions? Could we start on sound before picture was fully locked, on scenes that we knew wouldn't change? The editor and I proposed that we feed the sound team reels that had already been addressed by notes (a soft lock), and might only need minor timing tweaks. This would give the sound team a head start, and actually put us on schedule by the time the remaining reels were handed over with picture lock. The sound team was communicated precisely what reels were locked and might change, everyone was kept informed daily about progress, and we did eventually make our dates. | —delayed picture lock, assess flexibility, feed soft lock reels to mix

Question 42

The posting says you should be able to "juggle multiple projects without breaking a sweat." Tell me about your most stressful multi-project period and how you handled it.

Answer 42

The most intense period was probably during 2019 when I had three overlapping projects: a Netflix feature in final post, an HBO series episode in mid-post, and a Lionsgate project just starting. All three had deliverables within a two-week window, and all three hit complications simultaneously—VFX delays on Netflix, network notes requiring significant rework on HBO, and technical issues on the Lionsgate dailies. How I handled it: First, I didn't panic. I made a master list of every deliverable across all three projects with drop-dead deadlines. Then I identified what absolutely must happen each day to stay on track. Second, I communicated clearly with all stakeholders. I let each post supervisor know 'I'm coordinating three concurrent projects this week. I'm prioritizing the Netflix delivery due Thursday, but I'm still tracking everything else and will flag any issues immediately.' Transparency prevented anyone feeling neglected. Third, I ruthlessly protected time. I blocked my mornings for deep focus work—building tracking sheets, coordinating vendors—and kept afternoons for meetings and communication. Otherwise I'd get trapped in reactive mode. Fourth, I stayed organized. Every conversation, every decision, every deadline got documented immediately. My tracking sheets were updated in real-time. No information stayed just in my head. Fifth, I asked for help when needed. When the Lionsgate technical issue required hands-on troubleshooting, I looped in another AE to help diagnose while I kept the other projects moving. The honest answer is it was stressful, but it was also when I realized I thrive under that kind of pressure—when organization and logistics really matter. If I can coordinate three projects hitting crises simultaneously, I can absolutely handle a TV series post-production schedule.

Question 43

How do you stay organized when everything seems to be on fire at once? | —inventory, triage (urgent vs important), communicate, 100% focus, reset

Answer 43

First, note every single thing that needs attention. Second, triage ruthlessly (urgent-vs-important matrix) and assess consequences. Third, communicate immediately with anyone that is waiting on me for something that is non-urgent. Managing expectations prevents people from escalating unnecessarily. Fourth, handle the true crisis with 100% focus until it's handled. Fifth, reset as soon as the crisis is handled: update all my tracking sheets, send status emails so everyone knows where things stand, and make a plan for the next urgent item. The key is to stay calm and be methodical. | —inventory, triage (urgent vs important), communicate, 100% focus, reset

Question 44

Tell me about a time when you proactively identified a potential problem before anyone else noticed it.

Answer 44

On a Sony project, I was reviewing the delivery specifications for a broadcaster—just routine checking—and noticed they required closed captions in both English and French. Our budget and schedule only accounted for English captions. Nobody else had noticed this yet. The editorial team was focused on picture. The post supervisor was dealing with color and sound. It wasn't a problem today, but it would become a crisis in three weeks when we tried to deliver and didn't have French captions. I immediately flagged it: 'The delivery spec requires French captions, but we haven't budgeted or scheduled for those. We need to address this now.' I came with a solution: 'Here are three captioning vendors who handle French. Based on the episode length, it'll take 5-7 days and cost approximately $X. If we start next week, we'll have them ready for delivery. If we wait, we risk delaying delivery.' The post supervisor appreciated the catch. We added French captions to the schedule, got a revised budget approved, and the captions were ready on time. Crisis averted because I was reading delivery specs carefully and thinking ahead. That's the proactive approach I bring: I don't just execute tasks today, I'm always thinking two weeks ahead. What's coming up that we need to prepare for? What could go wrong that we should plan around? Catching problems early when they're still easy to solve is infinitely better than dealing with them as emergencies.

Question 45

What's your approach when you realize a deadline simply can't be met? | —assess as impossible or very hard, communicate, propose solutions—

Answer 45

First, assess if the deadline is actually impossible, or just very hard. Who owns the deadline? If it's an internal soft deadline, missing by a day might be acceptable. If it's a network delivery with contractual penalties, that's very different. Understanding the stakes helps prioritize solutions. If it's truly impossible, communicate this immediately. “Based on where we are now, we cannot meet the Friday delivery date because [specific reasons]. Here are the options: 1) Deliver Monday, which requires a 2-day extension. 2) Deliver partial Friday and complete Monday. 3) Deliver Friday with known issues that will need fixing. What's the best path forward?” The key is to propose solutions, not just problems. And to be specific about why the deadline can't be met, and what the alternatives are. Sometimes deadlines feel impossible, but with creative solutions—working weekends, bringing in additional resources, compressing other stages—they are achievable. After the crisis, do a post-mortem: Why didn't we see this coming? What can we do differently to avoid it next time? | —assess as impossible or very hard, communicate, propose solutions—

Question 46

You've worked on major productions for HBO, Netflix, Sony. How would you adjust to working on a potentially smaller-scale TV series? | —fundamentals are the same, but role requires wearing more hats—

Answer 46

The fundamentals are the same regardless of scale: maintain schedules, coordinate vendors, manage assets, ensure quality, communicate clearly. The difference is how many people are involved and how complex the workflows are. Major productions have extensive infrastructure to boost efficiencies, but with that comes more bureaucracy and less direct involvement. On a smaller-scale TV series, the coordinator role is even more critical because you're wearing more hats and handling more directly. If anything, my experience on complex large-scale productions means I can handle a smaller series very efficiently. | —fundamentals are the same, but role requires wearing more hats—

Question 47

Tell me about your experience with network timing sheets and turnover/deliverable requirements. | —track timing from rough cut onward, create a master delivery checklist

Answer 47

I’ve worked with network timing sheets extensively. Track timing from rough cuts onward and update as editorial makes changes so we can see if we're trending over or under the network requirements. Each network or platform has specific turnover/deliverable specs (file format, resolution, frame rate, audio configuration, closed captions, delivery method), so I create a master turnover checklist based on their spec document and verify every requirement before delivery. Missing a requirement (like delivering 5.1 audio when they required stereo, or forgetting to include textless elements) can cause delivery rejections and expensive re-work. | —track timing from rough cut onward, create a master delivery checklist

Question 48

Walk me through how you would coordinate a color session with a remote colorist. | —prep, tech logistics, take notes, follow up with colorist, QC, notify

Answer 48

First, ensure the colorist has everything prepped before the session: - conformed timeline at full resolution with final VFX integrated - reference stills or looks the director wants to match - any LUTs or color space information - a spotting document noting which scenes have specific color notes Then confirm technical logistics: What video conferencing platform are we using? Who needs to attend the session? What's the frame rate and resolution they'll be working in? What file format will they deliver when finished? During the session I’ll take notes (eg, Scene 12 approved, Scene 13 needs slightly warmer tones, Scene 14 redo the sky). After the session I’ll follow up with the colorist to recap the notes and confirm delivery specs (eg, We'll need the revised files by Friday. Deliver via Aspera to [link]. Let me know if you need any additional reference materials.) QC the files once they have been delivered. Do they match the approved look? Are they the right format and resolution? Then notify the team: “Color files received and verified, moving to sound mix stage. | —prep, tech logistics, take notes, follow up with colorist, QC, notify

Question 49

How do you handle version control when there are multiple cuts circulating (director's cut, producer's cut, network notes, etc.)? | —strict naming, tracking, communication, archiving, explicit approval—

Answer 49

First, strict naming conventions (E103_DirectorsCut_v1_2026-01-15.mov). Second, centralized tracking. Maintain a spreadsheet logging every version: date delivered, who it went to, what stage it represents (director's cut, producer's cut, network review), and its current status (in review, approved, revisions needed). Third, clear communication when distributing cuts. For example, “Attached is Episode 103 Director's Cut v1, delivered 1/15/26. This is for Director's review only. Please provide notes by 1/20. This is NOT the final cut.” Fourth, archiving. Once a version is superseded, move it to an “Archive” or “Previous Versions” folder. The active working folder only contains the current version and the immediately previous version. That prevents someone accidentally working from an old cut. Fifth, final approval is explicit. When a cut is truly approved and locked, it gets moved to a 'FINAL APPROVED' folder and confirmation is sent to everyone: “Episode 103 Producer's Cut v4 has been approved as picture lock. All future work will reference this version. | —strict naming, tracking, communication, archiving, explicit approval—

Question 50

Tell me about a time when you had to coordinate a rush delivery. What steps did you take? | —assess possibility, schedule, clear roadblock, stay available, check in

Answer 50

First, assess what is possible. Talk to each department. Second, create a mini-schedule working backward from the new rush deadline. Block out precisely when each stage needs to complete. Then communicate this timeline to everyone. Third, clear roadblocks. No one should be waiting on information. Fourth, stay available to solve problems. Fifth, check in regularly but not excessively. But don’t micromanage. | —assess possibility, schedule, clear roadblock, stay available, check in

Question 51

Why are you interested in working for Bamboo Shoots specifically? | —aligns with my career path, potential to grow into supervisory role—

Answer 51

First, the role aligns perfectly with where I have been steering my career. Second, knowing that there is potential to grow into supervisory responsibilities as the company takes on more series makes this an exciting long-term opportunity. Third, the opportunity to work with a team that values organization, clean workflows, and ensuring “every deliverable hits its mark”—that language tells me you understand what good post-production coordination looks like. I want to work with people who value what I bring to the table. | —aligns with my career path, potential to grow into supervisory role—

Question 52

This is a TV series. How does coordinating a series differ from coordinating a feature film?

Answer 52

The main difference is scale and rhythm. A feature is one large deliverable with a single delivery date. A series is multiple episodes with cascading deadlines, often with episodes at different stages simultaneously—Episode 1 in final color while Episode 3 is in rough cut while Episode 5 is just starting editorial. That requires more sophisticated tracking systems. You need to see the big picture across all episodes while also managing the details of each individual episode. It's a lot of plates spinning, which is honestly where I thrive. Series also tend to have tighter per-episode budgets and timelines. You can't take your time because the next episode is right behind. That rewards efficiency and good planning—exactly the skills I bring. On the positive side, series develop rhythm. By Episode 3 or 4, you know each vendor's quirks, you've refined your workflows, and everyone's working more efficiently. There's satisfaction in that optimization. Series also build relationships. You're working with the same vendors, same team, same facilities across multiple episodes or even seasons. That continuity lets you build strong working relationships, which makes coordination easier. I've worked on both features and series in my career, and honestly, I prefer series for all these reasons. The variety, the rhythm, the optimization opportunities—it plays to my organizational strengths.

Question 53

The posting mentions "possibilities for growth to full Supervisory position." Where do you see yourself in 2-3 years? | —in a coordinator role that focuses on workflow optimization—

Answer 53

In 2-3 years, I see myself in a coordinator (or project management) role that focuses on workflow optimization. I want to prove my value as a coordinator built on solid skills—mastering the logistics, scheduling, vendor management, organizational systems—and earn my career progression through performance. I'm not in a rush. | —in a coordinator role that focuses on workflow optimization—

Question 54

The posting uses the phrase "organizational engine." What does that mean to you?

Answer 54

To me, 'organizational engine' means being the driving force that keeps everything moving smoothly. An engine doesn't just run when things are easy—it provides power when there's resistance, when you're going uphill, when conditions are challenging. As an organizational engine, I'm the person who: - Builds the systems that keep projects on track - Anticipates problems before they become crises - Keeps communication flowing between departments - Ensures nothing falls through the cracks - Provides the steady, reliable momentum that lets everyone else do their best work It's about being proactive, not reactive. It's about creating order out of chaos. It's about being the person others can count on to have the answer or to find the answer quickly. When I read that phrase in your posting, I immediately thought: that's exactly what I've been doing for 13 years, I just haven't had a title that captured it. First Assistant Editor doesn't convey that organizational role, but that's what I've been—the engine keeping the post-production machine running smoothly.

Question 55

They mention loving "clean workflows." What does a clean workflow look like to you? | —clear documentation, efficient info flow, organization, handoffs, QC—

Answer 55

A clean workflow is one that allows everyone to do their best work efficiently, and one where: Documentation is clear. Everyone knows what's expected of them and when. There's no confusion about deadlines, deliverable formats, or who's responsible for what. Information flows efficiently. People don't have to hunt for files, dig through email threads, or ask the same questions repeatedly because there's no centralized information. Files and assets are organized logically. Handoffs between stages are seamless. Problems get caught early. QC checkpoints throughout the process mean issues are identified when they're easy to fix. | —clear documentation, efficient info flow, organization, handoffs, QC—

Question 56

How do you ensure "every deliverable hits its mark"? | —preparation, verification (QC), follow-through and attention to detail—

Answer 56

Preparation, verification (QC), follow-through and a systematic attention to detail. Prepare by having clarity on all specs up front, and track every deliverable’s deadline, requirements, and status. Build in buffer time wherever possible. Verify every deliverable before it’s handed off. Follow-through with the recipient that the deliverable is received and verified. If something does miss the mark, figure out why it happened and fix the process so it doesn't happen again. | —preparation, verification (QC), follow-through and attention to detail—

Question 57

What's your working style when things are calm versus when things are chaotic? | —calm: build, refine, plan, document; chaos: focus, triage, communicate—

Answer 57

When things are calm, I'm proactive and forward-thinking. I build systems, refine workflows, plan for upcoming stages, and create documentation. I use the calm periods to prepare for the busy periods. When things are chaotic, I get very focused and methodical. I triage ruthlessly, and I communicate more frequently but more concisely. The pace changes, but the fundamentals don’t: track everything, communicate clearly, and stay on top of details. | —calm: build, refine, plan, document; chaos: focus, triage, communicate—

Question 58

How do you celebrate wins or stay motivated during long post-production schedules? | —milestones completed, celebrate the daily successes, in the team itself

Answer 58

Take satisfaction in the milestone completions and celebrate the daily successes as well—when a tracking system works perfectly, when a potential problem gets solved smoothly, when a vendor delivers exactly what we needed on time. I also find motivation in the team itself. When I see the editor's creative work, or the colorist's stunning grade, or hear the sound designer's immersive mix, it is genuinely satisfying to know that my organizational work helped make that possible. I enable creativity by handling the logistics. That's meaningful work. | —milestones completed, celebrate the daily successes, in the team itself

Question 59

I notice you have 12 years of First AE experience (2011-2023) but it's now 2026. What have you been doing for the past couple of years? | —sabbaticals to recalibrate, prof. development, clarify career direction

Answer 59

After wrapping my last project in 2023, my partner and I purchased a home in Regina. Almost immediately, an insurance claim forced us out of the house for close to a year. (It was supposed to be six months; an excellent example of poor project management and coordination.) So we both used the opportunity to take sabbaticals and recalibrate. We moved to Europe, primarily Paris, and travelled extensively until the end of 2024. That’s when I made a deliberate decision to take some time for professional development and to clarify my career direction. I've done the work to understand what I want and what I bring to the table. | —sabbaticals to recalibrate, prof. development, clarify career direction

Question 60

Tell me more about your 2025 Project Management training. What specific skills did you develop? | —4 courses on coordination + workflow, I was already doing intuitively—

Answer 60

I finished 4 of 6 courses focused on project coordination and workflow management. The key skills I’ve developed so far have formalized a lot of what I was already doing intuitively. It's an investment that will pay off throughout my career. Scheduling and Timeline Management: Advanced techniques for building realistic schedules, identifying critical paths, managing dependencies, and adjusting timelines when variables change. I learned formal methodologies like Gantt charts and Kanban boards. Risk Management: How to identify potential problems early, assess their likelihood and impact, and create mitigation plans. Stakeholder Communication: Strategies for managing communication with different types of stakeholders (creative people versus technical people versus executives). Process Optimization: How to analyze workflows, identify bottlenecks, and implement improvements. Team Coordination: Cross-department coordination, managing external vendors, and facilitating collaboration. | —4 courses on coordination + workflow, I was already doing intuitively—

Question 61

Which of your listed credits (HBO, Netflix, etc.) are you most proud of and why?

Answer 61

That's tough because each project taught me something different, but I'd say I'm particularly proud of the Netflix work because of the complexity and scale involved. Netflix has extremely rigorous technical specifications and quality standards. Coordinating delivery for their platform meant absolutely everything had to be perfect—proper codecs, correct metadata, pristine quality control. What made me proud wasn't just that we delivered successfully, but that we built systems and workflows that made it repeatable. By the third episode, we had refined the process to the point where delivering to Netflix specs became routine rather than stressful. That's the kind of organizational achievement I value—taking something complex and making it manageable through good systems. I'm also proud of the Milton's Secret supervisory experience because it was a proving ground. Taking on both supervisor and AE responsibilities simultaneously was intense, but it showed me I could handle that level of responsibility and complexity. It was a preview of where I want my career to go. But honestly, every credit represents a team effort and professional relationships built. Whether it's HBO, Sony, or an independent film, I'm proud of delivering quality work consistently. That reliability—being someone people know they can count on—matters more to me than any specific brand name.

Question 62

Tell me about the Milton's Secret experience where you were both Post Supervisor and First AE. That sounds intense!

Answer 62

It was definitely intense, but also one of the most formative experiences of my career. Milton's Secret was an independent feature, so the budget meant we couldn't have separate people in each role. I needed to handle both the supervisory responsibilities—coordinating vendors, managing the schedule and budget, interfacing with the producers—and the AE responsibilities—dailies, media management, supporting the editor. What I learned was that I actually enjoyed the supervisory aspects more than the AE aspects. Building the delivery schedule, coordinating between the colorist and sound mixer, tracking vendor quotes—that's where I found satisfaction. The technical AE work was necessary, but it wasn't energizing me the way the coordination work was. The challenge was time management. I'd spend mornings doing AE work—syncing, organizing, prepping for the editor—and afternoons doing supervisor work—coordinating vendors, updating schedules, communicating with producers. It required serious discipline to keep both aspects moving forward. The experience taught me I could handle the responsibility of a supervisory role. It also clarified that I wanted to focus on coordination rather than staying in the AE technical track. That's why, even though I returned to AE roles after that project, I kept the coordination mindset and took on those responsibilities wherever possible. If I'm honest, that experience is a big reason I'm here. It showed me what's possible and what I want my career to be.