Junior Software Engineer

Llc (green)
Chandler, AZ, United States
9 days ago

Role details

Contract type
Permanent contract
Employment type
Full-time (> 32 hours)
Experience level
Starter
Compensation
$65,000.0 - $75,000.0
Working hours
Regular working hours
Job source

Tech stack

Application Programming Interfaces (APIs) Computing Platforms BASIC (Programming Language) Software Bug Management Command-Line Interface Software Quality Code Review Computer Programming Databases Data Structures Relational Databases Software Debugging
+16 more
PostgreSQL Project Management Software OAuth Pair Programming Software Engineering SQLite SQL Databases Postman Tailwind Backend Git Information Technology Production Code Front End Software Development Api Management Programming Languages

Job description

The Junior Software Engineer supports GTI’s internal construction-management platform by helping build and maintain software that connects field and office workflows, including tools such as Procore and related construction systems.

This entry-level role works closely with senior engineering staff to write production code, learn the full stack over time, and ship small, well-tested improvements to real users on active jobsites.

The position supports GTI’s ability to improve internal operations through reliable software, careful coding practices, and strong curiosity about how the business actually works.

2) Scope & Decision Rights

Owns: Assigned development tasks, small feature increments, bug fixes, clear commit messages, basic testing/verification, and timely status updates for assigned work.

Supports: Internal platform development; database-to-browser workflows; Procore and other construction-tool integrations; debugging; documentation updates; and gradual development across the full stack.

Coordinates with: Senior engineering staff, Enablement & IT partners, internal platform users, and other stakeholders as assigned.

Recommends/Prepares: Implementation options, technical questions, test notes, documentation updates, and small improvements to code, workflow, or user experience.

Escalates: Production-impacting issues, unclear requirements, security or data concerns, blockers, recurring defects, and work that requires senior engineering review.

3) Essential Duties and Standards

Build and maintain platform features: Support feature development across GTI’s internal construction-management platform, including work that spans database, backend, frontend, and browser-facing functionality.

Pair, review, and ship in small increments: Work closely with a senior engineer to design, review, test, and release changes in a pair-programming or close-mentorship style.

Write clean and readable code: Use clear naming, simple structure, careful edits, basic tests or verification steps, and clear commit messages; take feedback well and give it thoughtfully.

Support API integrations: Help connect third-party construction tools, including Procore and related systems, using documented APIs and supported integration patterns.

Debug real user issues: Reproduce, investigate, and help resolve issues reported by internal users; document findings and verify fixes before release.

Learn GTI’s stack: Develop working familiarity with Rust, WebAssembly, HTMX, Alpine.js, Tailwind CSS, SQLite/PostgreSQL, and related tools with mentorship along the way.

Communicate clearly: Ask good questions, share status early, flag blockers, and explain technical work in a way that supports business users and engineering teammates., Delivery: Completion of assigned features, bug fixes, and technical tasks in small, reviewed increments.

Code quality: Readable code, clear commit messages, practical verification, thoughtful review participation, and responsiveness to feedback.

Learning progression: Demonstrated growth across the stack, including Rust, WebAssembly, HTMX, SQL, API integrations, and platform architecture basics.

User support: Timely investigation of internal user issues, clear documentation of findings, and effective validation of fixes.

Collaboration: Reliable pairing habits, clear communication with senior engineering staff and stakeholders, and early escalation of blockers or unclear requirements.

Requirements

Software engineering fundamentals: Computer Programming; Software Development; Full Stack Development; Front End Software Engineering; Back End Software Engineering; Data Structures; SQL; Relational Databases.

Development workflow and tools: Git; Command-Line Interface; Application Programming Interface (API); API Integration; debugging; code review discipline; small-increment development.

GTI technology stack: Rust; WebAssembly; HTMX; Alpine.js; Tailwind CSS; SQLite; PostgreSQL; Procore, other construction-industry tools as assigned.

Professional: Communication; Willingness to Learn; Curiosity; Detail Oriented; Problem Solving; Collaboration; Reliability.

5) Qualifications

Qualifications: Degree in Computer Science or a related field, completion of a reputable coding bootcamp, or equivalent self-taught experience with a portfolio or project work to show.

Required: Solid programming fundamentals, comfort with at least one programming language, familiarity with SQL and relational databases, basic Git and command-line comfort, clear written and verbal communication, and ability to work a hybrid schedule out of the Phoenix-area office.

Preferred: Exposure to Rust, WebAssembly/Wasm, HTMX, Alpine.js, Tailwind CSS, REST/OAuth, API testing tools such as Postman or Bruno, construction-industry software, or a school, bootcamp, personal, or open-source project the candidate can walk through clearly.

Benefits & conditions

Pulled from the full job description Health insurance 401(k) matching Vision insurance Dental insurance, * 401(k) with company match

  • 100% employer-paid medical insurance (employee-only coverage)
  • Dental and Vision insurance
  • Sick Time

Apply for this position

This job is hosted externally. Click below to view the full posting and apply.

Apply on www.indeed.com

Good distractions

Talks and stories from around this role — technically off-topic, practically not.

6:21 min

Investigating push inefficiencies with upstream Git experts

Jonathan Creamer · Coffee With Developers

2:49 min

Adopting OAuth best practices and removing outdated grants

Alexander Schwartz Alexander Schwartz · World Congress 2026 Europe

6:36 min

Generating portable SQLite databases for peer-to-peer sharing

Glenn Wolfe · LIVE

43 sec

Software engineering journey and local Manchester roots

Jonathan Tang · Coffee With Developers

56 sec

Favorite git commands and the importance of patch commits

Eileen Uchitelle Eileen Uchitelle +1 · Coffee With Developers

2:12 min

Transitioning from adjacent functions into software engineering roles

Philipp Frauenthaler +1 · LIVE

Videos

See all

Related articles

See all