• The Systems Engineer designs, implements, and supports secure, scalable identity, endpoint, and SaaS administration platforms across the organization. • This role owns complex technical initiatives end to end, partners cross-functionally to improve reliability and security, and mentors junior engineers through strong standards, automation, and operational excellence.

• Providing technical leadership and establishing product architecture (cloud, mobile, and embedded) for digital and connected products. • Leading ecosystem alignment with smart home consortium and coordinating with internal team members and partners. • Bringing smart home water products from ideation to production. • Working in Architectural Frameworks (DoDAF, Zachman, TOGAF, etc.) to communicate architecture to the team members. • Guiding the product development teams with strategic direction regarding technology selection, sourcing, implementation, and support. • Collaborating with multidisciplinary teams of engineers to design an efficient solution for the entire system; coordinating technical activities across the entire project. • Delivering documentation and technical coordination across various engineering competencies. • Driving product solution requirements management (under both waterfall and agile methodologies), verification management, DFMEA, P-Diagrams, etc. • Working with Product Managers, Product Owners, and leadership on product requirements and goals. • Crafting our products with a forward-looking product lifecycle to be relevant and last years beyond the initial launch. • Delivering product development projects on target, with predictability in the design and verification phases. • Working with existing team members to coordinate capabilities and updates to products in production.

• Leads the process of system integration and commissioning for the OpenBlue Central Utility Plant (CUP) solution for district energy plants across the globe. • Acts as the project leader to plan, execute, and complete Central Utility Plant projects with assigned customers. • Partners with customers to meet the project implementation schedule goals. • Performs or delegates tasks as required to execute and fully complete assigned projects including: hardware design, system programming, installation coordination, system and network commissioning and project closeout. • Trains plant operators and other end users to take full advantage of the OpenBlue CUP software solution and provides technical support during the warranty period. • Operates on the job with the highest of ethics. • Adheres and ensures Johnson Controls staff and subcontractors adhere to all safety standards.

• The Business Systems Analyst is responsible for collaborating with the digital product managers (DPM), business system owners, and users to capture the right business requests and accurately translating them to specifications that aid design, coding and testing of complex software and/or data warehouse applications within the organization. • The BSA performs a liaison function between the DPM, business users, software engineers and QA analysts for implementing software solutions in order to accurately realize business goals. • Works with the business users and DPM/Proxy DPM to accurately capture all stakeholder requests and translate them into system specifications. • Writes user stories based on the epics or larger scope stories created by the DPM/Proxy DPM. • Meets INVEST and DOR criteria for stories. • Works with the Sprint team on breaking stories down into smaller vertical slices. • Identifies and captures Acceptance Criteria for user stories. • Works with the testers to ensure that all software components are tested adequately. • Reviews test cases in Test Rails, collaborates with Developers and Testers on the right number of tests, types of tests applicable for the story, and the story DOD. • Accepts the story on behalf of the DPM/Proxy DPM, confirms it meets the DOD. • Collaborates with QA on documenting bugs found in non-production environments, captures them in Jira, meets DOR for bugs. • Helps PDM/Proxy DPM prioritize non-prod bugs and issues, based on potential Production impact. • Assists Support group with identifying DOR for Production bugs. • Leads the end-to-end/integration testing, assists DPM in planning of the test effort. • Collaborates with the business users/SMEs/stakeholders on the use cases and test cases. • Maintains product and system documentation in Confluence, Miro, and other tools. • Collaborates with BPMs, analyzes, maps, and communicates current state and future state business processes. • Continuously builds relationships with business users (key and designated stakeholders, business users, BPMs), obtains and grows knowledge about the business process. • Serves as an SME on the Product Team. • Leads or assists DPM/Proxy DPM in sprint ceremonies like backlog refinement and sprint review/demo. • Assists DPM/Proxy DPM in in providing Release notes with a specific use case, screen shots, detail on the changes, etc. • Be the SME for the application area your team owns. Have deep understanding of the current workflow, rules, dependencies, potential impacted areas. Always continue learning your application, understand new features being developed, be the gatekeeper of the consistency and cohesiveness across screens, actions, data, etc. • Speak the Business language. Understand and be able to articulate the business process from the user’s standpoint. Remember, they are not limited to our application, their process involves multiple systems, as well as manual components (excel, email, verbal communication). • Build relationship with users and business SMEs, keep learning from them - shadow, ask for their training documents. • Create and maintain documentation, take initiative, refer other team members to your documents. • Write great user stories - small, concise, well defined, with just enough number of details. • Refine and break them down with the team, be the champion of the vertical story split. • Be the gatekeeper of quality on the team. • Create Acceptance criteria, help QA understand the system’s expected behavior. • Review the test cases in Test Rails, help QA find a way to figure out the system’s actual behavior and make sure it marches the AC. • Create plans for end-to-end testing, document use cases, hep QA plan. • Decide what needs to be automated as part of the regression test suite.