Staff Engineer
at Qvest Us
Austin, Texas; Anywhere in the USA, remote, staff, full time, 8–12 years
posted 20 Jul 2022
- Java
- SOA
- FP
- Microservices
- TypeScript
- OOP
- Kanban
- JavaScript
- CI/CD
- XP
- Scrum
- Python
About the role
Posted: 2022-07-20
What you would do
- As a mentor, you will help grow the careers of other team members, have the opportunity to participate in the hiring process, participate in the annual review cycle, and shape and contribute to the engineering culture as a place to learn and grow.
- As a technology Leader, you’ll work directly with Qvest leadership to impact projects, teams and the Qvest organization by creating, shaping, proposing and presenting engineering practices, architectures, and tech stacks. You will influence business development through your expertise by creating content and contributing to proposals. You will extract reusable components, patterns, concepts and lessons learned to be leveraged across the organization.
- As a project leader, you’ll help propose technologies to be used on specific projects, and define the shape of the team to build them. As a part of that team, you’ll help the team gather, translate and refine business requirements into deployable systems, extracting and leveraging repeatable design strategies, and creating reference implementations. You will lead by example through the code you contribute, the continuous improvement you foster, and the quality of documentation, architecture, code, and tests you and your teams will deliver.
What they are looking for
- 8-12+ years in software development, including working in teams
- Experience with agile methodologies such as Scrum, Kanban or XP
- Expertise in the language and library/framework ecosystems of Java, JavaScript/Typescript, or Python
- Definition, utilization and implementation of CI/CD pipelines
- Experience with SOA, Microservices, or similar architectural patterns
- Experience constructing systems by utilizing a separation of concerns (good OOP, FP design, etc)
- Experience with enterprise application integration, including defining the integration architecture, integration data flows and interfaces, integration mechanisms (e.g., async vs. synchronous), middleware, etc.
- Experience with typical AuthN/AuthZ methods and products
Read from jobs.lever.co, last seen 5d ago.