Skip to main content

Wyetech

Software Engineer 4

Annapolis Junction, Marylandsoftware engineering (full-time)midAdded today

About this role

Wyetech seeks a Software Engineer 4 to design and develop complex software systems for federal government clients. You'll work independently or in a lead technical role, analyzing requirements, architecting solutions, and resolving challenging technical problems while maintaining security-focused practices.

What you'll do

  • Design, develop, and maintain software systems for federal customers
  • Analyze stakeholder requirements and collaborate with systems engineers to define solutions
  • Develop software architecture, installation procedures, and build scripts
  • Identify and resolve system performance issues and complex technical challenges
  • Lead or mentor team members on software development activities
  • Document software systems and establish development processes

What they're looking for

  • Software design and architecture
  • Full-stack software development
  • Requirements analysis and stakeholder communication
  • System performance optimization
  • Build automation and deployment scripting
  • Technical leadership and mentoring
  • Complex problem-solving
  • Federal contracting environment experience
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Wyetech

Wyetech builds cloud infrastructure, cybersecurity solutions, and advanced software systems for federal government clients, leveraging AWS, Kubernetes, machine learning, and cyber range technologies. The company is hiring Cloud Platform Engineers, DevOps Engineers, Software Engineers, and Test Engineers to develop and maintain these mission-critical systems.

View all jobs at Wyetech

Likely interview questions

  • Describe your experience designing software architecture for complex systems. What approach did you take to gather and prioritize stakeholder requirements?
  • Tell us about a time you resolved a critical system performance issue. What was your methodology?