1

After Query Jobs in Chicago, IL (NOW HIRING)

This position will remain open for application based on business need, which may be before or after ... Advanced SQL capabilities, including performance tuning and query optimization. * Experience with ...

Benefit Analyst

Bolingbrook, IL · Hybrid

$66K - $80K/yr

After all, success breeds opportunity, and the opportunities to help drive an organization at the ... Query. * Knowledge of leave laws and regulations and HR/benefits laws, including ERISA, COBRA ...

Medical, Dental & Vision after 30 days * Earn PTO starting Day 1. Up to 80 hours accrued in 1st ... query. Important Note: Some positions require additional screening that may include employment and ...

... query functions using Radnet and Penrad systems. 8)Reviews previous mammographic reports and ... after each use. Ensure a secure and safe patient and work environment by maintaining continued ...

Benefit Analyst

Bolingbrook, IL · On-site

$66K - $80K/yr

After all, success breeds opportunity, and the opportunities to help drive an organization at the ... Query. * Knowledge of leave laws and regulations and HR/benefits laws, including ERISA, COBRA ...

Benefit Analyst

Bolingbrook, IL · Hybrid

$66K - $80K/yr

After all, success breeds opportunity, and the opportunities to help drive an organization at the ... Query. * Knowledge of leave laws and regulations and HR/benefits laws, including ERISA, COBRA ...

Showing results 41-60

After Query information

See Chicago, IL salary details

$5

$43

$66

How much do after query jobs pay per hour?

As of Aug 11, 2026, the average hourly pay for after query in Chicago, IL is $43.99, according to ZipRecruiter salary data. Most workers in this role earn between $30.72 and $52.50 per hour, depending on experience, location, and employer.

What is the difference between After Query vs Data Analyst?

AspectAfter QueryData Analyst
Required CredentialsTypically requires a basic understanding of database querying, often with certifications like SQL certificationRequires strong analytical skills, proficiency in SQL, Excel, and data visualization tools, often with a degree in data science, statistics, or related fields
Work EnvironmentPrimarily works in database environments, often within IT or database teamsWorks across departments, analyzing data to support business decisions in various industries
Employer & Industry UsageUsed mainly in IT, database management, and software companiesCommon in finance, marketing, healthcare, and consulting firms

While both roles involve working with data, After Query focuses on executing database queries to retrieve information, whereas Data Analysts interpret and analyze data to provide insights for decision-making.

What are the key skills and qualifications needed to thrive as an after query, and why are they important?

I'm sorry, but 'After Query' does not appear to be a recognized professional job title. Please provide a valid job title.

What are some common challenges faced by professionals in after query roles, and how can they be addressed?

In After Query roles, professionals often encounter challenges such as managing high volumes of post-query follow-ups, ensuring timely and accurate responses, and maintaining clear communication between departments. Balancing multiple requests while adhering to company policies requires strong organizational skills and attention to detail. Building effective workflows and leveraging customer relationship management (CRM) tools can help streamline processes and enhance collaboration with team members, ultimately improving the customer experience.

What is an after query?

After Query jobs typically refer to roles that involve analyzing, interpreting, and acting upon data results obtained after running database queries. These positions are common in data analytics, business intelligence, and IT, where professionals review query outputs to generate reports, provide insights, or inform business decisions. The job may include tasks such as validating data, ensuring query accuracy, and collaborating with stakeholders to communicate findings. Strong analytical skills and proficiency with SQL or other query languages are often required. These roles are vital for organizations that rely on data-driven decision-making.
What are popular job titles related to After Query jobs in Chicago, IL? For After Query jobs in Chicago, IL, the most frequently searched job titles are:
What cities near Chicago, IL are hiring for After Query jobs? Cities near Chicago, IL with the most After Query job openings:
Infographic showing various After Query job openings in Chicago, IL as of August 2026, with employment types broken down into 86% Full Time, 5% Part Time, and 9% Contract. Highlights an 81% Physical, 6% Hybrid, and 13% Remote job distribution, with an average salary of $91,505 per year, or $44 per hour.

Lead Backend Engineer/Technical Lead-Java Trading Systems

Ironbeam

Chicago, IL • On-site

Other

Posted 25 days ago


Job description

Candidates who are primarily looking for task-based development work may not be the right fit; this role requires technical ownership before, during, and after implementation.

We are seeking a hands-on Lead Backend Engineer / Technical Lead to help design, evolve, and extend the backend and middleware systems that support our trading and market data infrastructure.

This is not a ticket-only development role. We are looking for someone who can take business needs, operational problems, and high-level requirements and turn them into clear technical designs, implementation plans, acceptance criteria, and production-ready code.

You will work on real trading systems involving market data ingestion, exchange connectivity, clearing and regulatory workflows, pre-trade and post-trade processing, and internal services that must be correct, fast, observable, and resilient.

The right person is a strong Java engineer who can also think at the system level: understand tradeoffs, design service boundaries, challenge incomplete requirements, define edge cases, guide other developers, and own technical outcomes from concept through production.

What You’ll Own

  • Translate business and operational requirements into technical designs, implementation plans, and acceptance criteria
  • Design backend services and middleware components for trading, market data, clearing, regulatory, and post-trade workflows
  • Lead technical design discussions and make practical architecture decisions across services, databases, APIs, and integrations
  • Write high-quality code for low-latency, high-reliability systems
  • Define service contracts, data flows, error handling, observability, retry behavior, and failure modes
  • Design and optimize SQL schemas, queries, stored procedures, and data integrity rules
  • Integrate with exchanges, clearinghouses, regulatory systems, internal platforms, and third-party services
  • Review code and designs from other engineers with a focus on correctness, maintainability, performance, and operational risk
  • Identify architectural gaps, technical debt, production risks, and opportunities to simplify or harden the system
  • Partner with business stakeholders, product owners, operations, QA, and other developers to clarify requirements before implementation begins
  • Support production systems when needed and use incidents as feedback for better architecture and design
  • Help establish engineering standards, design patterns, documentation practices, and development best practices

What We’re Looking For

  • 8+ years of professional software engineering experience, with significant backend Java experience
  • Strong Java expertise, including concurrency, collections, memory behavior, performance tuning, and production debugging
  • Proven experience designing systems, not just implementing assigned tickets
  • Experience writing or contributing to technical design documents, architecture proposals, implementation plans, or RFCs
  • Ability to define acceptance criteria, edge cases, failure scenarios, and testable technical requirements
  • Experience with trading systems, market data platforms, financial infrastructure, or other high-throughput/low-latency systems
  • Strong understanding of distributed systems, messaging, service-oriented architecture, APIs, and data consistency
  • Strong SQL experience, including schema design, query tuning, indexing, data modeling, and transactional integrity
  • Ability to communicate clearly with both technical and non-technical stakeholders
  • Strong judgment around when to build, refactor, simplify, harden, or defer
  • Comfort working in regulated or compliance-driven environments

Preferred Experience

  • Exchange connectivity, FIX protocol, proprietary exchange APIs, or market data feeds
  • Clearing, settlement, allocation, give-up, regulatory, or post-trade workflows
  • Pre-trade risk, order routing, execution workflows, or brokerage/trading operations
  • Linux-based server environments
  • Message queues, streaming systems, event-driven architecture, or real-time processing
  • Observability tools, logging standards, metrics, alerting, and production diagnostics
  • Cloud or hybrid infrastructure experience
  • Experience mentoring developers or serving as a technical lead on complex backend systems

What Success Looks Like

Within the first 30 days, you will understand the core architecture, major data flows, production risks, and current development process.

Within 60 days, you will be contributing production code, reviewing designs, improving acceptance criteria, and helping shape implementation plans before development starts.

Within 90 days, you will be leading design for meaningful backend changes, identifying architectural risks, and helping the team move from ticket execution to better technical ownership.

This Role Is a Fit If You

  • Ask “what problem are we solving?” before jumping into code
  • Can turn ambiguity into a clear technical plan
  • Care about correctness, latency, resilience, and maintainability
  • Know how to make practical architecture decisions without over-engineering
  • Are comfortable challenging unclear requirements respectfully
  • Can still write serious production code while operating at a higher design level
  • Want ownership of systems, not just a queue of tickets