At a Glance
- Tasks: Lead architectural discussions and design innovative solutions for complex projects.
- Company: Join a forward-thinking organisation focused on technology transformation.
- Benefits: Attractive salary, flexible working options, and opportunities for professional growth.
- Other info: Dynamic role with excellent career advancement potential.
- Why this job: Shape the future of technology while making a real impact in the community.
- Qualifications: Experience in architecture design and strong collaboration skills required.
The predicted salary is between 36000 - 60000 £ per year.
There is a mandatory requirement for the Technical Solutions Architect to be involved in and consulted on all non-functional, architectural and design-led discussion and decision-making. The Architect is responsible for:
- Ensuring that enterprise architecture models are developed in a consistent and coherent manner within the Projects and EPF Programme and ensure that effective and efficient reuse/reapplication of materials is done to assist wider coherence with the programme architecture wherever practical.
- Leading the architecture development assignments across Projects and the Programme, including identifying and promoting technical innovation to solve challenges faced by the business by working closely with the client (business and technical staff) and alongside staff from other suppliers.
- Working with the Head of Technology Transformation and Business Solutions Analyst to understand business requirements and technical project inter-dependencies in order to work with the Project Manager to resolve them and translate the business requirements into options papers, implementation assessments and solution designs adhering to the Enterprise Architecture, feeding into the EPF Programme.
- Advising on and participating in the governance arrangements set up to ensure that the architecture delivers the desired benefits to an organisation including defining and managing the process for the selection of new technologies ensuring removal of redundant technologies.
- Serving as a subject matter expert for technical delivery on projects within the scope of the EPF Programme and architectural frameworks, methods and tools. This involves acting as a central hub on all technical designs for other technology teams.
EARLY ENGAGEMENT PHASE
- Engagement – must take place at the earliest opportunity within the project delivery.
- Contribution to Business Case preparation.
- Non-Functional Requirements document – consistent with Digital Division standard NFRs – standalone and also as input to ITT.
- Options Paper.
TENDER PHASE
- Engagement – Architect responsible for NFRs requires to engage via Procurement in tender responses and information requests via procurement in respect of suppliers.
- Scoring of the ITT responses.
- Feedback responses collated by procurement.
- Individual scoring spreadsheets with detailed constructive analysis/criticism of responses providing reasoning behind scores which can be used to feed back to tenderer.
DESIGN & IMPLEMENTATION PHASE
- Engagement – Collaboration between supplier, project team & stakeholders.
- Production/Review of the following artefacts:
- Designs – High Level and Low Level Design Documents showing how and where within the Police Scotland environment the service will be hosted or how we connect to the solution (if cloud hosted, etc.).
- Options Paper – pros, cons, costs, effort, etc. (e.g. if there are multiple options where systems should be hosted).
- Other common diagrams produced/reviewed by the Technical Solutions Architect during the Design & Implementation stage include:
- High Level Context Diagram
- Integrations Diagram
- Deployment / Physical Design Diagram
- Traffic / Data Flow Diagrams
- Server Build request forms
- Task raised to support build requirements from the design
- Briefing Papers where technical considerations/changes need to be conveyed, raised and agreed with senior management and business stakeholders.
- Failover/ continuity documentation (Project Deliverable) – Aspects of this will be present in design documentation but greater detail will be required. This is a project deliverable with a contribution from Technical Solutions Architect.
- Project Plan (Project Deliverable) - input into the steps required to build and deliver the documented design, any cutover/BRC/go-live activities, plus any decommissioning.
- High level presentations/overview of the solution, based on the requirements of the audience, such as the business or technical teams.
Format deconstructs technical details to promote higher level understanding suitable for non-technical staff.
Technical Solutions Architects contribute to the following Project Deliverables:
Technical Solutions Architect employer: Alphayotta
Join our dynamic team in Edinburgh as a Bid Writer, where we foster a collaborative work culture that values innovation and professional growth. We offer competitive benefits, including opportunities for continuous learning and development, ensuring you thrive in your career while contributing to impactful public sector projects. Experience the unique advantage of working in a vibrant city known for its rich history and supportive community.
StudySmarter Expert Advice🤫
We think this is how you could land Technical Solutions Architect
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Alphayotta or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Alphayotta.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Alphayotta.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Alphayotta that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Technical Solutions Architect
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Alphayotta.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Alphayotta and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Alphayotta
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Alphayotta uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.