1

Afternoon Software Engineer Jobs (NOW HIRING)

... Software Engineer to join the team behind Investigations, the part of the SpyCloud Console that ... A plan, its implementation, and its tests can all be drafted in an afternoon, so the review gates ...

Senior Software Engineer - HYBRID

Bonita Springs, FL · On-site

$115K - $152K/yr

Our ethos is simple: have an idea in the morning, ship it by the afternoon, and have data by the ... About ReachMobi An industry-leading mobile app developer, ReachMobi works tirelessly to connect ...

Senior Software Engineer - HYBRID

Bonita Springs, FL · On-site

$115K - $152K/yr

Our ethos is simple: have an idea in the morning, ship it by the afternoon, and have data by the ... About ReachMobi An industry-leading mobile app developer, ReachMobi works tirelessly to connect ...

Senior Software Engineer - HYBRID

Bonita Springs, FL · On-site +1

$115K - $152K/yr

Our ethos is simple: have an idea in the morning, ship it by the afternoon, and have data by the ... About ReachMobi An industry-leading mobile app developer, ReachMobi works tirelessly to connect ...

You Have * 1+ years of software engineering experience, with a track record of shipping LLM- or ... afternoon. Benefits * Start-up equity * Competitive Salary * 100% Paid health, dental & vision ...

In the afternoon, you might analyze compliance datasets to identify improvement opportunities ... Engineering, Mathematics, or a related field PREFERRED QUALIFICATIONS - 3+ years of full software ...

Showing results 41-60

Afternoon Software Engineer information

See salary details

$63.5K

$147.5K

$205.5K

How much do afternoon software engineer jobs pay per year?

As of Sep 11, 2026, the average yearly pay for afternoon software engineer in the United States is $147,524.00, according to ZipRecruiter salary data. Most workers in this role earn between $120,000.00 and $173,000.00 per year, depending on experience, location, and employer.

What is an afternoon software engineer?

Afternoon Software Engineers are professionals who typically work afternoon or evening shifts to develop, test, and maintain software applications. Their schedule may accommodate project demands, provide support across different time zones, or ensure round-the-clock development coverage. Like other software engineers, they write code, troubleshoot issues, and collaborate with team members, but their working hours are primarily in the afternoon. This role is especially common in companies that offer flexible schedules or operate on a 24/7 basis.

What are the key skills and qualifications needed to thrive as an afternoon software engineer?

To thrive as an Afternoon Software Engineer, you need strong programming skills in languages like Java, Python, or JavaScript, along with a relevant degree or equivalent experience. Familiarity with version control systems (e.g., Git), development frameworks, and cloud platforms is often required. Effective problem-solving, communication, and time management skills are crucial, especially when collaborating remotely or across different shifts. These abilities ensure you can contribute high-quality code, maintain team productivity, and support continuous development cycles.

What are some unique challenges and benefits of working as an afternoon software engineer compared to traditional daytime shifts?

As an Afternoon Software Engineer, you may encounter fewer real-time interactions with team members who work standard daytime hours, which can make synchronous communication and quick feedback more challenging. However, this shift often provides a quieter environment with fewer interruptions, allowing for longer periods of focused development work. Additionally, afternoon shifts can offer a better work-life balance for those who prefer later start times, and may present opportunities to collaborate with global teams in different time zones. It's important to proactively communicate and utilize collaboration tools to stay connected with your team and ensure project alignment.

What is the difference between Afternoon Software Engineer vs Morning Software Engineer?

AspectAfternoon Software EngineerMorning Software Engineer
Work HoursTypically works in the afternoon shift, e.g., 12 PM - 8 PMTypically works in the morning shift, e.g., 8 AM - 4 PM
CredentialsSame as other software engineers: Bachelor's in CS or related field, coding skillsSame as other software engineers: Bachelor's in CS or related field, coding skills
Work EnvironmentSame office or remote environment, different shift timingSame office or remote environment, different shift timing
Industry UsageCommon in companies with 24/7 operations or shift-based teamsCommon in standard day-shift tech teams

The main difference between an Afternoon Software Engineer and a Morning Software Engineer lies in their work hours. Both roles require similar skills and credentials but differ in shift timing, catering to companies with flexible or round-the-clock operations.

Do afternoon software engineers work 40 hours a week?

Afternoon software engineers typically work around 40 hours per week, similar to standard full-time schedules. However, work hours can vary depending on the company, project deadlines, and whether overtime or flexible hours are required.

Is 25 too late to become an afternoon software engineer?

Age is generally not a barrier to becoming an afternoon software engineer, as the role focuses on skills, experience, and adaptability. Many software engineers start or transition into the field at various ages, and employers value technical proficiency, problem-solving ability, and relevant certifications or education regardless of age.
More about Afternoon Software Engineer jobs

What cities are hiring for Afternoon Software Engineer jobs?

Cities with the most Afternoon Software Engineer job openings:

What are the most commonly searched types of Software Engineer jobs?

The most popular types of Software Engineer jobs are:

What states have the most Afternoon Software Engineer jobs?

States with the most job openings for Afternoon Software Engineer jobs include:

What are popular job titles related to Afternoon Software Engineer jobs?

For Afternoon Software Engineer jobs, the most frequently searched job titles are:

Infographic showing various Afternoon Software Engineer job openings in the United States as of September 2026, with employment types broken down into 67% Full Time, and 33% Part Time. Highlights an 100% In-person job distribution, with an average salary of $147,524 per year, or $70.9 per hour.

Senior Software Engineer, Investigations

Austin, TX

SpyCloud
Network Security • 11 - 50 employees

$131K - $170K/yr

Full-time

Posted 13 days ago


Job description

We're looking for a Senior Software Engineer to join the team behind Investigations, the part of the SpyCloud Console that analysts use to run down a lead. They start with a single identifier, usually an email address or a username, and we resolve it into the other personas behind it and the breach and malware records those personas appear in. The corpus is billions of recaptured records, and analysts expect an answer in seconds.

You'll work across the whole module: a Go API, a React front end built around an entity-relationship graph, and a Python agent that does the pivoting when an analyst asks a question in plain language. You'll work directly with a product lead and a designer, and the agentic side of the product is new enough that you'll help decide what it becomes.

Our Stack:

  • Front End: React, Vite, TypeScript
  • Back end: Golang, REST APIs
  • AI: Python, AWS Bedrock, LangGraph
  • Frameworks: Vite, MaterialUI, Gin
  • Data: PostgreSQL, Databricks
  • Infrastructure: AWS, Docker, Terraform

What You'll Do:

  1. Feature Development:
    • Take work from ambiguous business intent through to a shipped, operated service, directing AI agents through planning, implementation, and test generation, and staying accountable for the result.
    • Own production outcomes for Investigations: reliability, performance, and cost.
    • Troubleshoot customer-reported issues, including the ones that turn out to be a query plan change.
  2. Technical Leadership:
    • Make and defend design decisions on a module you will know better than anyone outside the team.
    • Set technical direction for Investigations, including the specs, context, and guardrails that decide whether agent-generated work is any good.
    • Own verification when generation is cheap. A plan, its implementation, and its tests can all be drafted in an afternoon, so the review gates that keep customer data trustworthy are a design problem, and yours to solve.
    • Raise the bar on testing, observability, and the interfaces between our module and the Console platform it deploys into.
  3. Team Collaboration and Improvement:
    • Adopt existing team practices and recommend improvements as needed.
    • Mentor engineers on the team, including how to work with agents effectively, and help build a culture of continuous learning.
    • Improve how the team builds, including the AI tooling and evaluation harnesses we use to move faster without shipping regressions.

Requirements:

  1. Professional Experience:
    • At least 5 years delivering production software, including work other teams depended on, and the judgment to know a design is wrong before it's expensive.
  2. Technical Proficiency: 
    • Depth in Go or TypeScript, and quick to pick up the other.
    • Designs, versions, and evolves RESTful APIs other teams depend on.
    • Fluent with PostgreSQL and with large analytical datasets
    • Strong fundamentals in data structures, algorithms, and system design.
  3. Cloud Experience:
    • Production experience with AWS Lambda, API Gateway, ECS, and EC2.
  4. Communication:
    • Sharp writing. Specs and design docs are the primary artifact, for humans and agents both.
  5.  Engineering Practices:
    • Full lifecycle fluency: code review, source control, build and deploy. We use GitHub, GitHub Actions, and AWS CodeBuild.
    • Owns testing, CI/CD, observability, and on-call for what you ship.
  6. How You Work:
    • Ships production code with agentic tools, and can say where they failed and what changed.
    • Decomposes ambiguous problems into work an agent can execute. The spec sets the ceiling.
    • Reads unfamiliar code fast and catches the plausible-but-wrong. Treats AI output as a draft, not an answer.
    • Digs into unfamiliar parts of a system rather than routing around them.
    • Learns deliberately, and can point to something picked up recently.

Nice to Have

  • Built an internal tool or agent workflow that other engineers adopted.
  • Built evals, golden datasets, or regression checks for LLM output, whether a product feature or code generation.
  • Adopted an AI-native delivery method such as spec-driven development or AWS's AI-DLC, including the agent rules that make it repeatable.
  • Large-scale data processing with Spark or Databricks.
  • Python for agent work, such as LangGraph or Bedrock.
  • Background in cybersecurity or identity threat protection.

Base Salary Range: $131,000 - $170,000

The salary range reflects the expected base compensation for a fully qualified candidate at this level based on experience, qualifications, and market data at the time of posting.