What does a typical day look like for a SETA (Systems Engineering and Technical Assistance) contractor? Here’s a glimpse into their schedule, showcasing the variety and demands of the role.
Morning Kick-Off: Grabbing Coffee & Reviewing Priorities
A typical morning for a SETA starts with a quick coffee in the office cafeteria before diving into daily tasks. Many SETAs work on-site at government facilities, co-located with government teams to facilitate seamless communication and foster a sense of camaraderie.
The first order of business: scanning your email inbox and project management tools. Is there a new data call from the Program Manager? A high-priority request could shift your entire day—perhaps a short-fuse technical assessment or a last-minute briefing for an executive. Flexibility is key in this role.
Late Morning: Meetings, Meetings, Meetings!
Meetings are a staple of a SETA’s day. A significant part of the role involves ensuring stakeholders are aligned and informed. A typical late-morning schedule might include:
- Program Status Updates: Meet with the government Program Manager and the contracting officer to review project timelines, budgets, and technical risks. Here, you might highlight risks requiring attention or suggest ways to optimize the current plan.
- Vendor Progress Reviews: Attending a contractor’s presentation on their latest design. As a SETA, you ask critical questions about system interfaces or security requirements, ensuring all aspects are thoroughly considered. Your goal is to mitigate risks while maintaining schedule and budget constraints.
- Technical Deep-Dives: Participating in an engineering working group session with subject-matter experts. This is where in-depth technical discussions happen. Your role is to keep the conversation aligned with the broader system architecture, compliance regulations, and mission objectives.
Lunch Break: Often a Working Lunch
Many SETAs work through lunch, catching up with the GPMO or developers—whether dialing into a quick status call or hashing out technical details. This could happen at your desk or during an informal brainstorming session. Despite the working nature of these breaks, they serve as an opportunity to foster collaboration and maintain momentum.
Afternoon: Document Review & Analysis
Afternoons often involve detailed analysis and documentation review, which are critical to supporting decision-making. Tasks might include:
- Evaluating a Risk Management Framework (RMF) Plan: For SETAs with a cybersecurity background, this could mean verifying whether a proposed system meets necessary security controls.
- Reviewing Documentation for Accuracy: For those working in acquisition programs, this could involve validating vendor documentation, cost estimates, schedules, or technical performance claims.
- Drafting Reports or Deliverables: You may be tasked with writing a "Technical Evaluation Memorandum" or summarizing the outcomes of a recent test event for leadership. This requires meticulous attention to detail and cross-referencing multiple data sources to ensure accuracy and alignment with mission goals. Since SETAs do not own the final product, their focus is on ensuring each component integrates effectively into the larger operational framework. Often, this means juggling multiple tasks simultaneously, adapting as needed to shifting priorities.
You may also like: You Manage Risk All the Time
Late Afternoon: Wrapping Up & Preparing for Tomorrow
As the day winds down, the focus shifts to finalizing deliverables and preparing for the next day’s workload.
- Final Check-In's: A quick desk drop-by or a scheduled call with a government colleague can help resolve any lingering issues before the end of the day.
- Tomorrow's To-do List: Before logging off, many SETAs compile a list of priorities and follow-ups for the morning, ensuring a structured start to the next day.
Working late may be necessary in high-priority environments, such as those supporting critical defense systems. However, many SETA-supported organizations emphasize work-life balance, offering a structured yet dynamic work environment compared to fast-paced development roles.
Conclusion
A SETA’s day is fast-paced, dynamic, and deeply impactful. From morning strategy sessions to afternoon deep-dives into technical and programmatic challenges, the role requires adaptability, critical thinking, and a mission-focused mindset. Whether you're facilitating stakeholder alignment, reviewing key documentation, or problem-solving on the fly, every day presents new opportunities to make a difference.
About This Series:
This blog is part of a series that explores the critical role of a SETA and what it takes to thrive in this profession. New posts drop Tuesdays and Wednesdays every other week—check back for insights into this dynamic field! In the coming weeks, we’ll explore topics such as:
✔ A Day in the Life of a SETA
The Best Parts of Being a SETA and The Challenges
The Big Picture: What Is a SETA?
From Requirements to Realization: Working with the Government Program Management Office
Adapting to New Technologies on the Fly
Cybersecurity in the Intelligence Community
Curious about working at Markon? Explore our Careers page to learn more about our award-winning team that values innovation, collaboration, and professional growth.
